darcmage
@darcmage@lemmy.dbzer0.com
- Comment on Self-Host Weekly (18 September 2026) by @eshol 3 weeks ago:
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.
- Comment on Self-Host Weekly (11 September 2026) 3 weeks ago:
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.
- Comment on Self-Host Weekly (11 September 2026) 4 weeks ago:
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.
- Comment on Self-Host Weekly (21 August 2026) 1 month ago:
Floppy seems cool. I am curious about how/why people use these types of tracking services for their media.
- Submitted 1 month ago to selfhosted@lemmy.world | 9 comments
- Comment on Self-Host Weekly (14 August 2026) 1 month ago:
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.
- Submitted 1 month ago to selfhosted@lemmy.world | 26 comments
- Comment on Self-Host Weekly (7 August 2026) 2 months ago:
That’s fair. I’m sure we have wildly different experiences around the discussion of vibe coded projects.
- Comment on Self-Host Weekly (7 August 2026) 2 months ago:
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.
- Submitted 2 months ago to selfhosted@lemmy.world | 18 comments
- Submitted 2 months ago to selfhosted@lemmy.world | 11 comments
- Comment on Daily Invidious Restarts 2 months ago:
I’d be surprised if most people running invidious for private use are following that advice. I’ve been on the master branch for a while and it gets updated fairly often. For my instance, I haven’t seen any reason to restart the service more often.
- Comment on I ❤️ selfhosting 7 months ago:
Well said.
- Comment on Self-Host Weekly #150: Watchtower No More 9 months ago:
github.com/nicholas-fedor/watchtower
Switched awhile back, no issues.