Please point out the actual transphobia? You can’t just use that word willy-nilly.

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…

What a weird set of events. It’s not even clear what was actually used as infection method.

I wonder what they consider deprecated.

Welp, this is the most left field KilledByGoogle entry yet.

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

Alternatively, “I am your father, you piece of shit.”

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

Fuck me, ten years already?

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…

How do these sickos actually find each other and can’t law enforcement go fish in that pond too?

Oh don’t forget illegal spyware and surveillance software.

Already?!

Hello neighbor! I’ve had them prescribed, but when asked if it was really necessary or if I could give it a bit longer to see if my body could deal with it on its own, my doctor got a big smile and told me he could. Then he said that the dominant demographic in my area is very persistent and pushy in demanding antibiotics for the slightest thing so he’s gotten a bit too used to prescribing them.

Used to be Sketchup, not sure if that’s still around for free. Used for a lot of architectural stuff and somewhat beginner friendly.

Me personally I’d use Blender, but that seemingly requires you to learn how to model donuts with sprinkles first…

There might be settings in the bios that allow you to disable the graphics card, not halt on errors or disable the internal screen, but they’re not usually exposed on laptop BIOS, they’re quite locked down.

They might have been required to, under the terms they negotiated.