this post was submitted on 18 Mar 2026
18 points (87.5% liked)
Programming
26105 readers
1001 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 !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The main problem here is persistance. Most users are on machines that get turned off. I could kinda see it for chat. If you think about walkie talkies people on on or not. A chat where each instance was a user would be like that. You get on and participate or not. CB's even have channels yeah.
This! It only works if you have a server that's online 24/7. Can be a VPS in a data centre, can be some Raspberry Pi running at your home with a DNS name pointing to it.
I did not mean to run locally. Every user has to deploy somewhere (like Hetzner) with public domain, tls, etc. Deployment should be simplified with a single command. But still the user has to create an account, buy a domain and needs to be somewhat familiar with command line.
Sounds like a good idea if you want to have around 5 active users.
Sorry for the sarcasm but I don't like the idea that only people privileged with a VPS can join.
No worries :) it is very likely true. Alternatively I could think of a managed option where each user has an instance in a separate container with separate sqlite database and with different subdomain.