Firefox users should add the following line to their userContent.css file:
A[HREF*="roughlydrafted"]:after { content: " [IDIOT WARNING]"!important ; color: red }
It highlights Roughly Drafted links with a suitable warning. Websites like Slashdot and, here, Engadget, have an annoying habit of posting links without actually indicating the source. It's worse than being rickrolled, at least when you're rickrolled you know the poster of the link wasn't as dumb as you feel.
You'll find your userContent.css file in the "chrome" subdirectory of your Mozilla/Firefox profile. The precise location depends on your OS, under GNU/Linux (Ubuntu, etc), you can open a shell, and type "gnome-open ~/.mozilla/firefox/*/chrome" to bring up the folder. If the file is not there, just copy userChome-example.css to userChrome.css, and open the file in Text Editor by right-clicking and selecting "Open file with "Text Editor"".
Reader Comments (Page 1 of 1)
squiggleslash @ Aug 29th 2008 10:07AM
Damned straight.
Firefox users should add the following line to their userContent.css file:
A[HREF*="roughlydrafted"]:after { content: " [IDIOT WARNING]"!important ; color: red }
It highlights Roughly Drafted links with a suitable warning. Websites like Slashdot and, here, Engadget, have an annoying habit of posting links without actually indicating the source. It's worse than being rickrolled, at least when you're rickrolled you know the poster of the link wasn't as dumb as you feel.
You'll find your userContent.css file in the "chrome" subdirectory of your Mozilla/Firefox profile. The precise location depends on your OS, under GNU/Linux (Ubuntu, etc), you can open a shell, and type "gnome-open ~/.mozilla/firefox/*/chrome" to bring up the folder. If the file is not there, just copy userChome-example.css to userChrome.css, and open the file in Text Editor by right-clicking and selecting "Open file with "Text Editor"".