pull down to refresh

First, a few meta-comments:
  • I subscribed to this thread shortly after you posted it, thinking that reacting to SN notifications would approximate "following" a conversation. Within a few hours, I had to unsubscribe, since the notifications came in faster than I could handle - and lacked, in my experience, the "context" I was hoping it would provide.
  • The above may well be just a function of my particular environment (number of tabs open on desktop and mobile, etc) so I'd love to hear how/if others managed to consume the content in a more practical, logical, efficient way?
  • Of course, it could also be me just showing my age. :)
Then, content-wise: Extremely impressed with the overall quality of the contributions. I've come across fast thinkers and typists before, but this was right up there with the best!
  • How do you manage to reply to comments so fast?
  • Are you using speech-to-text, by any chance? Other tools? Surely not all responses can be pre-authored?
I hope to be better prepared for Part 2.
Speaking personally, it's more dysfunction than anything -- I'm working, have a tab open w/ SN in my browser, and when the little red dot appears on the tab, I pounced, so that the person would feel attended to. Wasn't a great day for my productivity, it must be admitted, but it was fun for me :)
It was all manual typing. The only thing pre-authored were those initial seed questions.
I hope you don't feel like you need to do anything special to prepare, bc you really don't, other than reading the section of the book. And I'll try to make that less necessary to do next time, by providing some prompts that connect to the book but that someone who's been thinking about the btc space for a while can engage with.
It might be useful to @k00b if you described the context you wish the notifications might have had? I've been noodling on that, too, in a more general way: how could you make the notifications maximally useful for following a conversation?
reply
I subscribed to this thread shortly after you posted it, thinking that reacting to SN notifications would approximate "following" a conversation. Within a few hours, I had to unsubscribe, since the notifications came in faster than I could handle - and lacked, in my experience, the "context" I was hoping it would provide.
I can see that happening. What does it mean to follow a conversation to you? What are you hoping to gain?
reply
What does it mean to follow a conversation to you?
Probably (a lot) more screen real estate, lol. I can imagine following a conversation if somehow the whole thread could be made visible on a single screen, with a little red dot appearing whenever and wherever a participant adds a comment, Probably completely impractical, but that's how I'd describe it.
What are you hoping to gain?
I was hoping the notifications would point me to where we are in the conversation, but I couldn't figure out if/how the notifications were ordered / stacked, if that makes sense?
reply
That's helpful. It sounds like you might want an aggregate of what you've missed rather than a stream of everything that's happened.
I think this would be useful in all our conversation notifications - not just subscriptions. I'll think on it more.
reply
A trivial way that might help a bit is the notification provides some relevant sub-tree to contextualize the thing. At a minimum this could be the parent, but perhaps there could be more interesting ways to do it.
Notifications could also "roll up" the changed state (complete w/ relevant context) since you last saw it. Or maybe that's what you mean? That's probably what you mean.
I can imagine that re-loading a page (e.g,. this one) could have everything that was here last time I loaded the page be dimmed; everything new to me appears in its current illumination; and everything that would be an update (e.g., my own posts that have been zapped, replies to things I've said) would be highlighted or something. So the change set is easy to spot, and the relevant-to-me changeset is even easier?
reply
That's probably what you mean.
Yep!
I can imagine that re-loading a page (e.g,. this one) could have everything that was here last time I loaded the page be dimmed; everything new to me appears in its current illumination; and everything that would be an update (e.g., my own posts that have been zapped, replies to things I've said) would be highlighted or something. So the change set is easy to spot, and the relevant-to-me changeset is even easier?
Yep that's what I'm thinking to address the problem that this solution implies: Feature request: option to archive seen posts
Feature requests are often the wrong solution to the right problem ... is what I like to say.
reply
Sounds great, thanks!
reply