No, that’s ridiculous.

This Regulation does not apply to the processing of personal data: […] © by a natural person in the course of a purely personal or household activity;

As is stated, the call is processed locally in the user’s device. If that holds true, there is no recording and no third party processing going on. Your point does not make sense.

That’s a real world issue. AIs training on each other’s output and devolving because of it. There will be a point when vendors infringing on user content and training their AIs with it will leave them worse off.

It’s easy to train a model to do exactly what you want and have the seeming “personality” that you want. It’s just incredibly expensive. You need to vet and filter everything that you use to train the model. That’s a lot of person hours, days, years. The only reason the models act the way they do is because of the data that went in to train them. If you try and fit the model after the fact, it will always be imperfect and more or less easy to break out of those restrictions.

Don’t shoot the messenger. The regulations are pretty draconic. I have to ensure the training for that every year.

As a software dev myself: if time in your application’s internals jumps on DST, something has been implemented incorrectly. That’s what zone information is for, to make times uniquely identifiable and timers run the correct length. Getting the implementation right is hard, though. So, abolishing DST is very well worth it.

Seemingly one of the contributors has visited a disputed region and logged into GitHub from there. By law (export controls) Microsoft must not provide service to that place. So some automatism flagged the account and also the organic maps repo. So far so normal. But either Microsoft dragged it’s feet in communicating and resolving the issue or the organic maps team was not doing their part in the process. Doesn’t matter, the outcome is still worth it.