It’s absolutely fine, it was mildly annoying the first two times and now in glad I don’t have to hold the cap while drinking.

So you’re always behind, patching up small bits of code that don’t comply with your guidelines, while letting big changes with, by deduction, worse code quality through?

You don’t quite understand. One of the major drawbacks of UUIDs over monotonically increasing id’s is the lack of ability to sort them. Not just for manual querying, but for index operations, caching, data locality etc.

It’s very handy and is a big part of the reason why Twitter developed Snowflake IDs, which are basically like UUIDs v6 and v7.

The UUIDs specs are quite easy to understand and definitely not “enterprisey”.

They chose “version” because they are just that, versions. Improvements over the original design that benefit from new insights and technological improvements. We’re lucky they had the foresight to include a version number in the spec.

A lot of people in this thread who don’t fully understand how UUIDs work…

I wonder what they consider deprecated.

Depends on why you want to hide your server ip, what’s your use case? Is it to protect against DDOS?

Cloudflare is evil, but is there any other party you would trust to share everything with?

Don’t worry, it’s fine, there’s nothing inherently wrong with running stateful workload in a container.

You should really back that up with arguments as I don’t think a lot of people would agree with you.

I have an axe to grind with fakespot. My wife has a tiny business and is one of the most honest and sweet people I know. She would never pay for fake reviews and she wouldn’t even have the knowledge on how to do so. Someone (not even us, mind you) posted a link to her product on Reddit and a Fakespot robot instantly called her out for supposedly having suspicious reviews, even though each and every order (and thus each and every review resulting from that) was legit. Her product was then mocked and all it did was give my wife stress.

So yeah, take them with a grain of salt. They are probably pretty good on average but some innocent people get caught in it as collateral damage.

I highly recommend reading the Github thread as this is not at all an accurate representation. These features you’re talking about are off by default. Removing them from the existing package is just breaking existing users. There’s already a report from a user who can’t access their passwords because yubikey support was suddenly removed. You don’t do that to users just because you suddenly develop an opinion as a package maintainer that you feel is important. There was no dialogue, no consideration and a very rude, dismissive attitude of Julian.

https://github.com/keepassxreboot/keepassxc/issues/10725

Noot noot

Maybe they should pretend it’s right next to the WMDs. I’m sure they’ll find it then.

Either you misunderstand or the person you are responding to is. If you retroactively add a license to the current state of the code (for example by committing a new LICENSE file and adding the new license to the top of each file), or course that applies to the entire state of that code as of that commit. What is more difficult is that earlier commits won’t have that license explicitly unless you rewrite git history to make that happen (which is possible but tedious).

You can always relicense code you own the rights to. You can even dual license it, or continue to use it commercially in terms contradicting the license you open sourced it as, as long as you have the permission of every contributor.

The idea that a license added would only apply to code added after the license change is very funny.

Oh no! Anyway…

You do realize that “counting from 1900” meant storing only the last two digits and just hardcoding the programs to print"19" in front of it in those days? At best, an overflow would lead to 19100, 1910 or 1900, depending on the print routines.

Oh don’t forget illegal spyware and surveillance software.

That’s not what using proprietary code means in this case.

Besides, it’s possible they “legitimately” bought a copy of the game from a store that accidentally broke the embargo date. You can’t legally blame customers for that.

You’re not entirely clear on whether you want these services accessible from the internet or just internally. If the latter, change ACME settings to use DNS challenges instead of HTTP. If the former, recheck your dns records, maybe post them here (censored if you wish).

Torrents are usually not downloaded in order but (for all intents and purposes) randomly. That means that, even though 10% might already be downloaded, it might just be the final 10% of the movie (or more realistically, random snippets scattered throughout the file).

There used to be some torrent clients that were able to do what you ask, request pieces in order only, but I don’t know if they are still around and they could potentially affect your download speed.

Fuck rickrolls, I’d hide the EICAR test string and watch their lab computers lock up whenever they try to process my sample.