cross-posted from: https://scribe.disroot.org/post/12494755
No paywalls, no invites, and even no accounts required. However, you’ll have to read some documentation and set up your system to join a certain overlay P2P network where that mod is hosted. So a link to this mod is likely to look like that: http://[201:26a2:981f:768a:dd52:5129:f038:77a9]/ or http://127.0.0.1:43110/134coUQAQU9EFfGdLiyFcSK854XvDgtkfy/. Would you reject it immediately, or you might give it a try?
Why do I even overthinking like that, you ask? Well...
Aren’t we all in Fediverse seeking self-sovereignty in one way or another, or at least wanting to reduce our dependence on 3rdparty vendors? So do I. I started making mods fairly recently, and the distribution issue popped up immediately. Good thing admins of my instance runs Nextcloud as well! However, I still would like to distribute my mods via a purposefully-built P2P solution (which doesn’t exists yet), or, more realistically, share them via either my own server or a general-purpose P2P network. Or both.
The best way to do any of these involves some additional software on both sending and receiving ends, which means I have to ask my audience (which is barely there yet) to install and run this software, as briefly described above.
And I really don’t have confidence to ask for it. So I would like to gather some opinions beforehand. If even Fediverse users aren’t particularly enthusiastic about this idea, I’ll probably have to stick with more grounded methods. Hope you don’t mind!
Edit: Changed the title to better reflect the main point.


BitTorrent can also be an option, but it can only cover a fraction of what I’d like to have. The reason why I’m asking about some exotic P2P networks instead of well-known BitTorrent, is because they seem to be the least twisted way to have the entire mod sharing pipeline at once within a single solution, including web pages with descriptions, screenshots, mod files itself and so on. If I use BitTorrent, I still have to share these pages elsewhere.
And I’d like the entire pipeline to be self-sovereign, without strict dependence on any third-party service providers… and free of charge.
Is that makes sense?
So just host a webpage with your torrent link on it? You are not going to get adoption for whatever it is you’re proposing.
And that’s where the fun part begins! To host a webpage, you need to obtain a public IP address (or use something like Cloudflare Zero Trust for reverse-proxying) and a valid domain name. And both must be working together and (in my case) be free of charge. Maybe you know a DDNS provider that allows you to set a
CNAMErecord for its free domains? :D…Realistically speaking, I’ll likely end up taking this route, but there’s SO much more hassle in comparison to a self-sustaining P2P solution.