> 429 Too Many Requests Aight, level with me: Is every mastodon server running on a Raspberry Pi?
Not really: hhttps://leah.is/posts/scaling-the-mastodon/
They just got 6 times the normal requests:
https://chaos.social/@ordnung/110312089838674624
So this guy is now S3. All of S3
81–90 of 522 posts
Re: So this guy is now S3. All of S3
#82Earlier quoted context omitted.
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.
What about the next 500 easy-to-fix bugs?
Is there a public test suite?
Re: So this guy is now S3. All of S3
#83[flagged]
Re: So this guy is now S3. All of S3
#84This 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?
It's not about proving ownership, if it was about proving ownership we would do this via something at the registrar level.
It's about proving /control/. If a domain name is pointed to me (my IP/CNAME) I control it and it is reasonable to allow that person to issue an SSL certificate for a domain (or subdomain) under their control. If you, as the domain owner, want to restrict that, CAA exists as your tool to do so.
Re: So this guy is now S3. All of S3
#85bluesky dev here. whoops. as others mentioned, not a hard fix.
Do you have a public test suite so we can see how solid your protocol is?
Re: So this guy is now S3. All of S3
#86[flagged]
Re: So this guy is now S3. All of S3
#87This 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?
If you control a domain's DNS entry but I can serve arbitrary content to users from its servers, who really owns the domain?
Re: So this guy is now S3. All of S3
#88This 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?
DNS challenge is required for wildcards on LE at the very least.
But the reason for HTTP is pretty simple - it's extremely easy to implement. You only need to tell your ops to redir a subdomain to your app and you're done, you don't need DNS with API that have narrow enough permission to allow that one team in whole company to generate ACME stuff; most providers ACLs on DNS end at "this client have acesss to that domain via API".
Re: So this guy is now S3. All of S3
#89> 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.
> slowing down the entire site
This is mind-blowing. Last I checked, the front page of HN sends tens of requests per second to each link. There are humans who can pack envelopes faster than the typical mastodon server can answer GETs. I'd love to see someone benchmark the top servers for a few seconds to see what it takes to break a reasonable latency SLA.
Re: So this guy is now S3. All of S3
#90> 429 Too Many Requests Aight, level with me: Is every mastodon server running on a Raspberry Pi?
No trouble viewing it from another Mastodon server:
https://hachyderm.io/@jonty@chaos.social/110307532115312279
EDIT: Ah I guess if you're not logged into a hachyderm.io account, you get forwarded. So probably don't use the above link.