mastodon.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
The original server operated by the Mastodon gGmbH non-profit

Administered by:

Server stats:

329K
active users

#fastly

0 posts0 participants0 posts today

Welcome back @fastly as a @netdevconf 0x19 bronze sponsor! Thank you! @fastly is a programmable edge cloud platform that helps developers create secure, scalable, fast digital experiences. Open source is a part of the @fastly heritage, which is essential to their operations, and central to their future
netdevconf.info/0x19/news/bron #fastly #netdevconf

netdevconf.infoBronze Sponsor, FastlyFastly is an instant programmable platform that helps teams ofall sizes create secure, scalable, fast digital experiences. AtFastly, open source is a part of...
Continued thread

I’ve done a little bit more testing and it looks as though the IPv4 setup may have fallen over at the CDN, although it is still pingable via IPv6 (unfortunately for me, our network isn’t fully IPv6 enabled)?

Just noticed ... .social uses with ip location in ?!
Wouldn't it be better using Solutions from or ?
better for ...

really think of moving to an instance, that is hosted in EU or better Germany. Or maybe deploy my own instance and providing it to public... Since longer time I try to avoid US services as much I can.

#PyPI (za pośrednictwem #Fastly) teraz wymaga JavaScriptu, by dostać się na strony projektów. Wskutek tego, wszystkie przeglądarki tekstowe i proste narzędzia utraciły dostęp do serwisu.

Hosting projektów, który dotychczas uznawałem za najlepszy przykład dobrego webmasterstwa i dostępności, tak po prostu skoczył w najniższy krąg piekieł.

github.com/pypi/warehouse/issu
discuss.python.org/t/fastly-in

GitHubblocked with 200 status code: "JavaScript is disabled in your browser." · Issue #17285 · pypi/warehouseBy pajod

If you're running an #ActivityPub server, you might think carefully about how you use something like Cloudflare. I just spent 30 minutes troubleshooting why my AP server was getting a 403 when trying to pull up someone's webfinger, but I could issue the same exact command via curl (same UA, headers, HTTP version, IP address, etc.) and it worked fine.

I've finally decided that it's just Cloudflare being a jerk. AP is inherently pretty noisy, but I was making things worse by looking up the webfinger too often. So the server would get hit with 6 requests in quick succession and it seems to be triggering something with Cloudflare. I reduced that to 3 by looking up the webfinger locally, and I can get further. But I still can't pull up this particular full profile (e.g., requesting followers, following, outbox, in quick succession triggers the 403).

This seems to be an uncommon configuration (I have 64,131 Actors currently in my database), but it's annoying. Plus, #CloudflareSucks. They've always sucked.

Use #Fastly if you need a #CDN. Or do it yourself with #Varnish if you just need caching.