Live data from Hacker News

So this guy is now S3. All of S3

chaos.social

11–20 of 522 posts

Re: So this guy is now S3. All of S3

#11

Unless it's been recently updated their help article only lists TXT record for verification https://blueskyweb.xyz/blog/4-28-2023-domain-handle-tutorial

Everything is moving very quickly, this is just generally the case for anything related to at protocol/bluesky (which is fine, they've been quite busy).

Re: So this guy is now S3. All of S3

#12

Without understanding all the context, why not just serve files directly from your smartphone? You can approve your own contact list and share keys. Yes, of course bandwidth is a concern, but then again there should be our way to monetize, and that's entirely possible using direct payments which already exist. A little bit of cashing, CDN, and your phone as the initial file server. Tag a photo or video has shared. Re…

I think this is not about using s3 to serve files, but someone having verified owning s3 on bsky by putting some challenge file in his bucket. My guess, also missing context.

Re: So this guy is now S3. All of S3

#16

Without understanding all the context, why not just serve files directly from your smartphone? You can approve your own contact list and share keys. Yes, of course bandwidth is a concern, but then again there should be our way to monetize, and that's entirely possible using direct payments which already exist. A little bit of cashing, CDN, and your phone as the initial file server. Tag a photo or video has shared. Re…

I think this is not about using s3 to serve files, but someone having verified owning s3 on bsky by putting some challenge file in his bucket. My guess, also missing context.

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 "/xprc/com.atproto.identity.resolveHandle" rel="nofollow">https:///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.

Re: So this guy is now S3. All of S3

#18
post #2

I mean I think you could also do this on Mastodon but it would just show a "verified" highlight for amazon s3 in your profile, not that it would get verified as your username.

No, you can’t. To own s3.amazon.com the HTML on that exact domain and not a sub path needs to have a specific link back to your profile on it.
Post reply on HN