It’s useful for security researchers to collect and analyze what the newest attack bots are trying to do, in order to learn how to defend against it and study the malware they drop. There are some cool videos on YouTube about decompiling malware dropped by the bots.
I already force Wayland global for SDL games because the xwayland one has a horrible stutter while the native Wayland works flawlessly. Making it the default sounds reasonable to me. If specific programs don’t work with it, they can override it
Maybe try Stash, it has gallery support too https://github.com/stashapp/stash
Also, what about jellyfin itself? It also supports photos
Please do not use exfat on anything critical. It is slow as hell, it does not have journal or CoW to ensure consistency on unintended shutdown, and is designed to be extremely simple to implement, not robust. Good for flash drives and sd cards, but not normal storage.
It can handle websites like filejoker and nitroflare, which are behind captchas and things like mega that require JavaScript or an API to serve downloads
The reason I use a swap file is so that I can have only one partition backed by LUKS disk encryption, rather than having to screw around with lvm which comes with its own performance overhead and all. I’ve personally never had issues hibernating to.it, but given how much buggy uefi firmware is out there I’m not surprised to hear that other have issues
It’s been supported for several years now
Lots of malware gets hosted using dynamic DNS domains, so they (or more likely some bot) probably saw the domain frequently showing up in malicious activity and blocked it without understanding that it itself isn’t the source of the malicious activity.
You can use cryptsetup-reencrypt to encrypt an existing disk in place with LUKS. Then you just have to modify the initramfs/bootloader/fstab to point to the new configuration. See https://wiki.archlinux.org/title/Dm-crypt/Device_encryption#Encrypt_an_existing_unencrypted_file_system
When it was brand new there were some edge case bugs that broke on certain workflows and hardware, but that’s pretty much entirely fixed now and I’m guessing for a long time now it’s been more universally stable than pulseaudio was.
Also, some people just pointlessly dislike anything that’s new, or because it breaks their spacebar heating
Because it’s funny
I’ve been using Wayland on Nvidia with plasma for about a year and it’s been mostly fine. Only a few minor issues like night color not working or some Xwayland apps flickering, but the system feels far more responsive on Wayland so it’s well worth it to me
As long as the audio frequency is less than half the sample rate, it is a mathematical function with only one (exact) wave that is able to fit all 4 points, so it is perfectly reconstructed. This video provides a great visualization of it https://www.youtube.com/watch?v=cIQ9IXSUzuM
At both algorithms’ highest levels, xz seems to be on average a few percent better at compression ratio, but zstd is a bit faster at compression and much much faster at decompression. So if your goal is to compress as much as possible without regard to speed at all, xz -9 is better, but if you want compression that is almost as good but faster, zstd --long -19 is the way to go
At the lower compression presets, zstd is both faster and compresses better
It means it can capture any frequency up to half the sample rate, perfectly. The “extra detail” in the waveform is higher frequencies beyond the range of human hearing
Why? What reason could there possibly be to store frequencies as high as 96 kHz? The limit of human hearing is 20 kHz, hence why 44.1 and 48 kHz sample rates are used
However, it is very patent encumbered and therefore wouldn’t make for a good standard.
Both slower and worse at compression at all its levels.
I have a 5900x (zen3), and apparently I got a bit unlucky with the silicon and ended up with a CPU that’s slightly unstable at its stock voltages and stock boost clock. The system would freeze and reboot randomly, and the bios would report an MCE error. This crash could be reproduced with near 100% success by doing sha1 hashing specifically for some odd reason. This is not a Linux issue, it’s a hardware defect.
It may be an Asus motherboard specific thing, but I found a workaround by going to the bios settings, precision boost overdrive, and increasing the voltage scalar to like 7. Now it’s been two years and I have only ever had it happen once since I changed that, so I’m happy.