Web developer. Lead developer of PieFed

  • 69 Posts
  • 410 Comments
Joined 2 years ago
cake
Cake day: January 4th, 2024

help-circle

  • Community members pointed out that the indexable flag is enabled by default on many instances, which means that a significant number of accounts with the flag set never made a deliberate choice to be indexed. The flag that’s supposed to signal “this person consents to being searchable” frequently signals “this person’s server admin didn’t change the default”, and on a protocol-level, there is no difference between these two options.

    Maybe Mastodon could get the user to set this during onboarding. Then no one can say they didn’t choose.












  • This article is better than most like this in that it at least acknowledges the existence of the threadiverse and even explores some of it’s community-related features. Hurrah! But really it equates ActivityPub with just Mastodon, which leads to the conclusion it does. I believe that if they compared Lemmy/PF’s ActivtyPub with ATProto the conclusion might have been quite different.

    (Community lives in the heads of the people involved and their feelings of connection to and support for one another. But ok, let’s run with the assumption it’s a technology / protocol thing…)





  • It’s complicated.

    You could federate with millions of instances if the people using them are not doing very much. But a handful of instances could theoretically overwhelm the whole network if they had malicious bots spamming like crazy.

    The instance that hosts a community is responsible for sending copies of everything to all following instances, so most of the load is on those instances that host lots of popular communities. All other instances just need to be powerful enough to keep up with what they receive, which is 100x less work.

    So even more important than spreading users out among instances, is spreading communities out among instances. Communities cause most of the load.