Former "friend of the West" from the other side of the Iron Curtain. Left most English-speaking resources in 2024 after belatedly retaliating that our friendship is not welcome over there, and never really has been.
Depends on your region and what sites you're using. I live in the middle of nowhere far from civilization, and 1.1.1.1 returns terrible IPs for many sites including google.com (which pings at 350-400 ms if you resolve it through 1.1.1.1, but at 90-100 ms if you're using any other resolver). They do it because they block EDNS0 in order to protect your privacy or something like that.
So I use 8.8.8.8 and 9.9.9.9 in parallel through dnsmasq. Whoever responds the first wins. If you're not stuck in the middle of nowhere, you're probably better off with the latter as it's somewhat more trustworthy than Google.
Most unicorn companies with an average half-life measured in months, maybe. Most companies worldwide across all industries, probably not. The pendulum will swing the other way sooner or later anyway as it always does.
It also makes it easy to write and share your own packages when you need something that's not in the repos (or the AUR). The first package will take you about an hour of reading documentation (which is 10+ times less than it took to build my first Debian package), but the next ones will not take more than 5-10 minutes.
The difference was painfully obvious about 3-4 months in, this only confirms it. Everyone here keeps asking why would one pick AlmaLinux over literally anything else, while I'm sitting here asking myself how would anyone risk running his business on a distribution built on such a shady foundation, from sources obtained in a metaphorical back alley. Feels like a lawsuit waiting to happen, I wouldn't want to be on the receiving side of that for sure.
The "relying party" (the website you're trying to authenticate to) can request the browser to perform user verification and refuse to proceed without it. You'll need to type in your PIN then (or scan the fingerprint, or perform some other type of verification dance, whatever is supported by your device).
The RP can also request not to perform it, but IME Chromium asks for PIN anyway. Firefox is not so insistent.
You can play with parameters here (look for advanced settings):
> You are using a browser or device that does not support passkeys.
Yet again the supposedly open standard is compromised by terrible implementations. I already ranted about PayPal which has somehow managed to only support mobile devices and macOS:
I added passkey support to a couple of projects at $DAYJOB and they work just fine on Firefox or Chromium on Windows, Linux, or FreeBSD if you don't go out of your way to break them. WTF GitHub?
> if you have 4 KB-sector disks then you should probably use a physical block size granularity of 4 KB for your ZFS pool rather than 512 bytes
According to Allan Jude (OpenZFS & FreeBSD developer), you should never use 512-byte recordsize even on an HDD with 512-byte sectors. Always start from 4 KiBs, probably even from 8.
If you go by features, there aren't many alternatives. Unless I set up a database server, I consider checksums + snapshots + compression + reflinks to be table stakes these days. There is only one mainline filesystem that supports all of that, and it has its share of issues that are unlikely to ever be fixed, and is (probably permanently) tarnished in many users' eyes because it was pushed too early. So the question is, do we really need a second filesystem? (Yes?)
Recovery from out of space errors is difficult on any copy-on-write filesystem since you need to write more data to disk to actually delete anything. You'll find similar stories about ZFS if you care to look for them. btrfs has had some protection against out-of-space issues for some time now (look for "global reserve" in `btrfs filesystem usage`). I think ZFS has something similar, but I don't care enough to check since I'm very careful to never let it get that far.
I do something like this with ZFS snapshots and syncoid. It runs every 15 minutes and sends the diff from the latest snapshot onto a second ZFS pool made out of a single HDD (and then updates that snapshot and discards deleted data). Works fine for about a year now.
To get the best isolation you need to patch the source — the application needs to go through initial setup and then drop privileges to the absolute possible minimum. But it's easy to make custom wrappers for third-party applications — the above profiles taken from the OpenBSD ports tree are the proof.
bubblewrap does this and has been used by flatpak for years. firejail has a lot more features though (which is questionable for a security-critical application, sure), like setting up separate iptables rules, which you would have to do manually with bubblewrap.
I've been using it to wrap nodejs package managers in response to all malware shipped through them over the past few years. A simple wrapper script like this works fine (symlinked to `npm`/`yarn`/`pnpm` into whatever directory is the first in $PATH):
It gets read-write access to the current path, and to its own copy of ~/.cache and ~/.local/share. It doesn't see anything else from your home directory, including any adjacent projects. It can easily be locked down further by allowing read-only access to the project, and read-write access to node_modules and nothing else.
If you just "tried it", I doubt you'd seen even one percent of what they can do. I've been using IDEA for years and still learn new tricks every few days. The performance is atrocious, the well known bugs (like constantly losing caches) have been there for years, but I suffer through it because of the functionality.
I usually setup HTTP basic authentication for these types of things. It also prevents exploitation by bots when a zero day is out and you haven't patched yet. The username/password pair can be trivial, even something like `foo/bar` stops pretty much all automated scanning.
Why would they? Nobody except a few home users needs RAID 5/6. There's only a small handful of talented filesystem developers (never mind the filesystem, it's equally applicable to all of them), and there's always something to do which will benefit all of us. Especially for something so feature-packed and complicated.
Not surprised to see Kazakhstan at the bottom of the list (I am more surprised to find us there at all). We have insane levels of corruption: almost anything can be "solved" by knowing the right people and spending a bit of money. There has also been somewhat of a news streak recently about taxi drivers fleecing hundreds of dollars off credulous tourists for a ride around the block.
Most people communicate over the internet through WhatsApp and Telegram, but everyone I know has an email account and knows how to use it, so I don't think that's the reason.
The only consolation is that China has managed to score even worse.
If my Russian friends ignored the news as much as you did, at least some of them would be feeding worms right now. Most left the country when the news made it obvious that a mobilization order is to be declared — it was confirmed a couple of days thereafter.
Sun has picked the license specifically to make the project incompatible with the Linux kernel. If you start out with hostility, what treatment do you expect in return?
We see how well "including people into using your software" works out for pushover licenses almost every week now, FreeBSD itself being the prime example, having lost three major companies one after another from its list of users, sponsors, and developers a couple of years ago. Not that there were many to begin with. What Linus and the gang are doing have been working out great over the long term (much better than any competition, at least).
I've been using it for about 3 years now (the large ARM instance a bit less than that, but since about when it was introduced). There have been two outages about a minute each (seems like a no-no-downtime host migration, but I am not sure). For the cost, I am not complaining.
Both Canonical and Ubuntu have their own share of problems, and they've been struggling to monetize Ubuntu for the past few years. Once you get burned by one commercial vendor (not once actually… it's the third time afaik), it's probably wise to use this opportunity for migrating to a more stable distribution where commercial interest doesn't have much influence, and which has never intentionally burned its users (since Debian developers are users too and are also doing it for themselves).
Looking at how insistent many authoritarian regimes are at forcing international companies to host data in their own jurisdiction, you're probably right. I live in one of those countries and definitely prefer certain VPN and hosting companies to my own ISP.
Same domain doesn't always mean your information won't get leaked to wherever. For example, Sentry supports sending data through a proxy hosted on the same domain used by the website. If you don't block it, your data ends up on sentry.io anyway (in most cases; some users probably self-host their own Sentry instance, but how many? It's quite painful from my personal experience.)
You can always use a FIDO2.1 key as a passkey, they're not tied to the big tech. I don't even have a smartphone and have been using them on the couple of sites that support passkeys just fine.
We will also have at least one open software implementation when this gets merged:
that force you to use Android or iOS, but it's nothing new, they manage to fuck up everything they touch (for example, U2F 2FA only supports registering one hardware key and it has been that way for years).
When was that? I use a pair of cheap FIDO2 keys with both Firefox and the Linux PAM module. It's hell of a lot more convenient than typing in passwords to unlock LUKS volumes or sign in to web services, that's for sure. I use mini keys though, they barely stick out of USB ports.
There's life outside the United States, and $100/month is a decent chunk of a junior's salary in many parts of that. Two places I worked at migrated off Microsoft products to FOSS solutions for that reason alone (I was fortunate enough to initiate and complete this process for one of them) — something that has zero business sense according to most HN commenters.