Fediverse

Randomly stagger the times of each instance's request.

+1-300 seconds

Lemmy does this to itself, too - when you create a post it federates out and then every Lemmy instance that receives it makes a GET request to retrieve the post from the original server. Even though it just received the exact same data. Some other fedi software is even worse - Akkoma does a GET of the id of every activity it receives, not just for posts but for Likes too.

It's insane.

Anyway, proper caching at the reverse proxy / Cloudflare level solves it. The same kind of caching setup would do the same for sites serving HTML, like NPR too.

I don't really get it. The image is federated, there's no need for instances to refetch it. Just checked out some posts and indeed it's there, in the image property. With the URL pointing to the Lemmy instance.

So if this is actually an issue, that's just bad programming and needs to be fixed.

~~Edit: didn't notice OP uses Piefed. Unlike Lemmy and Mbin, it seems like Piefed doesn't federate it.~~

Edit: actually I'm blind, Piefed does federate it too, sorry piefed

Also https:// itsfoss.com/news/mastodon-link-problem/

smaller sites like NPR

I remember reading the same thing about reddit, slashdot, fark, and other sites. But I like the FASP idea as a way to relieve this.

they could include the link preview data as part of the federation

Is this why the automated title retrieval never works for NPR?

A slight delay would be perfectly sufficient.