Open chucker opened 5 years ago
Failing that, at least tagging statuses (e.g. with the tweet's web URL) so clients can ignore repeated arrivals of the same cross-posted status would be a good compromise. Ideally the tag's name would be neutral enough that cross-posts from other networks could be marked the same way, whether they be from Twitter, micro.blog, an RSS feed or whatever else one would want to feed into Mastodon.
This doesn't seem possible without changes to Mastodon. You would need a way to search Mastodon for other toots with this metadata, which is not currently possible.
Having the receiving user's server de-duplicate toots might be possible, but you'll have to check with Mastodon whether it is something they want to implement (I suspect no).
If two people both using the crossposter retweet the same tweet, this will currently result in two disparate Mastodon toots (with their own respective threads, even).
Could hidden metadata (such as the Twitter post ID) be added to the first toot so the second is skipped, and instead the first is boosted?