Lemmy.nz Support

362 readers

1 users here now

You can ask questions about the Lemmy.nz instance here.

This community also serves as our Meta community, with posts about updates to the Lemmy software on Lemmy.nz or other things relevant to Lemmy.nz users and not relevant to other instances.

founded 2 years ago

MODERATORS

Dave@lemmy.nz

Federation issues illustrated on lemmy-federate.com (hackertalks.com)

submitted 3 weeks ago by jet@hackertalks.com to c/support@lemmy.nz

5 comments fedilink hide all child comments

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.

top 5 comments

sorted by: hot top controversial new old

[–] Dave@lemmy.nz 3 points 3 weeks ago (1 children)

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:

settings showing things like that it's enabled, disables NSFW, requires fediseer endorsement

[–] jet@hackertalks.com 2 points 3 weeks ago* (last edited 3 weeks ago) (1 children)

It appears to be working now! Maybe all it needed was the mark 1 eyeball.

Sorry about the intense title!

[–] Dave@lemmy.nz 1 points 3 weeks ago (1 children)

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.

[–] jet@hackertalks.com 2 points 3 weeks ago (1 children)

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?

[–] Dave@lemmy.nz 3 points 3 weeks ago* (last edited 3 weeks ago)

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.