No, it isn’t.

There are different names for different airlines, like economy plus or extra. Usually it means something like a bit bigger seats (usually not lie flat though), a less crowded section, better food, etc.

But then it is the developers fault, never management

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.

The same goes for pretty much everything in life, not just games. It might suck in the short term, but just don’t put up with friends/partners/jobs you don’t like. Make a change

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.

What I meant was that if you are returning 404 for example when a user doesn’t exist. You can’t tell if the user doesn’t exist or someone changed the API to remove the endpoint.

But forcing HTTP codes without a moment to think it through seems to be the new fad.

The clown, but flipped with a success field. If it is true then command succeeded, if it false something was wrong and there should be an error field as well.

HTTP codes should be used for the actual transport, not shoe-horned to fit the data. I know not everyone will agree with this, but we don’t have to.

Rounded corners tho… <shudder>

Just a small gif (as png didn’t exist/widely supported) that had the rounded corner. Then if someone wanted to change the color or background you would have to redo all the images. Fun fun.

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.

Must be some weird AI bug, because in defensive wars you almost always get your allies to join.

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.

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.

Different workflows.