hartz

More widespread use of DNS-over-TLS/HTTPS/QUIC can't come soon enough

I'm also excited to see where this leads.

From the release notes:

> Go programs currently compile to one WebAssembly module that includes the Go runtime for goroutine scheduling, garbage collection, maps, etc. As a result, the resulting size is at minimum around 2 MB, or 500 KB compressed.

The minimum size is a bit unfortunate, but after all it is still just experimental.

Wow, I didn't know that they just shut down this month. I definitely still have the add-on installed in all my browsers, and thought it was still syncing...

You still see these "trackless trolleys" in Boston too where some of the old streetcar and trolley lines used to be. (Unfortunately, most of those streetcars were replaced with diesel busses instead)

I think it would be useful to implement some security against this at the registrar level (until a better fix is more broadly available). For example, if I'm registering "epic.com" (the ASCII version), the registrar could suggest that I also register "epic.com" (the Cyrillic version), or vice versa. This could at least help site owners avoid phishing attacks on their own domains.

Unfortunately, this would require all the big registrars to be on board for it to actually be effective.

The point of standards for browsers is that you shouldn't need a polyfill just to support a feature (localStorage) in one browser. Ideally, it would just destroy its contents after your private browsing session is done, just like the way (I believe) all browsers treat cookies in private browsing mode.

Probably not normal people using cards, but it wouldn't be hard to train cashiers/managers what to look for. However, this would probably just lead to shimmers made out of clear plastic