techposting
@itzpaquet Yeah! I think that approach is great. I've also been trying to keep the p2p bits as minimal as possible within the protocol handlers (basically at the level of GET/PUT/DELETE). Having a similar "metaphor" between them makes it easier to try out different ones. I think BitTorrent is a great one to focus on since it's well proven and there's lots of client implementations out there.
techposting
@itzpaquet Most of my BitTorrent integration stuff is within the bt-fetch module. https://github.com/RangerMauve/bt-fetch
In Agregore you can skip importing it and use the Browser's built-in `fetch()` API directly (or GET URLs anywhere there could be an HTTP URL).
You can also paste magnet links and have it auto-convert to `bittorrent://` URLs. The URLs are there to make relative URLs and cross-origin isolation easier.
