Normalize this
(Updated: I changed Twitter to X and User to Profile. I intentionally left out Bluesky because their approach to profile naming doesn't fit this paradigm and precedent.)
Normalize this
(Updated: I changed Twitter to X and User to Profile. I intentionally left out Bluesky because their approach to profile naming doesn't fit this paradigm and precedent.)
@jon Focus on the user and the NAMESPACE.
While mastodon.social is likely to continue using the Mastodon, ActivityPub federation is agnostic to which app the user accesses their account and the namespace (instance) may migrate from mastodon to another application.
@isagalaev Even if it belongs to a brand there's still a difference between [email protected], [email protected] and [email protected] ...
So namespacing does make sense. Even without socialism π
/cc @jon
@jon Easy to convey why this new way with now more than one social network doing the whole thing Twitter used to be alone in.
You donβt email: president. You email: [email protected]
Weβre out of the days off CompuServe style microblogging. Thereβs more than a major player now, time to do what we did once CompuServe needed to do more than 71234,56.
I get why press still put @ exampleusername and assume everyone will just think Twitter but that thinking is becoming dated.
or vomit on the commercial data collectors and propaganda turds.
@jon
An amendment I would add is the notion indicate whether this is is wenfingerable or not.
Alternatively, let the universal id be an HTTP URI. After all that is what ActivityPub standard calls for, as well.
@jon posts like this really make me miss tagging people in a retweet.
There is plenty of MSM in this platform - but they are mostly transmit only
@jon One great way to leverage this common sense solution is to contact the people responsible for widely used style guides.
For example, readers can contact the Chicago Manual of Style and ask them about this, pointing out this suggestion as a very good idea.
https://www.chicagomanualofstyle.org/qanda/submitaquestion.html