jfc this entire discussion is a meme, GNOME is a joke.
So. Discord is using what you guys gave them. GNOME folks refuse to implement the protocol (the ONLY compositor not to impl it) then says "UHHHH THEY SHOULDNT USE THIS"
Well they are using what YOU guys gave them. YOU guys did not provide an alternative, so discord has to use what is available.
Maybe instead of whining actually open a protocol discussion for something better then?
I would. I can't, I AM BANNED.
Gnome moment number 2 bajillion because NUH UH FUCK YOUR USECASE
Also fdo moment number 1 morbillion because NUH UH LETS BIKESHED
https://t.co/jzEAzqOA3D
@dewindells Play Integrity API isn't a legitimate security feature doesn't provide any serious checks for devices not being compromised. The strong integrity level permits devices which haven't received security updates since 2017 and the device integrity level supports even further back...
@StatsLime@Turret9999 They're actively interrogating, influencing and outright threatening OEMs to try to stop us having more options than Pixels. They're specifically doing that about GrapheneOS. They benefited a lot from GrapheneOS existing and yet are doing underhanded things to try to harm us.
Race @GoogleMaps Pegman through Tokyo's Shibuya Scramble Crossing to reach the Google building 🏃
Built with Gemini 4 Neon, this 3D runner turns nearly 1M tokens of real OpenStreetMap data (654 roads, 70 rail lines, and 280 building footprints) into a playable arcade map with custom Web Audio.
I want to thanks @SemiAnalysis_ for the motivation.
In the Gemini RL scaling team, we printed & put that article on our desks to be reminded daily of what used to be true at the time.
But the times they are changing :)
Google is sabotaging their OEM partners by making a growing number of features and updates exclusive to Pixels. At the same time, Google is trying to convince OEM partners not to support GrapheneOS or even bootloader unlocking. They're also trying to harm GrapheneOS directly.