I made two accounts on sh.it instance using the same email.
this isn’t possible, you can’t reuse the same email for multiple accounts on the same instance.
if you reset another account’s password with that it just means that you the user @emberinmoss@sh.itjust.works uses a different email address.
based on the creation date advertised by the instance, lemmy.ml exists since 2019-04-20. lemmy.world exists since 2023-06-01.
while this is generally what most people talk about when speaking of defederation, admins can also decide to remove communities locally without blocking the entire instance.
this is the important part.
when an account is deleted the associated private key used for signing activities is deleted as well. the activitypub protocol does not really define how software is supposed to deal with deleted and recreated actors (which includes users), so some software has been built with the assumption that any change of encryption keys for a user means it’s an invalid signature and will prevent activities involving that user to federate to that software.
I think most (especially mobile) clients simply don’t have this option and will always copy/share the “fedi link” - the url where the content is canonically hosted. all other URLs are simply cached representations of the original content.
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?
this feels like more db index corruption that already existed for users previously, unlikely to be an issue in lemmy itself
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.
It should be noted that the (visibility of) community bans are a result of better enforcement of site bans in 0.19.4, which for now is implemented by sending out community bans for local communities when a user gets instance banned: https://github.com/LemmyNet/lemmy/pull/4464
Prior to this, when a user got instance banned from .ml, they were also implicitly banned from .ml communities, but this was only known to the instance they were banned on. As a result, users were still able to post, comment, and vote on those communities, but it would be visible only on that user’s instance, not federated anywhere else. Visibility of this ban was exclusively on the banning instance’s modlog.
is that sync? sync has some issues with local communities. I think it might get better if you subscribe to the community.
compare with the web version to rule out account related issues.