5 ms·

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

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

opello 2y ago
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.
- watermelon0 2y ago
  I'd say that the beginning of the year ends at the end of Q1, if not earlier.
miyuru 2y ago
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#discussioncomment-4328175 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)
kawsper 2y ago
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-balancers https://ideas.digitalocean.com/network/p/ipv6-for-load-balan...
aftbit 2y ago
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.
- trashburger 2y ago
  Oh wow, leerob actually edited the post after this removing the ETA (due to management/embarrassment?).
  - aftbit 2y ago
    Archive.org captured the original text: https://web.archive.org/web/20240221195021/https://github.com/orgs/vercel/discussions/47 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.
    - averageRoyalty 2y ago
      Github is complicit too. No visual indicators or ways of seeing the comment was edited, just the original comment date.
seabass 2y ago
What is it about ipv6 that is so difficult for hosting providers to support?
- nijave 2y ago
  It costs money

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

opello 2y ago

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.

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

miyuru 2y ago

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#discussioncomment-4328175 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)

kawsper 2y ago

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-balancers https://ideas.digitalocean.com/network/p/ipv6-for-load-balan...

aftbit 2y ago

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.

trashburger 2y ago
Oh wow, leerob actually edited the post after this removing the ETA (due to management/embarrassment?).
- aftbit 2y ago
  Archive.org captured the original text: https://web.archive.org/web/20240221195021/https://github.com/orgs/vercel/discussions/47 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.
  - averageRoyalty 2y ago
    Github is complicit too. No visual indicators or ways of seeing the comment was edited, just the original comment date.

seabass 2y ago

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

nijave 2y ago
It costs money