@nickdowson well, it’s more a matter of volume. if i post in a group that has 1000 subscribers, that message has to get federated out to a maximum of 1000 pods, quickly. that is a different scaling problem than, say, Facebook has, because they can just spin up a bunch of web servers that all connect to the same database cluster. with us, we’re attempting to keep multiple databases in sync to ensure the data is distributed to each necessary outfit. by “group messaging”, i meant group posts, by the way…i’m just using the term “messaging” here to describe how pods communicate. sorry if my language is a bit unnecessarily esoteric.
anyway, my major concern is how are we going to distribute this data quickly and efficiently across a wide range of pods. in the current federation protocol, we do have some issues wherein a post won’t federate completely across everywhere it should be federating. i don’t believe there’s a fault-tolerance system baked in that ensures posts always make it to their destination. these features seem NECESSARY for group-based interaction, because suppose you make a post in a group and 50/100 of the pods that need to get it, don’t. that discussion either dies, or worse, it gets replied to. the replies federate across the group and are referencing a post that for half of the pods doesn’t even exist. before we implement a group feature, we need to figure out a solid solution to that problem.