this post was submitted on 13 Feb 2025
152 points (99.4% liked)

Programming

18314 readers
547 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]



founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 6 points 1 week ago* (last edited 1 week ago) (1 children)

Traditional server-based self-hosting will have lower average uptime, will be easier to attack, and will have a much higher chance of disappearing out of nowhere (bus factor event, or for any other reason).

A decentralized or distributed solution would make more sense as a suggestion here. Radicale (this one) is such an effort I'm aware of, although I never tried it myself or take a look at its architecture.

[โ€“] [email protected] 2 points 1 week ago

Traditional server-based self-hosting will have lower average uptime, will be easier to attack, and will have a much higher chance of disappearing out of nowhere (bus factor event, or for any other reason).

It's not a single point of failure at least but if your particular project is targeted then yeah. I was thinking more about using it for private repos, where it isn't public at all but that's a separate case.