# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 43
# self = https://watcher.sour.is/conv/4jk6bba
@prologic Hello, dear developer, I would like to ask a question: if I have an twtxt.txt document on a website that others can access via internet but cannot modify, is this twtxt.txt document really just acting as a RSS, not even a social network?
@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 https://feeds.twtxt.net/
@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 https://feeds.twtxt.net/
@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 https://feeds.twtxt.net/
@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 https://feeds.twtxt.net/
@prologic @nwu1dm well, a twtxt file only you can modify and nobody else *is* what twtxt is all about.
@prologic @nwu1dm well, a twtxt file only you can modify and nobody else *is* what twtxt is all about.
@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?! π
)
@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?! π
)
@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?! π
)
@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?! π
)
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 π
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 π
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 π
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 π
I think OP is trying to understand how twtxt works. There is a language barrier, but I think thatβs what he is asking.
@bender You're probably right. We'll do our best to explain how things work π€
@bender You're probably right. We'll do our best to explain how things work π€
@bender You're probably right. We'll do our best to explain how things work π€
@bender You're probably right. We'll do our best to explain how things work π€
@prologic OK, I'm understanding this way of using twtxt. I had followed "prologic https://twtxt.net/user/prologic/twtxt.txt", 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.
@nwu1dm How will it be a disaster? π€
@nwu1dm How will it be a disaster? π€
@nwu1dm How will it be a disaster? π€
@nwu1dm How will it be a disaster? π€
@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.
@nwu1dm I _think_ we're talking about different things. If by "disaster" you mean reading your twtxt.txt (feed) file, then yes, you need to have a "decent" client. There are a few around, not just yarnd.
That being said, you can and are free to create your own client however you wish. jenny for example (which you can find on the landing page at https://yarn.social) treats every Twt as an Email. And then you can use something like mutt to navigate your feeds you follow, replies and your "timeline".
Does this make sense? -- I _actually_ thought you were referring to some scalability problem, but I don't think you were, you were talking about the UX? Today the best clients that exist are the ones that are listed on Yarn.social. If someone comes up with another client that's just as compelling (good), we'll be sure to list it there ! π
@nwu1dm I _think_ we're talking about different things. If by "disaster" you mean reading your twtxt.txt (feed) file, then yes, you need to have a "decent" client. There are a few around, not just yarnd.
That being said, you can and are free to create your own client however you wish. jenny for example (which you can find on the landing page at https://yarn.social) treats every Twt as an Email. And then you can use something like mutt to navigate your feeds you follow, replies and your "timeline".
Does this make sense? -- I _actually_ thought you were referring to some scalability problem, but I don't think you were, you were talking about the UX? Today the best clients that exist are the ones that are listed on Yarn.social. If someone comes up with another client that's just as compelling (good), we'll be sure to list it there ! π
@nwu1dm I _think_ we're talking about different things. If by "disaster" you mean reading your twtxt.txt (feed) file, then yes, you need to have a "decent" client. There are a few around, not just yarnd.
That being said, you can and are free to create your own client however you wish. jenny for example (which you can find on the landing page at https://yarn.social) treats every Twt as an Email. And then you can use something like mutt to navigate your feeds you follow, replies and your "timeline".
Does this make sense? -- I _actually_ thought you were referring to some scalability problem, but I don't think you were, you were talking about the UX? Today the best clients that exist are the ones that are listed on Yarn.social. If someone comes up with another client that's just as compelling (good), we'll be sure to list it there ! π
@nwu1dm I _think_ we're talking about different things. If by "disaster" you mean reading your twtxt.txt (feed) file, then yes, you need to have a "decent" client. There are a few around, not just yarnd.
That being said, you can and are free to create your own client however you wish. jenny for example (which you can find on the landing page at https://yarn.social) treats every Twt as an Email. And then you can use something like mutt to navigate your feeds you follow, replies and your "timeline".
Does this make sense? -- I _actually_ thought you were referring to some scalability problem, but I don't think you were, you were talking about the UX? Today the best clients that exist are the ones that are listed on Yarn.social. If someone comes up with another client that's just as compelling (good), we'll be sure to list it there ! π
@prologic Thank you for your answer. I really like the feature of twtxt, which is complete control of my social data (that is, txt). I don't think UI/UX is the main problem. CLI clients is the best UX, simple and fast. And what is the direction of development in the future? In the context of a complete P2P network, how to find other users, that is to say, to play the function of social networks? For example, in the case of a single user instance of Mastondon, other users can be seen in the global interface.
@nwu1dm In order for you to find others to follow and they to follow you, I'd recommend using the search.twtxt.net search engine. As you've already found your way to my pod (a multi-user client with a Web App, API and Mobile App) you're already being followed by a few in the small but growing community π
-- Find folks is well hard in a true "decentralised" ecosystem. But we're here π
The best way to build your "network" is by interesting with others, you will find over time your network of followers will grow and change over time and what you follow will also π
feeds.twtxt.net is also a good course of "external feeds" (many of which are 1-way mirrors of Mastodon users or RSS feeds of websites, news, etc).
@nwu1dm In order for you to find others to follow and they to follow you, I'd recommend using the search.twtxt.net search engine. As you've already found your way to my pod (a multi-user client with a Web App, API and Mobile App) you're already being followed by a few in the small but growing community π
-- Find folks is well hard in a true "decentralised" ecosystem. But we're here π
The best way to build your "network" is by interesting with others, you will find over time your network of followers will grow and change over time and what you follow will also π
feeds.twtxt.net is also a good course of "external feeds" (many of which are 1-way mirrors of Mastodon users or RSS feeds of websites, news, etc).
@nwu1dm In order for you to find others to follow and they to follow you, I'd recommend using the search.twtxt.net search engine. As you've already found your way to my pod (a multi-user client with a Web App, API and Mobile App) you're already being followed by a few in the small but growing community π
-- Find folks is well hard in a true "decentralised" ecosystem. But we're here π
The best way to build your "network" is by interesting with others, you will find over time your network of followers will grow and change over time and what you follow will also π
feeds.twtxt.net is also a good course of "external feeds" (many of which are 1-way mirrors of Mastodon users or RSS feeds of websites, news, etc).
@nwu1dm In order for you to find others to follow and they to follow you, I'd recommend using the search.twtxt.net search engine. As you've already found your way to my pod (a multi-user client with a Web App, API and Mobile App) you're already being followed by a few in the small but growing community π
-- Find folks is well hard in a true "decentralised" ecosystem. But we're here π
The best way to build your "network" is by interesting with others, you will find over time your network of followers will grow and change over time and what you follow will also π
feeds.twtxt.net is also a good course of "external feeds" (many of which are 1-way mirrors of Mastodon users or RSS feeds of websites, news, etc).
@nwu1dm Also if you chose to host your own feed (you're welcome to keep using my pod, it's there for use by all!), one thing to keep in mind as you either pick a client, figure out how to host your feed, etc is the HTTP User-Agent header that many clients will use to tell you they have fetched your feed. This is an important discovery aspect of Twtxt and we extended this as well to support multi-user pods like yarnd.
See: https://dev.twtxt.net/doc/useragentextension.html
At a bare minimum, you basically need to parse your web server access logs. There is a tool that @lyse wrote called useragent that helps with this.
@nwu1dm Also if you chose to host your own feed (you're welcome to keep using my pod, it's there for use by all!), one thing to keep in mind as you either pick a client, figure out how to host your feed, etc is the HTTP User-Agent header that many clients will use to tell you they have fetched your feed. This is an important discovery aspect of Twtxt and we extended this as well to support multi-user pods like yarnd.
See: https://dev.twtxt.net/doc/useragentextension.html
At a bare minimum, you basically need to parse your web server access logs. There is a tool that @lyse wrote called useragent that helps with this.
@nwu1dm Also if you chose to host your own feed (you're welcome to keep using my pod, it's there for use by all!), one thing to keep in mind as you either pick a client, figure out how to host your feed, etc is the HTTP User-Agent header that many clients will use to tell you they have fetched your feed. This is an important discovery aspect of Twtxt and we extended this as well to support multi-user pods like yarnd.
See: https://dev.twtxt.net/doc/useragentextension.html
At a bare minimum, you basically need to parse your web server access logs. There is a tool that @lyse wrote called useragent that helps with this.
@nwu1dm Also if you chose to host your own feed (you're welcome to keep using my pod, it's there for use by all!), one thing to keep in mind as you either pick a client, figure out how to host your feed, etc is the HTTP User-Agent header that many clients will use to tell you they have fetched your feed. This is an important discovery aspect of Twtxt and we extended this as well to support multi-user pods like yarnd.
See: https://dev.twtxt.net/doc/useragentextension.html
At a bare minimum, you basically need to parse your web server access logs. There is a tool that @lyse wrote called useragent that helps with this.