Yarn

Recent twts in reply to #owkdycq

@prologic@twtxt.net I’m a bit confused about how the two different reply icon buttons behave. The speech bubble with a plus doesn’t supply a post id tag to the edit field at all, while the double speech (conversation?) icon supplies the id tag of the post you’re replying to rather than the original root. Shouldn’t both options supply some kind of id tag to the edit field?

⤋ Read More

@axodys@octobloc.xyz 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 👌

⤋ Read More

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? 🤔

⤋ Read More

@prologic@twtxt.net 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

⤋ Read More

Participate

Login to join in on this yarn.