It sort if have to be. In the end there has to be one source of truth for each TLD, otherwise who is to say who owns foo.com, and what it resolves to?

And then the same structure for assigning TLD ownership.

But there is nothing stopping you from running another DNS service, call it DNS2 with different root servers, etc. It is just going to be extemely hard to convince people to use it.

I never recline my seat, but if I was sitting infront of that guy I would move it down for a bit. Then up again. Then down again. Etc for however long the flight is

Yes, but it is also very different. I have a VR headset and use it every now and then. But compared to “normal” gaming it is quite different.

When playing a non-VR game you can just minimize the game and check stuff between rounds/matches/when you pause/etc. With VR I feel like you have to be there all the time, and the headsets are still heavy so you can’t play as long. Not to mention you are usually standing.

I like VR and think it will be good eventually, but it is not there yet. It is 100% playable as it is, but the overall tech is not quite there yet.

The first half of the page is AI/ads, and the rest is SEO optimized trash.

If any other search engine was worth any time, then those would be full of SEO as well. SEO is a huge buisness and as long as people just click on the first or second links (yes, they do) then it will continue.

Google and other search engines can try to combat it but as long as the money involved are good, it will not go away.

This is just gambling, betting that you’ll cash out before everyone else, but after the price has run up.

Even worse, it is unregulated gambling. In normal gambling there are rules. Yes, the house will always win in the long run as the odds are in their favor, but the game is set up in a transparent way and doesn’t change half way through.

Also the original idea of cryptocurrency was never speculation and cashing out. But sadly it has turned into that in 99% of the time.

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.

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.

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.

Security is hard. Especially at the scale of those companies. Since they are big, they get a lot more hacking attempts. Makes more sense for bad actors to attack someone with millions of customers than your mom & pop store that might have hundreds, if everything being equal.

More and more people and compa ies wants to store things “in the cloud”, (read: someone else’s server). It is for the most part a good thing as it makes it easier to access, but it also opens up bigger and other attack vectors.

So, I think the number of breeches will only increase. Not always because the companies have bad security (though sometimes it is 100% that), but also because the attack vectors keep growing due to changed business decisions and user preferences.

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.