@itsfoss That's the waf/cdn problem you're using. It is well known that shitflare is a most crappy company with the very bad behavior and policies as well. Yes, Mastodon issue it is too, but not only their. You're also a pretty lucky that shitflare doesn't ban your domain and/or domains/ip's of your readers/users, what they are doing very often. Just report this problem to Mastodon support and wait for the fix/solution from them. You can also temporarily use some url shortener/redirect service.
@itsfoss Have you considered doing static versions of the pages you share to Mastodon, and sharing those links instead? JS is almost entirely bloat and overhead.
@itsfoss You do realise that this is not a Mastodon problem per se, but rather an @itsfoss problem? The problem is the handling on the server side. The fact that Mastodon does a preview and queries the server is one thing, but the answer is the server's business. Today it's Mastodon and if @itsfoss can't handle the query/response then the ball is in your court. Balancing and such. Surely you are not saying that it only takes like maybe ten users (at a time) to share a link and you're DDOSed??
@gamingonlinux on the news website, we have a 2 CPU, 2 GB RAM server. On the main itsfoss website, we have 4 CPU, 8 GB RAM server. Both are on Digital Ocean and we use Ghost CMS with Cloudflare for caching.
@itsfoss I see a strong irony in a publication that’s literally all about FOSS saying *someone else* should fix this problem. If you want to see something fixed in a community-powered, open source project, why not roll up your sleeves and get to work on it?
@itsfoss so you’re using their pretty small cloud VPNs then, that on top of how ridiculously heavy your site is (which others have pointed out) is not helping
@itsfoss 🤔 ein wirklich interessanter und wichtiger Aspekt, den ich hier auch nicht kleinreden will. Aber der Lösungsansatz, die User zu bitten, keine Links mehr zu verbreiten, ist sinnlos. Für entsprechende Performance eines Servers oder einer Farm ist die Betreiberin verantwortlich: Caches, CDN etc.