It's great they are adopting the standard but those aliases are ugly.
Instead of openprotocolfanblog.wordpress.com@openprotocolfanblog.wordpress.com it should be openprotocolfanblog@wordpress.com
Instead of openprotocolfanblog.wordpress.com@openprotocolfanblog.wordpress.com it should be openprotocolfanblog@wordpress.com
For example: `openprotocolfanblog@wordpress.com` 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 `username@wordpress.com`.
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
This way, every Wordpress blog is for practical purposes its own instance.
That said, the username component does seem unnecessarily unwieldy.