Truly awful to have decentralized freedom.
The other advantage is that NOSTR doesn't necessarily run on the internet only. Things like LoRa and radio waves are within reach and even harder for eavesdropping. Not that I would care about protests nor governments in general, my typical focus is communication when electricity/internet are gone.
Bit torrent is a superior way to move data around (as compared with http downloads). But its early associations appear to have forever tainted it against widespread adoption.
Others peer to peer sharing platforms got much more popular despite mainstream news about them like LimeWire and eMule
That said, I don't think piracy is to blame here, but more the murky nature of copyright in general, with BitTorrent you automatically become redistributor of everything you download and that's just a huge liability and privacy risk that I can easily see browser developers wanting to avoid.
Also browser developers have gotten lazy, they couldn't even find the resources to keep FTP alive, so I doubt BitTorrent would have survived for long even if they tried adding it.
I don't think I'd even call it that. FTP had one purpose: it was an early protocol for remotely managing files. It never had any intent to support dynamically generated or otherwise "virtual" content (as supported by e.g. CGI scripts and mod_rewrite in Apache), and I don't think anyone has ever made a serious attempt to implement that. There's no practical use case for it.
Even as a file management protocol, though, FTP sucks. Its connection management is primitive in the extreme - one TCP connection per transfer - and that ruins performance for transfers involving many files, and is difficult to pass through firewalls and load balancers. FTPS encryption is an afterthought, and makes small-file performance even worse (as each connection requires separate TLS negotiation). There's no standard format for directory listings, just ad-hoc parsing of "ls -l" output. Support for modern filesystem features like extended attributes is largely nonexistent. Need I continue? :)
Hard to get the full context, it was before my time: my beard may be grey now, but I'm not that old.
But you should use SFTP instead. This is SSH's replacement for FTP. It's not the same as FTPS which is useless.
We don't have to keep old protocols that offer nothing alive. Maybe a couple of clients and servers to demonstrate with, but it's a museum piece, not useful code. That's not an insult - museums are important. But we don't run Network Control Protocol (IPv1) on the internet, either.
I proposed bittorrent as the solution and the sysadmin lost his mind.
Without the piracy stigma, I think we'd just have integrtated it into email clients. The user doesn't need to know that the "attachment" is actually a torrent file, they should just "download" it and end up with a reliable copy of what was sent.