nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq0dxafmw65292jj77fv3y8zmfc59lns47f4j6au2ahs47acy9ex7svv7wld (nprofile…7wld) Presentation design is *always*, *without exception*, about what matters to the user.
The pointers in the timeline belong to the user, and are managed by the client. The default should be 'Where was I? Ah yeah that was the last thing I was reading'. Most recently used pointer is stored by client and used on refresh of browser to position presentation in the timeline.
Continuous scroll presentation is leakage of server behaviour into user presentation space. It's allowable, because the user might want that. But I don't like it as a default behaviour.
*MS Teams*
This is a surprisingly good chat application from this point of view. Teams has a 'Last read' divider which sort-of implements the pointer I'm talking about. The client doesn't jump there as I believe it should, but it's there at least.
*Slack and reply-chaining*
Teams is better than Slack, imo. For instance I've always been puzzled by Slack's Reply behaviour. Operationally it should either be continuous in one thread (like Teams and WhatsApp) or cascade to ever-more-refined detail (like Reddit and, actually, Masto - another debate here). Instead, you get one sidebar with all Reply text in it. What happens if you reply to a reply? All goes in that one sidebar as though you're replying to the original post.
The way that Masto seems to store replies is in a tree. If alice writes a post, bob 's reply is a leaf off her post. And if charlie replies to bob, his reply a leaf off his post. But if dudu replies to alice, her post is another leaf off alice.
alice
├── bob
│ └── charlie
└── dudu
You can see how Masto deals with this in threads. It's not terrible. Is it better than Teams? Not sure. The consequence in Teams is that time ordering is presented before reply ordering. In Teams it depends on who replied first - their message comes first. In Mastodon and Reddit, it's first ordered by who is being replied to, then by time.
Mal /
npub192…terkn
2024-12-19 10:11:37
in reply to nevent1q…satl
Author Public Key
npub192t7fcharu62m5peyv5nt6uyx5plxge2lnwj3s2vlf065ss2rrmssterknPublished at
2024-12-19 10:11:37Event JSON
{
"id": "a99ab2fa1facc909e2d754d7c5bc0a1d7f93aaaab29e5ed8e24b8b85839724b3",
"pubkey": "2a97e4e2fd1f34add039232935eb843503f3232afcdd28c14cfa5faa420a18f7",
"created_at": 1734603097,
"kind": 1,
"tags": [
[
"p",
"7b4dd4eddaa28aa94bde4b22438b69c50bf9c2be4d65aef15dbc2beee085c9bd",
"wss://relay.mostr.pub"
],
[
"p",
"01ef3971581ee83aa79e241786a7ac50cf95ecd5a4e1c1d7f9a7e52dddd2a105",
"wss://relay.mostr.pub"
],
[
"e",
"868de848ba90edaf6fd817a46b29f18ba4d0591507c92761ab966d137fed3c9d",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://mastodon.africa/users/malmorrow/statuses/113678948582035572",
"activitypub"
]
],
"content": "nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq0dxafmw65292jj77fv3y8zmfc59lns47f4j6au2ahs47acy9ex7svv7wld Presentation design is *always*, *without exception*, about what matters to the user.\n\nThe pointers in the timeline belong to the user, and are managed by the client. The default should be 'Where was I? Ah yeah that was the last thing I was reading'. Most recently used pointer is stored by client and used on refresh of browser to position presentation in the timeline.\n\nContinuous scroll presentation is leakage of server behaviour into user presentation space. It's allowable, because the user might want that. But I don't like it as a default behaviour.\n\n*MS Teams*\n\nThis is a surprisingly good chat application from this point of view. Teams has a 'Last read' divider which sort-of implements the pointer I'm talking about. The client doesn't jump there as I believe it should, but it's there at least.\n\n*Slack and reply-chaining*\n\nTeams is better than Slack, imo. For instance I've always been puzzled by Slack's Reply behaviour. Operationally it should either be continuous in one thread (like Teams and WhatsApp) or cascade to ever-more-refined detail (like Reddit and, actually, Masto - another debate here). Instead, you get one sidebar with all Reply text in it. What happens if you reply to a reply? All goes in that one sidebar as though you're replying to the original post.\n\nThe way that Masto seems to store replies is in a tree. If alice writes a post, bob 's reply is a leaf off her post. And if charlie replies to bob, his reply a leaf off his post. But if dudu replies to alice, her post is another leaf off alice.\n\nalice\n├── bob\n│ └── charlie\n└── dudu\n\nYou can see how Masto deals with this in threads. It's not terrible. Is it better than Teams? Not sure. The consequence in Teams is that time ordering is presented before reply ordering. In Teams it depends on who replied first - their message comes first. In Mastodon and Reddit, it's first ordered by who is being replied to, then by time.",
"sig": "865f1f72906d8f2bbe34c24ca746f78bd3052dcef1a80c9c9907df7acc6d3d5e6198fb1d7118bb2cbd67eb8050eb85a3c5527ee993659775f7bc7eb380dcc427"
}