For interaction with different platforma it’s probably called interoperability. For its current state:

• Much of other platforma interoperate with Mastodon, but only at Mastodon’s lowest common denominator of “tweets” and links with lead. Lemmy communities are treated like “bots” reblogging anything posted to it,
• Almost any of not-vanilla-Mastodon allow Markdown formatting and Mastodon will show it normally. The same with posts over default 500 chars limit. You can read posts longer than you are able to write,
• Pixelfed deliberately narrows this denominator only to posts with images. However it allows posts with more than 4 images, but only not-vanilla-Mastodon instances will be able to see all of them. Posts can be geotagged, but AFAIK only Vernissage, Friendica and FediHood are able to swe these,
• Mastodon users can tag a Lemmy community to post to it. However you can not mod a comm from there,
• MBin allows to interact with content both from microblogging like Mastodon and with Lemmy. Lemmy interoperation is full, one with Mastodon lacks e.g. polls. Blog posts from WriteFreely and federated WordPress are shown in full. Unfortunately MBin does not work with Ghost,
• PieFed embraces and extends the format of Lemmy with e.g. flairs and polls. It also includes the best PeerTube compatibility among the Threadiverse (as federated reddit clones may be called). It has recently included events and support of following users from microblogs like Mastodon.

Nevermind, Noblogs is going down…

Hmm, this is strange. Nodeinfo indeed exists, but FediDB’s NodeInfo Explorer fails to fetch it. Nodeinfo is not excluded by robots.txt either: has Noblogs blocked FediDB and Fediverse.observer’s crawlers by other means?

Limited form of this is already used by PieFed instance chooser. Stability is calculated basing on number of admins with emergency access, non-admins paying enough for hosting and having automated daily backups.

Sites on noblogs.org are made on WordPress and they function like independent instances. They apparently do not expose their Nodeinfo, though.