Fwiw I use a fork called Apollo because it enables a headless setup

Thank you for taking the time to type out this thorough response

The only annoyance I’ve had with it is searches will sometimes default to another language, even though I set the language to only return English results.

Also, I’ve found that the image/map search capabilities are less performant than googles.

But I still use it because the search results are so clean and no-frills.

Do you worry about the sus new maintainer for syncthing-fork on android?

Solidworks not being supported.

The solution I’m working on is to connect to a Windows computer via moonlight for their solidworks stuff, hopefully freeing up the potential to do Linux on their main machine

What does budget friendly mean to you?

I was looking into team speak and found this video that captures someone else’s experience.

Tldw; lots of super neat features, some clunky interfaces that maybe highlight how used to discord we’ve gotten

You know how your favorite show got pulled by Netflix, and you can’t find it without subscribing to another service?

I self host to take control of that back.

For frigate, you don’t need to have object detection on, if you’ll know what times to look for for footage. You can also just use the CPU for object detection, but ymmv based on performance. FWIW the coral tpu I use for detection cost like $50.

Do you understand why folks are upset though?

I have not had to look at the code for any other self-hosted application when considering whether or not to use it. You can say that this is a self-levied requirement due to the suspicions of vibe-coding, and I’d fully agree.

I took a quick peek at your github profile, and you’ve been working on FOSS stuff before LLMs were a thing (thank you!), suggesting that you are more likely to actually know what you’re doing. However when you say you vibe-coded up an application, you’ve placed yourself in the same bucket as the vibe-coder who’s ai agent deleted a database despite being instructed that there was a code freeze. Yes, it was a developing product, and not prod, but yeah you’ve advertised that you use the same tools and techniques as this guy, which does not inspire confidence.

Am I correct that a few of you are mad that I included dockerfiles and docker compose examples in the repo? Where did I go wrong?

No, we’re not upset about docker. Did you read the majority of my last comment?

Correct. Saying you “vibe-coded” something up suggests that you didn’t do it yourself, or at least was only loosely invested in it. If you didn’t put much time into it, then it’s not as vetted for folks. Running your code on someones homelab is then akin to pushing the new grads vibe-coded refactor into prod, which I think we all know is a bad idea. The mitigation for that is for the user to vet the code themselves, which we already asserted earlier doesn’t really happen in practice. So we have two options, either push the vibe-coded refactor into prod, or acknowledge that we’ve introduced an additional requirement onto the users to vet the code themselves. Both are not ideal. I’m proposing that it is that friction that you’ve introduced that folks are upset about. The docker issue was just brought up as an example of what could go bad by running poorly vetted code on a machine.

Personally, whether or not this will be maintained in the future is the biggest reason why I’m unlikely to try this. If the main developer vibe-coded it up, then in my book there’s a lower chance that the codebase will be maintained in the future.

If your response to “How will you maintain this?” is “nothing is owed”, it really cements the idea that this will not be maintained.

If an application is unlikely to be maintained in the future, then the risk-reward ratio will rarely justify me incorporating it into my workflow.

When you run a self-hosted application, do you first go through and read all the code? I don’t, I’ll tell you that. I’m going to assert that most folks don’t, and unless I hear otherwise I’ll assume you don’t read all the code for every self-hosted application you use.

No one is complaining about Docker, they’re complaining about AI

Correct. Saying you “vibe-coded” something up suggests that you didn’t do it yourself, or at least was only loosely invested in it. If you didn’t put much time into it, then it’s not as vetted for folks. Running your code on someones homelab is then akin to pushing the new grads vibe-coded refactor into prod, which I think we all know is a bad idea. The mitigation for that is for the user to vet the code themselves, which we already asserted earlier doesn’t really happen in practice. So we have two options, either push the vibe-coded refactor into prod, or acknowledge that we’ve introduced an additional requirement onto the users to vet the code themselves. Both are not ideal. I’m proposing that it is that friction that you’ve introduced that folks are upset about. The docker issue was just brought up as an example of what could go bad by running poorly vetted code on a machine.

Also idk where you heard Docker is like giving root

If I’m not looking through all the code, then as a user I’ll just be following your included instructions, of which the recommended method is to fire up docker-compose. If docker-compose bind mounted mounted /, my understanding is that the container now has default write-access to the entire host - am I mistaken?

I appreciate the spirit, but to shine some more light around the negativity you’re seeing in the comments, it’s a lot to ask for others to run your code on their machines. If you want folks to be running in docker, that’s oftentimes basically giving root access.

If I’m giving root access, I’d at least want for the person who wrote the code to have a thorough understanding of what the code, which once again is running as root on my home network, is doing.

The LastPass hack a few years back was enabled by a self-hoster running an outdated version of Plex on their personal machine. There is weight in choosing what software to run and support in your personal setup. The negativity you’re seeing is due to the belief that vibe coding, while able to produce something functional, is not reflective of solid, sustainable, and secure software development practices, and simply does not meet the bar for code to give root access to. It’s (probably) not personal.

This is such a Lemmy/self hosted problem lol

I color code all my info. (…) Green means go, so I know to go ahead and shut up about it. Orange, means orange you glad you didn’t bring it up. Most colors mean don’t say it.

- Michael Scott

This does sound like it could be a liability issue if not done correctly

100%. This is just due to the cost of hitting their servers in case you can’t reach your network

As someone who has changed accounts you don’t really lose that much. Karmas not a concept here, so that’s the big one.

Besides that, most apps let you log into multiple accounts so you can still check all of the legacy interactions if you need to.

The main pain was subscribing to all the communities again.

EDIT: when I first made accounts, .ml was recommended, and I tried signing up cuz I thought, “I work with machine learning, sure!”

Oh, those were brighter days.