This may be useful for improving security, especially of CDNs. Binary Transparency seems to be one of the use cases mentioned in the spec[1] - perhaps someday this would be used for an unified scheme for signing application packages/updates, without reinventing the wheel every time.
As for binary transparency it's not enough to stamp the certificate (that's what CT logs do). The artifact would have to be stamped and published in a widely accessible source. Actually Binary Transparency doc published by Mozilla [1] creates a new regular certificate for new published binary thus utilizing CT infrastructure as it is today.
I'm not sure whether it's comparable, but Chris Squire from Yes spent months "hibernating" in a hotel after a bad trip with homemade acid:
“I’d had lots of good acid trips prior to that. But I made the mistake of trying some acid some friends of mine had homemade. That knocked me back, and I did sort of hibernate in an apartment in Kensington and spent quite a few months — maybe as much as a year — just playing bass.”
They are hands down the best email provider I've used. I moved from Gmail to them and the speed, support, and reliability is head and shoulders above even the paid Google service.
They don't really need a TLS cert for your domain - they don't host your website; the MX record in your domain just points at a host in one of their domains (for which they have the TLS certificate); and the 'mail.yourdomain' address just redirects to https://www.fastmail.com.
This won't work, at least on Chrome. It blocks all cross-domain requests to localhost[1]. Even if the target is used with a domain that resolves to 127.0.0.1, or has CORS completely disabled with "Access-Control-Allow-Origin: *".
Would be nice to have an option for different art pieces on different spaces as well. For example, I use 4 spaces on my primary display and 1 space on the external one and I'd be delighted if I had 5 different art pieces shown.
This may be useful for improving security, especially of CDNs. Binary Transparency seems to be one of the use cases mentioned in the spec[1] - perhaps someday this would be used for an unified scheme for signing application packages/updates, without reinventing the wheel every time.
[0]: https://developers.google.com/web/updates/2019/03/nic73#sgx
[1]: https://wicg.github.io/webpackage/draft-yasskin-http-origin-...