# 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 18
# self = https://watcher.sour.is/conv/swumzza
@prologic I made a quick PDF with my POV on the Reply button. Please feel free to ignore it, ask for more info, explain why I'm crazy π€ͺ, etc.
https://0x0.st/o-vj.pdf
Something I forgot to add, is that compared to Twitter, when you are replying to someone it's extremely redundant what and who are you replying to:
You get the text, a label (Replying to @), and a connection line between the previous Tweet, and that to be written.
Note: I'm not saying Yarn should behave like Twitter. It's more to take Jakob's law into consideration.
@eaplmx What do you mean by?
> Something I forgot to add, is that compared to Twitter, when you are replying to someone itβs extremely redundant what and who are you replying to:
π€
@eaplmx What do you mean by?
> Something I forgot to add, is that compared to Twitter, when you are replying to someone itβs extremely redundant what and who are you replying to:
π€
@eaplmx @prologic this is the movement of the post box I was mentioning a while back.
Somebody hits reply and the post box moves underneath what you're replying to. The same would apply to forks.
@ullarah Yeah I remember, and I _believe_ the intention was to make it a smaller textarea too right? Slice it in some with JS, with graceful degradation to current behaviour (_postbox at the top_)?
@ullarah Yeah I remember, and I _believe_ the intention was to make it a smaller textarea too right? Slice it in some with JS, with graceful degradation to current behaviour (_postbox at the top_)?
@prologic correct! I'll look into it tonight π
@eaplmx sorry mate I didn't see this PDF, I'll have a look at it more closely this evening π
@eaplmx sorry mate I didn't see this PDF, I'll have a look at it more closely this evening π
actually I just had a look at your PDF and your points are very valid and I think that is something we should try to improve the user experience for π
The underlying backend mechanics however are correct π
actually I just had a look at your PDF and your points are very valid and I think that is something we should try to improve the user experience for π
The underlying backend mechanics however are correct π
@eaplmx I fully agree, I don't understand this behavior either. The subject hashes are definitely missing, that's for sure.
@lyse They are there of course, but in the case of the "Conversation view" they are hidden input fields. This is so you don't accidently reply to the wrong conversation of course π
But I do agree we need to improve the UX of course! π Make it a bit more obvious what's going on...
@lyse They are there of course, but in the case of the "Conversation view" they are hidden input fields. This is so you don't accidently reply to the wrong conversation of course π
But I do agree we need to improve the UX of course! π Make it a bit more obvious what's going on...
@prologic Aha! I now get the idea behind it but to the user this is really weird and inconsistent. It just looks like you're starting off a new root twt. At least that's what I was thinking when I encountered that. Fun fact: Every now and then I just want to mention somebody in a new root twt, so I just reply to a conversation that person had participated in and remove all other mentions and the twt subject. This way I don't have to type out or copy-paste the mention myself. In tt that is.
@lyse Yup I agree with you in hindsight π€£
Just remember UI/UX is not my fortΓ© π But @ullarah OTOH is amazing π€
@lyse Yup I agree with you in hindsight π€£
Just remember UI/UX is not my fortΓ© π But @ullarah OTOH is amazing π€