@Darius Kazemi This could get the more interesting, the farther something is away from Mastodon.

Even if it can cope with Hubzilla which remains to be seen, I expect it to run into trouble when it has to deal with (streams). That's for two reasons:

One, (streams) is actually intentionally nameless and brandless and has next to no nodeinfo code, in case you need it. This also means that it doesn't have a unified instance identifier. Mastodon always identifies as "mastodon", as does Glitch. Pixelfed always identifies as "pixelfed". Lemmy always identifies as "lemmy". And so forth.

(streams) does not always identify as "streams" or "(streams)". (streams) instances may identify as whatever their admins want them to identify. The most important public instance identifies as "get ready to rumbly". Others have identified or still identify as "diversi spiritus" or "theshire" or "mordor" or "gondor" or "nomád". The creator and maintainer himself is on an instance branded "y" (because Y is not X). And so forth.

It's a free-text string that could be anything, including other Fediverse projects. In fact, this has actually happened in the past: (streams) instances can be upgraded from instances of Zap, the third Osada, Misty (a.k.a. Mistpark 2020), Redmatrix 2020 and Roadhouse (all five defunct as of New Year's Eve, 2022), and when this was done, the instances kept their old branding.

Good luck identifying (streams) instances and telling them from instances of everything else by the usual means.

Two, (streams) is one of the first two Fediverse server applications that have introduced decentralised IDs as per FEP-ef61. Addresses may have "/.well-known/apgateway/did:⁠key:(48 random letters and/or digits)/" in them. Not sure if that'll mess with the Observatory.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Streams #(streams)