> 429 Too Many Requests Aight, level with me: Is every mastodon server running on a Raspberry Pi?
Maybe, but the admin commented it was intentional for that specific post, it was slowing down the entire site.
So this guy is now S3. All of S3
61–70 of 522 posts
Re: So this guy is now S3. All of S3
#62Earlier quoted context omitted.
I don't personally believe that one mistake indicates ignorance of an entire topic.
In general - no, but this kind of fundamental mistake might.
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.
Re: So this guy is now S3. All of S3
#63Earlier quoted context omitted.
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…
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.
Re: So this guy is now S3. All of S3
#64> 429 Too Many Requests Aight, level with me: Is every mastodon server running on a Raspberry Pi?
Looks like we hugged it to death
Sites like HN and that other one should track this. It could work like flagging - if enough people mark it as hugged to death (HTD), it would say so next to the link. Maybe it could even redirect to an archive if it’s currently HTD.
Re: So this guy is now S3. All of S3
#65Earlier quoted context omitted.
It's ridiculous that this is not in the title.
FWIW it seemed obvious to me. I think a minority of people who play in this space can’t conceptualize others’ understandable ignorance of the norms and axioms. https://xkcd.com/2501/
You got all that from a "429 Too Many Requests". That's an impressive level of deduction Holmes!
Re: So this guy is now S3. All of S3
#66Re: So this guy is now S3. All of S3
#67Re: So this guy is now S3. All of S3
#68Earlier quoted context omitted.
This is a private beta. Nobody is suggesting that any of this be used for anything serious just yet. Development happens out in the open, you can go find out what else they've missed by doing the work, or by waiting until others you trust have done so. I myself have had an account for like a month now, but only started really using it a week ago, because that calculus changed for me, personally. Like, it's not even p…
Okay, yes, but this indicates that they didn't read the ActivityPub before developing their own new shiny protocol.
The pull of NIH is a strong one.
Re: So this guy is now S3. All of S3
#69> 429 Too Many Requests Aight, level with me: Is every mastodon server running on a Raspberry Pi?
From the instance admins: > We just started serving a http 429 error on the exact url of the post. So everything should go back to normal now.
If you go to the user's profile and then to the post, it seems to be okay. So perhaps also looking at Referrer.
Re: So this guy is now S3. All of S3
#70> 429 Too Many Requests Aight, level with me: Is every mastodon server running on a Raspberry Pi?
Aren’t federated services grand?