Please Don’t Share Our Links on Mastodon: Here’s Why!

Just put the site behind a cache, like Cloudflare, and set your cache control headers properly?

They mention that they are already using Cloudflare. I'm confused about what is actually causing the load. They don't mention any technical details, but it does kinda sound like their cache control headers are not set properly. I'm too lazy to check for myself though...

Even without Cloudflare, simple NGINX microcaching would help a ton there.

It's a blog, it doesn't need to regenerate a new page every single time for anonymous users. There's no reason it shouldn't be able to sustain 20k requests per second on a single server. Even a one second cache on the backend for anonymous users would help a ton there.

They have Cloudflare in front, the site should be up with the server being turned off entirely.
I've found that if left on default settings, CloudFlare is not that great at caching. It requires a bit of configuration to really make it sing. itsfoss.com thought they were "using CloudFlare" but probably not to it's fullest potential.
I'm confused about what is actually causing the load.

Thousands of instances simultaneously fetching link previews from a VPS w/2GB RAM.

https://mastodon.social/@itsfoss/112369476450719989
- If caching is properly configured, the cache (Cloudflare) will see thousands of requests, but the VPS should only see one request.
- This should be front and center, caching won’t be able to make up for that…

There's another reason I don't share "It's FOSS" links anywhere: this should have been a github issue but it's turned into a clickbaity headline. Every othe article coming out of "It's FOSS" is either low effort, sensationalist, or both.

The article mentions there are aleady a few issues, some quite old. The article is useful for raising awareness and hopefully getting the fix prioratized higher.

Real talk, the mastodon traffic stampede isn't that bad for a properly configured website.

I always downvote posts with titles like this. Here's Why -

same. read more to find out!

Their website isn't properly caching pages which is the real reason they're having problems.

I think they just advertised how trivial it would be to take their website down...

Direct link to article:

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

TL;DR:

When you share a link on Mastodon, a link preview is generated for it, right?

With Mastodon being a federated platform (a part of the Fediverse), the request to generate a link preview is not generated by just one Mastodon instance. There are many instances connected to it who also initiate requests for the content almost immediately.

And, this "fediverse effect" increases the load on the website's server in a big way.

Does Lemmy not cause this issue? Other federated software was not mentioned in the article at all.

So the preview should be federated as well?

How many requests are we actually talking about here, though? Is that better or worse than everyone clicking the link?
- There's some problem with a federated previews: tricking one instance into generating the wrong preview would spread to every instance. It's been exploited for malware and scam campaigns in message apps.
- 2 requests per instance - one for the HTML of the page and another for a preview image.
Lemmy (and Kbin for that matter) very much do the same thing for posts. I don't think they fetch URL previews for links in comments, but that doesn't matter: posts and comments are both fairly likely to end up spreading to Mastodon/etc anyway, so even comments will trigger this cascade.

Direct example: If you go to mastodon.social, stick @[email protected] in the search box at the topleft and click for the profile, you can end up browsing a large Mastodon server's view of this community, and your very link has a preview. (Unfortunately, links to federated communities just result in a redirect, so you have to navigate through Mastodon's UI.)
They say it's fediversal in the comments on Mastodon.

Gotta respect boycotting Cloudflare on principle.. but also, why?

It's an interesting and frustrating problem. I think there are three potential ways forward, but they're both flawed:

Quasi-Centralization: a project like Mastodon or a vetted Non-Profit entity operates a high-concurrency server whose sole purpose is to cache link metadata and Images. Servers initially pull preview data from that, instead of the direct page.
We find a way to do this in some zero-trust peer-to-peer way, where multiple servers compare their copies of the same data. Whatever doesn't match ends up not being used.
Servers cache link metadata and previews locally with a minimal amount of requests; any boost or reshare only reflects a proxied local preview of that link. Instead of doing this on a per-view or per-user basis, it's simply per-instance.

I honestly think the third option might be the least destructive, even if it's not as efficient as it could be.

As I understand it, 3) already happens. What causes the load is that each connected instance is also loading and caching the preview.
Or 4) Ignore noise and do nothing; this is a case of user talking about things they don’t understand at best, or a blog intentionally misleading others to drum up traffic for themselves at worst. This is literally not a problem. Serving that kind of traffic can be done on a single server without any CDN and they’ve got a CDN already.

That sounds a lot like a weird spin on the Slashdot effect, caused by content mirroring. It seems that it could be handled by tweaking the ActivityPub protocol to have one instance requesting to generate a link preview, and the other instances copying the link preview instead of sending their own requests.

But frankly? I think that the current way that ActivityPub works is outright silly. Here's what it does currently:

User is registered to instance A
Since A federates with B, A mirrors content from B into A
The backend is either specific to instance A (the site) or configured to use instance A (for a phone program)
When the user interacts with content from B, actually it's the mirrored version of content from B that is hosted in A

In my opinion a better approach would be:

User is registered to instance A
Since A federates with B, B accepts login credentials from A
The backend is instance-agnostic, so it's able to pull/send content from/to multiple instances at the same time
When the user interacts with content from B, the backend retrieves content from B, and uses the user's A credentials to send content to B

Note that the second way would not create this "automated Slashdot effect" - only A would be pulling info from the site, and then users (regardless of their instance) would pull it from A.

Now, here's my question: why does the ActivityPub work like in that first way, instead of this second one?

If server A makes one request, it keeps server B from being overload by thousands of requests from users A.
- "A" Users would need to send requests to some server anyway, either A or B; that's only diverting the load from B to A, but it isn't alleviating or even sharing it.
  
  Another issue with the current way that ActivityPub works is foul content, that needs to be removed. Remember when some muppet posted CP in LW?
Check out Nostr, ActivityPub alternative that does authentication separately from content, works more like that.
- I'm aware of Nostr. In my opinion it splits better back- and front-end tasks than the AP does, even if the later does some things better (as the balance between safeness and censorship-resistance). It's still an interesting counterpoint to ActivityPub.

So why doesn't a random follower posting a link on Mastodon cause server load issues, but a popular follower does?

i mean it's solid training but they do realise it's not limited to mastodon, right?

the slashdot effect has been around for years

Please Don’t Share Our Links on Mastodon: Here’s Why! | itsfoss.com