Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

changing username weirdly affects federation #226

wakest opened this issue Dec 22, 2019 · 1 comment

changing username weirdly affects federation #226

wakest opened this issue Dec 22, 2019 · 1 comment


Copy link

wakest commented Dec 22, 2019

I just noticed that you can change your username on writefreely and thought that was quite strange since its the first software I have noticed in the fediverse that has this ability. If I am following a writefreely account from mastodon and I change my username, I am not automatically following the new username, and I am still following the old one. so if I change my username 10 times I can separately follow 10 different accounts. I am unsure of all the repercussions of this but I can think of many. I think at the very least there should be a warning that changing the username is not recommended due to some incompatibilities or issues with federation between other parts of the fediverse.

was playing with the new instance (running writefreely v0.11.2)

Copy link

thebaer commented Dec 24, 2019

Hey, thanks for bringing this up! Yeah, we've always let people change their username, from before we added ActivityPub support. In my experience, it's pretty important for usability, so I wouldn't want to remove that feature. But I think your suggestion of adding a warning would be great -- whether that's in the app or just in the documentation.

Otherwise we'll need other fediverse platforms to agree on how they follow changed usernames. That could be 301 redirects on our end, as suggested in this SocialHub thread, or maybe something else.

For the WriteFreely side, let's continue this discussion on this Discuss thread and on SocialHub. I'll close this issue now since it's more of a feature request than a bug.

@thebaer thebaer closed this as completed Dec 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

No branches or pull requests

2 participants