Comment Re:That's progress (Score 2) 121
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
Comment Re:the micropayments nut (Score 1) 397
Comment In 30 years' time? (Score 1) 591
Comment This is fun (Score 2) 393
Comment Re:that always bothered me (Score 1) 158
Comment Re:Doesn't it HAVE to be anonymous? (Score 1) 422
Comment Re:What fails to be stated is that... (Score 1) 432
But since they are standard, the sender can expect the receiver to interpret it the same way.
Comment Re:Experience with IOMMU? (Score 1) 384
Comment Alpha 1 is early June, not end (Score 2, Informative) 319
It's important to say to the impatient among us that the first alpha release is not due earlier than the end of June,
Actually, the release schedule page has the first alpha release on June 3. The second alpha is end of June (actually July 1st.)
Comment Re:JavaScript (Score 1) 194
Comment Re:Reason (Score 2, Funny) 451
Comment Re:Do no evil, my ass. (Score 1) 271
Comment Re:Micropayments again (Score 1) 198
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.
Comment Re:Micropayments again (Score 1) 198
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.