zlacker

[parent] [thread] 5 comments
1. stevek+(OP)[view] [source] 2023-05-04 19:15:33
That is correct.

1. Bluesky allows you to use a domain as a handle by creating a TXT record on an _atproto subdomain of the domain you wish to use (see https://mxtoolbox.com/SuperTool.aspx?action=txt%3a_atproto.s... for mine)

2. You can also serve up your DID by having the URL "https://<handle>/xprc/com.atproto.identity.resolveHandle" return the DID.

3. AWS buckets have the URL structure http://s3.amazonaws.com/[bucket_name]/

4. register "xrpc" as an S3 bucket, drop a file named "com.atproto.identity.resolveHandle" with the correct JSON in it

5. boom! your username can now be s3.amazonaws.com

Hope that helps.

replies(2): >>silisi+y5 >>justin+eb
◧
2. silisi+y5[view] [source] 2023-05-04 19:39:48
>>stevek+(OP)
Thanks for the explanation. Kinda surprised xrpc hadn't been registered as a bucket name long ago. Or maybe it was.
replies(1): >>schlar+97
◧◩
3. schlar+97[view] [source] [discussion] 2023-05-04 19:46:57
>>silisi+y5
Just created it yesterday. I don't think there's as much incentive to squat on the S3 namespace like there is for domain names.
replies(1): >>Sohcah+Vc
◧
4. justin+eb[view] [source] 2023-05-04 20:07:32
>>stevek+(OP)
Sounds like Bluesky screwed up by not implementing the https://publicsuffix.org/ list
replies(1): >>stevek+se
◧◩◪
5. Sohcah+Vc[view] [source] [discussion] 2023-05-04 20:15:44
>>schlar+97
Yeah, a bucket name isn't the face of your company.

At a previous company I worked at, every bucket had the company name prefixed. Never had a problem with squatters.

I wonder if Amazon actually has any policies to prevent squatting.

◧◩
6. stevek+se[view] [source] [discussion] 2023-05-04 20:23:51
>>justin+eb
The root cause here IMHO is more subtle than that, but I do agree that implementing that at some point is probably a good idea.
[go to top]