> Your best bet seems to be webtorrents indeed.
I wish it was that easy. A few more details then.
#p2p #cdn #blossom #devstr
More precisely, p2p-media-loader is actually used in PeerTube: it's a wrapper that combines the usage of traditional CDN + WebTorrent, and they definitely have this complex design not out of the blue; others didn't really work.
https://github.com/Novage/p2p-media-loader#how-it-works
In an ideal world, I wish it was just normal Torrent (which is at least impossible from browser engines).
And with just WebTorrent (Torrent on top of WebRTC)—there are some WebRTC-related traps:
- at least the warm-up is too slow, according to p2p-media-loader devs
- due to privacy settings or/and ISPs behind certain kind of NATs, one may not have a functioning WebRTC-based peering at all (only connections through TURN, which is not supported in p2p-media-loader; because that would be an unnecessary complication since they have to use the CDN anyway).
There are more. There's no way to escape the WebTorrent tracker and use DHT due to some browser limitations, and at the same time you can't have too many of the trackers (iOS/Safari in particular may aggressively close WebSocket connections out of the blue if it decides there are too many of them, and it can be challenging to handle this properly if at all).
These are just a few things I recalled from when I was setting up vidstack player + p2p-media-loader on my website.
In two words, thing that will work in practice is (an event kind 10063 server list) of Blossom-based CDNs (at least for warm up) + p2p-media-loader (only helpful in case of multiple concurrent connections) + stable 1Gbps+ network.
Other paths are known frustrating traps; it's hard to even test/debug this stuff because you can't easily simulate the identical weird NATs some ISPs have.
codonaft
npub1al…7rg94
2026-10-14 05:10:22 UTC
in reply to nevent1q…cv6n
Author Public Key
npub1alptdev5srcw2hxg03567p4k6xs3lgj7f6545suc0rzp0xw98svse7rg94Published at
2026-10-14 05:10:22 UTCEvent JSON
{
"id": "0199c014aa3aa3fdf3e66206bb3b410e9b51293bfb9762c3a4ca57f11cabd754",
"pubkey": "efc2b6e59480f0e55cc87c69af06b6d1a11fa25e4ea95a439878c41799c53c19",
"created_at": 1791954622,
"kind": 1,
"tags": [
[
"e",
"ac1b71cf2e35c709dba9a1ebf70fa16aecd7d60c9ade282b08e2df76b6c7ed3f",
"",
"root"
],
[
"p",
"efc2b6e59480f0e55cc87c69af06b6d1a11fa25e4ea95a439878c41799c53c19"
],
[
"p",
"0bc7382c7f470914492147a717a7ee359a9d2bcad1206a40b43a3811989e1f2a"
],
[
"e",
"83ea624fbf92ea68c82b64e20c97f6bff92d4b4bfe67b47a961d4e92d99ce8aa",
"",
"reply"
],
[
"p",
"abaa09dab1fc3fffc1409fdb28b13832cd4031704c4df6198525fa7ea466bed2"
],
[
"t",
"p2p"
],
[
"t",
"cdn"
],
[
"t",
"blossom"
],
[
"t",
"devstr"
]
],
"content": "\u003e Your best bet seems to be webtorrents indeed.\n\nI wish it was that easy. A few more details then.\n\n#p2p #cdn #blossom #devstr\n\nMore precisely, p2p-media-loader is actually used in PeerTube: it's a wrapper that combines the usage of traditional CDN + WebTorrent, and they definitely have this complex design not out of the blue; others didn't really work.\n\nhttps://github.com/Novage/p2p-media-loader#how-it-works\n\nIn an ideal world, I wish it was just normal Torrent (which is at least impossible from browser engines).\n\nAnd with just WebTorrent (Torrent on top of WebRTC)—there are some WebRTC-related traps:\n\n- at least the warm-up is too slow, according to p2p-media-loader devs\n\n- due to privacy settings or/and ISPs behind certain kind of NATs, one may not have a functioning WebRTC-based peering at all (only connections through TURN, which is not supported in p2p-media-loader; because that would be an unnecessary complication since they have to use the CDN anyway).\n\nThere are more. There's no way to escape the WebTorrent tracker and use DHT due to some browser limitations, and at the same time you can't have too many of the trackers (iOS/Safari in particular may aggressively close WebSocket connections out of the blue if it decides there are too many of them, and it can be challenging to handle this properly if at all).\n\nThese are just a few things I recalled from when I was setting up vidstack player + p2p-media-loader on my website.\n\nIn two words, thing that will work in practice is (an event kind 10063 server list) of Blossom-based CDNs (at least for warm up) + p2p-media-loader (only helpful in case of multiple concurrent connections) + stable 1Gbps+ network.\n\nOther paths are known frustrating traps; it's hard to even test/debug this stuff because you can't easily simulate the identical weird NATs some ISPs have.",
"sig": "0f0b4bca6a0fb48be41d41435b9a0fc71ee59eee90604f72b3df2110c243b972c05fed577c217c5bde54cdb70565a655793a095eceac9aeb6ec4c6b1b058595f"
}