

This post requires an AI disclosure per the community rules.


This post requires an AI disclosure per the community rules.


On the flip side, if you’re vibe coding an app you should seriously consider whether it’s something you want to open source or make available publicly. There’s a social contract that comes with that.
I have 2 self hosted slop apps I build and maintain myself. I think people would genuinely get great use out of them.
…but then I’m inviting critiques and feature requests and am roped into supporting them so it’s not just a big pile of shit that wastes everyone’s time. And I don’t want to spend my limited free time making common sense improvements to improve it for others. I want to write a lazy Claude prompt with insufficient context, get it barely doing what I need, and then spend the rest of my time eating crayons and similar pastimes.


I use pangolin and traefik together and expose a few of my services that way. But not everything.
I slot services into categories based on:
Then the service is either not externally open at all, secured behind pangolin SSO, or secured behind pangolin SSO AND that service’s native auth. Which is an annoying double auth, but I feel like it’s another layer of protection in case one of them gets a 0-day exploit.


Daaamn that was the nerd version of a KenM rejoinder! Well played.


568C (the C is for chaos)
Wire in whatever way they fall in by themselves.
Then rewire the pins on the NICs so they can communicate.
It’s not so bad once you level up your soldering skills.
Spend the extra 25k. It’s worth it in case you end up stuck trying to download a 62TB torrent and suddenly can’t!
Just found the other rule post. Looks great!
I want a community where people can use AI to help build a tool and be able to post about it here. But unfortunately, I’m just not seeing that. The AI-generated apps seem to be coupled to a drive-by, AI generated post (and comment replies) all full of em dashes and the standard Claude slop language.
So, yes, mandate an AI tag. Hold posters to it and remove violators, because it seems to always be the same class of “contributors” that are cosplaying as software developers.
Not sure if your rule changes are touching this, but the worst offenders I don’t want to see here are:
The people doing that remind me of the people who would approach me 20 years ago saying “hey I have an idea for an app I want you to build and I’ll give you 5% of my company. It’s like Facebook for dogs, but I need you to sign an NDA before I say any more”.


Waddaya mean no cloud?
YOU ARE THE CLOUD NOW


Hey Claude! Nice work! Please spin up a new task branch and replace all text with random emojis. Deploy when done.


I have opinions, but none of them well enough formed to have suggestions on the new rule.
Try it for a while and see if it works! We know this community ain’t shy about sharing when something isn’t working for them!


I don’t care if an author is using AI in some capacity to write their app, but I draw a line when their posts on social media are also written by AI. There’s no human in it anymore.
The post was written by Claude. That’s its exact writing style I have to unpack every day during my day job.


It’s weird how many new apps show up in this community with long descriptions full of em dashes. Then the author starts replying using the same tone and word choices Claude uses.


How do you reconcile the Kobo wanting to sync reading position every time you turn it on? Or is that not a problem with your workflow?
I have issues in my own app and some other containers where the kobo is slow to upload reading stats, so every time my kobo wakes up, it throws up a dialog asking if I want to skip to my latest reading position. If I pick yes, it dumps me back 10-20 pages.
It’s easy enough to say no but it’s so annoying to have a delayed dialog every time I wake the thing up.
An AI disclosure for your app per the community rules, Claude.