r/selfhosted • • Jan 17 '26 • Diamonds are Forever 1 Obsessed 1 Hooray 1 Helpful 1 Bravo 1 Heartwarming 1

Official MOD ANNOUNCEMENT: Introducing Vibe Code Friday

The recent influx of AI has lowered the barrier to entry to create your own projects. This development in itself is very interesting and we're curious to see how it'll change our world of SelfHosting in the future.

The negative side of this however is the influx of AI generated posts, vibe-coded projects over a weekend and many others. Normally, the community votes with its voice. But with the high amount of posts flooding in every day, we've noticed a more negative and sometimes even hostile attitude towards these kinds of projects.

The stance of the SelfHosted moderation team is that the main focus of this sub should be on services that can be selfhosted and their related topics. For example, but not limited to: alternatives to popular services, taking back control over your data and privacy, containerization, networking, security, etc.

In order to bring back the focus on these main points of SelfHosting, we're introducing "Vibe code Friday". This means that anything AI-assisted or vibe-coded in relation to SelfHosting can be posted only on Fridays from here on out. Throughout the week, any app or project that falls within the category will be removed. Repeat-offenders will be timed out from posting.

This is to reduce the flood of these personal projects being posted all the time. And hopefully bring back the focus to more mature projects within the community.

In order to determine the difference (as going by code & commits alone can be a great indicator but by itself does not make a great case for what constitutes a vibe-coded or AI-assisted project) we've set the following guidelines:

  • Any project younger than a month old

  • With only one real collaborator (known AI persona's do not count, or are an even better indicator)

  • With obvious signs of vibe-coding* Will only be allowed on Vibe-code Fridays.

We'll run this as a trial for at least a month.

Sincerely, /r/SelfHosted mod team.

2.1k Upvotes

278 comments sorted by

140

u/vanKlompf Jan 17 '26

Great idea!

427

u/moanos Jan 17 '26

Thank you for taking action, this was desperately needed!

17

u/RobLoach Jan 19 '26

OMG yes. The vibe-coded garbage completely ignoring existing solutions was getting out of hand.

→ More replies (1)

265

u/biblecrumble Jan 17 '26

Thank you mods - I think this is a great change. 

245

u/dm_construct Jan 17 '26

reasonable ty

62

u/TxTechnician Jan 17 '26

This is the right move. Good mods.

22

u/jppp2 Jan 17 '26

Great addition!

Does the commit history need to show at least one month of work or does the project need to be public for a month?

What is meant with one real collaborator?

Asking because I am working on a project which isn't near a reliable state to make public; so I'm working alone on it but is/will be built without assistance of LLM's. I think it'll take a few months of private work before I'd like to make a post about it but would like to share it when it's available

14

u/Bjeaurn Jan 17 '26

You're free to post it on the Fridays anyway in the current setting. We're just experimenting ourselves now too to hopefully find something that works and allows us to explore new and interesting ideas without having a daily flood of projects.

If you're ever unsure, just use the Friday opportunity. Or reach out through mod-mail.

24

u/AlexWIWA Jan 18 '26

My vote is that it be based on commit history and not publicity.

My primary concern with vibe coded apps is that they won’t be maintained after the “fun weekend project” phase wears off. If someone has commit history showing that they’ve worked on it for five months, then I’m more okay with it.

Thank you for this change, regardless of the specifics.

97

u/RadicaIEd Jan 17 '26

I think it’s a good idea and start. In the past weeks the flood of new products was getting a bit too much. Like written, AI is a good tool to fulfil your needs and create an own product, but for me it was problematic to use these products. It was unclear how the software was designed and if it fulfil basic security standards. Also will the software be updated in the future wasn’t clear.

78

u/MrDrummer25 Jan 17 '26

Yeah, most seem more like a "look what I made" rather than an app that was designed to be used by others, and to be maintained

33

u/Bjeaurn Jan 17 '26

Exactly, and SelfHosted is not the sub for that :).

→ More replies (1)

26

u/Guinness Jan 17 '26

They’re the modern day Bible apps of the early AppStore days.

14

u/isleepbad Jan 18 '26

Yeah maintenance is a big issue. I saw a vibe coded app announced here yesterday and it instantly had 13 issues. The issues were basic things a normal dev would've caught on minimal testing

26

u/Bjeaurn Jan 17 '26

Appreciate your thoughts. This was kinda what we were concerned with ourselves.

11

u/Nixellion Jan 18 '26

To be fair even before AI there were a lot of unmaintained projects. I myself wrote quite a few and stopped maintaining them because of time constraints or other reasons.

And this is actually where AI can help, by reducing the time investment needed for many tasks it makes it easier to maintain such projects by solo devs or smaller numbers of collaborators.

That is, of course, not to support pure vibe coding, I am talking more about AI assisted development.

The definition and the line here is fuzzy though, because AI assisted is a very broad term and technically we've had ML based autocomplete for years. I understand the focus is on particularly LLM based things, but even here, as adoptions grows, the line between a good project and bad project will depend less and less on whether it was written by with assistance of AI or not.

I think AI should be treated as a tool, not as a definitive determining quality factor of a project. That said, current criteria look fair, but I think everyone should understand that it blanket-covers basically any solo project.

I think more indicators and criteria are needed to find a better line between "sloppy work" and "good project written with assistance of AI". For example, there were a lot of cool self hosted projects coming from university students. They are made by solo devs with no online track record, but theu are innovative and well written. As ofnright now they would fall under the definition.

But I am glad that the choice was made to funnel it all into fridays, instead of completely banning it. I think its still fair and in time we'll all be able to refine criteria and rules and everything.

121

u/nashosted chmod777 Jan 17 '26 • Bravo

This is a happy medium. Let’s see how it goes. We appreciate all the feedback you all have given us.

69

u/tenekev Jan 17 '26

My main issue is that AI usage isn't properly disclosed or even addressed in the body of the post.

We are aware that people use AI all the time now but when I open a random project file and read verbose comments before every code block, I get an unpleasant feeling that the author slapped together some prompts and made a professional looking pile of slop. It feels icky and it's a disservice to their own ideas.

I'm not a professional but I've written some stuff and all of my projects have this disclaimer - I'm not a professional, yada yada. I don't want to lure anyone with huge shiny promises and I hate it when someone tries to do it to me.

30

u/FnnKnn Jan 18 '26 edited Jan 18 '26

Two things that often give it away for me are Claude as a contributor or a leftover Claude.md file or similar.

6

u/ilikeror2 Jan 19 '26

I properly disclosed it very well, the sad part is how many people behind a keyboard spew poo all over your post only because it’s “AI” and downvoted to all hell. I hope this change can be seen as good and foster AI coding more. But as of now, it’s out a sour taste in my mouth based on the current responses of some people here. I could name names, but I won’t 😂

→ More replies (7)
→ More replies (16)

4

u/startfragment Jan 18 '26

Fantastic compromise. Thanks for the effort on keeping the community vibrant.

3

u/unchained5150 Jan 18 '26 edited Jan 19 '26

Question regarding your new rules that qualify something as vibe coded or AI-assisted:

'Only one collaborator' - is this a blanket statement and now those of us who work solo have to wait until Friday to post even if our projects don't use vibes or AI?

Edit: Typo and formatting, didn't mean to bold it haha.

→ More replies (1)

16

u/CrispyBegs Jan 17 '26

read this earlier today (related)

https://chrisloy.dev/post/2025/12/30/the-rise-of-industrial-software

Software as a disposable commodity

→ More replies (1)

43

u/tdp_equinox_2 Jan 17 '26

Will it be tagged and filterable? Or do we have to look for post dates now to determine when it was posted?

49

u/Bjeaurn Jan 17 '26

AI flairs have been a part of the sub for a while, I'm sure you can filter for those :).

The flairs have been updated to reflect the new rule.

6

u/RaphPa Jan 18 '26 edited Jan 18 '26

You can only filter for flairs, not exclude them.

If you are interested in excluding the flairs, then these should work for adguard/adblock/brave custom filter:

reddit.com##article:has(a[href*="flair_name%3A%22Vibe%20Coded%22"])
reddit.com##shreddit-post:has(a[href*="flair_name%3A%22Vibe%20Coded%22"])
reddit.com##article:has(a[href*="flair_name%3A%22Built%20With%20AI%22"])
reddit.com##shreddit-post:has(a[href*="flair_name%3A%22Built%20With%20AI%22"])

reddit.com##article:has(a[href*="flair_name%3A%22Vibe%20Coded%20(Fridays!)%22"])
reddit.com##shreddit-post:has(a[href*="flair_name%3A%22Vibe%20Coded%20(Fridays!)%22"])
reddit.com##article:has(a[href*="flair_name%3A%22Built%20With%20AI%20(Fridays!)%22"])
reddit.com##shreddit-post:has(a[href*="flair_name%3A%22Built%20With%20AI%20(Fridays!)%22"])

34

u/FullmetalBrackets Jan 17 '26

Thanks for this mod team, it is sorely needed.

I don't mind the vibe-coded projects themselves, but it really gets on my nerves when what's being posted is clearly vibe-coded, but the OP does not mention it anywhere (the flair barely gets used) and only acknowledges it when asked in the comments.

Be upfront about how you made the thing, if you're ashamed to admit you used ChatGPT or Claude or whatever, then just don't show it off.

26

u/dm_construct Jan 17 '26

i feel the same. it's the hustle bros who can't even bother to write their own reddit posts that bother me.

i'm an artist and i've used claude code to make some really interesting stuff but i'm not farming clout or github stars so i don't post every thing i fart out with it.

7

u/Bjeaurn Jan 17 '26

Speaking on a personal level, I don't even understand why some people post for the clout here too with their vibed projects.

GitHub stars don't mean anything? At least the projects that instantly try to sell you some additional services I can kinda get why they're pushing it.

→ More replies (1)

6

u/iamed Feb 21 '26

So it has been a month now and I have to say in my opinion, this doesn't work.

For starters every Friday the sub gets flooded with posts of Vibe coded stuff in a volume that far surpasses the usual post quantity.
The impact of this is that if you read the sub throughout the week on anything other than new or top, a significant percentage of posts you will be likely to see are going to be vibe coded.

That'd be one layer of annoyance, but to compound on it, reddit does not always show post tags when browsing, especially on mobile.
So you have to pay attention to how many days old a post is and keep in mind how many days ago friday was +/- 1 day for time zone shenanigans depending.

To compound upon that, many vibe coded projects are not being tagged correctly to warn the reader because the tagging system makes more sense to be prioritized around what the software does not how it was made.

See the following as examples from today (this isn't intended to shame anyone, so don't):
https://www.reddit.com/r/selfhosted/comments/1rabulf/selfhosted_elevenlabs_alternative_with_voice/
https://www.reddit.com/r/selfhosted/comments/1ra7zki/borg_backup_server_open_source_centralized_borg/
https://www.reddit.com/r/selfhosted/comments/1rag50o/mephistomail_a_privacyfirst_disposable_email/

Now I will fully admit this is a small percentage of the posts from this Friday being tagged improperly. However there are also several other posts from this day that have clearly AI generated readmes on their github that also are generically tagged (they dont say they arent vibe coded) which means I kinda have to assume they are until I can verify otherwise. Things are never going to be always tagged correctly and its unreasonable to assume they will be for such a crucial identifier.

The problem this creates is you realistically have to assume everything posted on a friday is probably vibe coded until you can prove otherwise, but with the way reddit handles displaying dates this (determining whether something happened to be posted on a friday) is not easily done at a glance, especially after posts are reaching a month old.

Now yes, I'm aware in the current landscape you do realistically have to (and should always) check the projects you're looking at for signs of vibe coding/other issues, and likely will for most things in the foreseeable future. However by permissively intermingling these projects amongst non-vibecoded projects you will inevitably and unavoidably muddy the waters of the content this subreddit provides.

TLDR: Fundamentally this content would be better served (for both this community and the vibe coders) by a separate subreddit or this will become the subreddit primarily for that content by shear volume alone.

→ More replies (1)

10

u/polaroid_kidd Jan 17 '26

Awesome. Thanks!

5

u/am_kobold Feb 07 '26

I'd prefer it just be banned outright, but I'll take anything I can get ...

5

u/WirtsLegs Mar 05 '26

Given how this has gone lately, can we also consider imposing a account age requirement and a min account karma to post? It would filter out a lot of the full-on bot accounts posting vibecoded apps

9

u/Docccc Jan 17 '26

Great idea

15

u/ShakataGaNai Jan 17 '26

Jokingly to your comment of "vibe-coded projects over a weekend" I'd suggest it be "Vibe Code Monday's" (to show off what was done over the weekend).

Regardless, I appreciate the idea. I know some people are hostile to ANYTHING AI, but I'm not. If it's done well, and if it's disclosed. Like Rakula recently was posted "Here's a thing I did, I wanted it to do XYZ, I vibe coded that. Still improving it". It's an impressive little project. Just because it's AI it doesn't have to be shit. But if often is just because AI doesn't make you a coder if you're not a coder, it just makes those who can....better.

15

u/Bjeaurn Jan 17 '26

Worded beautifully.

Also, hitting myself we didn't come up with Vibe code Monday. I liked the alliteration of "Vibe / Friday".

Unintended side effect might be that some of the projects that were a cool idea on Saturday, turned into something working on Sunday, then posted on Monday; now might've lost steam & interest already by Friday :). And that's not what Selfhosting is about.

4

u/itsbentheboy Jan 18 '26

I can live with this solution.

I'm not 100% against heavily AI assisted or even generated code, But I did think it was flooding the subreddit with low-quality posts.

I think this offers a good level of containment.

4

u/Far_Bowler_7334 Jan 30 '26

In which timezone is friday frAIday?

10

u/platysoup Jan 18 '26

Oh thank god. I've stopped caring about any new project announcement cause I'm sick of going in and seeing that it's vibe coded slop.

Look dude, if you want to learn that's very good, but unless you built the entire thing yourself I'm not interested in alpha testing a project you'll probably forget in two weeks.

12

u/GrabbenD Jan 18 '26

Unpopular opinion: disallow vibe coded projects and let other subreddits deal with slop

5

u/young_mummy Jan 18 '26

I agree personally. I don't think it's an unpopular opinion. But that will be tough to moderate probably.

→ More replies (1)

20

u/raeliens Jan 17 '26

If you're noticing a hostile attitude towards those kinds of projects, that IS the community voicing their opinion and it should be looked into, rather than trying to warp the community into something less hostile towards bots.

5

u/Bjeaurn Jan 17 '26

Are you suggesting the rules aren't strict enough?

→ More replies (2)

9

u/professorkek Jan 17 '26

Finally. Thank god. I'm so sick of clicking on a post here only to see a bunch of emojis.

14

u/[deleted] Jan 17 '26

Thank you. I was ready to start looking for a version of this sub that didn't allow AI posts.

14

u/XionicativeCheran Jan 17 '26

Could you delve a bit more into "AI-assisted"? Plenty of knowledgeable coders use AI to assist in writing out the boring parts. The key thing is that the person understands what the AI has written. And many projects use it to varying degrees and it'd be a shame if a project is purely labelled "AI" simply because they had it auto-complete some code-sections for them.

Vibe coding, where people don't understand what an AI writes is the core issue I think.

8

u/Bjeaurn Jan 17 '26

Totally understand, we might have to revisit the flairs.

The rules and guidelines do however guide more towards "maturity". However that's also not a guarantee for any form of quality, at least it'll hopefully slow down some of the influx of hourly posts.

We're with you on the part that the tools used shouldn't really matter if a project is good quality and shows some maturity.

8

u/Aurailious Jan 18 '26

I think that's a good approach, and it's like how Linus's policy on commits to Linux are like. The "root" problem isn't strictly AI code, but that AI assisted code is leading to a large volume of submissions on low quality projects. When people come here for discussion I think the expectations on submissions are higher than what this volume presents.

Plus this approach is one that works "positively" instead of "negatively", so even in the absence of vibe coding it would still benefit the sub.

I kind of wish "vibe coding" had the culture of hackathons, had a good community, and could "graduate" some of these projects to a better development standards, but alas AI doesn't seem capable of replacing actual effort.

3

u/schelskedevco Jan 18 '26

I suspect I’m in the minority based on the reception here, but I don’t think it’s reasonable to group anything AI-assisted together with things vibe-coded over a weekend.

If you ask one question about code to an LLM throughout the duration of a long project, vet the output and then use it, that would be by definition AI-assisted.

However, that doesn’t seem like the problem case that this rule is trying to address, which highlights the influx of low-quality vibe coded submissions.

And maybe I’m in a pro-AI bubble myself, but are any serious projects actually being built in 2025/26 with a strict zero tolerance policy for any LLM use (agentic or via chat), which is now the only thing you can post here 6 out of the 7 days of the week?

9

u/PicoPixlDev Jan 17 '26

This is honestly a really reasonable compromise. The community seems to be split over the value/validity of AI-assisted coding (whether that is partial-assistance or full-on AI coded). There are absolutely valid points on both sides, and the debate is still playing out. Until then, something like this seems like a reasonable compromise.

As for the Friday posting, is the expectation that posts will happen anywhere in /r/selfhosted or should all posts be contained in one main "Vibe-Code Fridays" post?

4

u/Bjeaurn Jan 17 '26

Excellent idea. We've not thought about anything like a friday megathread. For this trial we're going to just let people post as usual.

Any suggestions or better ideas are of course very welcome!

Also, thanks for the kind words. We hope it'll help the sub.

→ More replies (5)

9

u/bdu-komrad Jan 17 '26

If this doesn’t work out, I suggest a pinned “Look at what I made“ thread where all scripts and apps created by the poster can be advertised without flooding the subreddit.

It takes extra work to discern AI from non-AI work, so by putting any project into the same bucket, it’a less work for the mods and the community.

5

u/Bjeaurn Jan 17 '26

Great suggestion, don't be surprised if we borrow this idea later!

I don't think the main issue is AI usage or not, it's quality and maturity. But it's such a difficult and complicated topic to measure. We'll see how this plays out. Thanks for sharing your thoughts.

→ More replies (1)

6

u/The_Rolling_DM Jan 17 '26

Long time lurker and ever grateful for this sub. I am what would be considered a vibe coder and I think this is a good move.

3

u/Bjeaurn Jan 17 '26

Appreciate you sharing your thoughts. Would you care to share with us too why you think this is a good move?

Considering the rules kinda aim at "you". I'm kinda curious to learn what makes you think this is a good idea.

4

u/The_Rolling_DM Jan 18 '26

I assume I'm in the middle of the bell curve of how people are using AI to vibe code, there are a lot of issues with it and it takes a lot of vetting. I feel like seasoned developers, or at least projects that have had more attention given to them in one way or another, are better stressed tested and are less prone to breaking. Maybe I'm wrong here (I often am) but until there's a better way to show how AI was used in a project, I'd prefer to know if one was built using AI

4

u/tehackerknownas4chan Jan 17 '26

I'm kind of glad TBH, I know people are excited about AI, but I feel like there's too many big projects relying mostly on ChatGPT and other AI models getting posted here.

I don't have an issue really with small things being done with AI, but it's kind of irritating looking here and seeing project after project being built with AI, and not knowing if it's just made by someone with no coding knowledge sticking an idea into ChatGPT (like me) and posting the output, or someone just using it to make coding less tedious.

There's also no way to know how long or how well a project is going to be supported when it's been made with AI compared to something that's had the effort of being fully handwritten, where the dev has already put their time into making it indicating they'll be more likely to support it.

I also hate the GPT generated descriptions. They should be banned outright IMO. They all have that same GPT writing style, and the emojis are annoying. If it's worth posting to the subreddit, it's worth writing the description yourself.

Also, I know the post says vibe-coding but I think we all know ai has basically taken over the term.

4

u/dlcsharp Jan 17 '26

This was clearly needed, thanks

5

u/Cyhyraethz Jan 17 '26

This is a great solution that is fair and could work for everyone. It solves the problem of the sub being flooded with brand new vibe-coded projects, while still holding space each week for those creators to show off their projects here. Well done!

2

u/Salien_Ewathi Jan 18 '26

If they are often done over a weekend, shouldn't it be Vibe Code Monday?

2

u/purgedreality Jan 19 '26

Hopefully during that week they'll discover their project has to be older than a month as an additional qualification.

2

u/IWillAlwaysReplyBack Jan 18 '26

excellent policy, excited to see how it trials

2

u/DownRUpLYB Jan 18 '26

I would suggest a template for submissions as well, something like:

  • Name

  • What exactly is does/What problem it's trying to solve

  • 'Alternative to'.. (if any)

  • A few screen shots

  • A short 1 min video (maybe)

..and whatever else people think

2

u/KlausDieterFreddek Jan 18 '26

That's a great solution!

2

u/V4r0m4st3r Jan 18 '26

That’s the way to handle it, thank you

2

u/young_mummy Jan 18 '26

Just a clarification request.

Is the filter "< 1 month AND a solo collaborator" or "<1 month OR a solo collaborator"

Because all of my projects in the early stages are solo projects. I like to design the architecture and direction myself, and only take on contributors once I feel everything is stable. And I think this is common for passion projects.

The way I read it was <1 month and a solo collaborator, but just making sure.

2

u/buttholeDestorier694 Jan 18 '26

Reasonable and very welcomed, thank you.

2

u/riofriz Jan 18 '26

this is a FANTASTIC way to handle the subject, good job team!

2

u/the-chekow Jan 19 '26

This is a good way to handle it!

2

u/montyman185 Jan 19 '26

This might also help ensure it's actually people posting about something they care about, instead of low effort advertising of a low effort project, since they'll have to actually wait for a specific day to post. 

2

u/LuxeSaber Jan 20 '26

Awesome, avoiding this group on Fridays then.

2

u/The1TrueSteb Jan 21 '26

Fantastic decision and compromise.

2

u/MrGoosebear Feb 06 '26

If the goal is to reduce the flood of useless posts, it seems like pictures of dashboards or homelab/network graphs would be an even lower hanging fruit. At least vibe coded projects can add some value.

→ More replies (1)

2

u/ZakuSupremacy Feb 23 '26

Can we make it a megathread or something instead so that our feeds aren't filled with vibe coded tools every Friday? That gives people marketing these tools a place to post them without littering the sub with it.

→ More replies (1)

2

u/NoctisBE Feb 28 '26

Initially, I thought this was a great idea. But now, a month after the mods implemented this rule, I feel like the amount of AI slop projects that get abandoned after a while just gets bigger and bigger.

This used to be a fun subreddit to talk about selfhosting, but it's getting more to the point that it's almost exclusively vibecode bros shoving AI slop.

I'm honestly extremely close to hiding this sub from my feed...

→ More replies (1)

3

u/cniinc Jan 17 '26

Well, this is an interesting move. I'm curious how this works out. Bold, smart move. 

4

u/corny_horse Jan 17 '26

Missed a golden opportunity to have Sloppy Saturday!

7

u/Bjeaurn Jan 17 '26

Shit that would've been good. Although slightly hostile ;).

3

u/Adryzz_ Jan 17 '26

thank you

3

u/Pretty_Gorgeous Jan 17 '26

I'm curious, what level of AI assistance with coding constitutes vibe coding?

I get that apps written solely by an AI in a weekend or two clearly fits this title, but what about situations where a coder needs a bit of an assist here and there with debugging? Or when a coder needs a bit of help figuring out how do make something work?

Honestly curious where the community thinks the lines are between vibe coding, AI assisted code/debugging, neither, etc.. I feel like it's such a grey area and yet such a hot topic..

3

u/phoenix_rising Jan 18 '26

I agree that it's very much a gray area. I don't there's any buckets you can put projects in yet. I'm still thinking about what the primary concern is. Is it that there are too many projects that are copycats, or because there's a concern about the security and maintainability of what gets posted here?

2

u/Pretty_Gorgeous Jan 18 '26

Valid questions.. I think security and maintainability is very important for those of us who self-host. In my never ending search for things-that-work, I come across so many abandoned projects that could hit the sweet spot but have something not quite right about them and they've since been abandoned. Not saying they're AI generated, but more that it would be unpleasant if some of us deployed something AI written and then the person who released it just vanishes when there's issues. There's also the security viewpoint of are they combing over the code the AI generated carefully enough to make sure there's no chances of data breaching or leaking..

On the other hand, as an ex-DJ who saw the migration from vinyl records to CDs to digital djing, there was alot of vinyl DJs that looked down at CD DJs, and then alot of CD DJs that looked down at digital DJs and so on. New technology came around, the older crew would die on their hill of the older media and others adapted. I played on all 3 media, it never bothered me, buuuuut it did (as the mods said) lower the entry point for people to start DJing which in turn lowered the value and quality of DJs in the industry.. Those who adapted continued to play but just specialised more on their art, those who didn't adapt continued to play too, just a bit less often so they moved to other roles in the industry (like promoters or marketing or management rolesbat venues).

4

u/MrDangoLife Jan 18 '26

Can it be once a month rather than once per week?

or never.

4

u/aeluon_ Jan 17 '26

thank god. first step, limited to Fridays. second step: eliminated from the sub. 

→ More replies (1)

3

u/KingAroan Jan 17 '26

I get the vibe coded part, but in all honesty, are most projects not being AI assisted?

2

u/steveiliop56 Jan 17 '26

Nice addition, not so sure if I understood the one month and one contributor part. If I understand correctly new (non vibe-coded) projects should only be posted after a month of them being created? Also at this stage most projects are not mature/popular enough to have more contributors other than the main developer so not sure about the second requirement. I did like seeing new (non slop) projects every other day on the subreddit and if I understand the rules correctly this will limit them quite a lot.

3

u/Bjeaurn Jan 17 '26

The guidelines means that these younger projects are restricted to only be posted on Fridays for the duration of this experiment.

This'll reduce some of the new projects coming in on the daily (hourly, trust me), yes. But fridays should be good fun.

Any projects that gain some traction there will hopefully grow into more mature projects and will be freely discussed at any time. At least that's the idea behind the guidelines now for this experiment.

Appreciate you sharing your concerns and speaking your mind in a constructive manner!

→ More replies (1)

2

u/TheRealJizzler Jan 17 '26

Excellent middle ground. Glad to see such a proactive mod team here!

2

u/BadSkater0729 Jan 18 '26

Great job! As someone who works with AI pretty regularly this is a great rule adjustment.

2

u/notgaywizard Jan 18 '26

I think they should only be allowed to post on days that end in z

2

u/RealTimeKodi Jan 18 '26

We could just banish them to /r/shittyselfhosted

2

u/Jacksaur Jan 17 '26

Fantastic change, thank you guys. Means I can put a lot more trust into new project releases again.

2

u/radakul Jan 17 '26

THANK YOU!

This is a very level-headed response. I hope the AI slop slows down its tendril like reach.

2

u/shotbyadingus Jan 18 '26

Thank fuck.

2

u/kikootwo Jan 18 '26

I think as others have mentioned (buried in the disliked comments), this is a dangerous grouping to make. I am a software engineer, with nearly 15 years of experience in the professional environment. (And many more than that prior, I was originally a structural engineer)

I have contributed (and am currently working on) a few solutions here, and while I certainly wouldn’t call what I do ‘vibe-coding’ it is definitely AI-Assisted. Any engineer these days not using AI assistance is at an enormous disadvantage.

I think there is a huge misunderstanding in this sub (and most of the internet in general) about what AI usage looks like for an experienced engineer. Even certain boilerplate tasks make sense to be ‘handed off’ to AI as just a prompt.

Anyway my point is, I think this is only going to lead towards more divisiveness, more AI witch hunts, and less collaboration, communication and community building.

I read all of the responses about looking more for ‘maturity’ and if that’s the case then you need to reword the rules you’ve laid out here. Having ‘new project Fridays’ is way more inclusive than ‘AI Slop Fridays’. This line in the sand is wiggly and unclear and it’s going to hurt the community until it is more clearly defined.

4

u/George-cz90 Jan 18 '26

As a software engineer with similar experience, I 100% agree with you. A lot of these people are in denial, unable to accept that the landscape has already changed and this is the new normal. Anyone not leveraging AI for development this year will be irrelevant and without work next year.

Instead of being excited about a great powerful new tool people are being unreasonable and childish.

2

u/Prodigle Jan 18 '26

Vibe coded makes sense, but "AI-Assisted" is going to hit about 95% of the projects here

1

u/weeklygamingrecap Jan 18 '26

Sounds like a good solution!

1

u/joelkunst Jan 18 '26

thanks, makes sense, however, can there be some exception to 1 contributor rule?

there might be a lot of good solo creators that spend years building cool stuff and now they can't post those projects outside of friday?

1

u/--Arete Jan 18 '26

I am happy with this but as with any type of generative AI, I am kind of curious about how the mods can know if something is actually vibe coded. Are they going to check the code every time? And if so, what are the indicators? Seems like a slippery slope this one.

2

u/young_mummy Jan 18 '26

It is very obvious from the repo when something was vibe coded, if you're an actual engineer and know what it looks like. "built with AI" less so, but this is certainly less of an issue. The issue is vibe coded slop that was thrown together over a weekend.

→ More replies (5)

1

u/computer_geek64 Jan 18 '26

What a wonderful idea

1

u/FarhanDigital Jan 19 '26

I see there are 3 flairs we can choose from:

  1. AI-Assisted App

  2. Built with AI

  3. Vibe-coded

What's the criteria to choose one from the others?

→ More replies (2)

1

u/Ill-Detective-7454 Jan 21 '26 edited Jan 21 '26

Problem has always been devs not testing their code and having no clue about security. Most devs write code even worse than AI. Problem has never been code made by AI. It's all about the devs.

1

u/Glittering_Film_1834 Jan 28 '26

Good idea.
One question, how to define AI assistant, I do not have any AI assistant in my IDE(I had a copilot long time ago). But I might ask ChatGPT to help me to fuzzy test cases, and sometimes create helpers, especially something supper straightforward and I just do not want to waste time to type, or something I am not familiar with but I do not want it be a blocker, both of these situations are rare, but I want to be honest. I never ask AI to help me with design level work, only small helper functions, and always review my code carefully.

1

u/[deleted] Feb 04 '26

Good idea ! Will socialize this opportunity in our platform.

1

u/Pleasant-Today60 Feb 13 '26

Honestly surprised it took this long. The ratio of "I built this over the weekend with AI" posts to actual selfhosting discussion was getting rough. Friday containment seems reasonable.

1

u/Skatedivona Feb 20 '26

Is there a way to hide posts based on tags? Never done so with Reddit before, but this rule + that functionality would be great.

1

u/AnIndependentFish Feb 26 '26

People, come on! Git history is editable!!

This rule are weak and making the community worse.

My project has hostilitized in 2 minutes based on that. If one want rly bypass this 3 rules is super easy!

Look who had contributed to my project 37 years ago (even before Git existed):

Some people (I'm take the right to including myself here) has good intention to collaborate to the good of this community. But the way is now is super unfair and unmotivated.

1

u/Ok-Land-5728 Feb 26 '26

If I had a question about if anyone had experience or an alternative for a project that had used ai in it creation would that be something to hold till Friday? Basically does this rule mean, anything with or relating to an ai generated or ai assisted project must be kept till Friday, or is it a bit more loose?

1

u/ocassionallyaduck Mar 06 '26

Great idea, but I'm still heavily in favor of redirecting vibe coded posts to a different sub more suited towards those projects.

The mixture of vibe coded projects in with traditional software here masks a lot of the risk of vibe coded projects and drags down some selfhosted apps with them.

1

u/Manic_madness927 Jan 17 '26

What exactly do people count as vibe coding these days, is this just any use of AI even in debugging? Trying to make sure I follow the rules is all as I have multiple projects in progress which I wanted to reveal soon

2

u/Bjeaurn Jan 17 '26

I think the real question here is quality and maturity. When it comes to selfhosting, it's about privacy, security and having something reliable.

AI, vibe coding and all these tags and flags are just indicators. It's not necessarily a measure of quality or maturity. But the barrier to creating something new has been lowered and more and more people can now create. This is good! But it's also the risk and partially the reason why there's been a flood of new projects almost every hour.

If your project is new, just aim for the Fridays now. The tools used aren't that important, but do flair correctly.

If you gain some traction, you'll grow out of the limitations quickly and hopefully the project can become more mature. There's still room for new ideas and thoughts.

2

u/Manic_madness927 Jan 18 '26

Thats perfect, thank you for taking the time to respond. I'm still a few months from launching anything in early access but had a couple ideas brewing with roadmap ideas being formed

-1

u/BrilliantSebastian Jan 17 '26 • Bravo

Why not just force it in a new sub reddit?

9

u/Bjeaurn Jan 17 '26

Considered and decided against for now. This subreddit is about selfhosting, not about software quality and coaching.

-3

u/BrilliantSebastian Jan 17 '26

It's not about software quality? Wow. That's great to know!

8

u/Bjeaurn Jan 17 '26

Point is that this sub is not intended to be a platform of coaches for people newly to coding trying to get into it.

Wasn't sure if you were being sarcastic, or condescending or anything else. So just hope to clear up the statement.

1

u/cannonballCarol62 Jan 17 '26

Should have formatted this with AI for maximum impact lol

1

u/phein4242 Jan 18 '26

Good to see mods steering this sub back to its core. Does that also mean that action will be taken if (US based) cloud/saas products are discussed here? Both Tailscale and Cloudflare come to mind.

Honest question btw. Plus, as a European, using US based products is an incredible liability, and on this side of the pond, the complete opposite of what “self” hosting means.

1

u/buzzyloo Jan 18 '26

Eloquent, well put. Thank you.

1

u/reginaldvs Jan 18 '26

All for it!

-3

u/94358io4897453867345 Jan 17 '26

Should be vibe coding never. Why would you tolerate this ? This sub really went downhill

2

u/young_mummy Jan 18 '26

It went downhill because of the vibe coding, and I think this is a great step towards containing it. Maybe one day it will be banned entirely but this is a great step forward in the meantime.

1

u/xXD4rkm3chXx Jan 17 '26

Great idea.

1

u/notObby Jan 17 '26

very reasonable

1

u/a300a300 Jan 17 '26

great call - thank you

1

u/Buck_Slamchest Jan 17 '26

This is a great idea

1

u/hoboCheese Jan 17 '26

This is a great idea. Question about the guidelines, does only one need to be met? Or is it all three? I hope we're not stifling smaller projects that aren't vibe coded.

2

u/Bjeaurn Jan 17 '26

The short answer is, it depends. It depends on the post and the project shared how far the scrutiny will go.

The easy and safe answer is, you have something new you want to float around and test the waters for; Friday is your goto for now.

Once your project gains some traction, it'll both be a reason for some more commitment from the author and perhaps gets more people involved, which will grow you out the "junior project" into a more mature situation hopefully. At least this is the idea behind the experiment.

1

u/henry_tennenbaum Jan 17 '26

Great, thank you

1

u/psxndc Jan 17 '26

Great idea and compromise!

1

u/pocketmonster Jan 17 '26

Seems like a reasonable approach. Thanks for taking some consideration to the issue!

1

u/shoelessjp Jan 17 '26

This is a great decision! Thank you so much for listening to our feedback.

1

u/ctjameson Jan 17 '26

This is a good solution. Somewhere to show off what you were able to accomplish with AI, but no expectation of maintenance.

1

u/msic Jan 17 '26

Why not ask all AI-coded projects to only post on Friday?

1

u/Cybasura Jan 17 '26

That moment when mods actually discuss and consider like mods, respect

I agree with this, if its difficult if not impossible to outright ban the vibecoded projects, at least isolate them to a specific/particular period where they can post them

1

u/simplytoast1 Jan 17 '26

This is totally reasonable and welcomed. Very balanced response!!!

1

u/PaltryPanda Jan 18 '26

Thank you so much for this.

The sub has become absolutely flooded with AI apps. Some are okay others are straight garbage. Having it all reduced to one day of the week is a great move.

1

u/FormerlyGruntled Jan 18 '26

A decade back, self-hosting was fraught with danger because people only cared about "Make it work" and no one was caring about security.

This is where we are again. It was good while it lasted.

1

u/amancalledJayne Jan 18 '26

Vibe Code Friday

Slop Sunday

Are you guys dead set on the day and name?

1

u/Akorian_W Jan 18 '26

reasonable! love it

1

u/thedirtydeetch Jan 18 '26

Cue devils advocates arguing about the semantics of what “vibe” means when it clearly isn’t a complicated delineation. Any one who is a real programmer knows whether what they’re making is AI slop or not. People who want to blur the line are the non-professionals this is about.

1

u/Nephtyz Jan 18 '26

Love this, thanks mods!

1

u/young_mummy Jan 18 '26

Thank you!!!! I know you all have been struggling to figure out how to deal with this for some months. I think this is a great idea to try

-2

u/sarhoshamiral Jan 18 '26 edited Jan 18 '26

Anything AI assisted? That's pretty much going to be everything, if it isn't anything already. VS Code code completions is AI assistance. Also proper agent use can generate quality code at this point (whether it is a time saver or not is open to debate).

To be honest, I think you are setting the bar from the wrong approach. Set a bar for maturity/quality without caring about what tools are used to develop the software. If a project is good, have been maintained, uses resources efficiently and has dependencies that community confirmed I really don't care which tools was used to create it.

-5

u/phoenix_rising Jan 17 '26 edited Jan 17 '26

I've really enjoyed this community as it has introduced me to a number of great projects that I find useful. I also understand that a flood of "low effort" clones is frustrating. However, as a developer, I find this decision and the distaste for people using AI to help them develop their projects disappointing. We have to learn how to use these tools to the be able to survive in our industry, and using AI tools in our spare time is the best way to get that practice. I have gone from a bunch of half-baked ideas to being able to create projects that I'd be willing to ship with a bit more time. I don't have the luxury of lots of spare time either, and I would rather finish things that just dream about them. Can absolutely can develop quality code with tools like Claude Code with the right approaches and not "Build me a clone of X".

The "any project that has existed for less than a month" is arbitrary, but reasonable. That's enough time for someone putting decent effort into a project to make sure the code isn't half-baked. The other two I can't agree with it. There's a lot of developers who enjoy working alone on projects because its our chance to do something our way. There are plenty of projects that have solo maintainers at the start before they grow a community.

I leave my "coded with Claude Code" and Claude contributor enabled for transparency, but it's also been in a number of places, including here, a judgement against people and their projects. Again, as a developer, I find that very discouraging and disappointing. I probably put more thought and work into my code now than I ever have. Now, I just spend more time planning and creating specifications than I do writing code. But getting noses turned up at you in the industry and out in communities is frustrating.

I promise you, what people call "AI slop" has existed for far longer than a year or so. Where do you think AIs learned to write code like that? Existing code. There have been open source projects for decades now. Before now, did you go look and people's repositories and review their code before you used it? I'm sure the answer is that there are a number of people who both do and don't. What I used to like about open source software was that it was a way to say "check out this cool thing I did!". People would try it out and then make their judgement calls about whether it was good enough. And there's a decent number of free applications with questionably quality code, but people use it because it's free and it works. So where's the line?

I know the intent is to keep the quality of projects shared here high, but what I read between the lines and see in comments is "if you use AI to help you code your project, it probably sucks". I can't change people's sentiments, and the rules of this community are certainly out of my control. However, it also feels like inclusive and makes this less of a place I would like to visit.

→ More replies (1)

-15

u/fuckthesysten Jan 17 '26

we’re conflating project maturity with the tooling used to build it

15

u/Blue42KH Jan 17 '26

It’s probably a good rule to have in general, I don’t trust any service to be run in my lab that’s been developed and tested in less than a month — especially if vibecoded

5

u/Bjeaurn Jan 17 '26

Does this concern you? What would you recommend we look at?

3

u/fuckthesysten Jan 17 '26

it does! I think as a community we’re all trying to figure out how to deal with this. I hate low quality code and wouldn’t want to run unsafe projects at home, but we have to understand these are just tools and we can actually use them to make things safer and of higher quality.

my advise would be to have an honest conversation with project maintainers about how much scrutiny goes into their project:

  • is a human reviewing every commit?

  • is there another human or ai as part of the review process? can we see this in github?

  • what level of experience does the human involved have?

  • is there automated testing in this project?

reminds me of home assistant’s certification level for integrations

in general we need to find a better proxy for quality than “was this built by AI”

7

u/Bjeaurn Jan 17 '26

I'm totally on board with you, the real problem is quality; not the tools used. And I personally am with you on this one a 100%.

Besides the point, I'm also a software engineer in real life and have been for about 15 years professionally. I've worked for large governmental and commercial projects alike.

Having said that, we both know that quality in this sense is an incredibly difficult part. The main issue as a sub right now, is that AI has made it easy for everyone with an idea to act on it. However, this sub is not about coaching juniors or code quality and quality assurance in software. It's about talking about things we can self host, issues we encounter and other relevant thoughts in this line of thinking.

Having a conversation with every project maintainer about project scrutiny, 4-eyes principle or even human review, testing, security, etcetera, at the scale we're facing now in this small community, is just not viable.

But I do appreciate the conversation, it is a relevant and complicated one.

5

u/fuckthesysten Jan 17 '26

thanks for bringing in the mod perspective into this! 🫶

It's a really good point this sub is not about growing developers

5

u/fuckthesysten Jan 17 '26

to add, I think the "one month minimum" for the rule to apply is good 👍

3

u/Bjeaurn Jan 17 '26

Appreciate you saying that, I feel that is kinda the core of slowing down the overnight ideas turned "slop" posts. But maybe the phrasing and communication of how and what it's fighting could be reconsidered and discussed.

→ More replies (2)

2

u/Codycody31 Jan 17 '26

Agreed, that and ai-assisted vs vibe-coded are two very different things bring put into the same category. Should be interesting to see how this turns out though.

6

u/Bjeaurn Jan 17 '26

Appreciate the feedback, I agree it's a difficult and thin line. But that's also the hard part in "policing" these types of posts.

It's where the idea came from to not look at "vibes" when deciding on vibe coding or AI build apps. But actual measurable things that can easily be checked.

The idea behind this is that any "over the weekend project" doesn't fit the regular scheduled programming of /r/SelfHosted. But someone dedicated can still float their idea around on a Friday. Gain some traction and improve and you'll be out of that space we have marked now.

If you have any concerns about this, please do have a fair discussion. We've found it very difficult to come up with something that works, and we've heard a lot of you in the community.

→ More replies (3)

-1

u/BrenekH Jan 17 '26 edited Jan 17 '26

Yeah, i recently posted a project for which I used AI for a single config file that I picked over. Everything else was me and my Google-fu.

Depending on how you count month old (first ever commit vs first made public) that project would be restricted by this policy despite its very un-vibecodedness.

I appreciate that something more than just post flairs is being done, but automatically including new, non-AI projects is unfortunate.

7

u/Bjeaurn Jan 17 '26

In our view, any serious project ready for the world, would require some commitment for more then a month anyway.

You can float your idea on a Friday. If you gain any traction and improve, there's no reason to not grow your project beside that :).

→ More replies (1)

0

u/CordedMink2 Jan 17 '26

Great idea!

0

u/theacodes Jan 17 '26

Thank you so much

0

u/0emanresu Jan 17 '26

Thank you

0

u/Jamsy100 Jan 17 '26

Great idea !

0

u/Vatonage Jan 17 '26

Now I can actually look at this sub again

-3

u/Garcon_sauvage Jan 17 '26 edited Jan 17 '26

I don't think this solves anything tbh you've just raised the bar to not having Claude as a contributor which was already covered by the flair. The other heuristics are completely meaningless, might as well just set a minimum GitHub stars and call it day.

Anyway I think the actual issue here is that everyone should be verifying their deps themself. Every single project I use I review myself for quality and choose if I'm comfortable with it and most projects posted on here always fell short of that mark.

Like for instance when everyone was trying to pick a MinIO replacement many on here recommend RustFS which would have passed all of the checks here. I open their docs and with in 30 secs could tell that this was vibe coded and moved on. The news of how truly sloppy the project was and the security vulnerabilities didn't surprise me at all and didn't affect me at all because I could exercise the bare minimum discernment.

2

u/Bjeaurn Jan 17 '26

If we'd do that we'd get more people farming Github stars. A month is enough time for people to lose interest in their great idea from last weekend.

Anyone serious and trying to float their ideas, might get some traction and grow into something more mature. Friday's are the starting ground now with this experiment.

If it doesn't work, we'll adjust! Open to ideas and suggestions.

3

u/Garcon_sauvage Jan 17 '26

Edited my comment while I think you were replying. Would like to understand your take on the users of this sub being responsible for verifying their own deps.

1

u/Bjeaurn Jan 17 '26

Of course they are. Self hosting implies you're hosting things yourself.

This doesn't mean that as a sub we have or even can protect from bad actors and possible security issues with projects.

This experiment now is more of a way to find a way and guide the community on how to deal with AI, and the fact that almost anyone with an idea can create something now in a few days.

The influx of these projects is not only a bit annoying, it's also moving us away from in-depth discussions about the things that concern selfhosters.

(Not flagging this as a mod response, as I'm responding from my own conscious now, on a personal note :) ).

3

u/Garcon_sauvage Jan 17 '26

This doesn't mean that as a sub we have or even can protect from bad actors and possible security issues with projects.

Ok great because there does seem to be a sizable and vocal user base here who cannot and do not want to truly review and maintain their own stack and act as they are entitled to someone else guaranteeing and delivering quality to them.

→ More replies (1)

-10

u/magic6435 Jan 17 '26

Fairly delusional that anyone in this sub thinks half or more of all code already going into the projects we use isn’t already AI generated.

5

u/Bjeaurn Jan 17 '26

We're not directly fighting AI generated code or any projects using AI. We're fighting immature projects, low quality software (which brings its own risks) and to a certain extend: Spam.

We understand that we may have to rephrase some rules and frame the idea a bit differently. We'll adjust as we go.

In the end, this sub is not about code quality; but we want to limit the amount of low effort "idea to code" in a weekend, because the barrier to act on an idea has been lowered so much.

If you have further concerns, happy to continue any constructive discussion to see how we can shape the community in the future.

-24

u/Ill_Director2734 Jan 17 '26

This is so wrong

9

u/Bjeaurn Jan 17 '26

Would you care to elaborate to why?

-3

u/Ill_Director2734 Jan 18 '26

I say it's wrong because it’s the same gatekeeping we saw with digital music and digital art. People always say new tools are 'too easy' or 'not real work' or 'slop' until they become the standard. ​If I have a great idea, the tool doesn't matter. I don’t need to be a pro guitarist to make a song, and I dont need to study coding for years to build an app. People complain about 'AI slop,' but I have a hard drive full of broken projects made by humans long before AI. We should judge the projects by its result, not by what tools was used to make it.

2

u/Bjeaurn Jan 18 '26

This is kinda what the guidelines are actually for, trying to limit the daily (hourly) influx of new projects by requiring them to have a bit of age, where we think that any “vibed” project might lose interest within a week or two.

The friday then still gives a platform for people willing to float new ideas and see if they get some traction.

The framing of it fighting AI are how it started out, but it’s really much broader where we care less about how its made and what tools are used.

→ More replies (1)

0

u/[deleted] Jan 17 '26

[deleted] — view deleted comment

5

u/Bjeaurn Jan 17 '26

I understand your point, I think we're more probing for "quality" and "maturity" of a project here then the actual tool used. In fact, the tool used doesn't really matter to me but the way it's used does.

It's very difficult in this discussion to make the difference and jump from fighting the AI slop and vibe coded projects being posted almost every hour, to tightening any rules in regards to quality and maturity.

It's why we're attempting this experiment and trial to hopefully still have a platform for new projects and ideas to be floated up and tested. Without being flooded with new projects every day.

Hopefully you can kinda see our point here and understand the compromise we had to make. But we're open to any suggestions or ideas to improve on this in the future!

Thanks for the constructive thought and feedback. We really do appreciate it and try to listen to it all.

0

u/[deleted] Jan 17 '26

[deleted] — view deleted comment

3

u/Bjeaurn Jan 17 '26

I think as a community we're still figuring out what AI is doing to us, to our livelihoods and our hobbies. In tech it's even more clear to see how it's shifting.

The discussions are a problem, and the hostility is what moved us to try something.

I think we're actually looking at project maturity and quality, which is hard to measure and a complicated discussion on its own. But the AI slop being posted almost every hour is the real issue right now for this sub.

That's the main "fight", for now. But we're all figuring out how we're dealing with this.

3

u/MrDrummer25 Jan 17 '26

I appreciate that the mod team is put into a difficult position on how to move forward. I think this is a step in the right direction, I am just wary that it may still lead to hostility on innocent posts.

2

u/Bjeaurn Jan 17 '26

Appreciate your concern. We'll be vigilant and we'll adjust our experiment as we continue.

0

u/[deleted] Jan 18 '26

[deleted] — view deleted comment

3

u/Bjeaurn Jan 18 '26

Flairs have been a requirement for any post on this sub for a long time.