Subscription based teeth?

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.

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

Diverting is really expensive for the airlines, so you know they only do it if there is no other way. So it can't just have been a bit of a bad smell...

The problem is that it is almost always just one lf them. Let's say that v0.20 is called "Fuck Spez" and v0.21 is called "YouKnowWhatFuckMuskToo".

Most people are going to refer to them by either the number or the name, almost never are both used. The biggest problem with names is that they are rarely sortable (google did it with android, for a bit but not anymore), so in the future it is hard to know which is which without resorting to looking at a list of releases.

For example, in the future when we are on v0.30 someone might say "ah, but this has been an issue since "Fuck Spez"." And then most likely you have to look it up to know what they are talking about. If we coulld force everyone to alwaya write "version "Fuck Spez" (v0.20)" then it would be great, but that never happens.

I personally prefer just semantic versioning for this reason.

GPG signatures are set by the sender to prove the message is originating from the sender and is unchanged. It's signed with the private key and verified with the public key.

A bit of a nitpick, but important to keep in mind. The GPG signatures shows that someone that has access to the private key sent that message. If I somehow gets a hold of a copy of your key, I can send messages that seems to originate from you.

Just the ads, and you can't turn them off. Ever.

Have to be careful to not upset Big Wheel

I got super tired of google a few months ago. "Ah, you searched for these terms. But I am going to ignore that and instead show you results for these diffetent ones, because fu."

So I started using bing instead, I wouldn't say it is worse. Just differently bad. Some search things are much worse, some are much better.

Quite annoying how they keep pushing for "AI" all the time though, so might go back to google soon anyway.

I think it has the hallmarks of a classic hype cycle.

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

We are probably at around the peak of the hype cycle now. I am preparing the popcorns for when the next phase hits.

I seem to be at around 100 already, though some of those are probably already dead or moved to another instance.

But the easier it is to migrate the more people will do it, if that is the goal.

That is great, but it should ideally be built into Lemmy itself and not an external script that may or may not steal your credentials.

Just two buttons in the settings "Export User Data" and "Import User Data" would be enough.