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
Could you expand? How aren't they handling it well?
The biggest issues that have come up so far are moderation and database optimization. The moderation issue is significant enough that large instances have considered shutting down, but the database optimization thing is what really drives me crazy. It is absurdly expensive for hosts considering we only have 35k MAU (just one of our midsized instances should be able to host the whole userbase for the cost they currently pay) and it has been largely deprioritized to the point that contributors who have tried to fix it have been told off.
It’s one thing if it’s just a couple of devs working on the project and trying their best, it’s an entirely different thing when a couple of devs are shutting out large numbers of contributors (frequently subject matter experts which they desperately need at this point) over relatively trivial issues. At this point a significant number of users have been lost because the devs have been largely unable to capitalize on previous waves on growth due to slow development.
Not to mention things like authorized fetch, which if fixed would ensure Lemmy/Mastodon interoperability and would effectively make Lemmy the go to place for groups on the fediverse. This would constitute a huge boost in engagement from the broader fediverse.
Because of all this Lemmy has an awful reputation even among the rest of the fediverse and particularly among people who have tried to contribute. A fork would probably be a significant improvement as far as brand perception goes.
Exhibit 1: https://programming.dev/post/5180682
Definitely seen arguments on bugzilla, should disqualify Mozilla too.
That post seems like an overreaction. Which makes me think that the linked GitHub issue is just the straw that broke the patience of the developer that has moved on. Which is fair, but their action to post an emotional and negative public announcement is as immature as the thing they're complaining about.
I am a dev, but not a Rust dev.
Rust, Go, and C# look like the future to me. Everyone is moving to strongly typed, explicitly typed languages for a reason.
Rust is as fast as it gets, and much much safer and easier than C or C++ at the cost of slightly odder syntax than higher level languages.
Microsoft has done great things with C# and open source and multi-platforming. It's the easiest, quickest, safest way to develop business applications. The performance is really pretty good until you compare it to Rust.
Go is between the two, but probably a little closer to Rust.
Other languages will stick around the same way Fortran has still been in use despite being deprecated for 30 years. But really nobody should be developing anything new in PHP.
Lol, this was what I was going to link to
Yeah, that's a major fuckup from Snowe.