Arbitrary project/instance metadata

[agateblue]

Following the discussion at https://mastodon.indie.host/@lalop/99885178481926478, I think it's important to allow applications to define and use arbitrary metadata, in complement of the standard subset that will be agreed upon.

While some metrics/data are relevant to most if not all applications/instances (user count, open #, uptime, etc.), some are only relevant to specific applications yet very important for end users.

For PeerTube, it could be the user upload quota, for Funkwhale it could be the library size (how much artists, tracks, etc), for Mastodon it could be the number of other nodes an instance is connected to, etc.

What I'm suggesting is to dedicate a key in the JSON-LD payload to put this project-specific data, so it can still be accessed and collected.

[almereyda]

Following the course that libresh/awesome-librehosters#7 took, we may wish to escalate another issue about telling Wikibase to serve JSON-LD: @maxlath presented a serious case about using Wikibase for software ontology maintenance.

Unfortunately the other link you bring up seems to be private.

In the thread https://twitter.com/almereyda/status/971204773407002624 we finde nice visualisations of such metadata of:

The Fediverse based on OStatus, Diaspora, Zot, ActivityPub, ...

• https://the-federation.info/
• https://fediverse.network/

Federated Wiki

• http://search.fed.wiki.org/federation-search.html
• http://search.fed.wiki.org:3030/graph/bundle.html

The Matrix ecosystem presents itself as follows:

• https://matrixstats.org/
• https://voyager.t2bot.io/#/stats
• https://lag.t2bot.io/
• https://www.hello-matrix.net/public_servers.php

We may also want to wish to understand which kind of metadata is implicit, used or would be useful to learn from:

• https://fediverse.party/ (data)
• https://switching.social/
• https://github.com/redecentralize/alternative-internet
• http://prism-break.org/
• https://www.privacytools.io/

Seems we're touching quite a broad domain here.