If you expect a press-release-sized check, don't hold your breath. Big companies usually prefer to buy leverage instead, by upstreaming engineering time, sponsoring CI runners, donating hardware for NVENC and VideoToolbox tests, or funding maintainers rather than cutting a single headline check.
Concrete things that actually reduce risk are paying for continuous fuzzing with OSS-Fuzz on libavcodec, funding multi-arch CI that covers macOS, Windows, ARM and Nvidia GPU tests, and committing to upstream fixes instead of maintaining an internal fork. If a company does those three things you'll likely see fewer regressions, fewer security surprises, and much lower downstream maintenance cost than from a one-off bank transfer and a press release.
I think I remember using one of these apps around 2010 or so, and I think it just triggered the emoji keyboard to appear somehow? And once it was opened once, the ability to use it persisted. But that was just my guess as to what was happening as a user.
I really doubt Apple's sandbox would have permitted editing a global preferences file like that. That might have just been the first, and not the only, method to enable emoji that people discovered.
No, I think it really did allow it. You can see the source for those emoji enabler apps in [1]. I think that various AppKit APIs do end up writing to that file so r/w access to that file may have been required. And in those days sandboxing probably wasn't as tight.
It's so dumb that with Windows you need so many software just to undo Microsoft's "innovations" and make it somewhat usable. I finally switched all of my personal Machines over to Linux a few months back, since I felt the gaming situation was finally good enough, and I'm never looking back.
>This whole thing feels like a subversion, instead of having graphene independent from devices and widen the attack vector, now the spooks can just focus on the “supported official device” only.
Graphene is currently only supported on Pixels, so not sure what you mean by that.
Does the web app for the bank actually selectively block mobile phones? I just checked and Chase here in the US lets me log in on Brave Mobile on iOS. Perhaps your bank lets you log on in the browser.
My understanding (I'm in the US too) is that apps in many other countries don't even have a web app equivalent. If you want your money, you need an authentic android phone and a closed-source app. Or, you can buy a plane ticket somewhere else.
Is using a cheap Android device (the cheapest Android phones are less than $100 on Amazon) an option? The idea is to use that phone for 2FA or whatever is app is necessary for, and use a degoogled device for your other day-to-day activities. It's not ideal because you need to spend some extra money, but it buys you a lot of privacy.
And now is subject to the whims of Microsoft, wherever Windows, DirectX, Visual Studio go, Valve must follow.
Additionally, everyone is betting on Valve as if Steam would be around forever serving Linux gaming with Proton, except no one lives forever, and who knows what will happen to Valve, when current management passes the torch.
reply