Archived Comments (locked)
|
|
The following is an archive of comments made before threaded discussions was implemented (November 16th, 2008) |
|
|
I did it! I've posted an updated version of this script available here. The script is currently unlisted for some reason, but I have contacted the admins to hopefully change that. |
|
|
This script was awesome. Any chance there will be an update for the new AMO layout? I'll attempt to update it myself...could be a fun first script on US! |
|
|
Once again, AMO has been revised and has pulled the rug out from under this script. |
|
|
I have been looking for a script like this for a long time now, thank you! |
|
|
Many thanks. It works great. |
|
|
sharmard: Its now updated to work with the new AMO |
|
|
It looks like the new AMO look and feel has broken this script. Any plans to upgrade it? |
|
|
And while I am it (off topic), does anybody know why my punctuation marks propagate to the published comments as their encoded decimal equivalents? I seem to have this trouble on some sites, no trouble on others. |
|
|
Thanks for the reply, JohnM. Yes, I’m trying to restore something I removed using a red x. When I look at the entry in about:config, I don’t see a value. I know it should be there, but the string value is empty. It’s possible there’s a conflict with another script or extension that’s getting in the way. I do notice that if I change the options for the TargetAlert extension, ACR variously does or does not recognize previously-marked extensions. I’m assuming that it stores the specifics of the hyperlink for each, and TargetAlert probably modifies that. Anyway, back to the main point — any ideas on why I can’t see the string value in about:config or another alternative for editing the list? |
|
|
If its something you removed using the red x, you can modify the preference this script saves. I'm sorry I didn't make an easier way to do it. They are in a preference with the name greasemonkey.scriptvals.http://addons.mozilla.org/userscript/Addons Crap Remover.bad_titles
|
|
|
This is a great script which solved a particular pet peeve of mine — I couldn’t easily tell which extensions were new posts because of the clutter. I’m wondering, though, if there’s a way to remove an addon from the list? I tagged an addon I later decided I wanted to see. I know I can get the full list back if I want, but what I’d like to do is remove a specific addon from the list. What’s the easiest way to do this (I am admittedly not a GS expert)? |
|
|
I hate those conduits@amo. But really, I never thought of using GM script to get rid of them. Good work, John. |
|
|
It should be persistent. It saves the extensions removed with the red x in a preference and reads from those and adds it to the bad_titles array when it is loaded.
It works for me, but if it doesn't for you, you can always add it manually. |
|
|
Good update - esp the change to the bad_titles array. Is the red x removal function supposed to be persistent [as it is not for me] ? |
|
|
Updated:
|
|
|
Well I have added almost anything that has the word 'toolbar' in it and those extensions that seem to update twice a day just to stay at the top of the list. You've done the hard work - probably best left to the user to decide what to filter. |
|
|
If you tell me things I missed I can update the script to include those extensions. |
|
|
Absolutely fantastic I've added loads more to the script - makes amo almost usable again |
