# 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 14
# self = https://watcher.sour.is/conv/owkdycq
@axodys yeah, I think it is a bug, or more accurately. I think we only half completed the user and to device change there. 🤦♂️
@axodys yeah, I think it is a bug, or more accurately. I think we only half completed the user and to device change there. 🤦♂️
@axodys Well there is nothing to work-around per se, just ignore it for now. But yeah in general we're trying to remove the (#xxxxxxx) hash from the text area when replying and forking because we also shove it into a hidden field anyway, so we know what we're doing generally from the UI/UX and Backend. If you happen to have any Go experience we'd love some help here to finish this work 👌
@axodys Well there is nothing to work-around per se, just ignore it for now. But yeah in general we're trying to remove the (#xxxxxxx) hash from the text area when replying and forking because we also shove it into a hidden field anyway, so we know what we're doing generally from the UI/UX and Backend. If you happen to have any Go experience we'd love some help here to finish this work 👌
To further expand (I just re-explored this myself, I guess I'm used ot it? 🤔)
- In Timeline view, a Reply will show the (#hash) you're replying to.
- In Conversation view, a Reply _will not show the (#hash) you're replying to. It's implied from the Conversation view.
- In Conversation view, a Fork will show the (#hash) of the Twt you're replying to and forking.
I guess there's some subtle differences that we need to take care of in the UI/UX to make things a bit more obvious and clear before we go completely hide them from the interface? 🤔_
To further expand (I just re-explored this myself, I guess I'm used ot it? 🤔)
- In Timeline view, a Reply will show the (#hash) you're replying to.
- In Conversation view, a Reply _will not show the (#hash) you're replying to. It's implied from the Conversation view.
- In Conversation view, a Fork will show the (#hash) of the Twt you're replying to and forking.
I guess there's some subtle differences that we need to take care of in the UI/UX to make things a bit more obvious and clear before we go completely hide them from the interface? 🤔_
@prologic Sounds logic to me and yes and bit more context or mouse over info text would be nice.
@prologic i also find this confusing, both the text and icons for reply and fork so I'm planning to come up with a more clear design where there might also be some visual ques to if this is a reply to the ongoing conversation or a branc/fork/sub-tread