Here my switcher now -- there's our beloved dino!

If you want to set this up too, know that I had to jump through a few hoops to get it to work. The difficulty appeared to be a by-product of Fargo needing to get my authorization to connect to my Dropbox account (in technical terms, OAuth is a pain in the ass). The workaround was to get this authorization before creating the Fluid App.

1. Open Safari
2. Go to http://fargo.io to launch Fargo
3. Follow the prompts to authorize Fargo to connect to your Dropbox account
4. Close Safari (optional)
5. Create your Fargo Fluid App (follow the instructions on http://fluidapp.com/)
6. Launch your new Fargo Fluid App

Why did that work?!

I'm using a free version of Fluid (for now -- still kicking the tires). The free version doesn't have separate cookie storage -- it shares it with Safari (Fluid is built on Apple's WebKit, like Safari). So, by setting everything up in Safari first, Fluid was able to piggyback on that setup when it created the Fargo app. Neat trick -- but not a long term solution. For example, I want to pay for the full version of Fluid (to support the developer), but I suspect this trick won't work in the full version.

Queue config options:

• exclusive: delete when declaring connection closes. No other
  connection can even access this. Only queues can be exclusive.

• autodelete: delete when the last downstream thing (i.e. consumers for
  a queue, or queues for an exchange) goes away. Note that this isn't
  bound to channels or connections at all really.

• exclusive is more frequently useful than autodelete

More about auto-delete:

• auto_delete queues will delete themselves when their consumer count drops to 0 from a higher number. Otherwise
  they would delete themselves as soon as they were declared...

• The downside of exclusive queues is that they can only have consumers on the connection that created them. So this doesn't work for shared queues, or queues created by some app that are subsequently to be consumed from by some other app.

• Auto-Delete queues not getting deleted

Other options:

• Queue TTL

I'm currently dependent on the following fragile tools:

1. Twitter
2. Google Reader
3. To a lesser extent, Firefox and Chrome

What do I mean by "fragile tools"? Consider Twitter: It started as a fun ecosystem for development, where anyone could whip up an interesting alternative way to interact with the service. Now? Not so much. Remember "track"? Yeah.

And Google Reader seems to have only one developer -- just babysitting it. The API is not documented and can change at any moment, without notice. Plus, Google has been sunsetting services left and right. Having killed off virtually all competitors, when will Google shut down Reader?

Firefox and Chrome are both moving to narrow their feature sets. Both seem incredulous that I might want to enter the URL of an XML file and view that file in my browser window. On the plus side, both are light-years ahead of Internet Explorer or Safari in usability and reliability.

Any of these tools could very quickly stop offering key features or go away entirely. The precariousness of my position as a user of those tools leaves me in a constant state of anxiety.

P.S. This post primarily is intended to test a one of the plugins I'm using. So, it's really just a bunch of conclusory statements without any references or argument.

Apparently, this is a common problem.

First, I tried this supposed solution: disable 802.11b mode. No luck.

Then, I saw this suggestion: create an ACL whitelist entry for 224.0.0.251/255.255.255.255 in the IGMP proxy settings on the Actiontec router. That sounded ridiculous, so I kept looking.

Finally, I came across this: disable the IGMP proxy on the Actiontec router. I am loathe to disable a default setting that I don't understand, but this fixed my problem instantly, and I have yet to see any negative consequences.

My sons keep popping the keys off of my Enermax KB007U-B keyboard, and I was having a hard time putting them back on. But this picture proved very helpful because it shows how the little, white scissor hinges (or whatever the hell they are) are supposed to be connected.

brew install watch

Something I didn't realize until 10 minutes ago is that if you want to watch the output of something in your bash aliases, watch will complain because it cannot find the command. This is because watch evaluates the command you pass to it with 'sh -c', which does not expand aliases. However, if you also create an alias for watch itself, aliases will work. So, you can add the following to your .bashrc:

alias watch='watch '

Note the trailing space inside the quotation marks.

Link:

• using 'watch' on an alias in .bashrc

Solution: Run make install CFLAGS+=-O2 CXXFLAGS+=-O2 instead of just make install.

More info:

• Cannot compile node.js 0.8.2 under CentOS 6.2
• "make install": terminate called without an active exception
• build: fix spurious mksnapshot crashes for good

Now that you've cleaned out those unused indexes, restart Mongo. After the cache warms up (and depending on how many indexes you deleted), you could see a dramatic decrease in RAM consumption.

And, of course, git add the empty directory.

So helpful.

I could not understand what was going on. My code was basically structured like this:

Given that code, we know the req object is initialized with each function call. So, how could this script degrade over time?

Well, I finally tracked it down: COOKIES!

Yup, request has cookies enabled by default. So, I think what was happening was that cookies were being set (presumably, top domain-level cookies having the same name at different URLs or subdomains on the same domain) but the values in request's cookie jar were not being returned properly. That means the remote host was getting invalid cookies -- hence the 400 response for a "Bad Request."

I haven't yet spent the time to figure out if this is a bug in request. It's on my TODO list.

In the meantime, I've disabled cookies in the req object:
var req = { url: url, timeout: options.timeout, jar: false };

It's now working as expected.