“Thread closed due to inactivity.”
“Thread closed due to inactivity.”
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?
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.
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).
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.
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.
Or maybe it is a feeble attempt to annoy people that sign up with foo+service@somewhere.com
and then sort it into different inboxes (of course you can filter on other things but + is built into gmail). You can also use it to see who sold your info when you get spam on that adress.
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.
SSDs have a limited number of lifetime writes.
Yes, but in the real world it is not a concern. The number of writes you can do is so huge that you will never come even near it, and the speed boost from SSD far far outweighs it.
If you live in a city and have no backyard or similar, you should not be allowed to own a dog.
Yes, and it also pioneered many features we take for granted now. Like tabs, customizable interfacez etc.
But now it is just a reskinned Chrome.
That could be a workaround. Also maybe include a “edited” text or icon
A lot of non-bullshit answers for games link to reddit, so I still have my account logged in so I get old.reddit when I click them. When they decide to kill that one I don’t know what to do.
Recruiters can’t see the difference! (Ok, not all but a worrying high percentage)