bartle
  • Login
  • Public

    • Public
    • Network
    • Groups
    • Popular
    • People

Conversation

Notices

  1. Leah ⛤ (leah@chaos.social)'s status on Monday, 24-Jun-2024 16:28:40 CEST Leah ⛤ Leah ⛤

    The amount of FediFetcher instances scraping chaos.social is alarming. They all come from different Azure IPs because it's the recommended way to run it. Github reports: 1.361 deployments. We also see massive scraping from the TOR Network and scraping of RSS Feeds from SerendeputyBot. That sucks! #mastoadmin

    In conversation about 11 months ago from chaos.social permalink
    • Michael Vogel (heluecht@pirati.ca)'s status on Monday, 24-Jun-2024 16:28:40 CEST Michael Vogel Michael Vogel
      in reply to
      @leah I think the only way to stop it is to fix the underlying problem. As far as I understand the idea behind this tool, it is meant to fetch missing posts from a thread. So we could come up with an FEP that solves that problem. Then hopefully people will stop using the tool.
      In conversation about 11 months ago permalink
    • Tealk (tealk@rollenspiel.social)'s status on Monday, 24-Jun-2024 16:30:43 CEST Tealk Tealk
      in reply to

      @leah But blocking that doesn't make much sense, does it? It is a function that is urgently needed and whether it is controlled via an external tool or built into Mastodon, the load will be the same.

      I myself use an instance of FediFetcher on my infrastructure and would find it extremely bad if the tool stopped working.

      In conversation about 11 months ago permalink
    • Michael Vogel (heluecht@pirati.ca)'s status on Monday, 24-Jun-2024 16:30:43 CEST Michael Vogel Michael Vogel
      in reply to
      • Tealk
      @leah @Tealk These external tools will always put a higher stress onto a system, so I completely understand why these requests are evil to a system. But I'm all in for some mechanism to fetch missing posts of a thread.
      In conversation about 11 months ago permalink
    • Tealk (tealk@rollenspiel.social)'s status on Monday, 24-Jun-2024 16:42:25 CEST Tealk Tealk
      in reply to
      • Michael Vogel

      @heluecht @leah sure, it's not that i don't understand the load problem, it's just that i like my conversations in one piece :rm_stickingouttongue:

      In conversation about 11 months ago permalink
    • Michael Vogel (heluecht@pirati.ca)'s status on Monday, 24-Jun-2024 16:42:25 CEST Michael Vogel Michael Vogel
      in reply to
      • Michael Vogel
      • Tealk
      @leah @Tealk For many years we implemented such a mechanism into Friendica. It currently only works between two Friendica servers. We really should create an FEP where we describe Friendica's method. Then we can only hope that others will pick up or improve it.
      In conversation about 11 months ago permalink
    • Michael Vogel (heluecht@pirati.ca)'s status on Monday, 24-Jun-2024 20:36:56 CEST Michael Vogel Michael Vogel
      in reply to
      • Michael Vogel
      • Tealk
      • mcv
      @leah @Tealk @mcv Yes, when ActivityPub was designed I was pushing for the distribution method that Diaspora uses (the first post of a thread is responsible for distributing comments). This is possible in ActivityPub using LD signatures, but unfortunately it hasn't taken off. Unfortunately, the commenting systems now distribute their comments on their own, leading to the known problems.
      In conversation about 11 months ago permalink
    • mcv (mcv@friendica.opensocial.space)'s status on Monday, 24-Jun-2024 20:36:57 CEST mcv mcv
      in reply to
      • Michael Vogel
      • Tealk

      @heluecht @Tealk @leah

      Is that what this is for? Then I understand completely. I find incomplete conversations a failure of ActivityPub. It needs a fix that doesn't cause too much overhead.

      In conversation about 11 months ago permalink

Feeds

  • Activity Streams
  • RSS 2.0
  • Atom
  • Help
  • About
  • FAQ
  • Privacy
  • Source
  • Version
  • Contact

bartle is a social network. It runs on GNU social, version 2.0.1-beta0, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All bartle content and data are available under the Creative Commons Attribution 3.0 license.