Live data from Hacker News

So this guy is now S3. All of S3

chaos.social

151–160 of 522 posts

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

#151
post #118

Earlier quoted context omitted.

It's not that hard to modify code.. and I'd argue it's new enough that people should expect growing pains if they want to be early adopters... "Death" of a product for one bug? ....

This was a simple thing, the fact they got it so wrong only makes me wonder what other bad choices have been made.

Have you... ever worked at a software startup?

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

#152
post #60
post #50

> 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.

So to answer GP's question, yes.

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

#154
post #50

> 429 Too Many Requests Aight, level with me: Is every mastodon server running on a Raspberry Pi?

Not really: h https://leah.is/posts/scaling-the-mastodon/ They just got 6 times the normal requests: https://chaos.social/@ordnung/110312089838674624

unfortunately this is exactly why mastodon won't work

I already don't trust mastodon links because 9 times out of 10 they simply don't work. Everyone's tiny hobby server falls over when one post gets big, and obviously not everyone is going to scale their servers to support the load of a viral post that might happen once every 6 months and will be 100x their base load

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

#155
post #138
post #32

bluesky dev here. whoops. as others mentioned, not a hard fix.

[flagged]

(not paul)

Given that the AT Protocol is not compatible with ActivityPub, I don't see how the first step, let alone the second or third, is an accurate description of the dynamics at play here.

> And also how long until Twitter 2.0 or X app uses AT

Ironically, pre elon-buys-twitter, it did in fact look like Twitter was going to end up implementing AT, if all went to plan. But then post acquisition, if anything, that looks less likely.

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

#156

Earlier quoted context omitted.

What about serving the challenge file from the root or a near-root of the fully qualified url? Like www.domain.com/mastodon.txt or abc.freehost.com/mastodon.txt? Maybe I'm old but what are some popular use cases for webfinger? (I'm just learning about it now)

The /.well-known/ path prefix is the standard name to use ( https://www.rfc-editor.org/rfc/rfc8615 ) so that any sort of “we’ll host user content from our domain” thing can block it. (Hosting user content from the user’s domain is fine and doesn’t need this restriction.) A few things are effectively grandfathered in due to their vintage: /favicon.ico, /sitemap.xml and /robots.txt are the three that occur to me—so if…

I learned something new today. I guess .well-known's purpose isn't well known!

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

#158
post #134

Earlier quoted context omitted.

Aren’t federated services grand?

[flagged]

> It looks like these links auto-redirect when I access them from here, but when you access them from the homeserver they are served without redirect

"Works on my machine" isn't going to cut it for running a popular social network

Nobodies going to go around searching for mirrors, they'll just leave and go back to twitter

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

#160
post #42

Earlier quoted context omitted.

Stunning that there are (were) any 4-char bucket names left.

Path based bucket addressing isn't supported anymore, so this must be a legacy bucket: https://aws.amazon.com/blogs/aws/amazon-s3-path-deprecation-...

Path style access is supported for new buckets, at least for now

https://docs.aws.amazon.com/AmazonS3/latest/userguide/access...

Post reply on HN