this post was submitted on 14 Oct 2025
        
      
      11 points (92.3% liked)
      Open Source
    41729 readers
  
      
      296 users here now
      All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
        founded 6 years ago
      
      MODERATORS
      
    you are viewing a single comment's thread
view the rest of the comments
    view the rest of the comments
I'd say self-hosting is done for control over your data, not security. A typical end user will not know how to self-host, how to pick a privacy-respecting VPN, let alone secure their system. If your aim is to get to that same level of security, then I feel like the current direction is flawed, at least from what I took away from the readme.
Or, in other words, "self-hosting is more secure given the option" sounds kind of like "writing your own software is more secure".
it certainly gives more control over your own data, but (if you know what youre doing) from a cybersec perspective, it can help to reduce the "attack surface". the current direction is to allow users the flexibility from a version provided from me hosted on aws s3 or host it yourself from open source code. additionally, you can host your own peerjs-server as used for brokering connections... by default it connects to the public instance of peerjs-server (so its easier for users to get startedt).
im aiming for flexibility in "getting started" from ready-to-go to selfhosting. it all depends on if a user knows what theyre doing.