@cwebber another idea: a frontend-agnostic ActivityPub server daemon as a reference implementation. Much like Exim or Postfix for SMTP. Will manage sending and receiving queues, do other stuff like pulling conversations. On something binary-native like Rust. And, an interface library on Rust, so it can be called from any other language that can bind to binary libs (Python/Ruby/C/C++ etc). You need ActivityPub - here, call this lib and tell where the daemon is listening (socket or port). Done.
@banjofox so I was saying: maybe you guys at Aardwolf will pioneer groups. And then all be like "oh shit, groups are what we needed all along, let's make them".
@banjofox and you also have to pay for a server (or run it at home), possess skills to run a server and install an instance (which is NOT EASY, even for me). An average (non-Fediverse) person will say "fuck all that", and will go create a group on Facebook.
@banjofox I'm pushing for groups this passionately because making a new instance for every interest community is stupid and limiting - it places undue barriers on community creation and community participation. Like, if you are say painter AND writer AND LGBT - you are forced to choose between three instances to properly identify yourself (and you won't). This should not be the case. On the other end, to create a proper community you should own and pay for a domain name. This stinks as well.
@banjofox is it used on more than one server? The key issue is, groups should be interoperable between instances. A group originated, for example, on a small, one-user instance that can't federate is useless.
@banjofox@alice then I hope we'll convince Mastodon devs (and all others) to implement that too, so you don't have to have an Aardwolf account to join an Aardwolf group.