[FireInsight]

I am genuinely in the "target market" for a tool such as this, but having evaluated one previously I found the quality and self-hosting experience to be pretty bad, and that a proprietary freemium product was still a better experience.

I'm hesitant to even take a look at this project due to the whole "vibe coded in 3 weeks" thing, though. Hearing that says to me that this is not serious or battle-tested and might go unmaintained or such. Do you think these are valid concerns to have?

[spicyusername]

We're entering an era where the delivering of software is cheap. Basically any idea can have an MVP implemented by one or two people in just a month or two now. Very quickly the industry is learning what the next set of bottlenecks are, now that the bottleneck is no longer writing code.

Planning, design, management alignment, finding customers, integrating with other products, waiting for review, etc. Basically all the human stuff that can't be automated away.

Your comment reminds me to add building a support team to the list.

[localhoster]

Was it ever? Even before llm, writing software, or at least web clients, was as easy as it can get.

[written-beyond]

I agree, software (software startups) has always been the golden child of investors because of how cheap it is compared to hardware or any other physical good.

Good software is expensive regardless of the involvement of LLMs because you need someone to take responsibility. Large companies will save a buck because there may be fewer people needed to take said responsibility, but it's probably a marginal saving compared to the overall scheme of things.

[varispeed]

It was "easy" in the sense you could deploy 7B equivalent of a developer, who could get something sort of working eventually or you could spend a lot of money for actually getting the results from talented developers - equivalent of daily maxing out Opus 4.6.

[jcmeyrignac]

Delivering is cheap, but maintenance is expensive... if not impossible!

[holoduke]

It's not. Maintainance is easy now. We have at least 200 legacy products in various old languages. Never it has been easier to work on those since Claude came into the picture. The argument I hear about support being expensive is not true I think.

[apsurd]

Maintenance of mountains more agentic code.

The argument is the agents can maintain what the agents build. But someone has to manage the explosion in system complexity.

I just quit my job because there was top down explosion of shipping agentic code. I don't think it's going to work and I don't want my job to be maintaining someone else's 50x code output.

[KellyCriterion]

...and customer support!

[m000]

I agree. It's not like this project is disrupting an overpriced product/SaaS.

E.g. Buffer charges around $50 per year per social media account, which gives you an unlimited number of collaborating user accounts. And their single user plans are even cheaper.

I don't see how self-hosting would be a worthy investment of your time/effort in this case, unless you are in some grossly mismanaged organization where you have several devops engineers paid for doing literally nothing.

[bryanhogan]

$50 is a high price to ask, no? And I just looked it up, it's actually even more than that.

Consider having an account for each common social media platform, then multiply that for every project, that grows quickly.

[m000]

You are right. My memory failed me there. I should have done a quick lookup for the pricing.

It's $120/year/account for multi-user setup, and $60/year/account for single-user.

Which is still dirt cheap if you use social media professionally. E.g. what would $360 buy you if you try to do self-hosting? Maybe a day of work from a devops engineer to get this deployed for you?

[deaux]

I know solo bootstrappers who have 5+ accounts across platforms for one app, it's quite normal for B2C.

[sixtyj]

I see your point.

Last time I “vibe coded” something (internal) and I liked it because I couldn’t find external solution.

I admire coders who can finish their code into deliverable and usable piece.

Issue here is software abundance and ppl will start to hesitate due to absurd pile that they should evaluate.

It reminds me the statistics of ice cream global sales. People want certainty so they choose chocolate or vanilla :)

Therefore many good software projects will have a problem to find users.

[swasheck]

i think we need to encode (or refine) what we mean by “vibe code.” my original impression was that it was used to describe the process whereby someone with an idea but lacking development/engineering skills leveraged llm via an agent to create the mechanics to bring their idea to fruition. anymore it seems like if it has the hint of AI then it’s “vibe coded.”

ironically, i didn’t read the article because i come to comments now to see if its been identified as AI slop, so i don’t know which area this falls into

[dghlsakjg]

Definitely. The original vibe coding tweet is pretty explicit about “forgetting the code exists”, and “throwaway weekend projects” (https://x.com/karpathy/status/1886192184808149383)

Now however, many people just use it to mean any ai-assisted coding.

One person says “vibe coding” to mean a throwaway script to scrape some page. Others use it to mean a code reviewed app built by a team using Claude.

It is so broad as to be meaningless at this point

[theshrike79]

Some people (me included) are trying to separate Vibe Coding (no idea about code, just give me the result) from Vibe Engineering (I know how to do this, but can't be arsed to write. I also know what the result should look like)

[sixtyj]

Cool. Thus I am an ai/llm-assisted coder amateur. I don’t code for living, I know principles (or I think so) but don’t remember syntax (too old to learn new tricks :)

[63stack]

The era of sharing some small programs that you made with others to benefit from is over imo.

You can just vibe code it yourself. If your requirements are narrower (eg. you only need support for 3 networks and not 12), you will end up with something that takes less time to develop (possibly less than a day), it will have a smaller surface for problems, and it will be much better tailored to your specific needs. If you pay attention to what the LLM is doing it will also be easier to maintain or extend further.

The surface for security vulnerabilities also gets narrower, since you "only" have to trust the LLM (which is still a huge ask, but still better than LLM + 1 random person).

[ninkendo]

> The era of sharing some small programs that you made with others to benefit from is over imo. > You can just vibe code it yourself.

+1.

The password manager I use full time now is “Kenpass”, which has exactly one user: me. I have it on iOS/macOS/Linux, browser extensions, CLI and (native, no electron) UI for each, syncs with my homelab server over my wireguard tunnel, and it covers all my use cases. Took me maybe a week (a few hours total, spread around.) I feel no reason to share it with anyone, it does exactly what I need and I only need to fix the bugs I find, for myself.

We’re really living in crazy times.

> If you pay attention to what the LLM is doing it will also be easier to maintain or extend further

That's another nice part: I actually really enjoy feng-shui refactoring code to fit my tastes, and I've given the LLM's code a bunch of refactoring passes essentially "just for fun". I understand the codebase enough that sometimes I implement features myself instead of having the LLM do it, if I'm in the mood to. But I'd probably never have the time or energy to start such a project from scratch... having the initial MVP done in essentially one shot was a huge boost.

[deaux]

> I have it on iOS/macOS/Linux, browser extensions, CLI and (native, no electron) UI for each, syncs with my homelab server over my wireguard tunnel, and it covers all my use cases. Took me maybe a week (a few hours total, spread around.)

A few hours including iOS? Don't you need to go through lots of hoops even if it's only for personal use? Isn't it time-limited or something?

[ninkendo]

It does require a developer account at $100 a year, yes. But that's it: Once you have that, the app is not time-limited or anything. I can just install it to my device (wirelessly) via Xcode and I'm done.

It's probably only worth the $100/year if there are other apps you want to make for yourself though. I have other ideas for apps for my family, so I figured it's worth the cost. It sucks that I have to pay at all though, I admit.

[deaux]

That's interesting - I thought apps that didn't go through the App Store but were in "developer mode" were time-limited, but maybe I confused it with "share with family" rather than pure personal solo use.

Sounds like you wrote it in Swift(?), did it also do a good job at the autofill code? That's what I'd expect it to potentially struggle at, as it could be a rare and particularly native feature. But then the APIs should be well standardized for iOS.

Very cool and inspiring stuff!

[ninkendo]

The autofill code is actually Safari's, not the password manager. The password manager basically just needs to impmlement ASCredentialProviderViewController (https://developer.apple.com/documentation/authenticationserv...) and include the "AutoFill Credential Provider" entitlement and safari will ask if you want to sign in with Kenpass for websites and apps.

For firefox (desktop) it's a bit harder, you have to actually implement login box detection. It works like half the time, but I don't really mind much, because it's not a huge deal to just use the clipboard. Even when using 1Password I would so often find that the password autofill was so broken (or would constantly offer me to save passwords I don't want to, or for things that aren't even login boxes) that I actually actively hated it. When creating logins, I much prefer taking an explicit step to activate my password manager to do so, and when prompting for logging in, it's not a huge deal to simply copy/paste when the simple detection doesn't work.

[alasano]

> kenpass

> username "ninkendo"

Absolutely checks out.

Please share more ken related software names you use lol

[hk__2]

Fun fact: this wouldn’t work in France where "ken" is slang for "f*ck".

[flir]

Everyone needs a to-do list: kendo.

[KronisLV]

If you want to organize more work items, you might benefit from a Kenboard.

[theshrike79]

Nah, my whole Github is open. I've always "shared" what I do.

I just don't go run around different social media sites advertising my stuff. I built it for myself, if someone else likes it, they can use it.

If they want a feature they are free to suggest it, but I'm also free to ignore their wishes completely if I don't need the feature. It's an open license, they can fork it.

[ElFitz]

> The surface for security vulnerabilities also gets narrower, since you "only" have to trust the LLM (which is still a huge ask, but still better than LLM + 1 random person).

On top of which, any such vulnerabilities will be mostly low value: n different implementations, each with their own idiosyncrasies, 90% of them serving one person.

[jrm4]

My gut is -- of course these concerns are valid, but, especially with "newfangled" software projects like this, I'd genuinely be surprised to see major quality differences between "human" and "vibe-coded."

I think what I mean by "newfangled" is; this isn't a low-level C memory managed bit flipping thing; this is the sort of thing that's already built on top of layer of layer of the cruft that the web already is, for better or worse.

[bryanhogan]

I think the same way, I'd love a social media management tool, all of the ones I found were insanely expensive or not usable / had horrible usability issues. Pitching a product by telling me it's built quickly with AI does the opposite of convincing me to try it, even though I'm in the market for the solution offered.

[TrackerFF]

Lots and lots of commercial software is being vibe coded. Big difference here is that at least the OP honest about it.

[bdangubic]

I think our industry really needs to get on top of terms / names and fast. To me, “vibe coded” means “100% (or close to it) of this was written by LLM and I do not have a slightest clue about technology or hacking or anything related to this domain.” if this is the case here (or anywhere else) I am not touching it with a 10-foot pole (even with honesty of the author). something like “LLM assisted” would be a whole other thing.

[TrackerFF]

To me "vibe coding" is like Karpathy wrote in that tweet: You completely surrender to the model, accept everything, never look at the changes in code. Only feed prompts and check the resulting product.

But, of course, that's not how most programmers use - at least I'd like to think. One thing is when people with zero programming knowledge vibe code something in that fashion, but for serious (read: big) products I'd like to think that you're still forced to do some book keeping.

[flir]

I've done some personal CRUD stuff like that. Worked well - I fixed bugs as I found them, only hit one thing it couldn't do (I find codex weak at front-end stuff generally).

Would never publish it though, or approach paid work like that.

[kordlessagain]

I have a clue, a big one, and do 100% vibe coding. Stop splitting hairs.

[bdangubic]

if you had a clue you would not be doing 100% vibe coding :)

[baq]

You can vibe code minor fixes to some annoyances including the clanker managing the whole fork/pull request flow if you want to contribute back for $20/mo on codex or claude (though $20 is the free trial tier there, codex is nearly so since last week but should be good enough... for now).

[pablogiuffrida]

i did something similar, and i agree that 3 weeks sounds like a tight timeframe. You need to test what "vibe coding" delivers VERY thoroughly.

It can be done though. And i say it as a developer for 20 years now.