I'm glad I read the HN comments, now I'm excited to review the source.

Thanks for your hard work.

ETA: I like your option parser

You could even write a plugin for your favorite web browser to do that to every site you visit.

It seems hard to achieve the inverse that is (would you rather I use i.e.?) rewrite this paragraph as the original author did before they had an AI re--write it to make it clean, (--do you like oxford commas, and em/en dashes! Just prompt your AI) and easier to read

There are many places that don't even allow rights (or lefts) on red.

I got a right on red ticket once, and then I made it a point to obey the law -- especially at the intersections with the robots.

For things like traffic laws especially (where there are very simple cut and dry rules), why is it okay to break the law, and why is it not okay for robots to enforce the law?

There is a tacit agreement in polite society that people should be paid that minimum wage, and by tacit agreement I mean laws passed by the government that democratic countries voted for / approved of.

The gig economy found a way to ~~undermine that law~~ pay people (not employees, "gig workers") less than the minimum wage.

If you found a McDonalds paying people $1 per hour we would call it exploitative (even if those people are glad to earn $1 per hour at McDonalds, and would keep doing it, the theoretical company is violating the law). If you found someone delivering food for that McDonalds for $1 per hour we call them gig workers, and let them keep at it.

I mean yeah, it's not as bad as being tortured forever? I guess? What's your point?

[1] https://en.wikipedia.org/wiki/List_of_countries_by_minimum_w...

I really like having some JSON storage because I don't know my schema up front all the time, and just shoving every possible piece of potentially useful metadata in there has (generally) not bit me, but not having that critical piece of metadata has been annoying (that field that should be NOT NULL is NULL because I can't populated it after the fact).

I definitely use boiling water with my bagged breakfast tea, but boiling is too hot for white and green tea (especially fancier teas), and boiling water "scorches" the "delicate flavors" (using quotes since I'm sure there are better / nicer words than those), so you want to steep at 80C or lower depending on the tea, the quantity the vessel, and the process.

Great stuff. Thank you for linking this.

It's a regular occurrence that I visit a page with firefox either on android, or desktop linux, and a basically default ublock origin that fails to render. I generally then try the page in an incognito tab, and then try the page in chrome and it loads, and displays properly.

I'm also maybe moving the goal posts from "have feature parity with Chrome, and render HTML correctly" to "I never have to use vanilla chrome, because vanilla firefox just works". There are cases where sites claim DRM issues with firefox which I can kind of understand, but there are other sites that just refuse to work with vanilla firefox that work with chrome. I of course can't really point to any examples, because they're not sites I regularly visit, but they definitely exist.

I live in a place with a fixed VAT (that is included in the price on the shelf / menu / ...), but grew up in the US in several different weirdly taxed localities. It's just such a silly argument to say "we can't write the correct price on the shelf because the laws vary." The register knows the correct price, the labels on the shelf are computer generated, and updated regularly. The labels at many nation wide fast food type places are displays anyway.

If Baarle-Hertog and Baarle-Nassau can make it work I feel like it's at least imaginable that stores that already automate this weird complex tax code could print accurate labels instead of inaccurate labels, with an accurate calculation at sales time.

I know it's hard to imagine the price on the shelf being the price that you pay, but I believe it is possible even in complex tax situations.