# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 35
# self = https://watcher.sour.is/conv/7exlyga
See this previous chain got forked! 😁
See this previous chain got forked! 😁
@prologic I know, because fork makes it 100% sure to know who is replying to whom. Just like email's in-reply-to does (plus the message-id).
This is the problem of forking by default! 😥
This is the problem of forking by default! 😥\n\n
This is the problem of forking by default! 😥
Is this something jenny is doing specifically or you as the user? 🤔
Is this something jenny is doing specifically or you as the user? 🤔
It makes it very difficult to follow your “replies” if you fork every reply 😆
It makes it very difficult to follow your “replies” if you fork every reply 😆
It is all on the user, not jenny.
It makes it very difficult to follow your “replies” if you fork every reply! 😂
It makes it very difficult to follow your “replies” if you fork every reply! 😂
> Let’s just say, I’ve seen this happen with multiple products at work: Step 1, someone builds something which doesn’t support a “reply” feature at all. Step 2, the thing grows, now people want “reply”. Step 3, it gets confusing with all the linear replies and now people want “full threading”. 😁 That’s also basically what happened to twtxt/yarn. Maybe, over time, everything evolves into Usenet. 🤣
@movq was right.
\n> Let’s just say, I’ve seen this happen with multiple products at work: Step 1, someone builds something which doesn’t support a “reply” feature at all. Step 2, the thing grows, now people want “reply”. Step 3, it gets confusing with all the linear replies and now people want “full threading”. 😁 That’s also basically what happened to twtxt/yarn. Maybe, over time, everything evolves into Usenet. 🤣\n\n@https://www.uninformativ.de/twtxt.txt> was right.
@movq @mckinley No one ever said he wasn’t 😂 But I’m reluctant to change yarnd’s behavior here 😁
@movq @mckinley No one ever said he wasn’t 😂 But I’m reluctant to change yarnd’s behavior here 😁
@prologic You will have to agree that always using reply (like I am doing on this one) loses everything on translation after the third or fourth replies. It simply doesn't promote engagement. On top of that, all replies show on the timeline as well, without much---to none---context.
@prologic If the client isn't tweaked to accommodate "full threading" then the fork function shouldn't be used for replies. I've always treated it as an "off-topic response" button.
@quark I don’t entieely agree; I use “Fork” to mean an off-topic as-in @mckinley
@quark I don’t entieely agree; I use “Fork” to mean an off-topic as-in @mckinley
Humans are _actually_ pretty good at remembering context and have pretty good long-term memories, and only need to recall a partial context to recall the "gist" of the rest without having to go back and reread everything. LIke in this conv, you only have to scroll up a bit with either the yarnd Web interface or Goryon mobile client.
Humans are _actually_ pretty good at remembering context and have pretty good long-term memories, and only need to recall a partial context to recall the "gist" of the rest without having to go back and reread everything. LIke in this conv, you only have to scroll up a bit with either the yarnd Web interface or Goryon mobile client.
@prologic @quark @mckinley fair enough. I can subscribe to this, if the many agree. Yet, there is no way to enforce that onto others, so it will have to be something we are willing to live with. I know I am. 😊
@prologic
At first, there was only “reply” in jenny. Then you introduced “fork”, so I added that method. 😁 But there is no default, really. The example mutt config just installs two hotkeys and it’s up to the user which one to press.
I’m not sure which model is better, to be honest. 🤔
btw, jenny does not pre-fill mentions of all the people in the conversation. When you hit “reply” (or “fork”), you only get a mention of the person you’re replying to. I think that’s actually a *little* bit better, because those “mass-mentions” can get a bit noisy. 🤔 I regularly see mentions of my nick, but the person really was talking to someone else. I just happened to be “in the loop”. (Reminds me a bit of business e-mail. 🤣)
@prologic
At first, there was only “reply” in jenny. Then you introduced “fork”, so I added that method. 😁 But there is no default, really. The example mutt config just installs two hotkeys and it’s up to the user which one to press.
I’m not sure which model is better, to be honest. 🤔
btw, jenny does not pre-fill mentions of all the people in the conversation. When you hit “reply” (or “fork”), you only get a mention of the person you’re replying to. I think that’s actually a *little* bit better, because those “mass-mentions” can get a bit noisy. 🤔 I regularly see mentions of my nick, but the person really was talking to someone else. I just happened to be “in the loop”. (Reminds me a bit of business e-mail. 🤣)
@prologic \nAt first, there was only “reply” in jenny. Then you introduced “fork”, so I added that method. 😁 But there is no default, really. The example mutt config just installs two hotkeys and it’s up to the user which one to press.\n\nI’m not sure which model is better, to be honest. 🤔\n\nbtw, jenny does not pre-fill mentions of all the people in the conversation. When you hit “reply” (or “fork”), you only get a mention of the person you’re replying to. I think that’s actually a *little* bit better, because those “mass-mentions” can get a bit noisy. 🤔 I regularly see mentions of my nick, but the person really was talking to someone else. I just happened to be “in the loop”. (Reminds me a bit of business e-mail. 🤣)
@prologic
At first, there was only “reply” in jenny. Then you introduced “fork”, so I added that method. 😁 But there is no default, really. The example mutt config just installs two hotkeys and it’s up to the user which one to press.
I’m not sure which model is better, to be honest. 🤔
btw, jenny does not pre-fill mentions of all the people in the conversation. When you hit “reply” (or “fork”), you only get a mention of the person you’re replying to. I think that’s actually a *little* bit better, because those “mass-mentions” can get a bit noisy. 🤔 I regularly see mentions of my nick, but the person really was talking to someone else. I just happened to be “in the loop”. (Reminds me a bit of business e-mail. 🤣)
@movq Yeah I think your approach to just include the mention of the person you’re replying to might be better. I’ve noticed this over time too 👌
@movq Yeah I think your approach to just include the mention of the person you’re replying to might be better. I’ve noticed this over time too 👌