Lichtblitz

The issue isn't the numbers. The issue is that Musk previously claimed Teslas would retain value and would even gain value with new releases of auto pilot. With these expectations in mind, the numbers must look abyssal to Tesla fans.

No, that's ridiculous.

This Regulation does not apply to the processing of personal data: [...] (c) 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.

Also, revolt self hosting is broken. The web call functionality (WebRTC) is being rewritten but that effort is stale and out of the box it simply does not work. There is no real documentation about this either. It just won't work and you need to invest a lot of effort to figure out why. The moment self hosting properly works, I'll give it another shot. Not being able to connect without a fat client is a show stopper for me. There's no way I can get enough traction for my groups if the barrier to switch is higher than a sheet of paper.

When self hosting all the shortcomings you mentioned are perfectly acceptable for me.

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.

Many of the suggestions in the comments make sense and will work for some children. Just keep in mind that every child is different and during some developmental phases things can shift and change significantly. Just because something worked for other parents, it may do the exact opposite for you. Sometimes being patient and waiting for a phase to pass is the only thing that works. It can take a week or two and in some extreme cases months or even a few years. Also keep in mind that trying something different every day will likely make things worse. Try something and (gently) stick with it for a while before evaluating.

Good luck!

That's what containers are for. Fucking up the container won't fuck up the host. That was the best decision in self hosting I've done. Even that one virtual machine feels weird and uncomfortably legacy now but it needs to interact with hardware in a certain way that just won't fully work with docker.

Blue Byte's "Albion" https://en.m.wikipedia.org/wiki/Albion_(video_game)