So this guy is now S3. All of S3
101–110 of 522 posts
Re: So this guy is now S3. All of S3
#102Solution is also on the works like use /.well-known/, so this is more like funny, rather than a big problem. Key to trick was to have bucket named "xrpc" and store a file there: https://s3.amazonaws.com/xrpc/com.atproto.identity.resolveHa... There is also another funny thing in the image, the user posting about is sending one from "retr0-id.translate.goog", which is odd. Somehow he has got https://retr0-id.translate.…
Re: So this guy is now S3. All of S3
#103Unless it's been recently updated their help article only lists TXT record for verification https://blueskyweb.xyz/blog/4-28-2023-domain-handle-tutorial
edit: bsky.app links to blueskyweb.xyz so I guess so. weird.
Re: So this guy is now S3. All of S3
#104Seems like the crypto crowd is moving on to creating flaky decentralized twitter clones now
I'm sure just because of its age and principals involved it's been heavily influenced by the crypto crowd.
But suddenly, without anything else really stepping in to fill the void, it's the Twitter alternative of the day. Anyway not surprised to find some gotcha's like this all things considered.
Re: So this guy is now S3. All of S3
#105Re: So this guy is now S3. All of S3
#106Earlier quoted context omitted.
I hope I never work on software you folks use. The grand claims about something that is not even hard to fix is just wild to me.
What about the next 500 easy-to-fix bugs? Is there a public test suite?
The entire specification (which is admittedly incomplete) and implementation are open source.
I am not aware of a dedicated test suite for alternative implementations. It's too early, IMHO. I personally would much prefer the team to focus their time elsewhere for the time being.
Re: So this guy is now S3. All of S3
#107Re: So this guy is now S3. All of S3
#108Earlier quoted context omitted.
Thanks for the explanation. Kinda surprised xrpc hadn't been registered as a bucket name long ago. Or maybe it was.
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.
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.
Re: So this guy is now S3. All of S3
#109Does anyone have a screenshot? I'm getting a 429.
Re: So this guy is now S3. All of S3
#110Mastadon has no chance if every time something becomes a little bit viral it's instance dies over the traffic.