# 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 6
# self = https://watcher.sour.is/conv/tvotddq
@stackeffect @fastidious Let me ask you guys a question: What’s your workflow here? You hit the “reply” hotkey, the editor comes up, then what? You start writing and writing and then, at some point, you decide “nah” and just do :q!?
The reason why I’m asking: I think I sometimes hit :w in between. This is kind of muscle memory for me (I’m actually not 100% sure if I do it or not …). So a :q! wouldn’t work for me, because I would accidentally send a half-written twt.
Another thing to consider: Maybe users have configured their editors to do auto-save after a while. 🤔
Either way, I suspect the current way to cancel a twt (saving an empty file) has to stay (whether I implement an *additional* mechanism to detect “cancel” or not). It is very explicit and the user/editor won’t do it by accident.
So, yeah, what’s your workflow? How do you use it?
@stackeffect @fastidious Let me ask you guys a question: What’s your workflow here? You hit the “reply” hotkey, the editor comes up, then what? You start writing and writing and then, at some point, you decide “nah” and just do :q!?
The reason why I’m asking: I think I sometimes hit :w in between. This is kind of muscle memory for me (I’m actually not 100% sure if I do it or not …). So a :q! wouldn’t work for me, because I would accidentally send a half-written twt.
Another thing to consider: Maybe users have configured their editors to do auto-save after a while. 🤔
Either way, I suspect the current way to cancel a twt (saving an empty file) has to stay (whether I implement an *additional* mechanism to detect “cancel” or not). It is very explicit and the user/editor won’t do it by accident.
So, yeah, what’s your workflow? How do you use it?
@stackeffect @fastidious Let me ask you guys a question: What’s your workflow here? You hit the “reply” hotkey, the editor comes up, then what? You start writing and writing and then, at some point, you decide “nah” and just do :q!?
The reason why I’m asking: I think I sometimes hit :w in between. This is kind of muscle memory for me (I’m actually not 100% sure if I do it or not …). So a :q! wouldn’t work for me, because I would accidentally send a half-written twt.
Another thing to consider: Maybe users have configured their editors to do auto-save after a while. 🤔
Either way, I suspect the current way to cancel a twt (saving an empty file) has to stay (whether I implement an *additional* mechanism to detect “cancel” or not). It is very explicit and the user/editor won’t do it by accident.
So, yeah, what’s your workflow? How do you use it?
@movq Hah! well i use Nano so i just ctrl-x n
@movq Hah! well i use Nano so i just ctrl-x n
@xuu Well, the point is, things do not work like this.
Actually in nano you would have to ctrl-k ctrl-k ctrl-x y to discard your reply.