These are still used in CDN and internal browser caching

I can’t think of the wording right now but generally JS trying to crash the browser would say something like this page is taking a long time, do you want to wait. Something like that. In this case the browser just crashes.

It does seem like it’s full of AI. The Attack Scenarios are very suspicious.

Gitlab CI can do that. https://docs.gitlab.com/ee/ci/caching/#compute-the-cache-key...

Currently it is Globalstar

That is a different product. LSTC != IoT LSTC, it is so confusing. To get the IoT you have to sign lots of contracts, Microsoft sends you stickers to put on each stuff, stuff like that.

You should check out Huey next time. It is a lifesaver for us. Allows us to do the tasks via SQLite db

I use Huey too. Very simple and easy to manage. From a quick look the proposed tasks system seems similar to it.

Yeah that looks really promising. Haven't done Django as my daily driver for a few years now, and I don't recall stumbling upon it back then!

I wonder what provider they use for their website. Sounds like a lot of hoops to jump through for IPV6 when just about any other provider has IPv6 support.

  $ host www.tailscale.com
  www.tailscale.com has address 76.76.21.21  # Vercel
  www.tailscale.com has IPv6 address 2600:9000:a51d:27c1:6748:d035:a989:fb3c  # Amazon
  www.tailscale.com has IPv6 address 2600:9000:a602:b1e6:5b89:50a1:7cf7:67b8  # Amazon

IPv4 uses a Let's Encrypt certificate, while IPv6 uses an Amazon certificate.

The Vercel IPv6 feature request & surrounding discussion makes for frustrating reading: https://github.com/orgs/vercel/discussions/47

Wow, all comments removed as spam or hidden by default, update posted saying "We are targeting to land support for IPv6 towards the beginning of next year." Well, Q1 2024 has come and gone. Where's IPv6 support or the communication about what is happening? Good reason to never use Vercel if you ask me.

Oh wow, leerob actually edited the post after this removing the ETA (due to management/embarrassment?).

Archive.org captured the original text:

https://web.archive.org/web/20240221195021/https://github.co...

>I apologize for the slow response. We are targeting to land support for IPv6 towards the beginning of next year. We will communicate updates on this issue. Thanks for the patience.

So cringey. Why not just post a new post that said "sorry the deadline slipped, no new date available at the moment"? I will strongly recommend _against_ this company solely based on this communication. If this sort of gaslighting is how they handle their public comms, imagine how their support must be run.

Github is complicit too. No visual indicators or ways of seeing the comment was edited, just the original comment date.

Vercel's VP of product has been asking for requirements for IPv6 there. This should be a good one.

https://github.com/orgs/vercel/discussions/47#discussioncomm...

It painful to see tech providers go down this road, which is pretty similar to what's happening at Boeing. (Business taking over Engineering)

It feels like the same anywhere, sadly, DigitalOceans IPv6 support in their loadbalancer product have been "under review" since 2021: https://ideas.digitalocean.com/network/p/ipv6-for-load-balan...

Only if you expand all the discussion they've hidden! Ignorance is bliss, right?

> We are targeting to land support for IPv6 towards the beginning of next year. We will communicate updates on this issue.

Was from 2023-10-01, I guess it's early until June 30.

I'd say that the beginning of the year ends at the end of Q1, if not earlier.

What is it about ipv6 that is so difficult for hosting providers to support?

It costs money

I use it to get to the airport. No issue with luggage and cheaper than airport long term parking

Well for one there is a hard limit of 1000 s3 buckets per account

Hopefully this will disable the horrible on device AI as well