Antergo

Consent does indeed have to be given, not assumed. But "legitimate interest" cookies do not need consent

I don't think it will ever come to a lawsuit, nobody would ever want that. Under the GDPR you must be able to delete content, and the server must communicate this to all federated servers. So in effect, there is already a legally binding agreement between all servers that this deletion request must be honored (for people physically in the eu), it's just not.

lemmy servers are already breaking the GDPR if they don't follow forwarded deletion requests from people in the eu. This would just effectively be an extension of this to data from all people.

There could be a legally binding contract stating that any deletion request must be forwarded to all parties it was send to, and that upon receiving such a request the data must be deleted. I do not think this would be unreasonable to ask to servers, especially as this deletion receipt could be fully automated.

You can use wireless ADB, or try to set the battery limit to 80% and only set charging to only start below 30%. Wireless ADB settings can be found in the developer options. battery options don't always include the option to require battery level to drop below X% before charging starts again, and if it is, it is usually branded as battery saver feature or smth like that.

Toto, and civ 6!

I drew the arrow one way, just because you want to invert the arrow doesn't mean it's correct 🤷

Thats not how economics works, if the cost of a product goes up one way or another, the price goes up, one way or another

I mean, the dilivery company will have to pay for the damages. It's just scratches, probably a conversation starter of someone sees it haha

Every car maker did, VW took the blame but the whole industry was lying

Paper and cutting boards come from the exact same trees. However when I tell you to use a cutting board instead of cutting on the table, somehow everybody knows that they shouldn't use paper

I can really appreciate the performance is (should) be the same, makes a lot of sense

Gtk 3->4 made a lot of internal changes, and at least some were related to making wayland work. Wayland "worked" in gtk3, however it was very much an afterthought, and half the toolkit was useless under wayland. Other changes are usually required for changes related to rendering, gtk4 had vulcan rendering which may require some breaking changes. Another thing is just general breaking changes that are good, sometimes you realise some decision was bad, and a new major release is just a way to make these.

From the end users perspective nothing much changes, it maybe looks a bit different, but not much besides that. But a vulcan renderer and being fully wayland compatible are major improvements that also improve the user experience, even if you don't notice directly.