Hi there! As a novice (digging from a blog site -> that uses ASS -> that mentions twtxt in its one repo issue) here, I’m a bit confused when using Yarn pod site & Goryon Android APP.

While scrolling twts on Goryon, I’ll 100 percent press conversation btn if one twt interests me, to know the context. However scrolling down, I probably see the same twt in another twt’s conversation. So that means the upper subject just don’t show up when I check the conversation of one twt involved?

Then I turn to Yarn pod site to get some clues. In the main timeline page replies are called Yarn, same as Conversation in Goryon, right? hopping in then I finally know there’s a Root behind this twt. One more click, better than not knowing in Goryon.

Now I have a vague feeling that conversation Forks like a tree. A reply with replies to it becomes a subject that owns #hash.

Is it possible to see the path to the starting root more easily? Maybe a btn to reveal/fold upper subjects, always on first page/screen so no need to click a lot.

@loopsaisei@twtxt.net Hello! 👋 Welcome to my pod (one of many!) 🤗 – Let me try to clear some things up for you…

@loopsaisei@twtxt.net Hmmm after having read your Twt properly… Everything you said is correct. And you’ve clearly pointed out some inconsistencies in the two apps we build and maintain and their respective UI/UX 😢 – I’m sorry for that. We need help in the mobile app area especially 🙏

Anyway, yes essentially a Twt Subject is a formalisation of something we discovered in the Twtxt community at the time, so we formalised that into a Twt Subjec extension.

We then later realised that we could have “threading” if we build a way to address and provide clear lookups for a Twt by using content addressable hashes and so built the Twt Hash extension.

So “conversations’ (what most of us are now calling yarns, plural of yarn, to basically mean to have a conversation in some parts of the world) are really just chains of Twts across one or more feeds with a Twt Subject that matches a “rooted” Twt Hash.

Forking as you’ve no doubt found is where things can get interesting as we’ve had some pretty awesome and insane forks that go many levels deep and span many feeds across many domains, hosts and all around the globe 😅

@loopsaisei@twtxt.net

@prologic@twtxt.net Hey, I had no intent to complain or express frustration. Just really feel excited about what you ppl have created around twtxt and would like to engage to make things better.

This is awesome! 👌 We welcome any and all help we can get! 🙏 We especially need help in the UI/UX side of things, especially on the Mobile App 👌