Tag Archives: plugins

My current WordPress plugins

Because I have a friend who is kick­ing off a new WordPress-powered blog (Hi, Substitute!), I thought I’d list the plu­g­ins I use here at Netninja.com.  I have a whop­ping 32 of them, but many are sim­ple single-purpose things that are likely not of gen­eral inter­est.  My plu­g­ins can be be bro­ken down into a few cat­e­gories:

Administrative

  • After The Deadline — A spelling and gram­mar checker when writ­ing posts.
  • Akismet — Spam blocker
  • Categories to Tags Converter — I some­times get enough posts with a given tag, that I decide to pro­mote that tag to a cat­e­gory.  This plu­gin lets me do that.
  • Dashboard Links — This is just a sta­tic block of arbi­trary HTML you can put on your admin­is­tra­tive dash­board.  I use it to hold links to met­rics (Google Analytics, FeedBurner, etc.)
  • FeedBurner FeedSmith — Route your RSS through FeedBurner
  • Google Analytics for WordPress — Automatically inserts the magic JavaSript for Google Analytics with­out mess­ing directly with your theme files.
  • Google XML Sitemaps — Generates XML sitemaps for bet­ter Google index­ing
  • Maintenance Mode — Out to lunch, back in 5.
  • OpenID — I use netninja.com as an OpenID server.  This pro­vides that func­tion­al­ity.  It also pro­vides OpenID client func­tion­al­ity, like if some­one wants to leave a com­ment under their Blogger/LiveJournal/Yahoo/whatever account.
  • RSS Footer — A bit of boil­er­plate at the bot­tom of each RSS item, used to help pre­vent spam­mers from har­vest­ing my RSS for link farms.
  • WP Super Cache — A WordPress site with­out this will not hold up after being linked to by Digg, Slashdot, Reddit, etc.
Social/RSS
  • Get Comments Count — Comment count as an updat­ing image, so that RSS always has the cor­rect num­ber of com­ments.
  • Sociable — Buttons for folks to like it on Facebook, dig it on Digg, etc.
  • Subscribe to Comments — Allows peo­ple to sub­scribe to com­ments on a given post via email.  This is a lot eas­ier than try­ing to dig up the comment-specific RSS feed.
  • Twitter Tools — Tweet your posts, pull your recent tweets into the blog.
  • Twitter Tools Shortcode — Automatically short­ens the links when you tweet your posts.
  • Twitter Tools nja.me short­ener — I wrote this to over­ride Twitter Tools’ default short­code and instead us my own nja.me ser­vice.
  • Wordbooker — cross-post to Facebook
User Interface
  • Flickr Gallery — I use this to show recent Flickr posts on the home­page
  • Gravatar Hovercards — Fancy dis­play of Gravatar infor­ma­tion
  • Hipster PDA Shortcode — I wrote this to insert some boil­er­plate text at the top of all my Hipster PDA pages
  • List Pages Shortcode — I use this to show recent page updates on the home­page
  • Netninja Custom Meta — I hacked this together to stuff some spe­cific meta tags in all the head­ers
  • New Tag Cloud — The tag cloud on the home­page
  • NuRealm Get Posts — I use this to show the recent blog posts on the home­page
  • Popular Posts — I use this to show the most pop­u­lar posts in the side­bar
  • Post-Plugin Library — Prerequisite for Popular Posts and Recent Comments
  • Recent Comments — Show the recent com­ments in the side­bar
  • Snazzy Archives — Fancy graphic archives.  This cur­rently has a lot of left/right scrolling on the new theme; I’m work­ing on it.
  • WPTouch — All the magic CSS bet­ter iPhone access
  • Yet Another Related Posts Plugin — If you liked this post, you might also like...
At one point, I was using wp-typography and Extra Sentence Space.  The for­mer did some really nice hyphen­ation (though at the expense of cut-and-paste time­times hav­ing weird unprint­able junk in it) as well as con­vert­ing em-dashes and turn­ing reg­u­lar amper­sands into fanci­ness in alter­na­tive fonts.  The later enforced two spaces after a period.  They both sort of ate up a lot of CPU and as much as I liked them, they weren’t worth the extra bump in host­ing costs required to keep them run­ning.  The default WordPress install han­dles smart quotes and con­vert­ing space-hyphen-hyphen-space to an emdash fairly well.
I would also like to point out the new theme I am using.  I finally dropped Thesis as my theme and went with the default twen­tyeleven with a cus­tom CSS.  I’m not 100% happy with it yet, but like its visual and admin­is­tra­tive sim­plic­ity.

chrome_xml

XML in Google’s Chrome

The sup­port for view­ing XML returned from a server from within Chrome leaves a lit­tle to be desired.  Both Firefox and Internet Explorer (and I hate to admit it, but my mem­ory tells me that IE was the first to mar­ket with this fea­ture) show XML in an easy-to-deal-with way.  They for­mat it with indent­ing, allow you to expand and con­tract sec­tions, and syn­tax color the tags.  Chrome, on the other hand, tends to treat XML as HTML.  That means that tags that look like HTML are ren­dered as such.  Tags that are not rec­og­nized as HTML are not dis­played (which is exactly the way all browsers are sup­posed to work if you have a big HTML doc­u­ment with a few XML tags within).  With XML in Chrome, you can use the view-source com­mand to see every­thing, but it’s a lit­tle dif­fi­cult to nav­i­gate due to the raw for­mat­ting and lack of col­or­ing.

A cou­ple of months ago, I ran across a plu­gin for Chrome that really should be a stan­dard fea­ture.  The XML Tree exten­sion brings to the table every­thing that Firefox and IE do as well as adding XPath sup­port.  These days, it is one of the first exten­sions I install on a new copy of Chrome.

Posted in: Code Dear Diary

Forcing a fixed-in version with the Mantis bug tracker

At the office, we use Mantis, a pow­er­ful PHP-based bug track­ing sys­tem. It offers some great con­trol over process and work­flow, but not quite the gran­u­lar­ity that I need. Specifically, I work in an envi­ron­ment where it is vital that the “fixed-in” ver­sion is filled in when resolv­ing an issue as “fixed.” Without this, there is no easy way to gen­er­ate an accu­rate changelog. Although we all do our best to fill this field in, there are slipups. To bet­ter catch these slipups when they occur, I have writ­ten the ForceFixedIn plu­gin.

The plu­gin itself is rel­a­tively sim­ple and fol­lows this pseudocode:

  1. Is the issue get­ting marked as “resolved?”
  2. Is the issue get­ting marked as “fixed?”
  3. Does the issue belong to a project for which one or more ver­sions are defined?
  4. If all of the above is “yes,” then fail unless some­thing has been entered for a fixed-in ver­sion num­ber.

More infor­ma­tion, includ­ing require­ments, instal­la­tion instruc­tions, and the down­load link are avail­able at the project page: http://netninja.com/projects/forcefixedin/

Posted in: Code

The psychology of WordPress upgrades & plugins

WordCamp Portland was last month. Although WordPress 2.8 has made upgrad­ing one-click easy, there was a lot of shared sen­ti­ment about upgrades and plu­g­ins. These beliefs boil down into two groups and are sum­ma­rized with the fol­low­ing state­ments:

  • I don’t run WordPress with any plu­g­ins what­so­ever because an upgrade to the core of WordPress could break a plu­gin and mess up my site.”
  • I don’t upgrade WordPress because I am not sure which plu­g­ins will break.” This includes the unspo­ken corol­lary that the site is left vul­ner­a­ble to attack if any given upgrade is security-related.

I do not know what other folks are using plu­g­ins for, but on my site, they are grouped into “must-haves” and “fluff.” If any of the must-have plu­g­ins break, the upgrade is a deal-breaker. I won’t do it. If any of the fluff breaks, I could prob­a­bly deal with it. I would not be happy, and would anx­iously be await­ing an upgrade to the bro­ken plu­gin (or research­ing alter­na­tives that do work), but the site would not be down. The trick is to run very few must-have plu­g­ins and make sure they are from reli­able sources that seem to have enough devel­op­ment resources to test against betas and upgrades. That last bit is a tough call for a new­bie — how do you gauge a source’s reli­a­bil­ity? — but it becomes eas­ier with time and expe­ri­ence.

To demon­strate this, let me share with you my must-haves as well as the col­lec­tion of every­thing else. You will see that there are really only two plu­g­ins that, if bro­ken, would badly mess up my site. Those plu­g­ins come from, what seems like to me, trust­wor­thy, reli­able, hard-working sources — sources that would not be a let-down dur­ing big upgrades.

My Must-Haves

These are the must-have plu­g­ins I am run­ning on my site. Your list may vary.

  • Akismet — This is the canon­i­cal spam blocker.
  • OpenID — This allows me to log into other sites using my Netninja login.

Basically, my site (and my access to other sites) would not be func­tion­ing opti­mally with­out either of these two plu­g­ins. I am not wor­ried about Akismet break­ing in an upgrade because the pub­lisher is WordPress. I am also not wor­ried about the OpenID plu­gin break­ing dur­ing an upgrade because it seems to have an active devel­oper com­mu­nity behind it. There are fre­quent bug­fixes and fea­ture enhance­ments, such that I feel they are keep­ing on top of the WordPress 2.9 beta test­ing.

My Must-Haves With Workarounds

These would have gone in the must-have group, but they auto­mate tasks that I am con­fi­dent enough in my skills to man­u­ally per­form, if needed. Of course, I would pre­fer the auto­mated way.

  • Bad Behavior — Another spam blocker. This one is less WordPress-specific and is just a WordPress-plugin-wrapper around a more generic spam-bot catcher. If I had to, I could just fall back to using only Akismet.
  • Maintenance Mode — This plu­gin shows a nice lit­tle mes­sage stat­ing that the site is down for main­te­nance. Previous to this, I would man­u­ally tweak the .htac­cess file to enable HTTP-auth pass­word secu­rity, with the mes­sage “down for main­te­nance,” but this plu­gin is more clean.
  • Twitter Tools — New posts get tweeted. I could always do this man­u­ally or not at all.
  • WP Super Cache — I do not expect to get Slashdotted or Dugg-effected any time soon, but if I did, I can always fall back to the good ol’ .htac­cess redi­rect to a sta­tic file rou­tine. A bit of a pain, yes, but do-able. If you run a higher-traffic site than I, you would prob­a­bly want this in the above sec­tion.

Fluff

Everything in this sec­tion is icing on the cake. It is UI fluff that makes me happy, but does not func­tion­ally effect the site.

  • After The Deadline — This plu­gin checks spelling and gram­mar. Firefox itself has an inte­grated spellchecker, and I often find my gram­mar is okay.
  • Breadcrumb — This pro­vides a nav­i­ga­tional set of bread­crumbs across the top of “pages” (as opposed to “posts”), show­ing the cat­e­gory hier­ar­chy back to the top.
  • Clean Archives Reloaded — This is a fancy way to get to the archives, but I find peo­ple typ­i­cally arrive at archived pages via search.
  • Extra Sentence Space — I am often anal about print, includ­ing text pub­lished on the inter­net. Something that has always bugged me about HTML is that mul­ti­ple spaces get coa­lesced into a sin­gle space. A sen­tence ends in two spaces! Period! Space-space! This plu­gin pre­vents that double-space-coalescing, tak­ing the two spaces I type into the WordPress edi­tor and mak­ing them two spaces when you read the post.
  • FeedBurner FeedSmith — This plu­gin pro­vides sta­tis­tics for the RSS feed. It’s nerdy and nice to have. I should prob­a­bly review the stats more than I do.
  • Get Comments Count — This plu­gin dis­plays a dynamic image con­tain­ing text like “3 com­ments” in the RSS feed. The RSS con­tent itself stays the same, but the linked image updates to dis­play the num­ber of com­ments. This is mainly a nicety for when the feed gets syn­di­cated to LiveJournal.
  • Google Analytics for WordPress — This inte­grates the blog to my Google Analytics account. That’s another thing I should prob­a­bly be check­ing more often.
  • Google XML Sitemaps — This pro­vides Google with a nice lit­tle con­cise descrip­tion of the web­site, so it does not have to crawl the entire site as often.
  • RSS Footer — To dis­suade con­tent from being stolen by spam­mers and posted on a fake linkblog, this plu­gin pro­vides attri­bu­tion and a link back at the end of each RSS arti­cle.
  • StatPress Reloaded — You would think I had enough stats already. This is a sta­tis­tics plu­gin I actu­ally (some­times) use, pro­vid­ing inte­grated stats and real­time view­ing of traf­fic. It is not as com­pre­hen­sive as Google or Feedburner, but this one I actu­ally remem­ber to check occa­sion­ally.
  • Subscribe To Comments — This allows com­menters to receive email fol­lowups.
  • Wordbook — Most of my LiveJournal and MySpace friends have moved on to Facebook. This updates Facebook with a lit­tle blurb each time I post some­thing new. I may actu­ally drop this soon. At one point in the past Wordbook would include an excerpt and thumb­nail (if your post con­tained a pic­ture), but it is strictly the post’s title now. Twitter-Tools informs Twitter using just the title and a link to the blog post, and my Twitter posts get pushed to Facebook, so Wordbook in its cur­rent form pro­vides very lit­tle any­more.
  • WPtouch iPhone Theme — This is a dynamic theme for the iPhone. If some­one con­nects with their iPhone, this theme auto­mat­i­cally kicks in and makes the user expe­ri­ence opti­mized for that screen and input method.
  • Yet Another Related Posts Plugin — Do you see those “related by key­word” links below? This plu­gin auto­mat­i­cally gen­er­ates those.

Themes

I really have very lit­tle expe­ri­ence with themes and upgrad­ing. I started with WordPress 2.6 or 2.7 and a slight cus­tomiza­tion to a free­bie theme. When WordPress added threaded com­ments, they were not prop­erly reflected in my theme, so I just took the basic crappy theme (you know: black text on a white back­ground with that rounded blue rec­tan­gu­lar header at the top, that screams “I did not spend any time cus­tomiz­ing WordPress”) and played around with the CSS file until I got some­thing resem­bling what you see now. Presumably, when WordPress 2.9 arrives, if there are any UI changes, I would have to do the same, which is going to suck.

I would imag­ine if you shelled out money for a pre­mium theme like Thesis, then you should expect a level of qual­ity and ser­vice such that upgrades will “just work.” But again, I have lit­tle expe­ri­ence in this realm and will have to yield to oth­ers’ opin­ions.

Conclusion

To reit­er­ate what I said above, make a list of your plu­g­ins. Cross out any­thing that is not a must-have. You are then left with a list of “if this breaks I’m screwed” plu­g­ins. Is there any­thing on that list that WordPress could not do before, but now includes as inte­grated func­tion­al­ity? Do those plu­g­ins come from reli­able sources or can you not tell? Perhaps stop by Beer & Blog and ask. (Ironically, I’m pimp­ing Beer & Blog here, but have never been there myself due to my Friday sched­ule.) If they do come from less reli­able sources, are there alter­na­tives with sim­i­lar fea­tures but do come from reli­able sources?

Posted in: Code

Bookmark Material

I started to write a com­ment to the post Fear of (book­mark) com­mit­ment? Try I Need to Read This over on Silicon Florist, but what I found myself writ­ing started get­ting longer and longer and I real­ized I might be bet­ter off shar­ing as a fully hyper­linked blog post.

Rick talks about tem­porar­ily book­mark­ing arti­cles for return­ing to later. You prob­a­bly know the sort of thing: a long, but inter­est­ing look­ing arti­cle on Digg’s home­page that you do not cur­rently have time for, some cool video that a friend Twitters, a link to a pos­si­bly NSFW pic­ture via IM that you’d rather not chance look­ing at now. They are all links you want to get back to (after work, when the boss isn’t around, or on a higher band­width con­nec­tion), but they are not nec­es­sar­ily links you want to keep for­ever and ever.

He goes on to intro­duce a Portland-based ser­vice (yeay, Portland!) called I Need To Read This that fits that sit­u­a­tion.

One par­tic­u­lar quote in the arti­cle jumps out at me:

In short, you can’t com­mit to sav­ing it to your book­marks because you’re not sure if it’s book­mark mate­r­ial, yet.

I am not sure I agree with this state­ment. It sounds like I Need To Read This is a great ser­vice and I do not want to be the neg­a­tive get-offa-my-lawn guy, but I have been doing this tem­po­rary link sav­ing for years with noth­ing more than book­marks and a plu­g­ins I already use. Here’s my secret: every­thing is book­mark mate­r­ial. Or, at the very least, every­thing has book­mark poten­tial.

I have one spe­cial book­mark folder in my Firefox tool­bar called To Review. Anything that looks inter­est­ing, but I do not have the time to read (or oth­er­wise am not in a sit­u­a­tion in which read­ing is advised), I add as a book­mark in the To Review folder. All of the other book­marks and book­mark fold­ers are, as Rick says, “book­mark mate­r­ial.” This one folder is the wild­card anything-goes folder. To look at it like email, this is my inbox. Bookmarks can be deleted, Dugg, archived into other book­mark fold­ers, and what­not. I even try to use the Inbox Zero method­ol­ogy against this folder so that its size does not get out of con­trol.

The To Review folder is only half of the equa­tion. If you are the sort of per­son who only uses one browser on one com­puter (i.e. you carry your lap­top every­where or only do com­puter work in a home office), you’re done. You can stop read­ing here because every­thing you need is cov­ered.

I hap­pen to be in a sit­u­a­tion where I have a Linux box at work, a Mac lap­top, and a Mac desk­top. I end up hav­ing to syn­chro­nize my book­marks because of this. I want my quick-search book­marks to always be around (i.e. “pow harry pot­ter” in the URL bar searches Powell’s for Harry Potter books.) I want links to research required by my cur­rent work and per­sonal projects at hand. For me, syn­chro­niz­ing is a given. I guess I could be using Delicious — and do use it for really-really long-term book­marks — but I don’t use it for daily or secure stuff. Personally, I use Foxmarks (soon to be Xmarks) because I’m a Firefox guy that has to go across oper­at­ing sys­tems. Foxmarks makes sure that my To Review folder (as well as all other book­marks) stays in sync between all machines. With this method, any­thing that shows up on an RSS feed at work that looks inter­est­ing but too in-depth to cover in a cof­fee break gets book­marked and synced for when I get home. This is the syn­chro­nizer I hap­pen to use, but there are plenty out there.

A recent added bonus to Foxmarks/Xmarks is the new Safari plu­gin. This syn­chro­nizes Foxmarks with Safari — and more impor­tantly, the iPhone. It used to be that I had to go to a spe­cial myfox­marks web­site on the iPhone to get to these links, but now they sync as local book­marks. It is also nice to still have the option to go to myfox­marks if I have not synced in a lit­tle while.

So that is my method of mark­ing things to read for later. I can­not say “it doesn’t require a spe­cial plu­gin or book­marklet” because it does. It just doesn’t require a spe­cial plu­gin beyond those that I already need to use for other pur­poses. And get off my lawn!

Posted in: Dear Diary Portland

Google Chrome

Google’s new Chrome web browser looks quite promis­ing. I set up a vir­tual machine run­ning XP today to test it out. It turns out that it will not run on Win2K (my cur­rent vir­tual machine) and the XP install is from some expired MSDN disc or some­thing and does not have a func­tional Genuine Windows DisadvantageTM, so will implode or some­thing in 60 days. Hopefully they come out with their Mac ver­sion before then.

Overall, it’s quite snappy. I was happy to see that the embed­ded web server stuff we are doing at work runs just fine through Chrome. I actu­ally assumed it would, con­sid­er­ing the under­ly­ing engine is WebKit, and I split the major­ity of my devel­op­ment time between Firefox and Safari–but it was nice to see with my own eyes. The spar­tan user inter­face is refresh­ing. The mem­ory man­age­ment is incred­i­bly awe­some. It was very inter­est­ing to pop up the spe­cial­ized task man­ager and see how much mem­ory, for instance, the Digg home­page uses.

I would really like to try using it seri­ously day-to-day. Aside from the obvi­ous short­fall of no Mac ver­sion, there are two fea­tures that are deal-breakers in this regard. The first is an ad blocker. After so many years of using AdBlock on Firefox, I was sur­prised and shocked to see that the inter­net has ads! :-) The other fea­ture I would need is book­mark syn­chro­niza­tion. Between the office machine and two main home machines, I really can­not be doing this kind of thing man­u­ally. Foxmarks does this sur­pris­ingly well in Firefox. In Firefox 2, Google even had a Browser Sync plu­gin of their own (for not just book­marks, but cook­ies and his­tory), but sup­port for that was dropped when Firefox 3 was released.

And as an aside, is it just me, or does any­one else get a sort of GLaDOS vibe off of the icon? “The Enrichment Center is com­mit­ted to the well being of all par­tic­i­pants. Cake and grief coun­sel­ing will be avail­able at the con­clu­sion of the test. Thank you for help­ing us help you help us all.”

chrome-205_noshadow.png

Posted in: Dear Diary

My Firefox Plugins

This is mainly for my own ref­er­ence, although I fig­ured the list could be ben­e­fi­cial to oth­ers. These are the plu­g­ins and Greasemonkey scripts I am using under Firefox. They’re also doc­u­mented (and updated) at http://stackoverflow.org/wiki/My_Firefox_Plugin_Setup

Posted in: Dear Diary

First Post!

Welcome to the inau­gural post with the new blog setup!

I have been mean­ing to redo netninja.com for about a year now. Because of stuff I made avail­able there a long, long time ago and never got rid of (namely: BO and BO2K plu­g­ins), every web fil­ter declares it to be a mean, bad, nasty, evil hacker site. It even almost failed me from get­ting a job about 5 years ago because the HR depart­ment got scared. The cur­rent plan is to slowly migrate con­tent from netninja.COM over to netninja.ORG. The good stuff moves. The “naughty” stuff does not. Eventually, the netninja.COM con­tent is dumped and com­pletely replaced with the .ORG, so that both sites mir­ror the exact same con­tent.

For a long time, I was hes­i­tant to choose any given frame­work for build­ing the new site. I wanted to build it by hand because it gave me the most flex­i­bil­ity (and that is, basi­cally, how I do most of my sites — using PHP tem­plates to, effec­tively, present sta­tic con­tent.) On the other hand, there are a num­ber of blog and con­tent man­age­ment solu­tions that auto­mat­i­cally take care of every­thing, none of which I really liked, until I looked at WordPress again. The lat­est ver­sion seems flex­i­ble enough, with pow­er­ful plu­g­ins, and a good caching plu­gin (for slashdotting/digging), and I think I can live with it.

As part of this migra­tion, I am writ­ing my blog posts over at net­ninja (using meth­ods that I bla­tantly stole from Rich.) Don’t worry. Everything I post at net­ninja is auto­mat­i­cally mir­rored at LJ, and I still use LJ to read friends’ blogs so that I don’t miss out on any pro­tected posts. I’m not one of those peo­ple who posts a lot of “pri­vate” stuff, but in the rare event I do need to (e.g. a new phone num­ber, new mail­ing address, party invite, Wii friend code, etc.) I’ll just skip right over to LJ and post it with the proper friend per­mis­sions.

Firefox 2, Electric Boogaloo

Please note that all blog posts before 8 April 2007 were auto­mat­i­cally imported from LiveJournal.  To see the com­ments and any LiveJournal-specific extras such as polls and user icons, please find the source post­ing at http://brianenigma.livejournal.com/2006/07/

Okay, so I am slowly try­ing to migrate myself to Firefox 2.0 on the Mac. I have been using it at work and fig­ured it was about time to force myself to use it at home so that I can get a really good feel for how it works in com­par­i­son to Safari. Previously, I did the “30 sec­ond try­out” wherein I imme­di­ately declared that it sucks com­pared to Safari and left it at that. Now that it runs fast (and/or I have more mem­ory) and it has built-in spellcheck (the lack of which was pretty much a deal­breaker with Firefox 1.5 vs. Safari), I’m will­ing to give it a try.

I real­ize that plenty of peo­ple have been using mod­ern ver­sions of Firefox longer than I. I ask the fol­low­ing ques­tions with the hope that some­one can help answer them.

1. Is there a way to eas­ily “clone” (or bet­ter yet, syn­chro­nize) my exten­sions and/or Greasemonkey scripts between two machines? When I freshly install Firefox, it would be super-nice to auto­mat­i­cally have my exten­sions there (Adblock, Flashblock, etc.) When I install an exten­sion at home (or add an Adblock rule, even), it would be great to have that appear at work with­out hav­ing to think much about it.

2. Is there an exten­sion that works with Firefox 2.0 that lets me define hotkeys for “next tab” and “pre­vi­ous tab?” Previously, I was using either Keyconfig or some­thing sim­i­lar that let me do this with 1.5. There is a great lit­tle exten­sion called Nightly Tester Tools, which allows you to load “older” exten­sions into a “newer” Firefox ver­sion, which helped for some exten­sions, but not for this par­tic­u­lar one. They prob­a­bly changed an API or object model dras­ti­cally enough in 2.0 that a sim­ple ver­sion num­ber bump isn’t suf­fi­cient.

3. Is there a good place to browse pop­u­lar Greasemonkey scripts? I’ve seen userscripts.org, but it really only seems to be geared toward “I know what I’m look­ing for, let me search for it” as opposed to “I don’t yet know what I’m look­ing for, I just want to see what other peo­ple find use­ful.” I have a YouTube down­loader and a MySpace cus­tom theme killer, but won­der what other peo­ple find use­ful. (And no, I don’t need the “kill the LiveJournal navbar” thinger–contrary to pop­u­lar opin­ion, I rather like that thing.)

4. What exten­sions and Greasemonkey scripts do YOU find use­ful? I’ve been using:

  • Adblock — blocks ads by pat­tern match­ing; lets you right-click images/iframes to add new pat­terns
  • BugMeNot — gives you throw­away names+passwords for “reg­is­tra­tion required” sites
  • Distrust — The same thing as Safari’s “pri­vacy mode” — when enabled, sites don’t go into the his­tory or cache
  • Flashblock — Displays a place­holder where Flash would be dis­played on a page; click­ing the place­holder loads the Flash (good for ads and/or annoy­ing sites.)
  • Google Notebook — Lets you save text snip­pets and web pages in your Google note­book. Strangely, I’ve never used this beyond ini­tially test­ing it out; I tend to use my own Wiki for the same pur­pose.
  • Greasemonkey — Allows page tweak­ing
  • JavaScript Options — Lets you alter JavaScript behav­ior. Specifically, I use it to pre­vent pages from open­ing non-resizable win­dows. That bugs the crap out of me because they can never get the size right for my display/window-trimmings.
  • Nightly Tester Tools — Lets you install exten­sions that are not nec­es­sar­ily for the ver­sion of Firefox you are using.
  • Stumbleupon — Lets you “chan­nel surf” web pages. I’m about to delete this, as its use­ful­ness is pretty low.
Posted in: Code Software