|
|
|
|
|
by lapinot
893 days ago
|
|
Depends on the "algorithm"! At this point "algorithm" in the context of social media doesn't mean anything sensible. A very common "algorithm" used to order messages in email inboxes is by "read/unread" status, which very much helps you catch up efficiently. Chronological sorting is very limited, in comparison with the myriad of other ways you could organize such data. |
|
Everything else is either an attempt to do less work or an attempt to shape user experiences for your own goals.
Threading requires two data elements per message, generated at the time of message creation: a unique-enough message ID, and the parent message ID. The client needs to have a method of storing 1 bit of state per message, either locally or on a home server. If messages have a timestamp, then a high-water mark is a useful heuristic. If the messages have required subjects, tags or topic groups, you can significantly improve both performance and user experience.
Usenet shall be resurrected, time and time again.