Discover seems to be the best bet to me so far.

Discover is on the JCB, UnionPay, Troy and RuPay. (japan, China, turkey, and India respectively). Probably many more.

Similarly, a JCB card should work wherever Discover is. It’s a billateral alliance.

Oh, and all Discover cards work on Diners Club International because those two networks completely merged.

Alliance members are not 100% acceptance. It seems like 95%+ acceptance though (most JCB will accept most Discover cards and vice versa, though you will get confused looks from the locals). It sounds like there’s a lot of old equipment around the countries that break compatibility but cities and other urban areas with new equipment shouldn’t have any problems.

I’ll probably get a Discover card and start testing this out. I already have Visa and Mastercard but this new censorship issue seems serious enough to make me start supporting a 3rd place competitor.

Between Discover vs AmEx, it seems like AmEx is about elite club / customer service / returns etc. etc. nice features but I’m not sure if it’s worth the price.

Discover is free of annual fees, reasonable cash back, mediocre costs for the merchants (better than AmEx anyway and comparable vs Visa) and a surprisingly huge offering of international compatibility (RuPay, JCB, UnionPay, etc Etc). It seems like the winner to me as a 3rd card to experiment with.

That’s not what storage engineers mean when they say “bitrot”.

“Bitrot”, in the scope of ZFS and BTFS means the situation where a hard-drive’s “0” gets randomly flipped to “1” (or vice versa) during storage. It is a well known problem and can happen within “months”. Especially as a 20-TB drive these days is a collection of 160 Trillion bits, there’s a high chance that at least some of those bits malfunction over a period of ~double-digit months.

Each problem has a solution. In this case, Bitrot is “solved” by the above procedure because:

1. Bitrot usually doesn’t happen within single-digit months. So ~6 month regular scrubs nearly guarantees that any bitrot problems you find will be limited in scope, just a few bits at the most.

2. Filesystems like ZFS or BTFS, are designed to handle many many bits of bitrot safely.

3. Scrubbing is a process where you read, and if necessary restore, any files where bitrot has been detected.

Of course, if hard drives are of noticeably worse quality than expected (ex: if you do have a large number of failures in a shorter time frame), or if you’re not using the right filesystem, or if you go too long between your checks (ex: taking 25 months to scrub for bitrot instead of just 6 months), then you might lose data. But we can only plan for the “expected” kinds of bitrot. The kinds that happen within 25 months, or 50 months, or so.

If you’ve gotten screwed by a hard drive (or SSD) that bitrots away in like 5 days or something awful (maybe someone dropped the hard drive and the head scratched a ton of the data away), then there’s nothing you can really do about that.

Wait, what’s wrong with issuing “ZFS Scan” every 3 to 6 months or so? If it detects bitrot, it immediately fixes it. As long as the bitrot wasn’t too much, most of your data should be fixed. EDIT: I’m a dumb-dumb. The term was “ZFS scrub”, not scan.

If you’re playing with multiple computers, “choosing” one to be a NAS and being extremely careful with its data that its storing makes sense. Regularly scanning all files and attempting repairs (which is just a few clicks with most NAS software) is incredibly easy, and probably could be automated.