3 ms·
The 'magnet URI' was merely the right suggestion, for a tiny sliver of shared convention, at the right time. You can look at the original writeup – http://magn
by gojomo 15y ago
The 'magnet URI' was merely the right suggestion, for a tiny sliver of shared convention, at the right time.
You can look at the original writeup – http://magnet-uri.sourceforge.net/magnet-draft-overview.txt http://magnet-uri.sourceforge.net/magnet-draft-overview.txt – and find a goofy ad-hoc mechanism where local software interested in 'magnet' links listened for localhost web hits, in a certain port range, rather than fighting over the 'magnet' URI scheme handler. That could be seen as either a blathering kludge or a very early attempt at 'web intents'.
I don't know if any code other than my demo ever implemented that localhost-handler trick. But the main idea – of a generically-named URI that was descriptive rather than location-centric – had its own legs. It spread from software to software, even without any formal spec stewardship/revisions. A key step for its longevity, when 'magnet' was adopted to wrap the 'btih' identifiers for DHT-based torrent tracking, happened long after my attention moved elsewhere.
I'd like to think the continuing adoption was because the original draft, even though crude and incomplete, had the right mix of a familiar/defensible URI syntax, wide-open descriptor semantics, and a catchy name/icon.