dbuthay

it actually supports k2.6 since 2010. It runs on some of the newest Asus routers, so I wouldn't say those are obsolete.

Still, it is kind of a hack.

It's amazingly useful to have realtime throughput rates

tail -f query.log | pv -tri 1 > /dev/null

I think both are OK. Personally, I like whiteboards to outline solutions. A sheet of paper may serve the same purpose.

Once I decided how to solve the problem, vim comes in handy :)

I'd go for ROR, or maybe Sinatra + your favorite ORM.

If you don't want to host your own servers, you can grab an ec2 free micro instance, or just go with heroku or cloudfoundry.

probably they didn't do it because it takes too many resources to have a separate index for every user.

I thought about adding Facebook status updates to the index. If people start asking for it, I'll consider doing it.

What you see on your timeline at the time you sign up is indexed right away. After that, the app gets all your tweets and those from who you follow. As twitter has an hourly limit for API calls, it may take some time to index your friends history.

It depends on how many friends you have and how much they tweet

I keep all the tweets. So the answer is Yes, you'll be able to find tweets that twitter's search does not let you find.