This! Imagine we could get to the point where SH is a display layer on top of a distributed data layer of dev discussions. So deleting stuff from SH didn’t delete it from the underlying data layer. Then we could develop a process for pruning SH down to the strong wood. Akin to using git rebase to prune version history down to the key info.
OR we could keep SH as is, and use a federated forum at distillery.activitypub.rocks to create a more curated portal. If anyone disagreed with the curation approach, the underlying data is all still there, so they could fork the effort to demonstrate their approach on top of the same shared data layer.
Does this sound familiar? It should. It’s exactly how existing fediverse moderation works.
Fair point. This could be addressed by having action-specific Actor addresses (eg @discourse-crosspost@socialhub.ap.rocks). In the longer term there could be a different character to denote actions (eg !crosspost@ @discourse@socialhub.ap.rocks), although that would need pan-fediverse buy-in.
On top of this, I mentioned the option of limiting crossposting permission to fediverse accounts with privileges on the receiving forum (eg forum and category admins/mods only). That could further reduce the likelihood of accidental misuse, as well as intentional flooding.