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.
Retaining old content has value
this 100%. this is exactly why i wouldn’t recommend any communities to be removed if there is still content in there, worst case just lock it.
cleaning up communities doesn’t make lemmy more active either. it may help to make active communities stand out more against inactive ones though.
cleaning up dead communities isn’t a great experience as it is today.
admins could purge communities, but this can cause unexpected breakages with other activitypub software that is more strict about cryptographic verification, as purging a community erases all information about it from the local instance, including the cryptographic private key. purging a community also only removes it on the local instance, so other instances would still have a cached (although possibly marked as deleted) copy of it. this would be the only method that frees up the name to allow creating a new community under the same name later on. locally this would also remove all posts and comments associated in that community, but other instances may think that they have users subscribed to the community and may still have posts and comments in there. this also means if a new community is created with the same name again, the local instance will still not know about older posts, but users on other instances might see them still, and the local moderator might be unable to interact with them at all, e.g. to potentially remove old problematic content.
the next option is removing a community as (instance-)moderator action. this will only mark the community as removed without further impact. regular users won’t be able to access the community on the local or any other instance anymore, but its contents are preserved in case it gets restored at a later point in time. the name is not released and there isn’t even an error message shown when trying to create a new community with the same name.
another option could be to “take over” the community and delete it, which is the act of the top community mod deleting the community (not a moderation action). in this case only the same top community moderator can restore it. this behaves mostly the same as removing it.
none of these options are good to use. imo purging should be avoided in any case, and the other options both require admin intervention to release a community later on and have no user feedback in lemmy-ui at this time, at least on 0.19.5.
for communities entirely without posts it is probably ok to just remove them and restore and transfer them if someone requests them. for communities with content the next best thing might be locking the community, potentially locking all posts if it’s just a small number, to prevent unmoderated new content in that community, and put up a pinned post asking people to reach out if they want to take over the community. otherwise, if the community was removed or deleted, all the posts and comments within them would also be taken down with the community.
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.
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.
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.
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.
ah i was misreading your comment, i thought you were talking about the sending side. for the receiving side i agree, but the reason for the duplicate activities is yet to be found: https://github.com/LemmyNet/lemmy/issues/4609
records can’t be duplicated in the database, the activity id is a unique key:
lemmy=# \d sent_activity
Table "public.sent_activity"
Column | Type | Collation | Nullable | Default
-----------------------------+--------------------------+-----------+----------+-------------------------------------------
id | bigint | | not null | nextval('sent_activity_id_seq'::regclass)
ap_id | text | | not null |
data | json | | not null |
sensitive | boolean | | not null |
published | timestamp with time zone | | not null | now()
send_inboxes | text[] | | not null |
send_community_followers_of | integer | | |
send_all_instances | boolean | | not null |
actor_type | actor_type_enum | | not null |
actor_apub_id | text | | |
Indexes:
"sent_activity_pkey" PRIMARY KEY, btree (id)
"sent_activity_ap_id_key" UNIQUE CONSTRAINT, btree (ap_id)
verification emails are usually sent immediately. if there are delays you should check your junk folder, and if it’s not there it probably won’t arrive anymore. depending on the instance you signed up on there may be alternative methods to reach out to the instance admins about this. note that private messages from mastodon to lemmy do not work unfortunately.