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!

  • Dr. Wesker
    link
    fedilink
    English
    arrow-up
    3
    ·
    16 minutes ago

    Sounds like a security risk with no discernible advantage, for the end user.