• 10 Posts
  • 289 Comments
Joined 3 years ago
cake
Cake day: June 12th, 2023

help-circle


  • 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
    1. 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)
    2. 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)
    3. 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.


  • 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


  • Zangoose@lemmy.worldtomemes@lemmy.worldIt really is the worst image format
    link
    fedilink
    English
    arrow-up
    182
    arrow-down
    13
    ·
    edit-2
    8 days ago

    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 everyone the companies who refused to adopt it, thus breaking every normal image workflow? (Same thing can be said about JXL)

    Edit: fix vague wording








  • They are quite literally taking the “if you don’t like it, fork it yourself” approach. Who said they aren’t going to make changes/improvements on top of it?

    I don’t see anyone else mentioning it but this is also probably because brave browser is published under the MPL license so the licenses are actually compatible between projects. They don’t want to implement completely from scratch because there is a compatible existing implementation that they can build on top of instead of starting from scratch.