The blog Its FOSS has 15,000 followers for its Mastodon account — which they think is causing problems:

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.

Sure, some websites may not get overwhelmed with the requests, but Mastodon does generate numerous hits, increasing the load on the server. Especially, if the link reaches a profile with more followers (and a broader network of instances)… We tried it on our Mastodon profile, and every time we shared a link, we were able to successfully make our website unresponsive or slow to load.

It’s Foss blog says they found three GitHub issues about the same problem — one from 2017, and two more from 2023. And other blogs also reported the same issue over a year ago — including software developer Michael Nordmeyer and legendary Netscape programmer Jamie Zawinski.

And back in 2022, security engineer Chris Partridge wrote:

[A] single roughly ~3KB POST to Mastodon caused servers to pull a bit of HTML and… an image. In total, 114.7 MB of data was requested from my site in just under five minutes — making for a traffic amplification of 36704:1. [Not counting the image.]

Its Foss reports Mastodon’s official position that the issue has been “moved as a milestone for a future 4.4.0 release. As things stand now, the 4.4.0 release could take a year or more (who knows?).”

They also state their opinion that the issue “should have been prioritized for a faster fix… Don’t you think as a community-powered, open-source project, it should be possible to attend to a long-standing bug, as serious as this one?”

Abstract credit: https://slashdot.org/story/428030

  • dsemy@lemm.eeEnglish
    10·
    7 months ago

    I’m sure an affected website could have paid a web developer to find a solution to this issue in the past 7 years if it was that important to them.

    • 0x1C3B00DA@fedia.io
      2·
      7 months ago

      People have submitted various fixes but the lead developer blocks them. Expecting owners of small personal websites to pay to fix bugs of any random software that hits their site is ridiculous. This is mastodon’s fault and they should fix it. As long as the web has been around, the expected behavior has been for a software team to prioritize bugs that affect other sites.

      • dsemy@lemm.eeEnglish
        2·
        7 months ago

        If they don’t want to pay to fix it, they can just block the user agent (or just fix their website, this issue is affecting them so much mainly because they don’t cache).

        Relying on the competence of unaffiliated developers is not a good way to run a business.

        • 0x1C3B00DA@fedia.io
          2·
          7 months ago

          Relying on the competence of unaffiliated developers is not a good way to run a business.

          This affects any site that’s posted on the fediverse, including small personal sites. Some of these small sites are for people who didn’t set the site up themselves and don’t know how or can’t block a user agent. Mastodon letting a bug like this languish when it affects the small independent parts of the web that mastodon is supposed to be in favor of is directly antithetical to its mission.

          • dsemy@lemm.eeEnglish
            1·
            7 months ago

            The reason (IMO) this has languished as much as it has, is that most sites handle this fine; though I agree that it should have been fixed by now.