@wimpy its 2024 and they're moaning about getting slasdotted ?

and its happening even though they already use a CDN ?

Sounds like a them problem.

@wimpy It also does not speak well of their technical acumen if they don't realise that.

Can you imagine for a moment (and yes, I perfectly understand how unlikely it is on a non-federated social network) if they'd put out an article like that whinging about (pre-space karen) twitter ?

@FXBOY4EVA

The people at @itsfoss are really nice and friendly. They are a small team, publishing a lot of articles, and only have limited financial resources.

I am not a web professional, but I guess there should be html/css feature that allows to serve a static prepared image and teaser text for a website, instead of every instance having to pull the entire site (with all the rubbish on it) and having to generate its own preview. Or is there not?

@wimpy

@mina @itsfoss @wimpy

There are multiple methods they could use on their side to mitigate the issue there, including some things akin to what you suggest. Instead of complaining about, and blaming others for it.

That is what makes it rather churlish of them to publish an article, on their ostensibly technical news outlet, blaming others for the problem when it is in line with and entirely a consequence of the normal functioning of the internet.

@FXBOY4EVA @mina @itsfoss @wimpy

Hi there!

Well, allow me to clarify it here. I've made it obvious in my article that I don't blame Mastodon.

Sure, we're welcome to suggestions and misconfiguration hints. We're only human, I would take it that way.

I'm not the site admin here, but I've built sites before for clients. So, I think I know a few things (if not all).

Let me give you a comparison on why I think, this issue should be resolved on both sides (not just one):

@FXBOY4EVA @mina @itsfoss @wimpy

For starters, the sites have handled massive traffic spikes through Google News/Reddit/other platforms.

But, the misconfiguration/lack of proper caching technique kicks in only when our post goes on Mastodon?

So, it's not us alone, right?

If that was the case, this user here won't have complained about their website getting a mini DDoS here?

https://mstdn.social/@stux/112346188861924441?ref=news.itsfoss.com

Another one here: https://disabled.social/@richard/112367825632049001?ref=news.itsfoss.com

@FXBOY4EVA @mina @itsfoss @wimpy

I'm sure every site can do better (and we will too, with all the constructive suggestions we've been receiving).

But, the whole point of the article was to shed light on an issue that's existing for almost 6 years now, and has been pushed back.

If you think, our caching handling techniques are poor, as a technically inclined user, you should also realize that the issue highlighted for Mastodon is a fundamental one as well?