Cross-posting is a tricky thing to do. There are several possible routes we can take when implementing this and i would love to hear your feedback about this. However, take note it’s gonna be a bit technical (as it’s mostly a technical challenge).
First scenario is basically a post duplicated between multiple groups. You post a link to
group_a and by cross-posting it to
group_c, you’re basically duplicating the original link - so at the end of the process, we have three records of the same link, each one for each group. Each story has it’s own pool of comments and everything is 100% separated.
Pro of this is that it’s way simpler to implement. On the other hand, we’re getting duplicated stories and it’s hard to create a reliable “Front page of prismo instance” with stories gathered from all the local groups as it could display duplicated records.
Second scenario uses activitypub shares - when there is a story posted on
group_a, you can share it to other group just like you’re boosting something on mastodon or retweeting on twitter. Original story and all the shares has a separate pool of comments + in database, we have single story record + 2 shares and you can see what has been shared where, when and by who (if the group is public ofcourse). It’s also compatible with mastodon and other activitypub services which is pretty neat.
Huge pro of this solution is that we prevent stories duplication as much as it’s possible (it would still be possible to post the same story twice to different groups but using shares reduces the possibility of this) so wen can create a nice frontpage. Also, sharing is an activitypub concept and by using this, we’re doing something “fresh” in the link-aggregation world (i’m not aware any link-aggregation site has such feature?)