meta groups

I've implemented basic support for meta groups (groups of groups). There's a lot of redundancy because of the federated nature of the azoriverse, with similar groups duplicated across multiple servers. Meta groups are a solution, by presenting users with a (somewhat transparent) single group that collects all of the posts.

I've created two meta groups, metaprog and technoscience, for demo and testing.

This is still preliminary, so federation doesn't quite work yet, but eventually the goal would be that you can follow a metagroup, and it will forward activities. Instead of having to individually chase down every new programming group that gets created, you could delegate that the metaprog admin (me) to keep the group list updated.

smallcircles,
@smallcircles@social.coop avatar

@tedu

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).

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • Durango
  • DreamBathrooms
  • InstantRegret
  • magazineikmin
  • osvaldo12
  • everett
  • Youngstown
  • khanakhh
  • slotface
  • rosin
  • thenastyranch
  • ngwrru68w68
  • kavyap
  • normalnudes
  • megavids
  • ethstaker
  • GTA5RPClips
  • modclub
  • cisconetworking
  • mdbf
  • tacticalgear
  • cubers
  • provamag3
  • tester
  • anitta
  • Leos
  • JUstTest
  • lostlight
  • All magazines