yarnc sync command-line tool for this reason 👌 (_something I always wanted to have, for this very reason, for backups, etc_). @marado myself and a few others also use this 👌 Usage is simple:
$ yarnc -u https://twtxt.net login
$ yarnc sync twtxt.txt
yarnc sync command-line tool for this reason 👌 (_something I always wanted to have, for this very reason, for backups, etc_). @marado myself and a few others also use this 👌 Usage is simple:
$ yarnc -u https://twtxt.net login
$ yarnc sync twtxt.txt
yarnc sync command-line tool for this reason 👌 (_something I always wanted to have, for this very reason, for backups, etc_). @marado myself and a few others also use this 👌 Usage is simple:
$ yarnc -u https://twtxt.net login
$ yarnc sync twtxt.txt
yarnc sync command-line tool for this reason 👌 (_something I always wanted to have, for this very reason, for backups, etc_). @marado myself and a few others also use this 👌 Usage is simple:
$ yarnc -u https://twtxt.net login
$ yarnc sync twtxt.txt
https://meet.mills.io/call/Yarn.social
https://meet.mills.io/call/Yarn.social
https://meet.mills.io/call/Yarn.social
https://meet.mills.io/call/Yarn.social
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.
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.
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.
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.
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).
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).
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).
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).
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 ! 👌
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 ! 👌
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 ! 👌
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 ! 👌
