Isn't a lot of that just the suckiness of the IMAP protocol? Mozilla is pushing to add JMAP support to Thunderbird, and they're planning on using it in their upcoming Thundermail hosted email service.
I get this, but most email is through Google and Microsoft in NA, at least, neither of which seem to care to support JMAP at all, on fact they are getting locked down more and more.
Obviously they want you to use the web interface so they can show you ads and gather more data about you (for ads).
JMAP support turns out to be a strong signal for the business model of an e-mail provider. IMAP they have to have, JMAP is for those who actually care about supporting local client software.
Unless you're targeting really old browsers, lossless WebP is absolutely worth it over PNG.
As a test, I have a set of 36 old MS paint Drawings, originally drawn on Windows 98SE, originally saved in bitmap format with a total size of 53.4 MB.
Transcoded to PNG format using FFmpeg and the highest -compression_level of 100, this same set of images takes up 403.8 kB.
Transcoded to -lossless WebP format using FFmpeg and libwebp with the maximum -quality value of 100 and maximum -compression_level of 6, the set of images takes up 174.8 kB.
Transcoded to lossless JPEG XL format using cjxl in the highest compression settings, the 36 images only takes up 126.6 kB.
Given the computing power required to decode JPEG XL images and their limited support, it may not make sense to use JPEG XL for non-archival purposes, but lossless WebP is an excellent middle-ground, achieving over 2x the compression level of PNG.
Lossless WebP has also been supported by all major web browsers since September 2022, when Apple finally added full support for lossless and animated WebP images. It really doesn't make sense to still be using PNG, unless you're targeting really out-of-date Mac or iOS devices. Having drawings and illustrations be 50% smaller (versus PNG) is huge!
Personally, I avoid WebP out of spite. While it has greatly improved over previous formats in certain uses, it has been lacking or offering only marginal improvements in others. That didn’t stop Google from pushing it hard on the web.
I was left feeling like the next time we adopt a format that tries to do everything, it should actually do everything just as well or better than its predecessors. Lo and behold, JPEG XL is probably the first format which actually achieves this, covering all kinds of pictures you can think of and doing a pretty good job on all of them. So for the first time, I feel like the format has actually earned its place in the ecosystem, rather than just being some megacorporation’s personal favourite.
Of course, this point of view is emotional more than rational. Technically, WebP is a sensible choice, so I don’t mean to discourage anyone from using it today.
It wasn't some one company's choice and push. Almost everyone wins when bandwidth is cut and you get higher quality for less space. I'd argue most people's hatred for webp purely comes down to a few other corporations like microsoft, not supporting it well in the early days and blaming the format instead.
How so? This table [1] shows the adoption dates for WebP in various popular programs (as does Wikipedia [2]). Of all high-profile programs, Chrome was the only early adopter; other browsers were avoiding it for years, not to mention off-line software. Mozilla went as far as to work on a JPEG encoder [3] after WebP was introduced by Google, to see if maybe JPEG itself could be improved enough. How does that not read like one company’s choice and push?
> Almost everyone wins when bandwidth is cut and you get higher quality for less space.
Sure, but that doesn’t mean you immediately adopt every new codec that brings improvements in some area. With every new feature comes new code, new baggage, new potential attack surface. You have to ask if the improvements are big and consistent enough to go through the effort and burden the entire ecosystem with yet another format everyone now has to deal with. You need to think of the user and developer experience both in and outside of the web.
Microsoft would have been perfectly within their right to blame the format, since Google just decided to let it run wild on the web without garnering more support for it first. The format has its pros and cons, and it’s up to all the involved parties to weigh them and hopefully reach a consensus.
I'm sure they have some preferences for smaller pages.
If you're saying they did a thing where 200KB webp had an advantage over 200KB jpeg, please link your source. When I search I only see people saying that's not the case.
It's probably for the best. As recently as 2016 (and probably more recently; that's just the last time I tested this), they weren't even validating SPF records on their email-to-SMS gateway. You could spoof the "From" address to any email address you fancied and your messages would go through, appearing to be from that sender. Back in high school, my childish self had a field day showing off my phone's SMS inbox filled up with spam Viagra ads that were "sent by" Hillary Clinton's "hacked" email server.
It's not as funny in hindsight, given the unexpected results of that election, but at the time, it felt like top-tier humor.
I did too, but I really miss Mullvad's static port forwarding system. It's a pain having to continually run a NAT-PMP client, and it doesn't work when you're connecting to ProtonVPN on your router.
PowerAmp is paid, and Aurora Store can't do paid apps or in-app purchases without a Google Account. It's better to download the APK and buy a license key on the official website, which doesn't require Google Play Services if you do it that way.
Looks like they also allow you to buy with a credit card on their website, and they say Google Services aren't required if you buy that way. Very cool!
You can bind ports 1024-65535, and if you're in a home setting, you can just configure the port forwarding/DNAT settings on your home router to forward external ports 80/443 to whatever ports you're using internally.
Containers are nice, but they're not strictly necessary. On Google Pixel 6 and newer phones, you can take it a step further and root your phone and run a KVM-accellerated arm64 Linux virtual machine on your phone. There's a port of Limbo PC emulator that includes support for the KVM accelleration, and it works quite well! It even allows you to pass through USB devices to the guest.
Does your ISP router not allow you forward a port to a different port? I just assumed that was just a basic feature that any router would have. If the ISP router is that bad, it's definitely time to replace the ISP router or put in into bridge mode.
Old thin clients can be good deals too. Dell Wyse 5070s are great for basic tasks, especially if you can get the Pentium Silver J5005 models. They take M.2 SATA SSDs and they don't have UEFI whitelists on their M.2 WLAN cards, meaning you can get one of those M.2 A+E key SATA cards and connect a SATA HDD to it. Expect to pay around $40-$50 for a Dell Wyse 5070 with 4GB of RAM and eMMC storage. You can easily add an SSD, and since it takes M.2 SATA SSDs, you can buy lightly used ones relatively inexpensively.
Old Optiplex are also good deals. I bought a Dell Optiplex 5070 MT for $150 for myself and 2 Dell Optiplex 3070 SFF computers for $75 each to replace my mom's aging Windows 7 PC. All 3 computers take DDR4 and M.2 NVMe SSDs and have an Intel i5-9500 CPU that will also run Windows 11 pretty well, if you're into masochism that is.
If you're hosting behind a NAT device, you can just map external port 80/443 to internal port whatever. You can bind any port 1024 or higher.
Termux is only slower without root if you use proot. PRoot provides a limited implementation of chroot that runs unprivileged in userspace, but this also causes it to be pretty slow. If the server software you want to run is available in the Termux repos, you can use that and have it run at full-speed.
Termux works by patching all programs to treat /data/data/com.termux/files/usr as the root directory and /data/data/com.termux/files/home as the home directory. This introduces some compatibility issues, but it doesn't make it any slower.
