nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq4v73f6qqcu20d2euq0z0qdnw6ayca62ffzy9wctlsav2f60kn7qqave537 (nprofile…e537) Personally, I don't like the "Where Was I?" approach for social media with a timeline, because it's not how I like to use Mastodon or X or (even) Facebook. That's one of the reasons I railed so hard against FB and X's introduction of algorithms back in the day, and was one of my main drawcards for Mastodon.
Generally, I open my Mastodon client in the morning when I switch on my computer, and just let it stream while I'm working or doing other things. When I have a second to spare, I'll switch to it to see what's happening. I'm not interested in scrolling back to see everything that's happened since last I checked. I like the firehose, the constant stream of up-to-the-minute news and information. Similarly when I first open it in the morning, I want to see what's happening NOW; I don't scroll back to see what happened overnight. Same with Tusky on my phone. Although Tusky does tend to show me where I was last, 99% of the time I just ignore that and click the Home button to scroll to the top (i.e. most recent post).
If I see a post that I'd really like to reply to but don't have time right now, I'll bookmark it and reply tomorrow morning or when I have time... typically when I'm at my computer because a) when I'm on my phone I probably don't have time, and b) writing long-form posts on my phone is a pain. :-)
Re how Threads are displayed, I don't particularly like how any of those three applications (Mastodon, Teams, or Slack) *present* threads. I agree with the way Mastodon stores threads; I just wish they were displayed that way. More like Usenet, with a proper tree that you can expand and collapse to see exactly who replied to what and which comment *you're* replying to. Lots of little threads inside the main thread.
Obviously, in the Fediverse's case, that's a client function, and different clients may be better at presenting threads to the user, but I feel like the issue we now have with not seeing all replies because of how ActivityPub works, might be made even worse by displaying threads in a tree... Or maybe I'm wrong. Maybe it would make it actually not so bad, because you'd miss entire branches of the tree instead of individual posts, so you wouldn't notice it so much?
Graham Downs /
npub1q8…a5w8f
2024-12-19 10:27:38
in reply to nevent1q…qeh7
Author Public Key
npub1q8hnju2crm5r4fu7ystcdfav2r8etmx45nsur4le5ljjmhwj5yzs9a5w8fSeen on
wss://relay.nostr.bandPublished at
2024-12-19 10:27:38Event JSON
{
"id": "071e4089c940e34615fbf9b9fb16bfacaffb8e5f9beb42de3012933ba25f2afd",
"pubkey": "01ef3971581ee83aa79e241786a7ac50cf95ecd5a4e1c1d7f9a7e52dddd2a105",
"created_at": 1734604058,
"kind": 1,
"tags": [
[
"p",
"ab3d14e800c714f6ab3c03c4f0366ed7498ee949488857617f8758a4e9f69f80",
"wss://relay.mostr.pub"
],
[
"p",
"2a97e4e2fd1f34add039232935eb843503f3232afcdd28c14cfa5faa420a18f7",
"wss://relay.mostr.pub"
],
[
"e",
"a99ab2fa1facc909e2d754d7c5bc0a1d7f93aaaab29e5ed8e24b8b85839724b3",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://mastodon.africa/users/GrahamDowns/statuses/113679011553308681",
"activitypub"
]
],
"content": "nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq4v73f6qqcu20d2euq0z0qdnw6ayca62ffzy9wctlsav2f60kn7qqave537 Personally, I don't like the \"Where Was I?\" approach for social media with a timeline, because it's not how I like to use Mastodon or X or (even) Facebook. That's one of the reasons I railed so hard against FB and X's introduction of algorithms back in the day, and was one of my main drawcards for Mastodon.\n\nGenerally, I open my Mastodon client in the morning when I switch on my computer, and just let it stream while I'm working or doing other things. When I have a second to spare, I'll switch to it to see what's happening. I'm not interested in scrolling back to see everything that's happened since last I checked. I like the firehose, the constant stream of up-to-the-minute news and information. Similarly when I first open it in the morning, I want to see what's happening NOW; I don't scroll back to see what happened overnight. Same with Tusky on my phone. Although Tusky does tend to show me where I was last, 99% of the time I just ignore that and click the Home button to scroll to the top (i.e. most recent post).\n\nIf I see a post that I'd really like to reply to but don't have time right now, I'll bookmark it and reply tomorrow morning or when I have time... typically when I'm at my computer because a) when I'm on my phone I probably don't have time, and b) writing long-form posts on my phone is a pain. :-)\n\nRe how Threads are displayed, I don't particularly like how any of those three applications (Mastodon, Teams, or Slack) *present* threads. I agree with the way Mastodon stores threads; I just wish they were displayed that way. More like Usenet, with a proper tree that you can expand and collapse to see exactly who replied to what and which comment *you're* replying to. Lots of little threads inside the main thread.\n\nObviously, in the Fediverse's case, that's a client function, and different clients may be better at presenting threads to the user, but I feel like the issue we now have with not seeing all replies because of how ActivityPub works, might be made even worse by displaying threads in a tree... Or maybe I'm wrong. Maybe it would make it actually not so bad, because you'd miss entire branches of the tree instead of individual posts, so you wouldn't notice it so much?",
"sig": "dc5a9f8dc8a7bfc7eae0404f8c98efd4b80fa97e3f35800a02e89f9975a71efc8c27c06f95d124621eb84c740ce7b19aa8f3e7d288fda3eaab0162a418a957de"
}