Federation issues illustrated on lemmy-federate.com

Looking around lemmy-federate.com I see lemmy.nz showing up in the error and not allowed states for many of the federated communities.

For instance communities I moderate

As you can see it crosses over multiple instances.

5 comments

Just to be clear, you're not talking about federation issues where content federation is falling behind. Instead you're saying that new communities listed on lemmy-federate.com are not being automatically sent to Lemmy.nz. I think it's important to be clear on the difference because an instance failing to communicate with other instances is a high priority problem to solve, and you almost gave me a heart attack with your title 😆
I think the first community not federating because hackertalks.com isn't on fediseer? Fediseer is a "chain of trust" site where instances can show they are not spam instances or other reasons to be censured: https://fediseer.com/
I have enabled the option to only accept new communities from instances that have been endorsed on Fediseer. I think this is necessary, otherwise it's too easy to create a new instance, create a spam community, and start spamming posts to it having it federate to other instances without moderators being able to do anything because it's a remote community.
The other two? I am not sure what the issue is! Happy to take suggestions. I have no allow/block instances listed. I have these settings, which have not been changed recently:
- It appears to be working now! Maybe all it needed was the mark 1 eyeball.
  Sorry about the intense title!
  
  I don't think it is. I've opened links which may have triggered some posts to federate, but the three communities you linked all still show 0 local subscribers, so we aren't going to get new content. It should show 1 subscriber, the bot account that does the following.