I'm working on a new nostr:npub120zh308gs69j3vwgvvrzgglv58vsk3q0vef43uajyu0lc3mtldsq2p33r2 API schema that will be used in metrofive and our mobile apps.

The MastoAPI that currently powers our webUI and mobile apps provides a solid and well-known interface, but we're already outgrowing it (we extended it, using the optional `_pe=1` param for pixelfed entities)

The new schema is much more efficient for our use case, and we'll continue to support the MastoAPI too (with atleast 1 year notice if we deprecate it)