ipv6 vs ipv4:

ipv6 can't access github
ipv6 can't access bluesky

conclusion: ipv6 wins

if this post leaves target audience i'm killing myself !

@zen don’t do that

@nay @zen they're on AWS, they really have no excuse for this (and apparently you need IPv4 to run a PDS too, presumably because their relay doesn't support IPv6 either)

@sneexy i haven't gotten a single comment about claudeberg or mastodon yet so it's okay

@nay @noisytoot interesting that jetstreams are on ovh and do have v6

desktop@fedora:~$ host jetstream1.us-east.bsky.network
jetstream1.us-east.bsky.network is an alias for vps-f9e51aad.vps.ovh.us.
vps-f9e51aad.vps.ovh.us has address 15.204.205.133
vps-f9e51aad.vps.ovh.us has IPv6 address 2604:2dc0:101:200::2567

but the new sync-v1.1 relays are still v4 only, despite being owned and hosted by bsky pbc??

desktop@fedora:~$ host relay1.us-west.bsky.network
relay1.us-west.bsky.network has address 108.179.139.11

@zen wait isn’t Bluesky only a couple of years old how the fuck did they not add ipv6 support from the start

@zen I recently learned you can skip NAT entirely with IPv6 and now I kinda want DNS for IPv6 prefix. Like let me access [home.jellycopter.net::10.28]

@zen @nay AS19317 does not have IPv6 at all (and they don't seem to have any unannounced ARIN IPv6 allocations either)

@zen what is target audience

@gkrnours DNS A6 records were somewhat kind of supposed to give that. Great idea in theory, failed in practice. Everyone just went with AAAA because that actually worked. Simplifying somewhat.

(A6 RRs let you specify an arbitrary-length prefix by reference to another A6 RR. Which could come from anywhere, including from, say, your upstream router.)

@zen

@fauli1221
almost as if it was some kind of minimum viable pseudodecentralized sham. weird how those turn out to be technically lacking.
@zen