The problem with that approach is the content (snaps) posted within tribes isn't owned by the tribes it submitted into. The user merely decides to bring it into the tribe for discussion, expanding on the content, etc. At the end of the day we cannot give mods (from multiple tribes) the power to modify/merge snaps with other snaps that have been posted, this would end up having the possibility of becoming a complete disaster.
Even if it only affected Snaps within that particular tribe? So say, if a Snap was merged with another in /t/pics but not in /t/photography, it would still show as two separate snaps in /t/photography. That way each tribe could have different policies on what exactly constitutes a repost.
That's my biggest fear, that once we start treading on territory this complex (solution wise), it may be difficult for anyone to actually grasp. I think the simpler we can do it, the better. Still something that is worth to consider, should we find an elegantly simple solution for it.
What if, as I suggested earlier, two snaps are merged when they link directly to each other, the younger snap becoming a related link to the older? It could provoke a button to confirm the merge. It could be broken if one or both remove the link. Both keep their rep with the older snap joining the tribes from the younger snap. That has the benefit of not requiring moderator intervention.
The problem with that approach is the content (snaps) posted within tribes isn't owned by the tribes it submitted into. The user merely decides to bring it into the tribe for discussion, expanding on the content, etc. At the end of the day we cannot give mods (from multiple tribes) the power to modify/merge snaps with other snaps that have been posted, this would end up having the possibility of becoming a complete disaster.
Even if it only affected Snaps within that particular tribe? So say, if a Snap was merged with another in /t/pics but not in /t/photography, it would still show as two separate snaps in /t/photography. That way each tribe could have different policies on what exactly constitutes a repost.
That's my biggest fear, that once we start treading on territory this complex (solution wise), it may be difficult for anyone to actually grasp. I think the simpler we can do it, the better. Still something that is worth to consider, should we find an elegantly simple solution for it.
What if, as I suggested earlier, two snaps are merged when they link directly to each other, the younger snap becoming a related link to the older? It could provoke a button to confirm the merge. It could be broken if one or both remove the link. Both keep their rep with the older snap joining the tribes from the younger snap. That has the benefit of not requiring moderator intervention.