It was probably used for spam in the past, so they added a rule to trash all links to that domain.

I don’t mind it either, they need some way to finance the development. However I wish they would make packs of older DLCs and sell those cheaper.

For example in Europa Universalis IV you need a whole bunch of DLC, and buying seven 5 year old DLCs for full price is just not very appealing. Sure, you can try and wait for sales but they are not always available when you want to get them.

No, the main point of standing desk is that whoever has one talks about them all day, every day. At least, that was my experience 10-15 years ago, which was the last time I spent in an office.

Subscription based teeth?

Accidents have minor consequences compared to GTA IV.

I agree with you I much prefered the driving in 4 over any other that I can remember. However, one really weird thing was that sometimes you could hit a curb at relatively low speed and you would fly through the windshield. Other times you were totally indestructable.

For every FFF we are moving closer to bob & angels

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.

That seems to be the general atmosphere, “leaving money”. They probably analysed it and thought it wasn’t worth the effort. Companies like to make money after all.

You still need to keep supporting it for future releases, make sure it actually works and not just builds, test, update QA pipeline, tell support, etc etc

You are getting downvoted by people that have no idea how software development and maintence works.

Every feature cost. More than most people realise. Both in development time and to maintain it over time and releases. It all adds up, not saying EA are correct in not supporting it. But to think it is free is just incorrect.

They made a business decision to not support it. We think it is the wrong decision, but it is ultimately theirs to make.

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.

now that IPv6 has been adopted globally.

Now that is a quality joke

I think a better, but still not perfect, way to define it would be “This person wants to do X, but can’t support him/her/itself doing it.”

Of course, if you are already rich it doesn’t matter and then it is a bad metric (one of the reasons it isn’t perfect.) However, I think it is a better way to define it. Someone writing a few books as a hobby and then stops are not a failed writer, but someone that wants to be a writer but just can’t support it is.

Basically I think the intent matters, but that is impossible to measure (and people lie about it). So being able to do it as a profession is an ok metric.

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

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.

You can export the list of subscribed communities in 0.19.

If you do that every now and then a shutdown would still hurt. As all the communities hosted on it would be lost but at least you can import your subscription list on another server.