711 karma · joined August 24, 2007
http://www.skrenta.com/
Individual nodes can often make "personal" decisions about what to do in subobtimal situations. If you can answer an incoming request, even with partial or out-of-date data, do so; it's better than not replying. For the repair agent, each node can see its own view of "holes" in the 3-level replication, and offer to make copies of <3 buckets to bring back up to three copies.
You can see the full list of categories we're doing this for in a screenshot in the Search Engine Land post: http://searchengineland.com/blekko-slashes-more-spam-with-zo...
I realized that there were thousands of great HN threads that I hadn't seen because I hadn't been paying attention to the site when they were ranking.
So I pulled together a little db of the top 10,000 HN threads (loosely defined; a thread with >1 points, 1> comments, and some web link rank).
I put these into a random shuffle so that reload would give me 30 fresh threads that I (probably) hadn't seen before.
I'm pretty happy with this. Lets me scratch my HN itch when I've exhausted the main page, and it's often interesting to see the old material again.
Very handy. I put ehow.com on mine and never see results from them.
Sure, you can do that on a corporate blog too. But something about them, maybe the multiple authorship, or the fact that it is a company blogging and not an individual...I don't know, I don't tend to read a lot of corp blogs.
I posted the article - and included the embargo paras, which my co-founder and I nearly cut - because I thought the backstory would be useful/interesting to the folks there, who seemed to be unaware of the pr process during the prerelease of blekko. I wanted to open that up for them.
Your comment was spot-on good advice for the ycomb co's though. I voted it up.
Really irked that wsj broke our embargo. Irritated that I wasn't in the office when our site went live after 3.33 years, irritated that we didn't get to do the last bug-fix push to production, irritated that I knew TC wouldn't post, irritated that other journos would be irritated with me, irritated that it flatted the temporal curve on the launch pop. And for what?
Time-sync on stories is actually a good thing for the news stream. I don't see why journos don't get that.
But techcrunch has a policy of not posting their story if an embargo is broken, so we didn't get the TC story that we had briefed them on.
We're auto-firing slashtags for certain regular queries now, e.g. [cure for headaches] will auto-fire /health, [industrial design colleges] will auto-fire /colleges. We're doing this initially for health, lyrics, colleges, autos, hotels, recipes, and personal finance.
Getting the crap from sites like ehow out of the results and pushing results into a curated set of high-quality sites for queries in spammy categories really cleans up the results there.
Nevertheless, blekko should be open for everyone now...we'll keep it open if we can.
we're still in private beta, but happy to give invites to anyone here who wants one. just email me rich at blekko.
The best way to get an invite is hit us on twitter or facebook (see links from blekko.com). Then we can DM you an invite when we have them ready.
Generally we tried to delay the conversion of a component to C++ as late as possible, since it makes it so much harder to change and iterate on. We call it "pouring cement on the code". For some things it's absolutely necessary to drop to C for speed, others it doesn't make a lot of difference since you're bound by other constraints like I/O.