codeinthehole

6 ms·

1. 31.▲
   by codeinthehole 18y ago

   Interesting but all pretty straightforward. The more interesting question around caching is how to keep the cache fresh - do you just cache for short amounts of time and let them expire, or do something clever at the front end (such as tag
2. 32.▲
   by codeinthehole 18y ago

   It would help if you provided definitions for the returned words to aid matching an answer to the clue. Nice idea though.
3. 33.▲
   by codeinthehole 18y ago

   Great feedback - thanks! I've added all these as uservoice items so the non-HN crowd can look and vote. I'll definitely be implementing some of these over the weekend though. I'm looking forward to reading Google Analytics in the morning.
4. 34.▲
   by codeinthehole 18y ago

   No probs. Once the storm's over, I'll blog about the set-up.
5. 35.▲
   by codeinthehole 18y ago

   Great idea! Have added this to the uservoice suggestions and will have a look at how to implement. As NearlyFreeSpeech doesn't supper cron as yet - it might be easier to only tweet commands once they get more than 5 votes say.
6. 36.▲
   by codeinthehole 18y ago

   Whoops. You're right - I'll actually read the comments in future.
7. 37.▲
   by codeinthehole 18y ago

   Already on NFS but still having these problems
8. 38.▲
   by codeinthehole 18y ago

   That's with trouble with being on the frontpage of both reddit and hacker news. My hosts, NearlyFreeSpeech reckon their systems can handle the surge. But apparently not.
9. 39.▲
   Ask HN: Rate my webapp: commandlinefu.com

   51 points by codeinthehole 18y ago|43 comments