When a user has access to multiple servers QTweet is in, there is a chance they may be accessing multiple Sharded instances. In those cases, all those shards have access to the user's DMs, and the user receives multiple instances of the tweet.
One way to fix this is to change the way we dispatch tweets to make sure we send them to the first shard that can receive them, and not to every shard. But that would be a bit heavier resource-wise... To consider.
When a user has access to multiple servers QTweet is in, there is a chance they may be accessing multiple Sharded instances. In those cases, all those shards have access to the user's DMs, and the user receives multiple instances of the tweet.
One way to fix this is to change the way we dispatch tweets to make sure we send them to the first shard that can receive them, and not to every shard. But that would be a bit heavier resource-wise... To consider.