OK, one of my clients is a payday lender in a wealthy country. I have the complete banking histories of 10s of thousands of low income people in front of me.
I insist that the distinguishment proposed in the article is BS.
There is a small subset of clients with disabilities AND absense of insurance/government pensions, whose situation is permanent for all intents and purposes. But everyone else, one-off clients as well as regulars have ups and downs, and get through defaults or manage to repay their debt at times.
Gambling and alcohol are a clear factor (drug abuse is harder to identify on someone's bank statement), but cases such as divorce from a partner with abuse problems bring relief most of the time. Children grow up or grow older and require less work or even generate income of their own.
I know it's different, when you live in a low income country and everyone around is poor and scamming people on the internet or marine piracy are the only possible access options to wealth, but that's a different topic.
Question, how hard is it going to be to add XSLT back with WASM? I have built a few stylesheets for clients to view their raw XML in browser. I even add charts for data tables with XSLT.
In theory, there is rule of law, the intention of which is to prevent government's access to your property and body without a court order and any emergency access such as use of force at crime scenes being subject to public scrutiny.
I guess that was the idea when the USA was established as a country, but people forgot what their ancestors where fighting for.
Imagine a Russia-friendly party getting elected. Doesn't have to be overtly pro-russian. Can be someone very nationalist like Marine Le Pen in France. Or socialist like Sarah Wagenknecht in Germany. Just someone with financially dependent on Russia, or simply owing them favour.
Now imagine them accidentally leaving some loophole in the system, such that Russians get read or maybe even write access to data.