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.
…and it drives me insane when it is not real links but some javascript/button/div-with-onclick/etc and middle click won’t work
“Thread closed due to inactivity.”
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.
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).
The original idea was to take back control of our money from greedy and corrupt banks and politicians. Very very very few people use it as that now though. Most just see it as a get rich quick scheme.
As we are in the privacy sublemmy: All of the privacy issues have already been solved, those that keep saying that it is a log of everyone you ever paid kept forever have no idea what they are talking about. Just simple thing like that you should (almost) never use an address twice removes a lot of the privacy concerns. There are also other ways to obfuscate and stay anonymous.
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.
You would need to specify the new port when using ssh (using the -p$PORT option).
You can put a host entry for it in .ssh/config specifying the port.
Some countries have different age restrictions for hetro and homosexual encounters too. Not to mention that in a lot of countries it just outright illegal, and everything not condeming it can be seen as encouraging it and hence illegal too.
We humans make some weird laws around sex.
In some countries all forms of description of underage sexual activities are illegal. So the sentance “She was having sex” is perfectly legal, but add an age marker and it is illegal. “She was having sex on the day before her 18th birthday”.
It is hard to legislate around as there will always ve ways to avoid it and get around it. But all this just sounds like the normal hype => fear => hype => fear, etc cycle that all new tech goes through.
But then it is the developers fault, never management