[](https://twtxt.net/media/viu8LaUJpnfH4NwxuQySbR)
[](https://twtxt.net/media/viu8LaUJpnfH4NwxuQySbR)
\n\t\tTwtxt.net
\n\t\ta yarn.social\n\t
\n\t<a href="https://twtxt.net/">\n\t\t<img src="./yarn-logo.png" width="70" height="70"><br>\n\t\t<b>Twtxt.net</b><br>\n\t\t<small>a yarn.social</small>\n\t</a>And the PNG is not my original work. @prologic found it and shared it here some time ago.
https://twtxt.net/">
Twtxt.net
a yarn.social
\n\t\tTwtxt.net
\n\t\ta yarn.social\n\t
You can "try" it out at http://darch.dk/yarn-hack/YARN_Conversation_Nested.html
--max-cache-ttl and --max-cache-items limits meaning that you can't "arbitrarily" show nested or even flat conversations as far back as you want. Replies/Posts eventually fall off active caches into the archive. This is why content addressing / hashes are so important as it is the only way to bring up the matching root of a conversation -- even if that conversation is long gone, it could get "re-sparked"...
--max-cache-ttl and --max-cache-items limits meaning that you can't "arbitrarily" show nested or even flat conversations as far back as you want. Replies/Posts eventually fall off active caches into the archive. This is why content addressing / hashes are so important as it is the only way to bring up the matching root of a conversation -- even if that conversation is long gone, it could get "re-sparked"...
--max-cache-ttl and --max-cache-items limits meaning that you can't "arbitrarily" show nested or even flat conversations as far back as you want. Replies/Posts eventually fall off active caches into the archive. This is why content addressing / hashes are so important as it is the only way to bring up the matching root of a conversation -- even if that conversation is long gone, it could get "re-sparked"...