Tarsnap is really designed as a backup service rather than a synchronization service: While it is very good at recognizing duplicate data and only uploading new blocks when you create an archive, it has no such mechanism for making archive extraction more efficient -- I wrote it with the presumption that people would only be extracting archives after losing data. That said, I think I can see a way to implement "tarsnap -x --sync" efficiently.
But for right now, as much as I'd love to get more customers, I don't think Tarsnap really matches the submitter's requirements.
Bing is, in essence a relaunch of the MSN Search / Windows Live Search / Live Search; Wikipedia says that Live Search was discontinued on 21st May this year, redirecting from then to Bing.
Hence Bing becomes the built-in search for many old browsers in Windows land. Some default market share is expected. What would be interesting is how the expectation stacks up against the new data.
Seven old Slashdot stories: just news, no opinion/ask slashdot stories:
Barbara Liskov, Turing award laureate, presented a list of papers that led up to her work. An excellent introduction to the theory of object-oriented programming language design.
Long, wordy, buzz-word heavy article with a little bit of interesting content buried deep inside. I wish I hadn't bothered to read it.
In case you haven't, but are thinking you might: you can run machines that are never down, even when software is being updated, if you use a few tricks. I knew most of the one's they mentioned already, and use them on my company website, which is far from downtime-proof, but has a 3-year uptime so far: call my software maintenence status "fairly sturdy".
If you're interested in upgrading to software maintenance status "bulletproof", then read something about fault-tolerant computing in Erlang. You'll learn more that way.
There are running jobs. Why don't you go chase them?