Nothing4You

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.

Except it wasn’t created on lemmy.ml, it was created on lemmy.world.

lemmy.world then informed lemmy.ml that it is intended to be published in the community that it was created for.

It doesn’t say “crossposted from lemmy.world” but “crossposted from canonical_post_url”. This is not wrong in any way, although it might be a bit confusing and could likely be improved by including a reference to the community. The instance domain should for the most part just be a technical detail there.

It should also be noted that this format of crossposting is an implementation detail of Lemmy-UI and other clients may handle it differently (if they’re implementing crossposting in the first place).

I’m not saying it’s technically impossible, although it would likely be a bit challenging to integrate on the technical level, as the community instance has no authority to modify the post itself other than removing it from the community at this point.

The existing fedilink is already present for technical reasons anyway, so this is currently only showing existing data.

Why would you want a lemmy.ml link though? On Lemmy you’re typically intending to stay on your own instance, which many third party apps already implement. For Lemmy UI there is already a feature request to implement this, although it might still take some time to get done. If you have the canonical link to an object (which will always point to the users instance) Lemmy can look up which post/comment you’re referring to in its db without any network calls when it already knows about the entry. If you were linking to the lemmy.ml version of that post then the instance would first have to do a network request to resolve that and then it would realize it’s actually the lemmy.world version that it may or may not know about already.

it doesn’t matter whether you consider it reasonable, as it’s this way for technical reasons.

when a post or comment are created they are created on the users instance. the users instance then tells the community instance about the new post/comment and the community instance relays (announces) this to other instances that have community subscribers.

the fedilink is an id and reference to the original item. this unique id is known to all servers that know about this comment and it is what is used when updates to the post are distributed. except for the reference to the item on the originating instance, no instance stores information about where to find a specific post/comment on a random other instance.

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.

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 @SpaceCadet@feddit.nl