I'm seeing the same post from the same user posted in the same community but it seems to be delivered from multiple instances. I have the show all option turned off. Can't figure out why I'm seeing multiple, a good example is when you sort by top of day and you'll see a lot of duplicate post grouped together.
Edit- turning off the see all seems like it essentially forces it to local only, which sorta fixes it, but that's not what I want. On Jerboa for example, I can filter by all (multi instances), and only see one example of each post power community
Edit 2 - so it's something to do with using the 'see all' from multiple instances, even ones your not part of. The problem is it's don't the duplicating there, but seems to be for the same community, but something is of in the parity. For now I'm just using [email protected] and that seems to be better for now
Think of communities as being similar to email addresses. Just like
[email protected]and[email protected]are different email addresses,[[email protected]](/c/[email protected])and[[email protected]](/c/[email protected])are different communities. When someone posts the same content to both communities, they are posting to different groups of people. So, if you have things set up to see content from multiple instances you might see the same post in multiple identically named communities from multiple instances.This is similar to seeing the same post on reddit in /r/tech and /r/technology.
These aren't duplicate communities though. This is the same community, just being served twice from two different instances. Both are [email protected] . If you look at them, they have the same number of comments and everyone
If you compare to Jerboa for example, it only lists this post once.
Edit- Seems like this might be a federation sync issue. The two posts are slightly different, but it's a bit unclear what the actual issue is. When I go to the specific community, liftoff gives a null error, so can't verify what the exact issue is
Huh, sorry, I should have looked at the image more closely. That is odd! It sounds like a bug of some sort...