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. CydeWe+Qj[view] [source] 2023-05-04 20:26:22
>>mwint+s9
I guess I'm not too surprised in that, unlike domain names, these aren't obviously exposed to end users, so terseness doesn't particularly matter. Verbose and descriptive is honestly better for most names.
◧◩◪◨⬒
5. mikepu+Gr[view] [source] 2023-05-04 21:06:22
>>CydeWe+Qj
And given that bucket names are a giant shared namespace, there's absolutely an incentive toward lots of prefixing to help ensure you get the ones you want.
◧◩◪◨⬒⬓
6. jackso+NT[view] [source] 2023-05-05 00:12:35
>>mikepu+Gr
Yep, when writing IaC I always just give it a prefix like "$project-web" and terraform adds a long string of numbers at the end. It's going through CloudFront anyways, so no one should be referencing the bucket name directly unless they're writing to it (and writers can just do `aws s3 ls` to find the name).
[go to top]