I am fine with @ staying in Markdown-land rather than becoming a site-wide convention, or with it jumping in to general site-wide use.
If @ becomes more widely acceptable, or even becomes more used in the Markdown department, I'm leaning toward an implementation that allows for a user name and a domain that goes with it, because I'm trying to think of how it might be possible, for example, to gather the right user masthead for a Mastodon or other federated instance to indicate that it's Mastodon-as a service and also generate a correct link to the right user on that instance, since MAstodon doesn't have a central server idea like Twitter, tumblr, or Dreamwidth. If it's technically feasible to pull off this particular bit of wizardry, then @ syntax seems to have a possibility for doing all the things I would expect it to be used for.
no subject
If @ becomes more widely acceptable, or even becomes more used in the Markdown department, I'm leaning toward an implementation that allows for a user name and a domain that goes with it, because I'm trying to think of how it might be possible, for example, to gather the right user masthead for a Mastodon or other federated instance to indicate that it's Mastodon-as a service and also generate a correct link to the right user on that instance, since MAstodon doesn't have a central server idea like Twitter, tumblr, or Dreamwidth. If it's technically feasible to pull off this particular bit of wizardry, then @ syntax seems to have a possibility for doing all the things I would expect it to be used for.