I guess now you have a place to rest when you’re wheely tired.

Unfortunately you’ll have to do your own research, I only know this exists and have never used it because my vacuum is incompatible.

In case anyone’s interested, there’s actually open-source self-hosted robot vacuum firmware for select models

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.

Are we really going to start enlightened centrist memes over Linux?

I say this as someone who daily drives Linux on their framework laptop, who self hosts jellyfin, home assistant, searxng, ollama, etc.

For a lot of folks, their lives don’t revolve around computers. I know that folks on Lemmy tend to skew more towards that computer lifecycle, but we gotta recognize that we’re out of the norm in that regard.

I feel like they’re saying that what you described doesn’t equate to do getting hit in the face by your boyfriend, which is subjective.

How this same conversation can sound to non-technical folks:

“my boyfriend left his dirty socks in the living room AGAIN.”

“Well maybe you should switch boyfriends”

“…what?”

Damn, that actually was a wonderful talk, thank you for sharing.

To anyone who bristled at my earlier comment - if you’re looking for a solution, this video lays out a foundation for the different types of conversations folks can have, goes over why it’s important to differentiate between them, and gives concrete action items to take. It’s also just a well paced, riveting ted talk, to boot.

Ah, I understood your earlier comment to mean to find some FOSS alternative.

It now sounds like you meant “who cares if Autodesk is not performant if work forces you to use it”, which I’m down with, and is honestly mentioned in the original post itself as a reason why folks complain without switching.

I know this sounds like a grand stand but it’s just going to get your ass fired lol. Autodesk is an industry standard.

ITT: people who have never had to learn that sometimes when someone complains to you they are not solution oriented, and it genuinely just feels good to share something wry/ridiculous to bond over.

It’s a good skill to pick up, folks. Definitely comes into play in relationships.

If you recognize there’s a problem, and the problem disturbs you, and you CAN fix it, why not fix it?

Because if the fix for any particular problem is to learn a new OS, that’s a steep cost for things that can just be minor annoyances. If you’re in Lemmy, chances are you’re comfortable with nerdy shit, and not everyone is.

On top of that, Linux has its own quirks, so it’s not a panacea. There’s no easy way for me to change scroll speed on a track pad in fedora/gnome, for example.

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.

Agree. We have a few housing coops in town and I recommend them to everyone I know.

That’s all well and good, but how likely is that to actually happen?

The original commenters point was that corporate landlords are driven only by profit as they buy up rental property everywhere. Even preventing that is highly unlikely, if we’re being honest, but it is far more likely to happen than all rented houses being forcibly turned to rent to own contracts.

We all want the same thing, but there’s a tradeoff between grandiose ideals and feasibility. It does not seem wrong to support pushes for less radical but more realistic methods of improving housing if your goal is to improve housing.

Worker owned coops equivalent for housing is a housing coop complex, which I believe is the most sustainable model of housing.

However, I’m not sure how that would apply to single detached houses.

EDIT: I didn’t really address the original point.

The comparison was between Black Rock and Mom and pop landlords. You can bet your ass that black rock is trying to squeeze out profit. That statement does not hold as true for Mom and pops, because there are other reasons why they may be renting out.