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.
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
I both love and hate this. I love to see IRC getting some love and these features are massive QoL improvements. I say this as a regular IRC user. On the other hand though, no touch da fishy.
They do maintain the simplicity of the line oriented protocol, so I'm fine with that. :)
That's the strongest point of IRC, IMO, and why it's kept so simple : every instruction is a plain text line, period. It makes it incredibly simple to build on top of it. You don't need to introduce a dependency to a project that probably will be abandonned in a few years, at which point you'll have to rewrite your codebase to use an other dependency, for a few years. You just open a TCP connection, you read lines from the socket and write lines to it, each line is its own instruction structured in well known fields, and that's it. It's so simple!
As long as IRCv3 sticks to that, they have my blessing. :)