Yeah because Meltdown and Spectre [0] weren't a thing.

[0] https://spectreattack.com/

If passwords are fetched remotely on-demand, you steal the account API key from memory. If they're encrypted, you steal the master password or decryption key. ... So what's your solution?

That seems like it would be hard to see, even for the person sitting right in front of it.

My university also taught best practices alongside that, everytime. I am very grateful for that.

I get a choice, at least in the EU. Admittedly you need to scroll down a bit on mobile, which is not clear at first.

Heh (in the EU at least) the div container has a `has-reject-all-button` class.

    <div id="onetrust-button-group-parent" class="ot-sdk-columns has-reject-all-button ot-sdk-two">
        <div id="onetrust-button-group">
            <button id="onetrust-accept-btn-handler">
              Accept All
            </button>
            <button id="onetrust-reject-all-handler">
              Essential Cookies Only
            </button>
            <button id="onetrust-pc-btn-handler" aria-label="Show Purposes, Opens the preference center dialog">
              Show Purposes
            </button>
        </div>
    </div>

Would be funny if the button was merely hidden outside of the EU xD

It is not present in the DOM at all in my location (US).

Finally. It was the reason I was always reluctant to buy something from GOG.

This at the same time super cool and really disappointing, as I've been carrying around this idea in my head for maybe ten years as a cool side project and never got around to implementing it.

However, there might still be room for competition, heh. I always wanted to do this on the _entirety_ of Unicode to try getting the most possible resolution out of the image.