187
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 24 Apr 2024
187 points (98.4% liked)
Selfhosted
39937 readers
353 users here now
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!
founded 1 year ago
MODERATORS
To be fair, last update isn’t the end all be all. If the project is in a stable place, and there haven’t been any breaking changes, there’s just no need to update.
On the one hand, sure. On the other hand, if there hasn't been even a tiny bug fix or feature update in that long it calls into question (at least for me) whether when there is inevitably a breaking change, security issue with a library, whatever - that it will be addressed. If I don't have some level of confidence in that, I'd rather not rely on the tool.
This kind of concern could be handled by contacting the developer or engaging with the community around the tool to see what the project status is, and why it isn't being updated.