There's something to terminology and design to ponder, I think.
@diogo of #GNUSocial submitted the #UnboundGroups #FEP before, that can be used to indicate an #ActivityPub Group is 'spread out'/supported on multiple instances:
https://codeberg.org/fediverse/fep/src/branch/main/fep/2100/fep-2100.md
A metagroup has an unfortunate association to Meta. Is it an unbound group, or maybe a compound, or composite group?
For example:
"Front-end" group is a composite of "NodeJS" + "Deno" groups (where these groups may both be unbound too).
Ah, it’s just a name, easy to change, although I think it’s dumb we let corporations take words away from us. But I think composite sounds nice, and represents the concept well.
Thanks for the link. It currently requires less cooperation (none) between groups.
Actually, the way it’s currently headed, it’s working out more like a relay. It’s just a named, defined scope relay.
Azorius (software)
This is about the software. Development, operations, etc. Even the occasional bug report.