The whole thing is weird and the CEO especially so, and not weird in a good way: https://d-shoot.net/kagi.html

One example I can think of is Widevine DRM, which is owned by Google and is closed source: https://en.wikipedia.org/wiki/Widevine

Google currently allows Mozilla (and others) to distribute this within Firefox, allowing Netflix, Disney+, and various other video streaming services to work within Firefox without any technical work performed by the user

I don’t believe Google would ever willingly take this away from Mozilla, but it’s entirely possible that the movie and music industries pressure Google to reduce access to Widevine (the same way they pressured Netflix into adopting DRM)

For disappearing messages to work, your conversation partner has to promise they won’t take photos of their screen, and they have to promise to use an app that actually implements the feature instead of just pretending to, and the app developers have to promise to have implemented the code to delete a message when the service says it should

Is there actually a cryptographically-sound and physically-complete method for ensuring that a message is only legible for a temporary duration once it leaves your own device and is delivered to someone elses?

Hmmm, is CloudFlare known for being a bad actor in terms of privacy?

Setting that aside, no matter what you pick, you’ll be exposing your IP address, from which your ISP and/or general location may be derived

If you don’t trust CloudFlare with that information then you basically cannot trust anyone else, so maybe you’d need to run your own service and ping that instead now that you’re in a situation where you can only trust yourself 🤷

The other issue that comes to mind is that you’re only testing reachability to one address, which means you could get a false negative where that address stops working but the rest of the internet is actually fine

I did actually do this already, separate from working on this issue, but can confirm the intermittent problems with the combination of wpa_supplicant and systemd-networkd

I’m not an expert, but my understanding of the Global Shortcuts portal is that it’s very much designed for the push-to-talk use case where an app is not focused but still receives button events for exactly the keys its interested in and no other keys: I think this would cause problems if an app requested every key (e.g. if the request was approved then no keys would work in every other app)

It’ll be interesting to see how the remaining compatibility/accessibility issues are tackled, either in portals or in wayland protocols

There’s a portal for Global Shortcuts: https://flatpak.github.io/xdg-desktop-portal/docs/doc-org.freedesktop.portal.GlobalShortcuts.html

KDE and Hyprland already implement it, and COSMIC seems likely to

On the app side, if we can get the major toolkits to adopt it, then hopefully that covers most actively-maintained apps (but it’s unlikely to cover legacy apps): https://github.com/electron/electron/issues/38288

Gosh, I’m so fascinated by the concept of removing/hiding the tabs implementation from every app and relying 100% on the window manager to provide this