I had been led to believe that one of Wayland’s strength was solving the correct window coordinates save-and-restore problem. Does someone know what happened here?
It’s literally the opposite. Windows aren’t allowed to position themselves on Wayland (because it’s unsafe or something). Window state save restoration must implemented by the compositor itself. Not sure about GNOME, but KDE doesn’t have that.
Google-certified Android TV devices aren’t known to receive security updates either.
Does it really matter? It’s the usual corporate intrigues/power struggle/backstabbing/whatever. Just for some reason leaked into public view instead of being behind the scenes like it’s normally done, probably because someone is stupid.
Kaspersky is closely tied to Russian government. The dude himself (founder and CEO) has a government position as one of Putin’s advisors or something. Also he believes that anonymity should be purged from the internet, and every user should be personally indentified, enforced by the government. In the name of “security”, of course.
Russia already has national root TLS certificate that's must installed on all devices (basically government-mandated MITM). The next step is to start severely throttling (and optionally blocking) TLS connections that don't use it. Some popular foreign sites like Google can remain functional by replacing their certificate at ISP level (all ISPs are already controlled by the government).
What? I’m a Hodd Toward, please learn to spell names correctly!
Nah they should just upgrade their PCs
That’s how they do it. They send their “proposal” and immediately implement it in Chrome (with work on that being started long before “proposal” is made public obviously). Then they start using it on their own websites (with compatibility for now) and start propaganda campaign to push webdevs to use it too (which they do of course). Then they start complaining that other browsers’ developers are slow to implement this new “standard” (at this stage they won’t call it a “proposal” anymore) and are “stifling development of the web” or being actively malicious because they are jealous of Chrome or something. Then compatibility mode on their websites is first subtly broken so that users once again will witness how Chrome is superior browser and then removed outright. Boom, we have a new web standard!
Sounds like they didn’t test what happens with their apps when token is reset on server 🤔 should be reported to the apps devs. Thankfully with lemmy this is easier to fix than with proprietary services because you can self-host it and check various edge cases.
I’m fine when music content appears in Youtube recommendations, but videos in Music recommendations is absolute cancer.
I’m confused on how mobile clients work with Fediverse. Do they work with larger “threadiverse” like Lemmy and Kbin themselves or do they access it through specific Lemmy/Kbin instance? If it’s the latter, does this mean they use Lemmy-specific and Kbin-specific APIs?
Sure, it’s hard to craft a perfect solution. However the status quo for a long time was that applications were doing it themselves. And Wayland took it away without providing a replacement.