Adopt DNSLink for mapping domains to torrents

[RangerMauve]

Hey folks, I've been working on loading web content from BitTorrent for local-first / "dweb" use cases.

Primarily I've been working on this in the BitTorrent integration in the Agregore Browser and we're currently working on integrating it into the p2p site publishing in https://distributed.press and spreading to some of the groups we've been working with.

One of the things we've been doing for the sake of UX is having a way to map domains like example.com to p2p datasets so that users could load them via DNS instead of public keys or magnet links that aren't easy to type by hand.

For IPFS and Hypercore (formerly dat, now holepunch?) we've been making use of the DNSLink standard which lets us add TXT DNS entries that point to the p2p resource a client might try to resolve.

We'd like to do the same for BitTorrent URLs.

Would folks be interested in a BEP that solidifies this approach? Is there another way to map DNS to torrents that folks have been using which we should standardize around instead?