155
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 11 Feb 2026
155 points (90.6% liked)
Selfhosted
56299 readers
1085 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.
-
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!
founded 2 years ago
MODERATORS
This is so vibecoded 🤣 Nawthx
Based on what? A quick peek and I didn't see any of the stuff I expect from LLMs
Less than a 4 month commit history and one dev. Not impossible maybe, but sure is suspect.
I've built projects of the size in 5-7 months before we had LLM or ML coding tools.
With tabbed completion (Which most devs enjoy), and before full LLM code gen, 4-6 months.
With llm assistance, not vibe coding, it's possible to build projects like this in 1 to 2 months without sacrificing quality or safety. If you are an experienced engineer and have built projects like this before. A lot of these are boring, boilerplate, stuff.
So the time spent doesn't necessarily say that it's vibe coded but if this is an inexperienced engineer then it very well might be and may be full of holes and issues.
Absolutely not impossible for a skilled dev with lots of free time. This is still an Alpha after all.
Completely agree. If this is a skilled Dev who's built products like this before and you can build something like this in your afternoons and weekends in like 6 months without LLM tool assistance.
With basic assistance you can definitely cut that time down to 4 months or less easily.
And if this is a full-time project, you can probably get it out the door in 1 to 2 months with llm assistance. (Not vibe coding, two very different things)
Building the full stack of a functional real-time voice and video comms system as a lone dev is not a trivial undertaking.
Even if they put 40/wk or more into it, I'd still be impressed. Like I said, not impossible but these people are rare.
WebRTC is a thing. You don't have to build all that from scratch. It's very reasonable to piece together a lot of standard technologies to make this progress much quicker. I haven't looked into this project, so I don't know, but I know it was pretty trivial to setup a WebRTC app 10 years ago, which would appear to be a fully functioning video app.
Lolwut??? Did you check the GitHub at all?
What makes you say that?
Check the code
I took a look. Didn't seem vibe coded to me. Is there a specific area you looked at that looks vibe coded?
Here's a very simple list of issues that any Node dev would immediately say is generated and has not been cleaned up:
I mean I can keep going, but if you even glanced at this and didn't IMMEDIATELY get it, you are bad at your job.
Edit: This one is fucking hilarous
Dude, my team members put out code that's like this or worse on a regular basis that gets caught in PR review without using AI tooling...
I've supported legacy projects that of course were built without tooling that didn't exist. That are structured and written in ways that are far far worse than this.
Nothing here screams vibe coated.
Your hostility confuses me. I'm not a node dev.
I skimmed some of the server files and didn't see the normal vibe coded slop I normally see in other languages and was genuinely curious what you saw.
Thank you for your examples.
It's okay. I've got a few side projects in node and I also don't see anything too out of the ordinary here. If anything this looks more like someone's first project with some "make it work" rather than being perfect and pretty.
I don't understand the hostility. Even the bits that this guy talks about (duplicated code?) nothing looked duplicated - sure the names of the folders are the same but that's more of a naming convention problem when you have a client that needs to connect to servers (or in this case has screens and functionality to connect to servers).
And now I've probably spent more time and brainpower on this than I should have just because I was confused.
Then why if you aren't familiar would you make a comment you didn't see anything?
Do you randomly walk into other people's jobs with zero proficiency and speak to how they're doing at it?
That's it? That's why you're being such an arrogant prick?
Huh. You do you, I guess...
¯\_(ツ)_/¯
so that's not the same person you replied to. Nor am I.
This isn’t someone job tho it’s a public forum.