I have a few cheap TLDs because as an individual I didn’t want to pay a lot of money for the dot com versions. But I’m not a company.

Definitely make sure you think through all the physical security implications of having your house automatically unlock in any scenario.

Have the house auto unlock when getting home on a bicycle, sounds convenient until, as you point out, they could get stolen and now the thief has a convenient way to unlock your house. So you would not want that.

You would definitely not want the house to STAY unlocked when something like a tag is in range. If your kid is home alone, you want them to be able to re-lock the house (or in general, you want to be able to lock your house while the kid is home).

Whatever solution you wind up with, you are going to be trading physical security for ease of use (and complicated fun task). Be safe. Make sure the tradeoffs are actually thought through and worth it.

Hard to unlock the house based on media playing if the kid is outside though.

Oh look. Debian changed the keepassxc package and now the keepassxc repo is getting all the bug reports for it. Their stance is “it will go away in a year or so”

Regardless of whether or not it is a good idea, it’s undeniable that Debian makes a lot of decisions that negatively impact their upstream. And since it’s someone else’s problem, oh well.

There is a reason upstream repo maintainers wind up angry about problems that someone else caused.

In pineapple express they call it “the dopest dope I ever smoked”… But I now realize that movie is almost 20 years old.

A lot of people don’t know this though. They think it is the “won’t fall over” type. They hear “use debian over ubuntu, because it’s more stable” or “use debian for servers, because it’s more stable” and think it means “You want uptime, so you dont want something crashing”. So when they see a bug, it is concerning to them. A distro focused on not falling over must super care about reducing crashes, and don’t realize the exact opposite is actually true. The bug was fixed a long time ago, but you don’t get it because “don’t change” is more important than “don’t crash”.

If the bug is in a popular package (ie, a super common screensaver) in a very popular distro (and a lot of people have chosen the distro because they think it has less bugs than others), I can imagine the maintainer getting fed up with the bug reports for a bug that was already fixed.

Most people I’ve seen on Lemmy understands that “stable” means “unchanging”… But every person I’ve talked to outside of lemmy, thinks it means “less bugs”. So clearly it’s a very big misunderstanding (Which is basically confirmed by the fact that xscreensaver gets so many invalid bug reports that they felt necessary to do this.)

If you received constant complaints from users about bugs that you had resolved years ago, but package maintainers refused to package, you’d probably get sick of it too.

Daniel Stenberg (author of curl) has blog posts about how everyone in the world uses curl, and as a result include the curl license in their readme, which means he gets mail from people upset about their car not working.

Steam had a big thing recently because the snap of Steam is not official. But yet, they get a TON of bug reports for things that are only broken in the snap.

I imagine having the same conversation of “That bug is already fixed as of 8 months ago” “Well how do I install the latest release?” “I dunno, talk to your distro about that” on a super regular basis, it starts being something that is incredibly infuriating. No one wants to take the anger of aggressive upset people, especially when the fault lies with someone else. He has asked Debian to stop shipping out of date versions of his software in the past. But because open source, they are not obligated to, so he has very limited ways to protect his own interests.

Your issue sounds like it’s with Debian for shipping incredibly out of date software and putting jwz into this position in the first place and not with jwz.

This is a daily reminder that “stable” means “unchanging” and in no way refers to the quality of the code. It doesn’t mean “won’t fall over”… That’s a different type of stable which debian stable absolutely does not guarantee.

A bug in debian will remain present in debian until the next update a year from now. If the bug breaks your workflow, then find a new workflow or a new distro.

Interesting. I upvoted because I saw this 11 years ago and it made me nostalgic. 11 years is a huge gap in repost time.

I was at a track meet once and the lady running high jump was doing a horrible job. She was finally figuring out what she was doing and said : OK, we got this. Next height will be 5’12"

When you’re a trans teen from OK getting beaten to death by classmates, the culture war feels a lot more urgent to focus on in the moment. Survival isn’t something you can be passive about.

Some people partake in the culture war as part of manipulation by the rich… Some people are forced into it by defending themselves from the first group. And some people are compelled into it to protect the second group.

While you’re not wrong about how we got here, it feels like it would be too easy for one side of the culture war to spin this as “Ignore my bigotry, Wall St is the real enemy!”

He saw himself having an epiphany about privilege in general, so he had to swerve and add race into the mix so he could say a true (albeit unrelated) thing and miss the point.

It’s like when anti BLM people say “All lives matter” … Sure, all lives DO matter, but they’re intentionally missing the point, so they don’t have to acknowledge that police brutality disproportionately affects black lives.

Saying unrelated “true” things to undermine the original statement is a bit telling about intentions.

My dad once told me my mom didnt feel safe walking alone at night in the neighborhood and asked if I felt the same. I said I didnt feel any concerns, but added the caveat that Im not a small woman, and Im a large man.

He paused for a minute, nodded and said “that makes sense.” Then after another few seconds goes “That’s not white privilege.”

The internet and cloud points are my favorite. Specifically the fact that those things are out of the picture.

No VLAN configuration necessary. The hub is “the VLAN”. They literally can’t phone home because they have no route to the internet, with no extra setup necessary. For WiFi devices, I have to make sure they’re connecting to the right VLAN and controlled properly, and if I misconfigure something, they are phoning home or joining a botnet.

(This stops being as applicable if you have a sketchy hub you don’t trust, but I trust deconz and ZHA fine enough in this context).

https://www.youtube.com/watch?v=wKegmu0V75s https://www.youtube.com/watch?v=-IjUryQOlgk

They love taking money and then not delivering products in a timely manner and they take several months to issue refunds as well. Probably among other things.

I switched to FreshRSS which works just as well, and doesn’t have a toxic dev

Refreshrate is the magnet probably because it feels like the only one that isn’t covered by “yeah, ubuntu is shit. I agree.” And I understand fully how much refresh matters. I use 144 and 240hz monitors because low refresh bothers me. It was intended as less of a “this shouldn’t bother you” and more of a “this is an edge case feature that not even my blu ray player handles, and that’s built for the specific purpose of watching videos.” It’s purely a use case I had never heard of before, so declaring Linux not ready for desktop over a completely niche feature feels unfair. (But again, I would check for Xorg vs Wayland)

Ubuntu has been moving more and more of their software away from deb packaging and towards “snaps” which are their own thing. And snaps are terrible. imo, Canonical is basically trying to figure out how to turn Ubuntu into a walled garden like Microsoft and Apple have.

So Ubuntu handling it’s packaging poorly and having out of date software with poor configurations doesn’t surprise me at all. I can’t counter your argument there because I agree with you that Ubuntu isn’t good for desktop. I’m not ignoring those issues, I’m agreeing (just about Ubuntu, and not necessarily Linux as a whole, which has a separate set of issues, like driving you towards Ubuntu in the first place)

“Stable” here means “unchanging” and not “crash proof” unfortunately. Shipping software that is already 1-2 years out of date for a server that I intend to stay up all the time means that by the time I get a chance to run updates, the software is even more out of date.

The OP’s SMB issue is exactly the kind of thing that would be WORSE on debian. “We’re going to stick with SMBv1 by default, because not changing it is more ‘stable’ even though it’s incredibly out of date”

And now you are stuck with this decision because you can’t afford downtime on your server to resolve it. Shipping drastically out of date software isn’t always a good thing either. Refusing to ship SMBv2 (again, I don’t know what version of SMB Debian ships, using this purely as an example of the type of thing they do) in the name of “stability” even though it solves a ton of problems with SMBv1 is not a good experience.

They try to backport security fixes, but there are times where those get missed, and it also means that they aren’t backporting bugfixes that they don’t find “critical” enough.

So yes, Debian is only good for the scenario where you would prefer to have the same bugs for a year on end because “unchanging” is more important than “up to date, and patched”

I understand that 24/60 doesn’t divide evenly. My point is just that televisions don’t have this feature either. When I watch movies, even if the source is 24hz, my TV stays at 60hz.

Either way, there certainly is “an API” to do it. With xrandr you can just xrandr --refresh 24 and it would work. It’s something that is absolutely doable. Whatever xrandr is doing clearly the X server is exposing ways to change it. So anyone saying “X can’t do that” is probably wrong.

I don’t know much about Ubuntu other than everyone recommends it because it’s overly simple and then inevitably things go wrong with it and it’s impossible to fix because its overly simple. If I had to guess, this is something specific about Ubuntu and it using wayland by default. Wayland is the X replacement, so any fixes for Xorg refresh rate changing definitely don’t apply.

Potential solution : if you log out, on the log in screen it should give you an option of which desktop environment to log into (a gear in the bottom right corner with an option for “Ubuntu on Xorg”)…

It’s possible that Ubuntu has removed this option recently. Wayland is the future, but it is different from X and not all software is ready for that change. My guess is that the checkbox in Kodi uses the Xorg APIs to change refresh rate, and Wayland doesn’t use those APIs, so it just doesn’t work. Wayland is in awkward teenage years where it’s trying to pretend like it’s ready to take on the world, but it’s got a lot of rough edges still.

I would say that refresh rate changing doesn’t really reflect on “linux on desktop” (a normal desktop use case doesn’t have refresh rates changing regularly), but rather “linux as a HTPC/media center”. And furthermore, most of your complaints are specific about Ubuntu. The biggest “Linux has issues” problem is that people are still using Ubuntu and picking a distro is way too much work, and the wayland transition is breaking some functionality of some software that hasn’t updated yet.

I would like to point out that you have come into a Linux community and lead off with “this is a terrible experience” and then described quite a few issues that either “Ubuntu” (not “Linux”) issues or otherwise somewhat non-standard uses. So if you’re getting a weird mix of “defensive,” “agreement that Ubuntu sucks, use something else,” and “utter confusion about the use case” … its probably the way the conversation started.

Also, this wouldn’t be the first thread where someone shows up and complains purely on the basis of “linux isn’t windows” so the community is already primed to be agitated about threads like this. Kneejerk reactions aren’t the best, but I’m sure you weren’t trying to come in here and coming across as aggressive either.

I have literally never in my life had my monitor’s refresh rate switch to match the framerate of the video I’m watching. What refresh rate was it, and what’s the framerate that you wanted it to match? I’m trying to wrap my head around what it is that you’re watching that just letting the screen refresh at 60Hz or whatever speed it was going at won’t cut it.

was also heavily wondering this. Most TVs don’t change their refresh rate to their content. they just output 1080p 60hz (or whatever) and only do the updates every 24hz and will just double up frames. Expecting to change your output based on the content feels real weird.

if this person has stuttery video, its something else or they have a very niche use case.