# Twtxt is an open, distributed microblogging platform that
# uses human-readable text files, common transport protocols,
# and free software.
#
# Learn more about twtxt at  https://github.com/buckket/twtxt
#
# This is hosted by a Yarn.social pod twtxt.net running yarnd 0.0.0@HEAD  go1.22.2
# Learn more about Yarn.social at https://yarn.social
#
# nick        = loopsaisei
# url         = https://twtxt.net/user/loopsaisei/twtxt.txt
# avatar      = https://twtxt.net/user/loopsaisei/avatar#p3m6yyu6z5d2puonornj35gypach3rh3i4gmhjtdbbun4wizmeaa
# description = 
#
# following   = 4
##
# follow = loopsaisei https://twtxt.net/user/loopsaisei/twtxt.txt
# follow = news https://twtxt.net/user/news/twtxt.txt
# follow = prologic https://twtxt.net/user/prologic/twtxt.txt
# follow = support https://twtxt.net/user/support/twtxt.txt

2023-01-05T13:48:45Z	Hi there! As a novice (digging from a blog site -> that uses ASS -> that mentions twtxt in its [one repo issue](https://github.com/dzwdz/ass/issues/1)) 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 __Fork__s 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.
2023-01-06T16:23:29Z	@<prologic https://twtxt.net/user/prologic/twtxt.txt> (#qsjny5a) 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.

Recording the resistance in my process of "trying to figure out what you guys are talking about" / providing an outsider's view (not like the ppl in conversations who know the context well) may do help in some ways, I guess. And it's my turn to say sorry for my limited technical skills 🙈.

Thanks for your clarification and I'll take time to learn more about existing extensions.