Post AvIXaa2QXHtPPRcgoS by scott@sfba.social
 (DIR) More posts by scott@sfba.social
 (DIR) Post #AvIXaa2QXHtPPRcgoS by scott@sfba.social
       2025-06-19T18:05:31Z
       
       0 likes, 0 repeats
       
       Hey #Mastodon #Fediverse nerds: has anyone mapped federation topology yet?https://mastodon.social/@floatybirb/114711176066850583
       
 (DIR) Post #AvIXaaw5CMPcC3f8Yy by simonzerafa@infosec.exchange
       2025-06-19T19:02:32Z
       
       0 likes, 0 repeats
       
       @scott I wonder if @jerry might know? It would be an interesting diagram/map to see if it exists 🙂
       
 (DIR) Post #AvIXabwTSOJrJYqxoO by jerry@infosec.exchange
       2025-06-19T19:18:52Z
       
       0 likes, 0 repeats
       
       @simonzerafa @scott you know, it’s funny. Years ago, they were three unwritten rules of the fediverse: no searching posts; no quote posts; and no, keeping track of which instances blocked which other instances. Since the first two have fallen away, perhaps the third one can now as well.
       
 (DIR) Post #AvIXacjkVBjbmNuJcG by feld@friedcheese.us
       2025-06-19T19:33:14.607609Z
       
       1 likes, 0 repeats
       
       @jerry @simonzerafa @scott Pleroma has exposed instance blocks in the API by default for a long time nowand honestly it's kind of required. If a server blocks you, you should want to add a reciprocal block to make sure you don't fetch any posts from them either. @sun went through this problem a while ago and had to write a script to automate reciprocal blocks but we should probably integrate functionality that does it automatically... though it would only work for other Pleroma instances right now unless a standard is developed