3 ms·

Reminds me of an 2007 talk from CCC, sadly in German: https://media.ccc.de/v/24c3-2355-de-trecker_fahrn https://media.ccc.de/v/24c3-2355-de-trecker_fahrn It's

Reminds me of an 2007 talk from CCC, sadly in German: https://media.ccc.de/v/24c3-2355-de-trecker_fahrn https://media.ccc.de/v/24c3-2355-de-trecker_fahrn It's how they wrote one of the first "performing trackers" as most others around the time where python or php based. https://en.wikipedia.org/wiki/Opentracker https://en.wikipedia.org/wiki/Opentracker And it seems OpenTrackr from the article is based on Opentracker software. It's an really entertaining talk. They destroyer a router from hetzner when they first rented a server because of the traffic.

toomuchtodo 3y ago
> It's an really entertaining talk. They destroyer a router from hetzner when they first rented a server because of the traffic. Would magnet torrents fit in DNS TXT records? Seems like an interesting way to distribute load across global DNS servers. https://news.ycombinator.com/item?id=36945177 https://news.ycombinator.com/item?id=36945177 ("Show HN: File distribution over DNS: (ab)using DNS as a CDN")
- Scaevolus 3y ago
  Open trackers like this don't distribute the torrent files themselves-- all they do is help you find the swarm for a torrent given a hash as input. A magnet hash is little more than a hex-encoded infohash along with a few trackers to use for coordination and a filename wrapped in a URI, so DNS TXT wouldn't provide much compression (~30B DNS record to ~200B magnet URI). Given an infohash, a torrent client has to find a swarm member (or DHT) to download the full torrent metadata.
  - deleted 3y ago
    [deleted]