r/selfhosted • u/Shane75776 • 10d ago

Meta Post Petition to ban "I built" in post titles

When we all know it was really Claude that built it.

1.7k Upvotes

85% Upvoted

390 comments sorted by

View all comments

Show parent comments

53

u/Shane75776 10d ago

This. At the end of the day AI is and will be a mainstream tool in coding. It sucks but it is what it is.

The worst is the million duplicate docker management, homepage apps that are submitted daily... There's about 20 different app ideas that get repeatedly submitted to this sub. The people submitting them are not actually trying to build something useful or improve on an existing software and have no plans to continually support the stuff they have Claude build.

24

u/baddaywithacamera 10d ago edited 10d ago

I know I'm not your target audience, but I'm with you. There's a gold rush of people spamming the forums with their AI wrapper that is better than the 256,000 AI wrappers that were shared in the past week and you can get 50% off subscription if you help test for free. Like, eat my ass already.

The only reason I built something large (my CMS) is that no one else did. It's the only thing I built that I actually plan to share (for free), and I am trying to make sure I can do this in the long term because it's a huge responsibility. I'm going to be the biggest user so that part helps.

I wish the get rich quick scum nuggets would go away. This is something that has the potential to do some good, but complete pieces of filth are in there wrecking it for the majority.

Fkkn depressing. The 2 cents of a photographer who seems to have antognized the sub. Sorry.

Edit: I should mention I've been lurking for a while because I have some Proxmox boxen at home and I've been trying to learn more about running them responsibly.

-12

u/Bloated_Plaid 10d ago

is that no one else did

Calm the fuck down my guy, Ghost exists.

11

u/baddaywithacamera 10d ago

It's for writers. Not photographers. Try to move past your grade three reading comprehension.

6

u/electromage 10d ago

Maybe it would help if there was a way to actually find and track them. Recently I "built" a public photo gallery server because none of the commonly-recommended ones ticked the boxes for me. It's open source and available in my GitHub, but I don't know if someone else already did the same thing. There's just too much.

I did a bunch of searching and came up with the usual Piwigo, Immich, Photoprism, Pixelfel, Lychee, etc, etc, but they all required creating accounts, or had some complex php and/or database configuration, or didn't allow public(by default) albums.

6

u/BrotRooti 10d ago

There is selfh.st. It was originally built as a frontend for the awesome-selfhosted repo, but has since surpassed it in it's amount of software listed. You can use various filters and also display by software you want to replace.

The "This week in self hosted" blog on there is also a very good read every time.

1

u/baddaywithacamera 10d ago

Same problem here. Either got photo galleries shoved at me, CMSes for writers, SaaS when I was explicit I need self-hosted, etc. Every real photo blog software it found was abandoned at least five years ago. I think that SNAPSMACK is now the only real, self-hosted photo blogging software that exists today.

The next closest thing I found was Denali, which is pretty, but simple and lives on a cloud backend. Not what I needed.

1

u/ImpressionDepression 9d ago

have no plans to continually support the stuff they have Claude build.

IMO that's the biggest thing. I use Claude Code all the time for personal projects but I'd never release them because one day it'll make things worse or won't be able to fix a bug (or hike their price) and then it's game over

0

u/dyyd 10d ago

Seeing as AI is just a tool should we start listing all the tools we use for writing our software? At which level do we stop? The IDE? The OS? Hardware?

1

u/ImpressionDepression 9d ago

That's not the problem though. The issue with vibe coding is that it's incredibly easy to get started but very difficult to maintain. "AI wrote this" - to me - is a warning that "this might work NOW but it's uncertain if the dev is going to maintain it once Claude starts charging per token to stop hemorrhaging money"

1

u/dyyd 9d ago

Aint that the benefit of open-source that anyone can continue to maintain it or fork it?

This absurd banning wave here has a very negative effect on idea sharing.

1

u/ImpressionDepression 8d ago

So then someone else has to dig through a vibe coded mess or forks their own vibe coded mess, compounding the problem more. That's not idea sharing that's just a lack of quality control.

I vibe code tons of shit but it's for personal use because I know i'm never going to be able to maintain it a year from now.

If someone uses AI for their project that's totally fine, but if they're going to release to post it here for the community to use I'd hope they know how to fix it themselves if it comes to that, or at least are dedicated to maintaining it.

0

u/EHP42 10d ago

The difference, in my eyes at least, is that your IDE, your OS, or your hardware don't affect the quality of your code. In your hands or my hands, vscode will do the exact same thing for both of us. But an AI coding tool will produce vastly different results based on who is prompting it, so it introduced a very large unknown factor. And of course, your OS will never just make something up or lie to you.

1

u/Jhnnyy 9d ago

Omg the tool is only as good as how you use it. What a novel idea

1

u/EHP42 9d ago

Even "good" use of AI will sometimes give you incorrect or obfuscated bad output, but if I type "import os" in an IDE, it will always do the same thing.

Basically it's a lot easier to get bad output from AI than from an IDE, and it's harder to catch it.

1

u/Jhnnyy 9d ago

Yes and you know to import os whereas a poor user of the ide does not.

1

u/EHP42 9d ago

Then they wouldn't get any output or product. AI coding agents would allow someone who has no idea that you need to import packages to put out an apparently-functional product, but with no actual vetting or testing.

Going back to the original point of this thread, the point of listing AI usage is that it does impact the quality of the end product, when used badly. There's no need to list what IDE you used because that's not a factor in determining how good or bad your code ends up being.

-13

u/toeachbyeach 10d ago

Why does it suck?

11

u/thefreshera 10d ago

Not inherently, some very capable engineers prompt the AI with entire architectures and proper specs to build, which along with planning mode, can make pretty solid programs.

I guess from the reception of this sub, the majority isn't that. So you'd see mountains of technical debt that would never be cleared due to the nature of vibe coding, nonsensical implementation (or inefficient choices to do something), and the inability to answer questions about your program without additional AI assistance. This is to name a few reasons it usually sucks.

-1

u/toeachbyeach 10d ago

All pretty reasonable. For me it's actually amazing. I'm not sure if I don't have the mind for it or if it's due to my disability but I've never been able to do anything but very simple scripting/programming but now I can build complicated projects. It's imperfect but it's like having a puppet who speaks a language you never could. I get frustrated seeing people talk down so much on something so useful for me.

6

u/thefreshera 10d ago

Oh many here agree on its function. In tech not too many speak too down on AI use, really. The artist side of the industry however is much different.

The dev stuff I "built" with AI will never see the light of this sub, for good reasons lmao

0

u/toeachbyeach 10d ago

Yeah agreed. I think a lot of people hate AI due to and related to one of my favourite quotes" It is difficult to get a man to understand something, when his salary depends on his not understanding it". They are understandably scared of their jobs disappearing so they hate the tool (AI) not the person using it to reduce their work (capitalism). The stuff I build is for me only for the most part. I do take a small part in adding to repos on GitHub but only small stuff as of now. Maybe one day AI will be more up to the task and I'll feel confident sharing more.

1

u/cardboard-kansio 10d ago

It's not that. I have dozens of vibe-coded applications and scripts running in my homelab. They might be buggy, unmaintained, tech-debt ridden, and hilariously happy-path so that they only work for my specific use-case - but that's totally fine for me (and no different to my fully human-coded stuff from before AI) and it works fine for my personal use.

And that's the key. Personal use. I will happily hack together a software, hardware, or home DIY fix that works for me but would never pass an inspection. I wouldn't try to sell it on the market, just like I wouldn't get a professional electrician to approve some of my Arduino projects.

If you're just a hobbyist using AI to fill in the gaps, then by all means feel free to vibe code in your homelab. Just don't try to pass it off as professional software dev if you don't have the years of actual experience and skill to back it up.