(#4jk6bba) @nwu1dm That would basically just be a read-only feed. And in that case, yeah it would act a bit like RSS feeds. In fact this is how we do RSS -> Twtxt via

(#4jk6bba) @nwu1dm What's your use-case? 🤔

@prologic @nwu1dm (#4jk6bba) well, a twtxt file only you can modify and nobody else *is* what twtxt is all about.

(#4jk6bba) @marado Yeah to be honest I'm a bit confused by the OP's question here really (sorry @nwu1dm) -- hence why I'm asking what the "use-case" is... -- In case it's not clear, @marado is 100% correct, Twtxt and also Yarn.social (which uses Twtxt and some Extensions) are arguably (IMO) the only truly decentralised social ecosystem that I know of in existence today (bay maybe a few other obscure ones, do we count finger?! 😅)

(#4jk6bba) Even as a user on my multi-user pod (twtxt.net) you are free to do what you want, and even host your feed in multiple places just as @marado does, and I believe takes advantage of the `yarnc sync` tool and api 👌

(#4jk6bba) I think OP is trying to understand how twtxt works. There is a language barrier, but I think that’s what he is asking.

(#4jk6bba) @bender You're probably right. We'll do our best to explain how things work 🤞

(#4jk6bba) @prologic OK, I'm understanding this way of using twtxt. I had followed "prologic then I could read twtxt timeline. When I need to reply to you, I need to @prologic in my txt file and then say something. After that, you would refresh the timeline in your txt file to see my reply. But when I have thousands of friends who follow each other, it will be a disaster.

(#4jk6bba) @nwu1dm How will it be a disaster? 🤔

(#4jk6bba) @prologic Traditionally, I can read timeline line by line. In addition, I can also use some Linux scripts to classify user text. Either way is very painful. I think this is also the reason why yarn "front-end" appears.