That article could be reduced to one phrase: "banks off-load mortgage risk by selling that debt to investors".
But that doesn't drive clicks or strike the fear of corporations into your soul.
> Mondex was a smart card electronic cash system, implemented as a stored-value card and owned by Mastercard.
> Mondex allowed users to use its electronic card as they would with cash, enabling peer-to-peer offline transfers between cards, which did not need any authorization, via Mondex ATMs, computer card readers, personal 'wallets' and specialized telephones. This offline nature of the system and other unique features made Mondex stand out from leading competitors at the time, such as Visa Cash, which was a closed system and was much closer in concept to a traditional payment cards' transactional operation.
I find MongoDB's ESR (Equality, Sort, Range) Guideline[0] quite helpful in that regard, which applies to SQL databases as well (since nearly all of them too use B-trees).
> Index keys correspond to document fields. In most cases, applying the ESR (Equality, Sort, Range) Guideline to arrange the index keys helps to create a more efficient compound index.
> Ensure that equality fields always come first. Applying equality to the leading field(s) of the compound index allows you to take advantage of the rest of the field values being in sorted order. Choose whether to use a sort or range field next based on your index's specific needs:
> * If avoiding in-memory sorts is critical, place sort fields before range fields (ESR)
> * If your range predicate in the query is very selective, then put it before sort fields (ERS)
Untrusted doesn’t always mean adversarial IMO, even a bitrot can invalidate your entire input and possibly also trigger undefined behaviour if you aren’t prepared to handle that.
I was using a checksum to protect against "bitrot" since this was over a very noisy serial transmission line (over a slip ring). So, no, there was no "undefined behavior" and it's quite easy to avoid.
> UPDATE: We’ve received notice from Salesforce that our Slack workspace WILL NOT BE DOWNGRADED on June 20th. Stand by for more details, but for now, there is no urgency to back up private channels or direct messages.
For those who didn’t read the full article, because people often don’t, here is the actual / other major reason why Sci-Hub stopped:
> Why Sci-Hub stopped
> The court order was not the main reason Sci-Hub stopped releasing new papers: by 2022 most university libraries implemented two-factor authentication, and as a result, Sci-Hub could not automatically login to libraries using student / researcher username and password to download new papers. Those paywall-circumvention methods that worked well in 2011-2015 became useless in 2022.
They could've defined it as multiple filter lists for different kinds of content like uBlock does, but they chose not to. Therefore, anyone who (understandably and rightfully) want to block CSAM etc are now inadvertently blocking everything else that Protocol Labs disagrees with (e.g. copyright violation).
https://www.bitsaboutmoney.com/archive/mortgages-are-a-manuf...