How (why) does that site block reader mode... At least on Firefox Android it offers the reader mode button, but turning it on just redirects back to the page (which is too wide, hence the reader mode attempt)
Juxt's Allium https://juxt.github.io/allium/ is an interesting entry in this 'pseudo DSL' space to define and store system specifications and requirements. I think it's likely that this sort of 'persistent specifications to help bots work correctly' will be a good approach when things finally cool down a bit.
Onego Bio is using fungi to produce ovalbumin, one of the major protein in eggs. Their process seems stable, so it might play a big role especially in industrial food production pretty quickly
Humble Bundle has spoiled me and my ebook library has grown by around a 100 books this year...
Tech book recommendations: 'Secure by Design', 'Designing Data-Intensive Applications', 'Building Secure and Reliable Systems' and 'Fundamentals of Software Architecture'.
For scifi: 'Murderbot Diaries' and 'The Expanse' - both are just great entertainment
From a user perspective, yeah, practically every site I have to create an account for would be better if the signup was that simple. They're all basically one time throwaway accounts anyway, so why not treat them as such at the service level. Of course from the business view, there's all sorts of reasons, but one can dream...
Thanks for pointing out the terms of service agreement thing - it was so unobtrusive that I just glanced over it!
What I was refering to was the "why", not the "what" or "how". This is not a good function name to my eye, but YMMV: get-station-id-working-around-vendor-limitation-that-forces-us-to-route-the-call-through-an-intermediary-entity.
Instead, a comment can clearly and succintly tell me why this implementation is seemingly more complex than it needs to be, link to relevant documentations or issues etc.
> Comments is a self-admission you failed to write readable code, and you can fix your failure by refactoring code into self-descriptive member functions
This may be true for some cases, but I don't see a non-contrived way for code to describe why it was written in the way it does or why the feature is implemented the way it is. If all comments are bad, then this kind of documentation needs to be written somewhere else, where it will be disconnected from the implementation and most probably forgotten
Pi-hole is such a great tool. I've been running it for a few years on a raspberry pi zero, and am constantly astonished by the sheer amount of cruft it blocks for me.
Congratulations to the team for the release - happy to support you via Patreon!