magnet:?xt=urn:btih:abac45ddab754409d67e99fa661db98d31cbfa70
Great thread. Excellent post. Would read again. URIs are my favorite short-form genre.
Can we get a tracker or ten for that? Whatever it is, 24 hours of peer exchange hasn't turned up anyone in my peer cloud of '80s mecha enthusiasts who happens to have the torrent file.
I wonder why every net protocol you see linked does the stupid web browser // thing but magnet
anyway, here is a certified [DQN] quality torrent [EHT PERSONALIZED TORRENT - DO NOT REDISTRIBUTE] https://ehtracker.org/get/1045523/80b70fc90825533cba01e9ad6d803ba3395f74ba.torrent
>>4
The earliest piece of evidence I can find that references protocols other than http: and uses "//" is RFC 1738. They say
>The scheme specific data start with a double slash "//" to indicate
>that it complies with the common Internet scheme syntax.
by which they appear to mean "The WWW is really hot right now, so we're just going to copy Berners-Lee's URLs".
Also, http://magnet-uri.sourceforge.net/magnet-draft-overview.txt says
>FYI, EDonkey URIs violate many provisos of RFCs 1738 and
>2396, including the use of "//" at the front of a non-
>hierarchical namespace and the use of illegal/disfavored
>(when not escaped) characters
It's a bit of a jump from "common Internet scheme syntax" to "hierarchical namespace", but it sort of makes sense.
As to the torrent, thank you. I am now assured of its DQN quality.
>>6
I don't follow. Suppose that the format for http links just dropped the // completely. What's an example of an formerly unambiguous URL which would be ambiguated by this change?
>>7
Most browsers today even detect and hide/correct this because it should not be your job as the end user to unfuck the protocol end of URLs when you are implicitly only much interested in HTTP.
Nonetheless, a lot of the Internet runs on pure inertia and ad-hoc trying shit out. That many Internet "standards" are technically just IETF RFCs is not a mistake. "Some people started singing it, not knowing what it was...."
>>7
Nothing, the leading // are the one thing that the W3C's supreme leader has publicly come out as regretting the most.
None of it really matters, the web standard is complete garbage that was aptly compared to drowning in a sea of pufferfish that are pregnant with freddy krugar.