zlacker

[return to "So this guy is now S3. All of S3"]
1. sidmit+72[view] [source] 2023-05-04 19:03:05
>>aendru+(OP)
For those not getting the context(like me), this seems to be about the Bluesky Social(https://bsky.app/), a twitter alternative.
◧◩
2. pyentr+d7[view] [source] 2023-05-04 19:24:57
>>sidmit+72
Further context: Bluesky lets you use a domain name you own as a user handle.

The official method is to set a TXT record, but apparently their "AT protocol" also lets you confirm a domain by serving `GET your.domainname.com/xrpc/com.atproto.identity.resolveHandle`

and `xrpc` was available as an S3 bucket name :)

◧◩◪
3. mwint+s9[view] [source] 2023-05-04 19:35:11
>>pyentr+d7
Stunning that there are (were) any 4-char bucket names left.
◧◩◪◨
4. ec1096+4k[view] [source] 2023-05-04 20:27:20
>>mwint+s9
Path based bucket addressing isn't supported anymore, so this must be a legacy bucket: https://aws.amazon.com/blogs/aws/amazon-s3-path-deprecation-...
◧◩◪◨⬒
5. electr+Oz[view] [source] 2023-05-04 21:51:42
>>ec1096+4k
No, they indefinitely delayed that deprecation. It's still delayed. I bet[1] it never happens. They haven't figured out what to do with S3 VPC endpoints and buckets with dots in the name, which both to this day require path-based addressing and are both completely legitimate uses. They just stopped talking about this plan entirely and it's been years; I think it's dead.

[1] If they ever actually turn off path-style addressing, come find me and I'll PayPal you a dollar. I don't think it'll ever happen.

[go to top]