i_stole_ur_taco

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:

• do I really need to be able to access this externally?
• …with full admin rights?
• what write/delete access am I granting?
• if an attacker got in, how much damage could they do with what they could access?

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.

If you’re not creating or tweaking recipes, a paper notebook is fantastic. It gives you something to do while you’re waiting on the boil.

I have a notebook with a page for every brew session: date, full recipe, steps, observations, and things I fucked up. Update it until the beer is done and there’s tasting notes. It’s fun to reread in later years. I have a few early brews that I noted got “infected” - and after some experience I had a good laugh because the “infection” was the shitty recipe I designed.

If you’re building a recipe you really need to use software (unless you don’t care about calculating estimated alcohol or IBU up front). The alternative is a level of referencing tables and doing arithmetic that exceeds what I want to see in my hobbies.

But if you aren’t trying to be scientific or you’re just following a basic kit? The only technology that should be involved is your phone playing music!

Beersmith is still around and still ugly, but www.brewersfriend.com is rather nice for recipe design.

How many roles did he play?

Bester still gives me the creeps.

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:

• posting and commenting text written entirely by AI
• not open sourcing or giving any visibility into their code
• adopting a paid model

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

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!

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.

5 em dashes.

That’s how I’d answer if I set something up years ago and it was stable and never required me to come tinker with it.

Read the email again. The key word in their marketing slop is “alternatively”. You have a Plex Pass and are the server admin. Your users need to do nothing.

Unfortunately, that does mean I have to respond to messages from all my users asking what that email means and convince them they can just ignore it.

A second “nice” part of this change is that iOS users no longer have to buy the Plex app on the App Store to stream longer than a minute. The app is only like 5 bucks one time, but it was a barrier when trying to convince stubborn people to just fucking TRY my Plex server.