source namespace: what service should be used for Fediverse platform accounts?

[Oblomov]

Fediverse platforms all use the same form to identify users (@username@server). Should the service in this case identify the platform (e.g. Mastodon vs Pleroma vs Akkoma vs PixelFed or whatever), the specific server (e.g. mas.to vs pixelfed.social or whatever, in which case the username/handle could omit the server part), or something else that identifies the generic naming scheme?

[scripting]

@Oblomov -- I'm having trouble parsing the question. Can you provide an example of the XML you plan to use.

[Oblomov]

Considering a feed generated on Mastodon or PixelFed (both Fediverse platforms). How would the source:account specify the service and account?

Possibilities:

<source:account service="mastodon">@[email protected]</source:account>
<source:account service="pixelfed">@[email protected]</source:account>

or

<source:account service="mastodon.example.com">username</source:account>
<source:account service="pixelfed.example.com">username</source:account>

or

<source:account service="fediverse">@[email protected]</source:account>
<source:account service="fediverse">@[email protected]</source:account>

[scripting]

All those look fine to me. Remember I am a total newbie on Mastodon and I cannot tell you what to do here.

Are you the software developer who has to make this decision or is that someone else?

[Oblomov]

I don't have immediate plans to work on implementing this, it was more of something that jumped to my attention while I was reading the spec.