Prevent duplicate statuses in home timeline (reblogs) about mastodon HOT 1 CLOSED

Suggestion:

Home timelines are sorted sets in Redis, with a score and a value. Right now, both the score and the value are the same thing (the status ID). Since IDs increment over time, it's essentially like using a sort by created_at (with the exception that in some cases, an older status from a remote instance may come in later and get a later ID than some other status). The status ID stored is always of the wrapper statuses, even if it's a reblog. This could be changed easily:

Leave the wrapper status ID as the score, ensuring (mostly) correct causal sorting. But as the value, store the original status ID, so for reblogs it would be the ID of the reblogged status, for original statuses just the normal ID. When a newer reblog would be inserted into the set, the score of the old one would be updated, but a double entry would be avoided.

from mastodon.