Thank god we have crypto bros like Sigma G and Sina_21st to get the inside scoop on the Chinese rural bank loan crisis.
Thank god we have crypto bros like Sigma G and Sina_21st to get the inside scoop on the Chinese rural bank loan crisis.
ZFS doesn't have fsck because it already does the equivalent during import, reads and scrubs. Since it's CoW and transaction based, it can rollback to a good state after power loss. So not only does it automatically check and fix things, it's less likely to have a problem from power loss in the first place. I've used it on a home NAS for 10 years, survived many power outages without a UPS. Of course things can go terribly wrong and you end up with an unrecoverable dataset, and a UPS isn't a bad idea for any computer if you want reliability.
Totally agree about mainline kernel inclusion, just makes everything easier and ZFS will always be a weird add-on in Linux.
They should bring back the original https://www.youtube.com/watch?v=tPYbzfwIJRA
Main thing is the lug width. You could get a few straps on the smaller side and they'll fit inside bigger lugs, just not look ideal.
Something that can be worth buying in person, even a mall key/watch repair stall would have a variety of types and sizes on hand and can find you something suitable on the spot.
To be fair, these folks are advocating for plain text emails, not surprising they are against encrypted emails.
The only problem I run into is sites that use Bluetooth or USB APIs to talk to a local device. Both Firefox and Safari don't implement them due to security concerns.
I've dabbled in a couple recently, xTTS v2 in Coqui sounds pretty good and is pretty quick. Especially if you use one of the built in voices. Has a weird "only for non commercial use" licence if that bothers you.
To me I'd consider Linux not standardized since anything outside the kernel can be swapped out. Want a GUI? There are competing standards, X vs Wayland, with multiple implementations with different feature sets. Want audio? There's ALSA or OSS, then on top of those there is pulse audio, or jack, or pipewire. Multiple desktop environments, which don't just change the look and feel but also how apps need to be written. Heck there are even multiple C/POSIX libraries that can be used.
It certainly can be a strength for flexibility, and distros attempt to create a stable and reliable setup of one set of systems.
I'm moving house this week and unearthed my galaxy invader 1000 handheld. Had to play a couple rounds on the spot! Apparently from 1980.
It was meant in jest, I should have contrasted plain text / cipher text to be more clear. Though it's a similar kind of extenstion to email technology that they are advocating against.
These folks want to read their emails in their terminal email client, and for you to cater to their limitations. If you use tuta and send them an email, tuta just emails them a link to view the message on tuta's webapp. I'd say this anti-HTML group aren't fans of that.
Not to argue semantics, but I would consider encryption in general is a change in message formatting. The client needs to change how the bytes are interpreted. It adds complexity, and clients may not support it, their exact arguments against HTML.
My partner worked for a local council. They reset your password every 90 days which prevented you from logging in via the VPN remotely. To fix it you'd call IT and they'll demand you tell them your current password and new password so they can change it themselves on your behalf.
Even worse, requesting a work iphone meant filling out an IT support ticket. So that IT could set up your phone for you, the ticket demanded your work domain username and password, along with your personal apple account username and password.