5 ms·
I’ll bite: How do you think this happened?
by alanh 11y ago
I’ll bite: How do you think this happened?
- emodendroket 11y agoLocal test servers I guess? I doubt someone goes through by hand finding these links.
- JoshTriplett 11y agoAutomated system with little to no oversight?
- omouse 11y agoArmy of lawyers and business people with zero technical knowledge?
- JadeNB 11y agoOther replies have indicated, surely incontrovertibly, that this is some sort of automated framework gone wrong (or wrong-er); but, in that case, I think a question is: what's changed so that that automated framework has discovered 127.0.0.1 now, and not before?
- emodendroket 11y agoProbably someone forgetting to comment out some debug code or whatever... it doesn't take much imagination to see how this might happen.
- oddevan 11y agoMy money's on someone running a Plex server (or something similar) on their own machine, then going to reddit and saying "I have a copy of [X], you can watch it here:" with a link to 127.0.0.1 (since that's how they watch it, so why wouldn't it work for anyone else?). I.E. We're dealing with the intersection of an automated framework with a "normal."
- scintill76 11y agoPlausible explanation here: https://news.ycombinator.com/item?id=9931765 https://news.ycombinator.com/item?id=9931765 . In short, a certain filesharing client serves content on http://127.0.0.1 http://127.0.0.1 and links to that are distributed around the web.
- touristtam 11y agowild guess: a branch of popcorntime in French?