Are the user's IPs or other connection information being exposed to one another?
Could users fake the upstream response, sending a fake/false image instead?
If a user visits the page over a 14.4 modem, is he equally likely to have other users try to load over his connection as the Google Fiber user?
This seems really cool, but I wouldn't trust my sites with it yet ;)
So what? If I wanted to get a bunch of random IPs to attack, I could host a picture of a cat on my server, log IPs, and post the link on reddit. Or I could just scan random IPs within home ISP IP ranges.
I agree that there's a lot of work to be done to product-ize it-- we just couldn't wait to show off the demo!
We're adding functionality to rate peers by latency and bandwith, so consistently slow peers are removed from the network eventually.
We'll add IP profiling for geolocation and bandwith capability later on.
> Symbolism can be culture-specific. The check mark means correct or OK in many countries. In some countries, however, such as Japan, it can be used to mean that something is incorrect. Japanese localizers may need to convert check marks to circles (their symbol for 'correct') as part of the localization process.
Although to be fair, the tick (checkmark) that westerners use is not really the same as what Japanese to use to mark things as incorrect since they more closely resemble V than a tick.
Other then that, sweet proof of concept.
Red means bad but checkmark means good, so red checkmark means... what?
It's using the https://developer.mozilla.org/en-US/docs/DOM/window.URL.crea... API to get data on page, so not slow and inefficient like data urls
In most of the stuff I've worked on, it was either a database or an analysis backend the requests were blocking in.
More power to 'em though, love stuff like this. :)
On the other hand, I think a lot of people would be willing to permanently donate some upload bandwidth and processing power to wikipedia if it were feasible to take advantage of it.