Your ISP sells you a product which they know is oversold in capacity. Instead of fixing their capacity problem they now try to get you a their consumer to not use their product (the cap limit).

The concept of TOECDN solves the distribution of static content on the Internet. NetFlix, Youtube, Steam and whatever you are using to go over your cap can and should be fixed by TOECDN.

TOECDN place the cache server as close as possible to you as a consumer - even with the possibility to have your own cache server at home!

If you place cache-servers within the ISP networks, they, as a benefit, don't have to upgrade their networks connection to be able to push out more data to their consumers.

Before anyone reply and say: it won't work, it will never work, I will make sure its not going to work, I have invested heavenly in CDN companies stocks so your solution can not see the light, etc...

I would like to ask you: How does _your_ solution looks like to be able to let anyone on the Internet to cache their content on cache-servers within a ISP?

http://www.toecdn.org/

take a look at hyperdex if your are looking for a NoSQL DB: http://www.hyperdex.org/

What do you think of The Open Edge Content Delivery Network as a concept?

http://www.toecdn.org/

turn of javascript for slashdot.org, fsdn.com, googleadservices.com and truste.com.

problem solved.

butterfly labs and josh "inaba" zerlan.

he's is they guy how can fix anything in just two weeks (tm).

BFL is known for their accurate power calculation when they are designing their products. that's why nvidia hired them.

Dear samzenpus,

Please don't include any link directly to the documentation.

Regards

The Community.

no I didn't. I sad HOW they got hand of the e-mail addresses.

they did get the MD5 hashes from Disqus, from their api.

to know which e-mail address it belongs to, Expressen.se did generate MD5 hashes of all their e-mail addresses that they have in their (e-mail) system.

now they know which hash belongs to which e-mail address and can then continues the search for who his/she is what that specific MD5 hash.

that's why you using username-vendor@yourowndomain.com. works everywhere.