We have decided to do it like that, because it is an easy and nice way to have a unique ID that works with or without a custom domain.
For example: `[email protected]` makes only sense if you use the wordpress.com subdomain. If you have your own domain, you want to have something like `username@domain` not `[email protected]`.
Besides of that, you will be able to activate user-accounts (next to the blog-account) on higher plans. That means we had to choose something that is consistent but causes no collisions with usernames.
For example: `[email protected]` makes only sense if you use the wordpress.com subdomain. If you have your own domain, you want to have something like `username@domain` not `[email protected]`.
Besides of that, you will be able to activate user-accounts (next to the blog-account) on higher plans. That means we had to choose something that is consistent but causes no collisions with usernames.
And finally Mastodon and others only show the part before the @, that makes the ID very similar to what Bluesky is doing. https://mastodon.social/@pfefferle/111220452911718192