@itsfoss Your page loads 6MB of data with uBlock Origin, 55MB without it and never stops piling on more and more. Seems to load some Google Ads garbage over and over again?
In the time between the first sentence and now, it loaded 30MB more data. Please fix your site.
@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.
@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?
@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 so you’re using their pretty small cloud VPS then, that on top of how ridiculously heavy your site is (which others have pointed out) is not helping
@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??
@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 I wonder why it needs to generate thumbnail/preview again and again when viewing the original post from other instances?
imo it will be way simpler if the thumbnail is generated once (when initially posted) and then stored on that original instance. And when the post is viewed/boosted that stored thumbnail will be transferred along instead of re-generating from the source url.. 🤔
@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.
My issue with itsfoss is not about being unreachable occasionally. It is the massive wall of adds. So much that some browsers reload your page multiple times before being able to read a mere 300 words article.
And so much that I am almost seeing the adds for diapers, watches, adobe products and temu intimidating that I want to opt out of your page.
Add comment