Nothing4You

it’s like @Xyre@lemmus.org described. old content does not get federated unless there is new activity on it and someone on your instance is subscribed to the community it happens in.

this isn’t anyone’s fault, it’s just a matter of the instance not being around that long that some historic content will be missing.

so just dropping duplicates then?

are there no references to the duplicates from posts? if there are and the duplicate rows are just deleted it’ll cascade deletion and purge all those posts from the db as well

how are you planning to fix this?

delegating authentication to another service.

one of the more commonly known options would be sign in with google, but this is also quite useful for providers hosting multiple services. a provider could host a service that handles authentication and then you only have to login once and will automatically get logged in for their lemmy, xmpp, wiki and other services they might be providing.

this feels like more db index corruption that already existed for users previously, unlikely to be an issue in lemmy itself

also adding my vote for the second one

It seems that p.d didn’t or wasn’t able to fetch the community moderator list yet, which would prevent it from accepting any new posts to the community, as it’s set to allow posting by mods only and the bot isn’t detected as mod yet.

I think the only way (without manual intervention) might be to access the community after 24h to have Lemmy refresh this from the origin server.