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.
Fediverse
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, Mbin, etc).
If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration)
Why is that? Those are centralized platforms, they should only need to retrieve the preview once each?
https://en.wikipedia.org/wiki/Slashdot_effect but people were going in, looking at the link, sometimes overwhelming the server
That's not at all the same thing. That's just the inability to handle large amounts of unexpected normal user traffic.
This is essentially bot traffic driven by servers all independently but simultaneously fetching the same image, without even a single human necessarily looking at it.
From server's perspective the only difference between those is the user-agent. Traffic is the same
But what OP is talking about is a technical detail that can be fixed.
Yes, but then a comment mentioned the "hug of death" - high spike of requests resulting from a link being shared on some site, and OP asked why centralized sites were also creating problems
There was another post regarding previews some months/(knowing me probably a year) ago and personally I would go with federating previews. With a button for mods to refresh it from source for when something goes fucky
But social networks have been creating random bursts of requests, this way or another, even in the times of centralized socials
The origin and purpose of the traffic is not the same. That's why they block one and not the other.
This probably why my place of work blocked it behind the firewall
Do they block the useragent or the URL? NPR apparently blocks the former.
You're talking about 2 different kinds of blocking here. NPR can't block a URL, that concept doesn't really exist at this level. They could block ip addresses, or user agents as you mentioned.
A workplace can't block by user agent (at least not on any website using TLS), as this header is not readable by any intermediary devices.
NPR can't block a URL
I wasn't talking about NPR, I was talking about their employer...
You mentioned both in the same comment...
[...] NPR apparently blocks the former
I'm just saying, their employer can't block like NPR does, because they are fundamentally different things. The one is a server receiving a request, the other is a firewall seeing encrypted packets.
Edit: the other could also be a DNS resolver that just does not resolve certain domains.
This was my first thought too.