gnud

Seems like the owner of the github repo claims copyright, though. Since they provide a license.

For Knuth's sake: The GDPR is NOT about cookies! The older 'cookie directive' is also NOT about cookies! They're about a third party storing their data on your computer, or storing your personal data on their computers - no matter what technology is used.

Nothing in the GDPR stops websites from honoring "Do not track" and then _not asking_ if it's present. They don't have to ask if they don't track you! They don't have to ask for a technically necessary session cookie that appears after you actively log in!

Websites ask because they want to track you! A 'law targeting browsers' would not help because people would say no to cookies, and then websites would ask about some other way to track you. Because they want to track you.

Switched from Gmail to Fastmail about 10 years ago.

2-3 spam emails slip through every week, and sometimes a false positive happens when I sign up for something new. I don't see this as a huge problem, and I doubt Gmail is significantly better.

Pretty sure Zed won't let me pay for an editor without any "sign in" or LLM features?

The 'no to tracking' cookie doesn't need to be identifiable in any way.

Luckily, GDPR isn't about cookies, it's about processing personal information. Doesn't matter if you use cookies, localstorage, or carrier pigeon.

The older EU 'cookie directive' only mentions cookies as an example of storage in a footnote. The regulative is actually about any storage on the users computer.

Marketers would like you to believe that the stupid banners are about cookies. They're not - they're about processing your personal information.

This will give more resources to tenants that schedule more jobs.

If tenant A schedules 99 jobs and tenant B schedules 1 job, a "fair" algorithm would pick B's job either first or second, RANDOM() will not.

I'm assuming they disallow bot use in their TOS. So they can probably offer unlimited searches that you run yourself by typing in the terms.

Spam texts are not really a thing here in Norway, either.

I do get three to four phonecalls from spoofed UK numbers every month. I havn't picked up for a year or so, but last time I did, it was a fake "Microsoft Support" scam.

It's actually less of a risk than I thought, because the configuration is on your local install of KeePass, not in the database file.

If an attacker can modify your local install, you've lost anyway....

As I understand it, if you modify the xml, Keepass will silently export entries in the database once you load it (by providing the password).

Keepass will (by default) not ask for the password a second time before exporting - but you have to decrypt the database once before it can be exported.

So this is not a risk if your threat model is "attacker obtains a copy of my .kdbx", but it is a risk if your threat model is "attacker can modify .kdbx without me noticing, and can access my local computer or a mounted network disk to read the exported passwords".

You can approximate something by defining the valid TokenTable keys as an enum, and using a mapped type for the actual TokenTable type.

There's some boilerplate in the definition, but it's fairly clean and non-repetitive. And easy to use in the "client code".

https://www.typescriptlang.org/play?#code/KYOwrgtgBAKg9ga1AS...

Really not a lawyer, and not in the US, so not sure I understand the 'work for hire'. But 'work for hire' requires some sort of employment contract, surely? And the pay was part of that contract?

So if Disney doesn't uphold the contract, doesn't that mean it wasn't a work for hire, and therefore the copyright belongs to the author?

An Armbanduhr is a wrist watch, not just a watch. I'm sure the Germans often shorten to it 'uhr', just like the English do.

Capital is short for capital city.

Vacuum is also short for vacuum cleaner.

I'll grant you Aussehen - that's a single word in english. But longer than the German one.

Also, "consent" has a specific meaning in GDPR, see article 4(11) [0]:

> Consent of the data subject means any freely given, specific, informed and unambiguous indication of the data subject’s wishes by which he or she, by a statement or by a clear affirmative action, signifies agreement to the processing of personal data relating to him or her.

Which is why I suspect almost all "cookie banners" are worthless. They don't give a clear, informed consent, so the site operator is still not allowed to use the data for anything at all.

0: https://gdpr.eu/article-4-definitions/

I've never actually used these, I just knew they existed. I found them via DuckDuckGo, in the github repository of qBittorrent. They have a step-by-step guide for using them, without mentioning kdevelop:

https://github.com/qbittorrent/qBittorrent/wiki/Setup-GDB-wi...

As I understand it, you can plug in the qt pretty printers from https://invent.kde.org/kdevelop/kdevelop/-/tree/master/plugi...

> My code is not theirs and this is the core issue.

This is _exactly_ why a lot of jurisdictions assign/assume copyright by default, and make it hard to 'remove'. Otherwise authors would see their work ripped off in a lot of inventive ways.

When the default state is that every work is copyrighted, that removes a lot of possible confusion, and possible excuses.

It's a fine article, but not a fine introduction. I read more as a list of all the things the author didn't understand (or pretended not to understand), because they couldn't describe them mathematically.

I assume it's written partly tongue-in-cheek, to show how arbitrary a lot of music tradition is, and how it creates a barrier to entry.

And the article didn't even mention different clefs or transposing instruments!

Professors could change the numbers in the questions every year, without really changing the questions.

And then give the answers after the homework was handed in, if they want to grade the homework. Or compromise, by giving answers to half the assignments, and not grading those.

This sort of regulation is not new when it comes to health data. I'm actually surprised storing medical data outside the country was legal in France at any point, I don't think it would have been in my country.

So blaming the GDPR and new rules, seems a bit weird in this case.

Now, consumer protection regulation is always a balancing act. And most consumer protection laws will hurt some companies that didn't actually do anything bad. That doesn't mean I don't want any regulations. Particularly when it comes to healthcare.

I clicked around a bit trying to find out who creates and runs Session. And of course it's built by someone pushing a new crypto currency. That made me really really sad.

Fastmail handles my email anyway. So there's no extra risk in having them manage som extra email aliases.

Storing an IP address in RAM until you have sent the response is _obviously_ a technically necessary use of personal data.

But who knows what else google does? The "privacy info" for site owners using google fonts says nothing about what they use any collected data for.

When you share personal data about your visitors with a data processor, you need an agreement that specifies how that data is treated.

Using a third party is not illegal in itself. But you need an agreement with the third party as to how they will store/process any user data they collect.

This is fairly fundamental under GDPR. It's the 'data controller'/'data processor' split.

I suspect (but IANAL of course) that most CDNs would fail here, because the blanket agreements they offer are basically worthless.

But it's easy to imagine a CDN that has a different business model (charges a tiny amount pr. resource stored, for example), and is completely fine under the GDPR.

This filter seems to work for me, but it'll probably break soon.

    ##:xpath(//div[@role="feed"]//div[.//a[@aria-label="Sponsored"]])

> No installation makes an app better.

Yet Another Account makes an app worse.

> Simple collaboration and sharing with anyone, including people on weird devices like Chromebooks, makes an app greater.

Web apps usually only lets you share within the app. You can't use the data in ways not imagined by the developers, and you force the app onto those you want to collaborate with.

> Automatic updating makes an app greater.

Not really, no. It usually makes me worried the developers will pull the rug out under me.

It wasn't meant as dismissive of the project. It's totally fine to write a UI library that has another focus (games, for example). I'm just tired of those projects being suggested as alternatives to native/GTK/Qt in discussions here and elsewhere.

If Iced actually gets cross-platform accessibility support, that's great! Very few projects have that today. More certainly wouldn't hurt. But until it does, you shouldn't base a DE on it.

Edit: The issue you linked to is about RTL support. That's also required, but doesn't touch on a11y.

I'm assuming Iced has no A11 support (these projects never do). Probably no RTL support. Possibly no reusable "system" widgets like open/save dialogs.

> video based tutorials

there's your problem.