Self-Host Weekly (21 August 2026)
member since 4 Jan 2024 18:25
I’m guessing the blurb was provided by coder and not written by the author. Like someone else said, it could’ve been worded better.
From the newsletter:
no record of what they touched
From the site:
Centralized model access and policy-controlled environments with full observability and auditability across all AI usage.
We might have some wires crossed somewhere.
Floppy seems cool. I am curious about how/why people use these types of tracking services for their media.
It’s really annoying to go into each entry for items in my local domain and change the detection to host and do that for every service I spin up.
That’s fair. I’m sure we have wildly different experiences around the discussion of vibe coded projects.
It’s cool that he vibe coded something for his specific needs but the lamenting of being unable to share it because of the fear of a backlash is a bit premature. I wonder how long he (and others like him) will be able to keep his project going when he eventually adds more features that introduce more bugs and the effort/cost of maintaining the project becomes too much. We’ve already seen that for the majority of people vibe coding stuff, the answer is relatively quickly.
I’ve found interesting projects that have been vibe coded and seem to be well-maintained but I think vibe coded projects need at least 6 months to a year of history before they replace anything critical in my stack.
I remember reading that thread and what a shitshow. I ran grimmory for a while and the metadata scraping was inconsistent, especially with goodreads. Bookorbit seems to work so I’ll keep using it for now. I’ll probably end up switching back once bookorbit gets too bloated with all the stuff he’s been adding lately.