Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

So this guy is now S3. All of S3

chaos.social

Post reply on HN
Print view View original

51–60 of 522 posts

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

#51

Post by silisili »

steveklabnik wrote: post #16
silisili wrote: post #12

Earlier quoted context omitted.

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…

Thanks for the explanation. Kinda surprised xrpc hadn't been registered as a bucket name long ago. Or maybe it was.

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

#52

Post by chrismorgan »

bob1029 wrote: post #47
paxys wrote: post #15

This is a terrible implementation of domain verification. dns-01 and http-01 are more or less standardized at this point. Use them, and don't roll your own. Reference: https://letsencrypt.org/docs/challenge-types/ .

I don't get http-based verification in general. If you want to really prove someone owns a domain, make them change an authoritative DNS record. Everything else feels like it is begging for edge cases to crop up. Why should my social media or SSL certificate vendor care about my web servers?

Convenience. DNS is routinely not automatable by API, or inconvenient to automate. HTTP, however, is normally easy to work with.

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

#53

Post by seba_dos1 »

steveklabnik wrote: post #43
YtvwlD wrote: post #38

Earlier quoted context omitted.

Okay, yes, but this indicates that they didn't read the ActivityPub before developing their own new shiny protocol.

I don't personally believe that one mistake indicates ignorance of an entire topic.

In general - no, but this kind of fundamental mistake might.

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

#54

Post by [deleted] »

bob1029 wrote: post #47
paxys wrote: post #15

This is a terrible implementation of domain verification. dns-01 and http-01 are more or less standardized at this point. Use them, and don't roll your own. Reference: https://letsencrypt.org/docs/challenge-types/ .

I don't get http-based verification in general. If you want to really prove someone owns a domain, make them change an authoritative DNS record. Everything else feels like it is begging for edge cases to crop up. Why should my social media or SSL certificate vendor care about my web servers?

[deleted]

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

#59

Post by jeroenhd »

NavinF wrote: post #50

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

The server itself seems to work fine. It only seems to be this specific post that's being 429'd. I'm guessing it's some kind of anti-DDoS setup kicking in.

Mastodon is also quite heavy to host, my single user instance will easily gobble up several gigabytes of memory if you let it. There are more efficient ActivityPub servers but specifically Mastodon seems to be written for running efficiently on huge servers.

Post reply on HN