Nothing4You

The "fediverse link" on a post always points to the instance of the person who posted it, not the community instance. When posting from a lemmy.world account this means the fedilink is always the lemmy.world post link.

It is only shown for content coming from remote instances in Lemmy UI 0.19.3, although a later version changed that to always show.

What do you mean by "finish federation"?

Generally, individual activities (subscriptions, posts, comments, votes, etc) are federated within less than a minute of them being created. Your instance learns about other instances e.g. from votes seen on other instances. You'll need to start subscribing to some communities on other instances to get started. You may want to check out Lemmy Explorer or Lemmy Community Browser to find communities and Lemmy Federate to automatically subscribe to other communities and get content sent to you.

The allowed instances list means that the instance will only connect to those instances and will refuse to send activities to any other instance.

for content that was not federated prior to defederation, yes.

this is by design. actor ids (unique identifier for accounts) should not be reused due to undefined behavior for how other instances will deal with that.

if you want to have a more technical explanation, https://socialhub.activitypub.rocks/t/reuse-of-identity-channel-addresses-revocation-reissue-of-keys/2888 does a decent job at explaining some of the issues with this.

it should be noted that these bans are community bans, not instance bans. your title makes it look like people are getting instance banned from lemmy.world, while the examples you've shown are about community bans.

if i'm not mistaken, several/most of the lemmy.ml bans/ban complaints have been about instance bans, which affect all communities on the instance.

except instance A will actively reject such content from B users when it hears about it from C.

generally it should be expected not to see any new content from B, but historic content will still exist and basically be in a frozen state.

the main problem is still that reports are not reliably getting to remote moderators: https://github.com/LemmyNet/lemmy/issues/4744

other than that it should be working.

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.

fyi @[email protected]

I've submitted a PR to fix this, it might still make it into 0.19.4.

fyi @[email protected]

curious, what do you mean by checking them?

if you open https://lemmy.world/api/v3/user/unread_count after being logged in, it should at least tell you what kind of unread message it is.

with that information it can probably be narrowed down a bit.

i don't think this is related to an inconsistency with blocked users, as that is only being fixed in 0.19.4 or 0.19.5: https://github.com/LemmyNet/lemmy/issues/4227

moderated or deleted comments as mentioned by others don't look like they would be the case when i'm looking at the 0.19.3 code.

the bot reply mentioned by @[email protected] seems like a very plausible explanation, as bot accounts are hidden from the comment reply list in the api, but they're not currently excluded from the notification count.

i'll have a look at whether that is still the case in the current development version in a bit and submit a pr to fix that if it is.

starting with 0.19.4, at least user settings will default to their browser's accepted languages on registration: https://github.com/LemmyNet/lemmy/pull/4550

this doesn't solve actually tagging content, but it some progress at least.