Remember that Discover is self-banked (unlike Visa/Mastercard that banks sign up with). This means that every credit line needs to be backed by… well … A bank.
Bigger banks mean more credit opportunities, better interest rates (etc. etc). Deeper credit lines.
What’s wrong with Capital One? I feel like Discover/Capital One / Diner’s Club network is a good thing for Discover customers.
Discover and Diners Club merged a few years ago btw. Discover also has an alliance with JCB.
So Discover network is actually really, really big.
Discover has an alliance with JCB. So that’s just Discover in the USA.
Ummmm.
ACH is how you get your paycheck, and it’s being updated to FedNow.
Zelle is an independent network as well.
And of course, there is Discover and AmEx.
There is also cash, check, money order. They still work today, just people largely forgot how to use them.
IIRC some Brazilian network was getting very popular off of this. If you want to look at non-US options.
There are plenty of competitors to Visa/Mastercard/Paypal.
Hmm. Hear me out. Let’s say we have a medallion system where government regulated drivers drive tracked cars so that there were some assurances that the drivers are trustworthy.
Then the next Billionaire with a massive ego and huge budget comes out and makes another one.
Or we get Jack Dorsey making a new company for a 3rd time.
My post above is 376 characters, which would have required three tweets under the original 140 character limit.
Mastodon, for better or worse, has captured a bunch of people who are hooked on the original super-short posting style, which I feel is a form of Newspeak / 1984-style dumbing down of language and discussion that removed nuance. Yes, Mastodon has removed the limit and we have better abilities to discuss today, but that doesn’t change the years of training (erm… untraining?) we need to do to de-program people off of this toxic style.
Especially when Mastodon is trying to cater to people who are used to tweets.
Your post could fit on Mastodon
EDIT: and second, Mastodon doesn’t have the toxic-FOMO effect that hooks people into Twitter (or Threads, or Bluesky).
People post not because short sentences are good. They post and doom-scroll because they don’t want to feel left out of something. Mastodon is healthier for you, but also less intoxicating / less pushy. Its somewhat doomed to failure, as the very point of these short posts / short-engagement stuff is basically crowd manipulation, FOMO and algorithmic manipulation.
Without that kind of manipulation, we won’t get the kinds of engagement on Mastodon (or Lemmy for that matter).
Because Threads and BlueSky form effective competition with Twitter.
Also, short form content with just a few sentences per post sucks. It’s become obvious. That Twitter was mostly algorithm hype and FOMO.
Mastodon tries to be healthier but I’m not convinced that microblogs in general are that useful, especially to a techie audience who knows RSS and other publishing formats.
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:
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.
Filesystems like ZFS or BTFS, are designed to handle many many bits of bitrot safely.
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.
If you have a NAS, then just put iSCSI disks on the NAS, and network-share those iSCSI fake-disks to your mini-PCs.
iSCSI is “pretend to be a hard-drive over the network”. iSCSI can exist “after” ZFS or BTRFS, meaning your scrubs / scans will fix any issues. So your mini-PC can have a small C: drive, but then be configured so that iSCSI is mostly over the D: iSCSI / Network drive.
iSCSI is very low-level. Windows literally thinks its dealing with a (slow) hard drive over the network. As such, it works even in complex situations like Steam installations, albeit at slower network-speeds (it gotta talk to the NAS before the data comes in) rather than faster direct connection to hard drive (or SSD) speeds.
Bitrot is a solved problem. It is solved by using bitrot-resilient filesystems with regular scans / scrubs. You build everything on top of solved problems, so that you never have to worry about the problem ever again.
deleted by creator
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.
Honestly, Docker is solving the problems in a lot of practice.
Its kinda stupid that so many dependencies need to be kept track of that its easier to spin up a (vm-like) environment to run Linux binaries more properly. But… it does work. With a bit more spit-shine / polish, Docker is probably the way to move forward on this issue.
But Docker is just not there yet. Because Linux is Open Source, there’s no license-penalties to just carrying an entire Linux-distro with your binaries all over the place. And who cares if a binary is like 4GB? Does it work? Yes. Does it work across many versions of Linux? Yes (for… the right versions of Linux with the right compilation versions of Docker, but yes!! It works).
Get those Dockers a bit more long-term stability and compatibility, and I think we’re going somewhere with that. Hard Drives these days are $150 for 12TB and SSDs are $80 for 2TB, we can afford to store those fat binaries, as inefficient as it all feels.
I did have a throw-away line with MUSL problems, but honestly, we’ve already to incredibly fat dockers laying around everywhere. Why are the OSS guys trying to save like 100MB here and there when no one actually cares? Just run glibc, stop adding incompatibilities for honestly, tiny amounts of space savings.
Because it isn’t inferior.
Ubuntu barely can run programs from 5 years ago, backwards compatibility is terrible. Red Hat was doing good but it just shit the bed. To have any degree of consistenty, you need to wrap all apps inside of a Docker and carry with you all the dependencies (but this leads you to obscure musl bugs in practice, because musl has different bugs than glibc).
For better or worse, Windows programs with dependency on kernel32.dll (at the C++ level) have remained consistently deployed since the early 1990s and rarely break. C# programs have had good measures of stability. DirectX9, DirectX10, DirectX11, and DirectX12 all had major changes to how the hardware works and yet all the hardware automatically functions on Windows. You can play Starcraft from 1998 without any problems despite it being a DirectX6 game.
Switch back over to Ubuntu land, and Wayland is… maybe working? Eventually? Good luck reaching back to programs using X.org dependencies or systemd.
Windows is definitely a better experience than Ubuntu. I think Red Hat has the right idea but IBM is seemingly killing all good will built up to Red Hat and CentOS. SUSE linux is probably our best bet moving forward as a platform that cares about binary stability.
Windows networking stack is also far superior for organizations. SAMBA on Linux works best if you have… a Windows Server instance holding the group-policies and ACLs on a centralized server. Yes, $1000 software works better than $0 software. Windows Server is expensive but its what organizations need to handle ~50 to ~1000 computers inside of a typical office building.
Good luck deploying basic security measures in an IT department with Linux. The only hope, in my experience, is to buy Windows Server, and then run SAMBA (and deal with SAMBA bugs as appropriate). I’m not sure if I ever got a Linux-as-Windows-server ever working well. Its not like Linux development community understands what an ACL is in practice.
I dunno the one you’re talking about, but I use search-lemmy.com
As I said in my post, one community I follow (RealTesla) keeps track of this. Years ago there was this French case: https://www.bloomberg.com/news/articles/2021-12-16/why-the-ev-world-should-worry-about-unintended-acceleration
And several other cases over the years, the Chinese case I linked above being one of the more recent ones I remember personally.
This report changes everything. All of these events were dismissed by Tesla engineers recovering the black box and saying that the pedal was pushed the whole time.
Alas, we now know that when the ADC miscalibrates, the Tesla computer thinks (for a few minutes) that the computer thinks the accelerator is pressed even when it isn’t pressed in reality. This complaint is very enlightening, we cannot trust the Tesla telematics / logs. The computer is wrong at the fundamental analog level before the data even leaves the ADC.
Itch.io is currently saying the problem is Stripe, and maybe Visa.
Historically (ex: https://otakuusamagazine.com/visa-and-mastercard-refuse-to-work-with-another-doujinshi-retailer/), I’d say Mastercard and Visa are both to blame. But the jury is still out on wtf is going on here.
I’m not sure who pressured Steam. But Itch.io (https://aftermath.site/steam-itch-porn-censorship-collective-shout-visa-mastercard-paypal) is claiming Stripe and Visa are pressuring them.