A 13 HOUR OLD repo? no thanks

figassis 4 hours ago | parent | next [-]

I don’t get this. So today he can build the experience he wants with little effort (he likely spent lots of tokens). You made no judgement in the quality or on his experience, only on the age of the repo. Why exactly is that?

I get there will be a lot of crapware, but you’re hackers no? Why all the gatekeeping even amongst yourselves? How much time did the openclaw guy take to built it? A weekend?

Sure, you could say “no thanks”. But all the labs certainly thought it was useful enough to replicate. And yes, it was, still is an insecure mess littered with bugs, but why are we all so repulsed?

It’s a genuine need. I build my own version of this, also on go, haven’t shared bc I am not sure how legal it is to distribute, but I have been using it for months and definitely beats running 6+ apps that keep breaking. I run one binary + jellyfin, never going back.

▲

vekntksijdhric 3 hours ago | parent [-]

The problem is not the vibecoding, it is the release of a public facing internet app that is not a day old, hence it is impossible to know if it has security issues. He is supposedly a security engineer and he RELEASES a repo with less than a day old? how do you know it is secure? Again, this is something that will interact with the open internet.

Gatekeeping would be "do not write vibecoded apps for yourself", which is not the case here, this is releasing code for the public in an irresponsible manner.

	▲	Oxodao 3 hours ago \| parent \| next [-]
		Also I do not want to rely on an app that can vanish any day. Established app are way less suceptible to that.
	▲	hatsix 2 hours ago \| parent \| prev \| next [-]
		I mean, every repo was 13 hours at some point. can't hardly get security updates unless others can see and review it. I mean, I feel you... there's no way I'm running it when it's this new... I'll let others spend their tokens probing it and check it out in a month... no shade in the dude for releasing it, but anyone who has it running right now inside their network... I hope nothing bad happens.
	▲	xprnio 3 hours ago \| parent \| prev [-]
		Good thing it’s open source, so the user can verify the code themselves.

▲

andrew_eu 40 minutes ago | parent | prev | next [-]

What stands out to me isn't only that the repo was made less than 20 hours ago, but that they've released from 1.0.0 to 1.0.10 since then.

But at the same time the PR numbering is much older, with 1.0.10 coming from #197. It makes me think the repository was private for some time and then made public recently. But still -- 10 releases in a few hours isn't a stability signal. Especially when one of the advertising points is to simplify the update cycle from all the "arr"s.

▲

hsuduebc2 4 hours ago | parent | prev | next [-]

tiresome

▲

mlnj 4 hours ago | parent | prev [-]

Perhaps you will wait for the dry-aged repo.

I believe things will be from now on. People see a gap in the offerings out there and they just whip it up. There will be a certain amount of stability that the LLMs will add by default to all of them and that's it. If you are interested, go ahead and use it.

	▲	vekntksijdhric 3 hours ago \| parent [-]
		I create my own vibecoded apps for my own use, that is not the problem. releasing them for others (who might not know this hasn't been tested) is irresponsible.