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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post.
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 made the mistake of installing Starling recently, not realizing how it was made. I contributed a PR to it, wrote a few issues describing some showstopping bugs, and since then there's been absolutely no activity from the creator.
That's fine, they are under no obligation to work for free. But I wouldn't have installed it if I knew it was abandonware.
Are there any obvious signs of it being vibe coded that I'm missing?
In my experience, projects not being very active, especially small ones by a single person, isn't anything new that has much to do with LLMs, it was always that way for hobby projects. And it was inactive for only about a month now, with the author replying within one day before that. I have a few hobby projects myself and don't reserve time every month to work on them or check on their repos.
If you have access to their git, watch out for the commit history. Check how much code each commit is introducing and/or editing and how fast they are, and how many times these big commits happen.
If you see a project with big commits in very short interval of times, it’s a sign that it was vibe coded
No obvious signs, nope. It wasn't until I started using it in earnest that I got suspicious and then when trying to work on the code it became very clear.
This in my experience is the hallmark of a vibe coded project. Individual pieces of code can be perfectly fine, but when you zoom out into an overall structure things get weird. Design patterns changing, same/similar problems solved in different, sometimes conflicting ways.
Been working on a project like that at work. Initially I enjoyed the change of pace, but as I realised that there's no coherence at all in the project structure my joy turned into frustration.
To me, the most frustrating thing is that you can't ask someone why something is done in a particular way, because no decision was ever made because no one was there to make a decision. Things just happened.
How's it made?
Seems like your PR was merged by the creator? If you are mad that the creator isn't doing anything with THEIR OWN project, fork it and fix it yourself.. No need to get pissy and make a full complaint post in here about it.
It doesn't sound like OP is mad at the creator, but annoyed at the increased number of projects that are abandoned
It's hard to judge the longevity of a project, and LLMs can make a project look more stable and professional than it is. It's fair to feel annoyed if you mess up that call and move your workflow to something that gets abandoned.
No one got "mad" or "pissy" or filed a complaint. I feel they they were very explicit that it was not a complaint.
Disagreed. You should blast and air everyone's embarassing trash as loud as possible so no one misses it.