It doesn’t really matter how you measure it, number of flights, duration, distance traveled, etc… No matter which, air travel is by far the safest option. The only other that comes anywhere near is trains. Going by car is bad (though motorcycle is even worse), but so many are afraid of flying that they instead takes the car. Which is among the worst things you could do from a safety point of view.

Humans are awful at accessing risk and chance, one of the reasons casinos and lotteries thrive.

Look at fear of flying for an example, all statistics say you are many many many times over more likely to get into a car accident on your way to the airport, than during the flight. Even when the ride to the airport is usually short and the flight very long. Yet people are afraid of flying, but not going by car. By percentage, there are of course those, rightly so, afraid of cars as well.

I open the series folder from the mounted network share and watch it in VLC.

Similar, but I have a RPI by the TV running LibreELEC and Kodi.

The unstable part is just compared to other versions of Debian. Every now and then a package dependency breaks, but usually nothing serious and you can still use the system until it is fixed within hours. It is not like the system will constantly crash, it is still linux.

I have used sid for years without any major problems. Usually only on desktop though.

Pretty naive to think someone isn’t doing it already, but as someone else said you don’t need to shutdown for it. Infact it is worse if you shut down as you don’t get new data.

It should be doable to so some audio analysis of the episodes. They “always” (I am sure some forget every now and then), have an outro and intro around the ad block. With a clearly defined jingle per podcast. You should be able to make a program that analyses the audio and listens for that block and cuts it out for you.

Nice rack!

That exact same phrase is used in a very different context in other communities!

Yepp. Started using Debian around the Ham/Slink releases, haven’t found any reason to change yet.

More often than not that is corporate speak for “we fired the old team and replaced them with cheaper workers. And we didn’t want to pay them to learn the old code/they tried but failed, so we are dumping features now”

Missed to change the legend to “North Canada” or just simply “Canada”

Re: Downvote bots. I can’t say they’re necessarily bots, but my instance has scripts that flag accounts that exclusively give out downvotes and then bans them. That’s about the best I can do, at present, to counter those for my users.

It is usually not a good idea to specify what your exact metrics are for a ban. A bad actor could see that and then get around it by randomly upvoting something every now and then.

There is also the risk of homograph attacks. The link below is for domain name encoding via IDN, but the same applies to usernames. You could easily impersonate another user by having chars that look similar.

https://en.wikipedia.org/wiki/IDN_homograph_attack

Sure, but even if they started tomorrow it would probably be years before it even could be considered experimental outside of the most daring early adaptors.

Having a combability layer is not ideal but it would mean they could have something worker for more users faster and at the same time see which modules/drivers they should focus on.

“Thread closed due to inactivity.”

He could have handled it better. But he didn’t call the code crap directly, just the bundle of everything.

Having a meta package and let users choose seems like the best way. But this is a Debian issue, and not a keepassxc issue. It is up to Debian to package it anyway they want.

Exactly. And if you want those features, you install the full version. Packages can break in sid, that is the whole point of it.

I am also running sid and keepassxc and I see no problem with this change. In fact it seems like a very sane thing to do, and something I wished more packages did.

Why not just go full WSL?

Most of those cookie banners are not even needed, you only need them for tracking cookie, not login and session cookies. But of course everyone decided it is just easier to nag all the users with a big splash screen.

A lot of them are not even doing it right, you are not allowed to hint the user that accept all is the “correct” choice by having it in a different color than the others. And being able to say no to all shouls be as easy as accepting all, often it isn’t.

Basically, cookie banners are usually not needed and when they are they are most often incorrectlt designed (not by accident).

Then the bot would be useful, now it is just spam. If you want to watch it somewhere else: Use a browser plugin for it, don’t spam every thread.

Or maybe it is a feeble attempt to annoy people that sign up with foo+service@somewhere.com and then sort it into different inboxes (of course you can filter on other things but + is built into gmail). You can also use it to see who sold your info when you get spam on that adress.