How are downloads performed over http "potentially malicious"?
Mozilla is foolish to buy into Google's bad faith attempt to create barriers to entry for small/old sites and further centralize the web.
Mozilla: Okay, done.
21–30 of 235 posts
How are downloads performed over http "potentially malicious"?
Mozilla is foolish to buy into Google's bad faith attempt to create barriers to entry for small/old sites and further centralize the web.
Mozilla: Okay, done.
Give me a way to pay for Firefox, please, and use the proceeds to hire a full development team that can hopefully catch up and overtake Chrome? Please?
Earlier quoted context omitted.
A MitM (e.g. an untrusted WiFi network) could replace a download by a malicious version.
In that case the html text of the page could be replaced by the attacker so the download link points to an https link.
> Firefox now supports the new AVIF image format PARTY! I've been waiting for this for a long time. The last big hurdle for this was that color spaces weren't applied correctly. If you haven't taken a look at AVIF, do. You can get a similar looking image in AVIF at half the size as a JPEG. I find AVIF's image artifacts preferable to JPEG's.
I'm looking forward to the wide adoption of JPEG XL (.jxl - "jixel") file format. It's the format that will replace JPEG! https://jpegxl.info/
Earlier quoted context omitted.
I'm looking forward to the wide adoption of JPEG XL (.jxl - "jixel") file format. It's the format that will replace JPEG! https://jpegxl.info/
I kind of doubt it. JPEG is good enough, and is pervasive. JPEG XL is better, but removing an incumbent file format requires more than just being better. We'll see.
A great blog post on this by one of the creators of the format, Jon Sneyers:
https://cloudinary.com/blog/time_for_next_gen_codecs_to_deth...
How are downloads performed over http "potentially malicious"?
Talking about certs, nowadays it seems browsers want to make you believe that self signed certs are some diabolical work straight from hell. Using self signed certs with websockets on Firefox is actually nearly impossible [1].
> Firefox now supports the new AVIF image format PARTY! I've been waiting for this for a long time. The last big hurdle for this was that color spaces weren't applied correctly. If you haven't taken a look at AVIF, do. You can get a similar looking image in AVIF at half the size as a JPEG. I find AVIF's image artifacts preferable to JPEG's.
I'm looking forward to the wide adoption of JPEG XL (.jxl - "jixel") file format. It's the format that will replace JPEG! https://jpegxl.info/
> Firefox now supports the new AVIF image format PARTY! I've been waiting for this for a long time. The last big hurdle for this was that color spaces weren't applied correctly. If you haven't taken a look at AVIF, do. You can get a similar looking image in AVIF at half the size as a JPEG. I find AVIF's image artifacts preferable to JPEG's.
Do you know when we can expect .heic?
If you mean the image format, probably never. It's based on the HEVC/H.265 licensing minefield. For that reason, I don't expect it to ever be supported on Chromium or Firefox based browsers.
Earlier quoted context omitted.
I'm looking forward to the wide adoption of JPEG XL (.jxl - "jixel") file format. It's the format that will replace JPEG! https://jpegxl.info/
I kind of doubt it. JPEG is good enough, and is pervasive. JPEG XL is better, but removing an incumbent file format requires more than just being better. We'll see.
Give me a way to pay for Firefox, please, and use the proceeds to hire a full development team that can hopefully catch up and overtake Chrome? Please?
https://donate.mozilla.org ?
This goes to the Mozilla Foundation and not to the browser's development. As far as I know there is currently no way to donate to the browser's development.