Tagging Fediverse/Mastodon accounts (renaming contact:mastodon to contact:fediverse)

At the moment, we have contact:mastodon (~400 uses). Surely this should actually be contact:fediverse, as the entire point of the Fediverse is that accounts are interoperable?

What do people think about an automated edit to switch to contact:fediverse?

1 Like

How i understand everything:
Fediverse accounts can interact from mastodon with friendica and pixelfed, but that does not mean a mastodon-account is automatically a friendica or pixelfed account.

That does mean a company can actually have two different accounts, one on pixelfed and one on mastodon, that differ.

5 Likes

that’s a fair point. In that case, how about a third level like contact:fediverse:mastodon=* ? Trying to parse and keep track of them will be a pain otherwise

At the risk of becoming another phone=* vs contact:phone=*, or the equivalent with Facebook, the tag contact:mastodon=* or contact:bluesky=* etc. would make the most sense. Just because they can talk with each other doesn’t mean they need a common tag. We don’t tag contact:ATT:phone=* or contact:ATT:fax=* because phones are interoperable just as federation is.

3 Likes

Sharing a resource which helps untangle the various Fediverse-related services and protocols: from Fediverse - Wikipedia
File:A view into the Fediverse.png - Wikimedia Commons

1 Like

There’s very little point in making a difference between the various kind of fedi software, as from an OSM data consumer POV, the end user could reach the account in the value with any kind of fedi software they’re using.

Do keep in mind, however, that Bluesky, Threads etc. are not to be considered part of the fediverse, they’re commercial, proprietary software that supports very basic communication with the fediverse but is generally regarded as hostile from within (cf. fedipact).