gslin

The latest deployment seems using Service Worker API, which causes broken on "old" browsers because the API is not supported on these browsers.

Some people like me who block Service Worker API all the time are also affected, like https://chromewebstore.google.com/detail/no-service-worker/m... this.

It seems also answer https://retrocomputing.stackexchange.com/questions/14903/why... this.

Something related/non-related, it's still painful to read specific timezone not UTC.

This reminds me some other interesting things (but from Linux to FreeBSD) around 15-20 years ago:

* https://www.daemonology.net/depenguinator/

This makes me watch https://en.wikipedia.org/wiki/11001001 again.

https://archive.is/hYvUp for most contents.

$10/mo + usage fee:

    Amsterdam $0.01 / GB
    Atlanta $0.01 / GB
    Bangalore $0.05 / GB
    Chicago $0.01 / GB
    Dallas $0.01 / GB
    Delhi NCR $0.05 / GB
    Frankfurt $0.01 / GB
    Honolulu $0.01 / GB
    Johannesburg $0.05 / GB
    London $0.01 / GB
    Los Angeles $0.01 / GB
    Madrid $0.01 / GB
    Manchester $0.01 / GB
    Melbourne $0.05 / GB
    Mexico City $0.05 / GB
    Miami $0.01 / GB
    Mumbai $0.05 / GB
    New Jersey $0.01 / GB
    Osaka $0.03 / GB
    Paris $0.01 / GB
    Santiago $0.05 / GB
    São Paulo $0.05 / GB
    Seattle $0.01 / GB
    Seoul $0.05 / GB
    Silicon Valley $0.01 / GB
    Singapore $0.03 / GB
    Stockholm $0.01 / GB
    Sydney $0.05 / GB
    Tel Aviv $0.05 / GB
    Tokyo $0.03 / GB
    Toronto $0.01 / GB
    Warsaw $0.01 / GB

Their topology page has information about PHL/AMS and FRE (seems like Fremont datacenter):

https://web.archive.org/web/20240111132224/https://man.sr.ht...

Also https://archive.is/C7fu0

Also screenshoted at https://web.archive.org/web/20231005115750/https://hn.algoli... and https://archive.ph/JLqBo

This page is somehow quite interesting, returning 404:

    $ http https://openai.com/dall-e-3
    HTTP/1.1 404 Not Found
    Cache-Control: no-cache
    Connection: keep-alive
    Content-Encoding: gzip

But others seem returning normal 200.

> We reported the vulnerability at 2023-07-12 20:15:43 UTC and received the ACK at 2023-07-12 01:34:54 UTC.

I am not sure the timeline...

More discussion in https://news.ycombinator.com/item?id=18097661 (2018).

The author is a SRE of HashiCorp (from LinkedIn), so I guess (yeah just guess) what he mentioned in the article is Terraform Cloud, based on the growing business.

The old one: https://web.archive.org/web/20230530172255/https://stackover...

concatenate strings.