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.
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.
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.
I’m not sure the bot backfills.
However, the core issue was the ERROR page showing up when trying to load a new-to-you community, and that has resolved at least for my above examples.
I picked a random community from the lemmy-federate bot
https://lemmy.nz/c/chiefs@midwest.social
that still gets the error, maybe there is just a lag to load the metadata for a new community?
The way Lemmy federation works, is a logged in user on an instance can search for a community and it will pull a handful of posts for the front page (if I remember rightly, it’s only posts no comments or votes).
That’s a “pull”, requesting the content. The instance will get no further posts except from a “push”. A push happens when a user subscribes to a community on a remote instance, then that community adds the instance of the subscriber to its list of places to send new content. Once there is a subscriber, any new content (posts, comments, votes) get sent to that instance. The bot doesn’t do anything except subscribe.
That first “pull” federation doesn’t really count. Communities aren’t really visible to users unless they are showing in feeds, and to do that they need new content and votes.
I’m heading to bed but will pop a post in the lemmy-federate community asking for more info on what might be going wrong.