Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
These other responses are annoying. This looks really cool, and I hope that it works well for you and your friends! We definitely need good discord alternatives ASAP, and more options are better imo.
One cool feature would be some sort of official support for interop/bridging to other services. That might help to boost adoption and would make the "why not just contribute to Y" people be quiet.
Heh, I've been around a while. I expect people to pick it apart so they can get that kick out of being right or whatever.
It does what I need, thought other people might have found a use for it. I'm always happy for constructive criticism on my code or feature suggestions but people crying because I used Claude to give me a template for the readme can kick stones.
I'm sort of reluctant to add bridging mechanics for a couple of reasons. I don't think my coding ability is up to it and it's not something I'm really interested in or a goal for the project. I set out to make something that can be spun up pretty quickly for a group of people to have voice/text/screenshare when gaming. I never intended for it to be federated or hook into all sorts of services, just a self contained service for mostly private comms that doesn't report back all your activity to Palantir or advertisers.
Sensible, limiting scope and knowing your limits are wisdoms all too many lack. Having something that fills the text/sound/vidya needs and is easy to spin up will find uses, doesn't need to do everything.
To the end of being easy to spin up, which is likely to attract other developers in time if that's something you'd like, consider wrapping it up in a docker container. It's not that hard, basically follow your own instructions in a special docker build format.
Thank you for your feedback.
Honestly, there are a few more features I want to add like markdown/gif support, image/video uploads and user settings (push to talk, volume leveling, etc. are sorely needed) but outside of that and cleaning up bits of the UI, I'm terrified of creating an unwieldy codebase. I don't want something that requires constant tweaks and updates, just something that focuses on those core features and nails them down. You can just install it and pretty much forget about it.
Docker is definitely on my list, I was going to have a chat with one of my mates that lives in docker land to see if he could give me a hand setting it up properly. I've used docker before but mostly in hacky ways rather than something I'd be comfortable deploying to other people.
I'd be happy to contribute the docker stuff if you want as well. I do it for fun and profit, and I'm gonna be awake for the next three months straight with a newborn so I'd absolutely welcome the opportunity to do something other than feed this poor child.
My only hope is that you include one weird nonstandard Markdown feature so you can come up with a name for your yet-another-almost-markdown-but-not-quite-standard-markdown version. Just because. :)
I think we can all agree coming up with names is not one of my key skills. Not following standards, however, is. Hold my beer, I got this.
Sounds good.