Nothing4You

this is only for setting the default user language during registration based on the browsers accept language headers.

this is likely related to https://github.com/LemmyNet/lemmy/issues/4971

this isn’t true. it was incorrectly stated in the upgrade guide but has been removed a while ago. it was supposed to be a recommendation due to some issues with postgres 15. there is no postgres upgrade required between 0.19 releases.

account names cannot be changed.

you can only change your display name, which is available in the settings.

whether display names or usernames are shown depends on the interface/client and user settings where available.

the only way to change the username is to create a new account.

it seems to have become more frequent recently.

i’ve been experiencing the same on firefox and i’ve also heard other people report the same on firefox, which happened around the time of the firefox 129 release. i didn’t see anything noteworthy in the release notes though that’d explain this. it seems like it might be related to enhanced tracking protection and cookie isolation.

this is a lemm.ee limitation, not a Lemmy limitation, so this is the wrong community.

if you look at the instance sidebar at https://lemm.ee/ you can see that it’s 4 weeks.

for sure, but they’re neither mentioned on https://join-lemmy.org/docs/users/02-media.html nor on the linked CommonMark tutorial.

It’s not even just that. It seems that the extra @ acts as a separator, so you can’t even autocomplete e.g. @threelonmusketeers@sh as that’ll try to autocomplete @sh instead of taking the instance domain as part of the mention.

I’ve raised a GitHub issue for this now: https://github.com/LemmyNet/lemmy-ui/issues/2652

on firefox, if i type @gedal and click or press tab once it replaces the text with [@gedaliyah@lemmy.world](https://lemmy.world/u/gedaliyah) . the behavior is the same whether i hit tab, enter or click the text.

just as great as lemmy-ui

it does, but only if you use the autocomplete feature. it’s also a bit delayed without any indicator that it’s loading.

if you type @gedal and wait a moment it’ll load @gedaliyah@lemmy.world to be selected:

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.

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.