nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq4v73f6qqcu20d2euq0z0qdnw6ayca62ffzy9wctlsav2f60kn7qqave537 (nprofile…e537) LOL There's more than enough room for both of us, I think. ;-)
I hear what you're saying, and it makes sense that this should be an option. Just as bottom-posting in email is entirely possible, if you want to. And I do from time to time; you know when people say things like, "Comments below in red?" Well, I hate that because I've overridden the colours in my email client and forced everything to white text on a black background because of my RP, and I have to keep reminding people that I can't see their replies in different colours. :P But I do occasionally say, "Comments below", and will prefix their message with > (the old fashioned way; the way my friend does it), and then put my responses inline.
I think for WhatsApp and other chatty applications, it also kinda makes sense, but for anything that continually streams, I personally feel more comfortable with newest on top.
Don't think of it as "top = future", think of it as "top = current". When you open your client, you want to see the most up-to-the-minute news right there in front of you, and you could scroll down to see things further and further back in time. If the newest stuff was on the bottom, then what would have to happen when you first open your client?
Would it be like when you open a long ChatGPT conversation because you want to add something to it, and you first have to wait a minute or more for it to scroll all the way to the bottom to see your most recent question/answer? Or would you see only a single post (the most recent one) and then have it continually shunted down to make way for a new post each time one came in? Or something else?
Threads are different because when you click on a thread to open it up, you're working in a contained bucket. It (ostensibly, notwithstanding the Fediverse's issue with threads, where replies come from other instances that yours doesn't federate with) already has all the replies you need to see, and it's not going to be loading in messages dated before the one you're looking at, which would cause the one you're looking at to be shunted downward as you're reading it.
Know what I mean? 🤔
Graham Downs /
npub1q8…a5w8f
2024-12-19 08:20:38
in reply to nevent1q…u2h0
Author Public Key
npub1q8hnju2crm5r4fu7ystcdfav2r8etmx45nsur4le5ljjmhwj5yzs9a5w8fSeen on
wss://relay.nostr.bandPublished at
2024-12-19 08:20:38Event JSON
{
"id": "c4dc26f354be9c366264c95f0e065bf99aca5d3802dcf8f5ff4ee05aa03ad329",
"pubkey": "01ef3971581ee83aa79e241786a7ac50cf95ecd5a4e1c1d7f9a7e52dddd2a105",
"created_at": 1734596438,
"kind": 1,
"tags": [
[
"p",
"ab3d14e800c714f6ab3c03c4f0366ed7498ee949488857617f8758a4e9f69f80",
"wss://relay.mostr.pub"
],
[
"p",
"2a97e4e2fd1f34add039232935eb843503f3232afcdd28c14cfa5faa420a18f7",
"wss://relay.mostr.pub"
],
[
"e",
"ba37cd58b8de05086a895cda59ce25a665fc184a6db0f597b0b3bd0a912927a0",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://mastodon.africa/users/GrahamDowns/statuses/113678512177488283",
"activitypub"
]
],
"content": "nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq4v73f6qqcu20d2euq0z0qdnw6ayca62ffzy9wctlsav2f60kn7qqave537 LOL There's more than enough room for both of us, I think. ;-)\n\nI hear what you're saying, and it makes sense that this should be an option. Just as bottom-posting in email is entirely possible, if you want to. And I do from time to time; you know when people say things like, \"Comments below in red?\" Well, I hate that because I've overridden the colours in my email client and forced everything to white text on a black background because of my RP, and I have to keep reminding people that I can't see their replies in different colours. :P But I do occasionally say, \"Comments below\", and will prefix their message with \u003e (the old fashioned way; the way my friend does it), and then put my responses inline.\n\nI think for WhatsApp and other chatty applications, it also kinda makes sense, but for anything that continually streams, I personally feel more comfortable with newest on top.\n\nDon't think of it as \"top = future\", think of it as \"top = current\". When you open your client, you want to see the most up-to-the-minute news right there in front of you, and you could scroll down to see things further and further back in time. If the newest stuff was on the bottom, then what would have to happen when you first open your client?\n\nWould it be like when you open a long ChatGPT conversation because you want to add something to it, and you first have to wait a minute or more for it to scroll all the way to the bottom to see your most recent question/answer? Or would you see only a single post (the most recent one) and then have it continually shunted down to make way for a new post each time one came in? Or something else?\n\nThreads are different because when you click on a thread to open it up, you're working in a contained bucket. It (ostensibly, notwithstanding the Fediverse's issue with threads, where replies come from other instances that yours doesn't federate with) already has all the replies you need to see, and it's not going to be loading in messages dated before the one you're looking at, which would cause the one you're looking at to be shunted downward as you're reading it.\n\nKnow what I mean? 🤔",
"sig": "6e5a39ddc3c8d5489ae81c5da5465dc9b4e5b2554c3299dece343c5f02cff7a05d7a4d456c3b3b0430a40d6df16f66c56e2ff08a97476b3ea3131b536125631d"
}