Meanwhile, .tech exists and is not country-specific but is far less popular for some reason.

Simple answer: length.

Two chars look a lot better than something with more chars, and all two chars TLD are ccTLDs.

Only issue I see is that the 8 chars required is very short and easy to brute force. You would hope that people would go for the recommended instead, but doubt it.

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.

Sometimes they can be challenging or overgrown, so you have to know what you’re doing and be prepared to turn back if necessary, but I owe a lot of truly incredible experiences to this app.

Since it uses OpenStreetMap you should consider updating it for others later. Don’t think you can do it in Organic, but it can be as simple as in a browser adding a note to a trail about what state it is in.

And ethernet port!

“Thread closed due to inactivity.”

And if it succesful, or at least passenger doesn’t boycott them over it, it is just a question of time until other airlines adds it as well

That is still source code, obfuscated but still source code.

Counting in lines of code is the most stupid metric.

It works quite fine, use it daily. Well, XMMS2 to be pedantic.

Just some shellscripts bound to windows-keys to pause/play and load new files.

The question is whether x86 is even relevant anymore

Also RISC-V, though that is probably a few years away at least.

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.

It is still just a “trust us” deal. They say they have deleted it, and all you can do is trust them. They could possibly get into legal troubles if it was shown they were lying, but that could be easily avoided as well.

GDPR is ok, but much of it is based on good actors doing what they should.

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

…and when they don’t pay Discord under the table. Discord wouldn’t be unique if this was the case either.

I don’t know where you are getting those numbers from. Most put chrome in around 78%, edge at 10% and then everything else. And all chrome re-skins are just that, google still controls it. There is a reason one of the biggest software companies in the world just gave up their own browser engine and runs a competitor’s with some face paint.

Google are in a far better position to push something like this through than Microsoft ever where, due to their near monopoly on searches. Any site not using it would be more or less dead. Just going from number 1 to 2 on a google search can mean a huge drop in traffic, and then imagine not even being on it at all.