Google code search is still up, just at a different URL here:
http://code.google.com/codesearch

And it's not limited to just Google's own code. From this blog post: http://googlesystem.blogspot.com/2012/01/google-code-search-still-available.html

http://flattr.com/ seems to have it about right. You add money to your flattr account, then you can pay in small amounts and it all gets totaled up and distributed at the end of the month, where they take a flat 10%.

I am more concerned about what happens to all these big-name games with online requirements in 30 years' time. When the online servers are gone, what will we be left with? It used to be that when you bought a game, you actually got a complete copy of the game itself, so people at least had something to try and preserve. Now, it seems the trend is to just give you an interface, with essential pieces of the game existing only on a server somewhere, to never be distributed...

Oh man, I have a strong desire to get apache running in this, just so I can have the web browser serving pages to itself =) We just need a network driver...

But there could be a source of particles outside our galaxy that is only encountering the Milky Way in a specific spot / from a specific direction. We'd be out of the path (or shielded from them) until our solar system periodically ends up on that side of the galaxy.

Only as anonymous as precise location information can be. It's still going to show the start and end address of every trip you make, which includes your home and work addresses among other things.

Yeah, well technically the same is true for the text. The actual letters aren't sent over the internet, just a simple index which is used to choose a representation to draw locally.
But since they are standard, the sender can expect the receiver to interpret it the same way.

Xen has been making some progress with VGA passthrough (support was added in 4.0.0, http://wiki.xensource.com/xenwiki/XenVGAPassthrough .) Some Intel, AMD, and nVidia graphics cards are reported to work, and AMD has recenly submited patches for vga passthrough to their mailing list. I don't have any experience with it yet myself though.

Actually, the release schedule page has the first alpha release on June 3. The second alpha is end of June (actually July 1st.)

I see the appeal, but I prefer being able to see the source code for an programs my browser is running. If we move to distributing byte code, we lose that ability - if we wanted to know what a web app was having our browser do, we'd have to fall back on reading disassembly. It seems that could ultimately hurt the openness of the web.

Incidentally, it is also an anagram for Grab at Rich

What's your point? If you are using a proxy server, then you would presumably get an address closer to the proxy server rather than close to yourself. Since all your traffic will be going through the proxy server anyway, that's still an improvement.

Unless you regularly send emails to people you don't know (and so wouldn't have you in their address book), I don't see why you'd need to have more than a few dollars in your account. So if your computer is owned, sure, you might lose those few dollars, but nothing more. It would be an incentive to clean up your system.

And as has been mentioned before, using an escrow-like service similar to Paypal would largely avoid a need for credit-card processing fees, etc, right? It seems all the payment between users of such a service could just be handled internally.

I don't see why mailing lists are an issue with a micro-payments system. There would be no need to attach a payment to mailing list emails (or to emails with friends/family, etc) since supposedly you would just add that address to your address book and they would be allowed through. After all *you* subscribed to the mailing list, so you are expecting emails from them.

It seems you would only need to attach a payment to an email if the recipient doesn't know you (and so wouldn't have you in their address book) or if it is urgent enough that you want to make *sure* it gets read.

To be fair, reading the referenced bug report it looks like the corruption has only being reported by one user. Apparently no one else has reproduced it, and faulty memory has not been ruled out as a suspected cause.

It is prudent to mention in the release notes, but doesn't quite seem worth holding up the release for.