made you look
It’s not really Ext4 doing that, it’s a bunch of tricks in the OS layer and the way apps write files to storage that limits it.
You’ll see it if you use something like a BT client without pre-allocation, those files can get heavily fragmented depending on the download speed.
It’s got nothing to do with the specific search engine, it’s Firefox thinking the URL itself is a search query and sending it as-is to the search engine.
I just tested it and it sent the URL to both DDG and to Google.
She used all the code words and dog whistles from the start.
PNG gets you the best compatibility and features, at the expense of file size. But I probably wouldn’t use it for uploading photographs to the web of course.
WebP is the same, it’s got a lossy mode (VP8) and a lossless mode (Which is more limited than PNG, but beats it where it overlaps). But to make it more complicated the lossless mode also has lossy processing modes, where it alters the image first to achieve smaller output sizes.
People have a long habit of turning JPEG files into PNG files, the file extension won’t help you there. They also could have reduced the colour depth or resized it, all lossy operations. All it really tells you is that it can have an alpha channel.
As for AVIF, personally I don’t like the format, it feels like an “open media” (But still patented) version of HEIF to oppose Apple. Like WebP it makes the (baseless IMO) assumption that a format designed to encode motion data is better at encoding still data than a format designed to encode still data. It’s got all the limitations of a video format (It’s got a max resolution, only supports 12bit images, and no progressive decoding), and they left out all the enhancements from WebP (The dedicated lossless mode, “lossless AVIF” files are huge and the last I checked badly supported, so nobody actually used them, and they just called very high quality settings “lossless”)
A team inside of Google was working on WebP2 around the same time, that used AV1 but actually added the useful stuff like efficient lossless encoding, it got killed too in favour of AVIF.
So it depends on the specific HDR encoding used, Rec2020 is the most common ones you’ll see (It’s meant for “pure” setups, i.e. where the source and output are tightly linked, e.g. gaming consoles or blu-ray, or so) and the raw data won’t look great. While something like HLG (Hybrid-Log Gamma) is designed for better fallback (As it’s meant for TV broadcast, where the output device is “whatever TV the user has”), so should just look dimmer.
This is a HDR screenshot I took of Destiny 2, which uses Rec2020, tone mapped to SDR
And here’s the raw screenshot data from before tonemapping.
If the second image had all the right HDR metadata, and the viewer supported it properly, then both images would match.
AVIF is generally smaller in size than both WebP and PNG. AVIF supports animation while PNG does not.
The lossless mode in AVIF is so bad that a BMP in a ZIP file produces smaller results.
Which makes sense, as it doesn’t actually have a dedicated lossless mode (like WebP does), the encoder is just to not quantise the video data it produces.
JXL can do lossy images (like JPEG) and lossless ones (like PNG), and on average it’ll produce smaller file sizes than both (While beating JPEG quality wise). The killer feature is that it can do lossless recompression of existing JPEG files and shave off about 20% of the file size, and it’s reversible so you can turn those JXL files back into JPEG images for existing software.
The downside is that it was created by Google Research (among others), but the Chrome team made AVIF instead and decided that’s what they’d support and nothing else.
At least Safari supports it.
For a community called “technology” there’s a pretty strong anti-AI bubble going on here.
Are you surprised people have opinions about technology, in a community dedicated to discussing technology?
Use Zola or Hugo then
Tizen (resting place of Meego)
I’d say SailfishOS is the final resting place of Meego, especially since it’s maintained by ex-Nokia devs.
I mean, the point of the init process is to bring up the filesystem and disks, if the configuration is wrong that’ll be the process to complain about it.
“No, go away.”
That’s a perfectly valid way to deal with toxic contributors. There’s always people with better social skills and equal developer skills out there, you don’t have to accept and include toxic people just because they wrote some code.
I’d double check, if you haven’t picked an option specifically it might just default to the fallback (i.e. BOOTX64) It’ll be under the boot device order section.
(Not my picture, stole it from Reddit)
Here it’s listing all the possible boot options this mobo can find, but there’s a generic “UEFI OS” option which I’d bet is the fallback. And once a choice is made it’s kept unless something resets it, so if it just happened to be set to the fallback once it’ll stick with that until a change is forced.
When installing windows while there is a Linux install, windows will see the EFI partition already there and just decides to share it, and doesn’t create its own.
That’s what it’s supposed to do, it’s a plain FAT32 partition, the bootloaders are just files you put in there.
Part of the issue is that while a well-made motherboard will look for all bootloaders on the partition and present them as options in the firmware UI, bad ones will only look for a specific file (\EFI\BOOT\BOOTX64.EFI) and use that. For an OS to have a chance of booting on those boards it has to overwrite that file, blowing away whatever other bootloader was there before.
It’s annoying, since Windows is mostly well behaved here (It puts the main copy of the bootloader at \EFI\Microsoft\Boot\bootmgfw.efi and Linux bootloaders can see that and offer it, the reverse isn’t true) and can co-exist with Linux well (Well…), but manufacturers cutting corners causes more problems for everybody.
And there’s still web directories hanging around, similar to the now dead dmoz site.
https://url.town/ and https://curlie.org/ for example
Good news, they’re making it easier to fix stuff like “spurious double clicks”.
https://who-t.blogspot.com/2025/05/libinput-and-lua-plugins.html
True, that’d definitely make it a lot more viable to hold corporations to account.
There was Secure Scuttblebutt, but it had issues that hindered adoption.
Nostr does actually seem like a more usable version of it, but the only people I’ve ever seen use it are cryptobros, so it’s got a kind of anti-network effect.
Edit: Honestly a “SSB2” running over something like Veilid could be real nice, but it’s still early days.