Readit News(Or use any other OCR solution you like; I've got a prototype that takes a screenshot and runs it through tesseract.)
We'll come full-circle when web authors provide custom-made glasses to decipher their sites, as the plain rendering will be obfuscated to prevent OCR too.
This goes well beyond accessibility and bots. I guess the Reader mode, a basic web browser feature meant precisely to read articles, wasn't an expected use case either?
The solution is to lose even more of your time (as if public transport wasn't slow enough already) and be at the station already for the previous schedule of what you'd ideally need to take. But at that point, sometimes it's just better to go a longer route by subway, or if traffic is not bad, go ahead by car for those occasions.
Until web browsers started to believe that no, that was too much of a convenience, so now long expiration certs became rejected. What's the proposed solution from the "industry"? to run a whole automation pipeline just to update a file in each example folder every few months? bonkers. These should be static examples, no reason to having to update those any earlier than every few years, at most.
Except that making their client FOSS would help a lot to replicate the APIs and create a FOSS server, which would definitely make a difference on how they make money.
Docker has security issues if you're not careful, and it's frankly kind of a shitshow out of the box with defaults. Maybe that's part of the reason. But I struggle to see how a bespoke solution like this is the right answer.
This is unfortunately going to be the deal breaker for wide adoption. Self hosting is great, but manually importing data from dozens of accounts every day and entering every single transaction as you make it is simply too much of a burden.
Here are some other ones I've tried and used in the past:
I know this is a dumb idea, but I would love to know exactly why.