New Mastodon update… I notice they're finally implementing some of those new features from Bluesky
@mcc look what we can mimic at a fraction of their cost
@mcc we are all free from the madness forever
@mcc looks like traefik or so, without valid backend. Because why would you return a proper error, like 502.
@waldi @mcc i mean to me it smells kubernetes ingress-nginx but it's incredibly generic and i might just be jaded
@mcc That just looks like what my reverse proxy spits out when a container is still spinning up (or has gone down, or is misconfigured, etc) 👀

@mcc

Clearly, this is the modern DDoS prevention tactic. /s

@mcc
What can't you see, cannot hurt you
@mcc Reminds me, I need to look into Docker Rollout.

@mcc
Yes, @pachli showed me the following error message…

❝A network error occurred: your server is mis-configured and returned 'HTTP 404: GET /api/v1/statuses/116455746087232677' with the wrong content-type, 'text/plain; charset=utf-8'

RETRY❞

I had to attempt posting this message twice because I got HTTP 404 errors about uploading the image.

@sloanlance @mcc Unfortunately, this is a long-standing Mastodon bug.

https://github.com/mastodon/mastodon/issues/25939

HTTP 503 from API endpoint returns HTML, not JSON · Issue #25939 · mastodon/mastodon

Steps to reproduce the problem Call https://mastodon.social/api/v1/notifications/ while the server is unavailable Expected behaviour An HTTP 503 with JSON content (possibly empty) Actual behaviour ...

GitHub