darcmage

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’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.

It is and I thought it would be abandoned like most other AI slop but it has dev has been pretty active since I first became aware of it.

Adding github.com/Ivan-Malinovski/calino to the ones already mentioned. I need to stop being lazy and spin it up.

github.com/andrii-kryvoviaz/slink found at selfh.st/apps/?tag=Image+Sharing

Seems like it would fit the bill.

Can you elaborate on what you didn’t like about what you’ve seen so far? I imagine most guides advise you to spin up an AIO instance of nextcloud in docker.

Well said.

github.com/nicholas-fedor/watchtower

Switched awhile back, no issues.