31–40 of 43 posts
Will get a heck of a lot easier once the people at FaceBook, Google, Apple, NSA, et all get their way with IPv6. And please don't try to tell me more about "privacy extensions". When I swim in a see of 4.3 billion address, I'm forced to share, leaving an undeniable possibility that I could be another person. While 3.4×10^38 identifiers could be so huge I never have the same address twice, the implementation does not…
I like your idea, especially the number of servers you used. I'm only concerned that using a full HTTP GET to measure the latency (function request_image() in src/ping.js) makes the results possibly way more random than measuring the TCP/IP RTT server-side. That is, your method seems to measure the latency in higher net layer than TCP. Anyway, nice idea :)
Will get a heck of a lot easier once the people at FaceBook, Google, Apple, NSA, et all get their way with IPv6. And please don't try to tell me more about "privacy extensions". When I swim in a see of 4.3 billion address, I'm forced to share, leaving an undeniable possibility that I could be another person. While 3.4×10^38 identifiers could be so huge I never have the same address twice, the implementation does not…
Feels a bit overconfident - it was much better than the previous approach, and it got better over the iterations, getting very close - but however, 100% of the time my actual location was outside the circle. I.e., the center points seem reasonable, but the size of circle is unreasonably small because it's obviously smaller than your actual precision.
Can I assume this was meant to show my own location? If so, I can assure you I'm not in India, Pakistan or Oman (or the middle of the Indian Ocean) as it suggested.
I have to agree with this. I'm pretty sure that the middle of the Atlantic Ocean isn't quite the same as the U.S. East Coast...
Ran this about 10 times, it never once entered the correct hemisphere. Hint: I don't live in the northern one.
Idea is good however needs more refinement. Currently it detects way wrong at least for me (Europe)
I wonder if it connected to various servers using websockets and did some in/out message timing. I think it needs to have some knowledge of backbones or something like. Wonder if you had a bunch of signals, like telco, and timing informations, you could throw it into an ML tool and it could learn the backbone topology implicitly....