Have medical researchers not heard of gitignore? Any hypothesis about the mechanism here?

Absolutely not.

I wish everyone knew the difference between patents and copyright.

You can download an open source HEVC codec, and use it for all they care according to their copyright. But! You also owe MPEG-LA 0.2 USD if you want to use it, not to mention an undisclosed sum to actors like HEVC Advance and all the other patent owners I don't remember, because they have their own terms, and it's not their problem that you compiled an open source implementation.

Thanks for the link!

Hi fellow Kate user. I agree.

Ah, much better source: iOS is the answer to where the vulnerability was – right in the headline. I could not find that by searching for the usual keywords in the original post.

What a 90s thing to do! Shrug!

fast forward to the 2020s

Is there an app for that? I don't know how to put a shortcut on the a desktop anymore.

I thought so, but that's what I came to the comment section to know ;-)

Setting a variable by split identifier is surprisingly common in CMake (because functions can't return a value):

> set(${VAR}_VERSION ${VERSION})

This is the main reason I don't like CMake.

But not all governments, thankfully. Remember DVD-Jon? He won the trial for breaking DVD crypto, because consumer rights stood above trade secrets.

I see this as an attempt at a lesser evil, and I would support that (see my EME DRM comment), but I have one concern:

Does this new "privacy preserving attribution" feature respect multi-account containers? Or is it somehow not considered necessary, because it's meant to be less invasive than the tracking cookies it's supposed to replace? Call me skeptical for now.

I'm a happy user of multi-account containers, which lets me separate my cookie identities in Firefox. Before, I had to use different browsers for work and private, and yes, it solves this problem, but the best part is that I don't have to worry about tracking cookies, because they aren't tied to my personal accounts: In my experience, I can to a great extent escape the echo chamber I'm in, and the ads I see in it, by just deleting the cookies of my sacrificial default container.

Other than that, considering the status quo – that the web is already an unfriendly GDPR nightmare, I'm positive to the initiative. And because of the power of the default, I can understand that the feature wouldn't likely take off if it was opt-in, so I won't criticize Mozilla for that move either.