The obvious 'let's use email instead of that @you thing' would make implementation really non obvious, because it dramatically changes the @ role from the current usage: @ means 'adressed to', not 'residing at' like email/xmpp.
I'd reverse the order, which would read much better and follow known ordering conventions (FQDNs, email...):
email tag syntax inspired: @abc%example.com. That would be @marcoarment%twitter.com and @marco%app.net.
FQDN inspired: @abc.example.com looks much better. That would be @marcoarment.twitter.com and @marco.app.net. It would follow the convention that a non qualified name belongs to the local net. I don't know how that could possibly extend to actually integrate with DNS itself, so that a something-record @marco.marco.org. would resolve to the service handling marco's status stream, MX style.
You will soon be able to use your own domain names so ^https://example.com will be possible.