quote:
But, if you're going to be directing millions of people through Flickr's website (as an example), they've got to pay for the hardware and bandwidth it uses, and they're most likely to pass the costs on to the company responsible for all that extra traffic.
But that's what Flickr
do. That's like saying Flickr should charge Google because Google directs a lot of traffic to Flickr. Flickr
want traffic.
If we're talking about scraping Flickr's info
without going to the site then that's a different thing. But we're not.
The routing and encryption stuff is eye-wateringly complex, aye. But there are already far more robust solutions for that than this would need. This would only
need to be as secure as the current web services are (not very secure at all). Anything on top of that would be an added benefit.
The major problem is that routing through a dynamic network of nodes is not currently going to be as fast as a simple web server. But, well, that
is done currently through a distributed system currently (DNS) so that's probably solvable.