In case you don't want to install an extension, search in about:config for "image.webp.enabled" and set it to false. Worth mentioning, there's also a "image.avif.enabled" entry.
That is not the same thing. This addon does not modify "image.webp.enabled" or "image.avif.enabled", it modifies the accept header. If you modify the preferences you mention you will still be served AVIF and WebP, but viewing will break...
> Does WebP provide a savings against jpeg for these photos?
“WebP seems to have about 10% better compression compared to libjpeg in most cases, except with 1500px images where the compression is about equal.”[1]
mozjpeg JPEGs + AVIF in a <picture> element is the way to go now. You will probably always want to serve JPEGs as an alternative WebP and AVIF and that makes WebP is a waste of disk space for lossy compression of photographs.
I'm amazed the “WebP is such a goated format” blog post made in to the front page of HN.
Off the top of my head, Matrix clients with full support for E2EE include:
* Element Web (via matrix-js-sdk)
* Element iOS (via matrix-ios-sdk)
* Element Android (via matrix-android-sdk2)
* ElementX iOS (via matrix-rust-sdk)
* Fluffychat (via Dart Matrix SDK)
* Fractal (via matrix-rust-sdk)
* Hydrogen (via hydrogen-sdk)
* Syphon (built into its Dart codebase)
* Thunderbird (via matrix-js-sdk)
* Cinny (via matrix-js-sdk)
* weechat-matrix (matrix-nio)
* weechat-matrix-rs (matrix-rust-sdk)
* nheko-reborn (mtxclient)
* mirage (matrix-nio)
* gomuks (gomautrix)
* ocrcc-chatbox (matrix-js-sdk)
...and a bunch of abandoned ones too, like Riot Android (matrix-android-sdk), Seaglass (matrix-ios-sdk) and Daydream (matrix-rust-sdk).
Meanwhile any Matrix client can speak E2EE if you connect it via the pantalaimon E2EE proxy (powered by matrix-nio).
In other words, the whole "almost every Matrix client out there has no support for E2EE" is really not true - there are loads of them, spanning many different platforms, built using different independent SDKs.
Good point but I don't really care about E2EE for my usecase. I mainly use it for my local bridges and my Matrix instance isn't even publicly accessible or linked to the rest of the matrix network. So for my use it really doesn't matter.
I think Nheko suffers from low-density UI the same as Element. Especially the room list. But unlike Element it does support tags properly which is indeed great.
A PR was merged recently to make reading encrypted messages in libquotient (the lib used by both Quatermion and NeoChat). Another one is in the work to send encrypted messages.
> indeed, the other is a proof of concept and will remain as is.
I've always said that a easy to deploy CMS is one of the missing pieces for the IndieWeb. Preferably it should work on any shared hosting. PHP/SQLite would be a good fit, but I understand if you have other preferences.
> I've never attached my 2020 LG 4k 65" to any network and it works great.
I guess that would work as long as you move to a place far away from humanity. It definitely won't work if a neighbour runs a WiFi hotspot without password protection.
What would happen if you configured manual network and gave it a fake DNS or sent it over to PiHole for example? Wouldnt there be plenty of ways to capture the traffic and stop it from going where it wants to go? I would think the tech savvy folks on this site would be able to figure something out if it is a big enough concern of theirs.