• 0 Posts
  • 27 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle







  • IMO it can be MUCH simpler. Deleting content should propagate across federation just like adding content does. De-federating should retroactively remove all content that it would normally keep from propagating (possibly leaving “this post/comment deleted” markers so that replies make sense). And losing track of an instance for long enough (e.g. a week, or a month) should be equivalent to de-federating, possibly with the option to resurrect content when and if the instance comes back online.

    I believe that would remove a lot of the issues with extra traffic, and possibly a lot of the issues with extra processing. I don’t know enough about the protocol to tell whether it would add requirements for extra data, but I suspect it wouldn’t.











  • Meta makes their own nice, QoL-rich instance that could integrate with Facebook/Instagram.

    This part could actually be enough on its own, TBH. Imagine that there’s one Fediverse instance where you can interact with the rest of the Fediverse and interact with FB and IG, but it doesn’t propagate stuff between the two networks (i.e. it doesn’t allow people on Beehaw to see what someone on FB posts, and vice versa). Now there’s a reason for everyone to migrate to Meta’s instance, and a built-in way for Meta to advertise the migration to everyone in the FV. Once it sucks up enough users, it just de-federates from everything else and goes on its own way.