Sorry had it the other way around, it uses gecko but then uses the Android system WebView as a renderer. I think it’s similar in iOS (but with the iOS equivalent of WebView because of iOS limitations) Either way, mixing and matching like that is generally less secure
- 0 Posts
- 6 Comments
For the record I didn’t downvote you, but if I was actually being serious about opsec I’d say not to use anything based on mobile Firefox at all :)
warning: info dump ahead
- Firefox mobile is inherently less secure because on mobile because it’s basically just slapping a new renderer on top of either safari or Chromium’s browser engine. This is partially because, everywhere except the EU, Apple requires all iOS browsers to use the safari engine under the hood, so it doesn’t make sense for them to develop their own mobile engine just for EU and Android. If you’re actually serious about opsec, just use safari on iOS, Vanadium on GrapheneOS, or Brave (brave is also lame tho :/ There might be a better chromium fork I’m not aware of)
- Fennec/Ironfox still have cookies, they won’t sign you out of things every time. The improvements come based on actively blocking more telemetry (and hardening it with things like always-https and DNS-over-https, and tracking blockers on by default)
- I don’t actually have a 3rd thing I’m basically just trolling at this point. Rule of 3s and all. Have a good day.
Fennec and Ironfox are improved versions of Firefox with better privacy/security hardening so picking either is probably preferable to base Firefox
I’m realizing my wording might be vague, by “everyone” I meant the big tech companies that didn’t implement it, like Google, Apple, Microsoft, and Adobe. AFAIK most of the open source apps actually implemented support pretty quickly, and obviously it wouldn’t be the end users’ fault because they can’t change what formats are supported
Why are we sending someone to “Extra Hell” for making an improved image format that has better compression and is an overall improvement over all 3 of the existing formats it replaces (jpeg, png, gif)?
Shouldn’t this apply to
everyonethe companies who refused to adopt it, thus breaking every normal image workflow? (Same thing can be said about JXL)Edit: fix vague wording
Steam also makes and distributes their own DRM but it’s optional whether or not publishers choose to include it in their games.
It’s still ultimately optional but definitely more than just “allowing games with DRM to be published”. They are offering a ready-made solution for it as well.