# 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 41
# self = https://watcher.sour.is/conv/tsvhqdq
@gmj Yup it is! I loved it so much I built this web app and backend for what is essentially a multi-user client with API and we have a team of 5 that also built a Mobile App π LMK if youβre interest in learning more π
@gmj Yup it is! I loved it so much I built this web app and backend for what is essentially a multi-user client with API and we have a team of 5 that also built a Mobile App π LMK if youβre interest in learning more π
@gmj Yup it is! I loved it so much I built this web app and backend for what is essentially a multi-user client with API and we have a team of 5 that also built a Mobile App π LMK if youβre interest in learning more π
@prologic For now I think I will stay with primitave tools.
@prologic twtxt is so simple one could read with netcat, cat and tail. I like that.
@prologic also the lack of a login and complete decntralization is a big win.
@prologic and the fact that I just used /bin/ed to fix spelling before pushing :-)
These are indeed some of the nice _aspects_ of the whole Twtxt idea... However bear in mind that folks like you and me are "technically minded" and we are (_by the looks_) UNIX buffs π That is to say, (_as I said_) I loved the whole idea so much I wanted to bring it to everyone! Yes there are lots of clients of all kinds of different capabilities. I intend to blog about the non-breaking extensions we made to Twtxt.net to enhance the UX (_User eXperience_). Remember though that it is still decentralised π
These are indeed some of the nice _aspects_ of the whole Twtxt idea... However bear in mind that folks like you and me are "technically minded" and we are (_by the looks_) UNIX buffs π That is to say, (_as I said_) I loved the whole idea so much I wanted to bring it to everyone! Yes there are lots of clients of all kinds of different capabilities. I intend to blog about the non-breaking extensions we made to Twtxt.net to enhance the UX (_User eXperience_). Remember though that it is still decentralised π
These are indeed some of the nice _aspects_ of the whole Twtxt idea... However bear in mind that folks like you and me are "technically minded" and we are (_by the looks_) UNIX buffs π That is to say, (_as I said_) I loved the whole idea so much I wanted to bring it to everyone! Yes there are lots of clients of all kinds of different capabilities. I intend to blog about the non-breaking extensions we made to Twtxt.net to enhance the UX (_User eXperience_). Remember though that it is still decentralised π
@prologic I will probably stick with command line client just to make sure it keeps working
one problme I'm seeing already is that the "micro" part is loosing out. Things are routinely getting longer than 140 characters
Re "140 chars", pods are configurable. I configure this pod (twtxt.net) to be 288. It also supports both short and long forms (Twts and Blogs). It does both. You can read some of my blog posts at https://twtxt.net/blogs/prologic for example.
Re "140 chars", pods are configurable. I configure this pod (twtxt.net) to be 288. It also supports both short and long forms (Twts and Blogs). It does both. You can read some of my blog posts at https://twtxt.net/blogs/prologic for example.
Re "140 chars", pods are configurable. I configure this pod (twtxt.net) to be 288. It also supports both short and long forms (Twts and Blogs). It does both. You can read some of my blog posts at https://twtxt.net/blogs/prologic for example.
Re "140 chars", pods are configurable. I configure this pod (twtxt.net) to be 288. It also supports both short and long forms (Twts and Blogs). It does both. You can read some of my blog posts at https://twtxt.net/blogs/prologic for example.
Re "140 chars", pods are configurable. I configure this pod (twtxt.net) to be 288. It also supports both short and long forms (Twts and Blogs). It does both. You can read some of my blog posts at https://twtxt.net/blogs/prologic for example.
Re "140 chars", pods are configurable. I configure this pod (twtxt.net) to be 288. It also supports both short and long forms (Twts and Blogs). It does both. You can read some of my blog posts at https://twtxt.net/blogs/prologic for example.
Re "External September", if this _were_ to happen (_hopefully not too soon!_) this would be awesome, I would celebrate some level of success π That being said, I get the overwhelming problems that can incur. Fortunately as you know Twtxt is designed to be decentralised, so are Twt.social pods like this one (twtxt.net), it is just one of quite a few now (_10 to that we know of so far, 1 of which has nothing to do with us_).
Re "External September", if this _were_ to happen (_hopefully not too soon!_) this would be awesome, I would celebrate some level of success π That being said, I get the overwhelming problems that can incur. Fortunately as you know Twtxt is designed to be decentralised, so are Twt.social pods like this one (twtxt.net), it is just one of quite a few now (_10 to that we know of so far, 1 of which has nothing to do with us_).
Re "External September", if this _were_ to happen (_hopefully not too soon!_) this would be awesome, I would celebrate some level of success π That being said, I get the overwhelming problems that can incur. Fortunately as you know Twtxt is designed to be decentralised, so are Twt.social pods like this one (twtxt.net), it is just one of quite a few now (_10 to that we know of so far, 1 of which has nothing to do with us_).
Re "Conversations". Please read my blog post Making Twtxt Better for an explanation of this. Basically we hash each Twt with a Blake2B hash and use that as the "Subject". The Twt must exist to be replied to form a conversation, you can't just make up a hash. The nice thing however is that this works across pods too. A conversation that starts on one pod and has participants in another pod, the twts get mirrorred there with the same hashes .
Re "Conversations". Please read my blog post Making Twtxt Better for an explanation of this. Basically we hash each Twt with a Blake2B hash and use that as the "Subject". The Twt must exist to be replied to form a conversation, you can't just make up a hash. The nice thing however is that this works across pods too. A conversation that starts on one pod and has participants in another pod, the twts get mirrorred there with the same hashes .
Re "Conversations". Please read my blog post Making Twtxt Better for an explanation of this. Basically we hash each Twt with a Blake2B hash and use that as the "Subject". The Twt must exist to be replied to form a conversation, you can't just make up a hash. The nice thing however is that this works across pods too. A conversation that starts on one pod and has participants in another pod, the twts get mirrorred there with the same hashes .
yes. I read that. Nice post. Brave browser at least has trouble with formatting. The regexp got lost when renederd. Eww (emacs text browser) doees just fine with it :-)
What flavor or regexp? I tried here https://regexr.com/ with both PCRE and JavaScript and neither seems quite right. I'm relatively good with regexps, but they tend to be write-only :-/
in the original twtxt your URL is your identity. No need for anyone outside your control to do account managment. One reason I'll likely be sticking with command line. But, great work
@gmj Re "Your identity is your Twt URI", to be honest I'm not 100% convinced of this per se. What if you decide to change where/how you host your twtxt.txt feed? I did! Many others have too. See the last line of my old feed at https://prologic.github.io/twtxt.txt π In any case it really doesn't matter tbh, since I have done so far and continue to plan to do so, keep backwards compatibility with the Twtxt spec/format and this means _any_ client _should_ work.
@gmj Re "Your identity is your Twt URI", to be honest I'm not 100% convinced of this per se. What if you decide to change where/how you host your twtxt.txt feed? I did! Many others have too. See the last line of my old feed at https://prologic.github.io/twtxt.txt π In any case it really doesn't matter tbh, since I have done so far and continue to plan to do so, keep backwards compatibility with the Twtxt spec/format and this means _any_ client _should_ work.
@gmj Re "Your identity is your Twt URI", to be honest I'm not 100% convinced of this per se. What if you decide to change where/how you host your twtxt.txt feed? I did! Many others have too. See the last line of my old feed at https://prologic.github.io/twtxt.txt π In any case it really doesn't matter tbh, since I have done so far and continue to plan to do so, keep backwards compatibility with the Twtxt spec/format and this means _any_ client _should_ work.
@gmj Oh _should_ have mentioned this before, but Twtxt.net (_and other Twt.social pods_) also have an API, this means we can do interesting things like for example have a mobile app. We have one for Android in the Play Store which you can find/install here if you're on an Android device.
@gmj Oh _should_ have mentioned this before, but Twtxt.net (_and other Twt.social pods_) also have an API, this means we can do interesting things like for example have a mobile app. We have one for Android in the Play Store which you can find/install here if you're on an Android device.
@gmj Oh _should_ have mentioned this before, but Twtxt.net (_and other Twt.social pods_) also have an API, this means we can do interesting things like for example have a mobile app. We have one for Android in the Play Store which you can find/install here if you're on an Android device.
@gmj Btw... You _should_ read my Hacktober Blog Post, if you're any good with programming and/or Go we could use the help! That post also outlines some interesting things we want to do, for example Git integration so that one could primarily keep their twtxt.txt file in a Git repo somewhere, but still have say a twtxt.net account and use the Web App, API and Mobile apps as well as the command-line when they're at a terminal with access t their Git repo, etc...
@gmj Btw... You _should_ read my Hacktober Blog Post, if you're any good with programming and/or Go we could use the help! That post also outlines some interesting things we want to do, for example Git integration so that one could primarily keep their twtxt.txt file in a Git repo somewhere, but still have say a twtxt.net account and use the Web App, API and Mobile apps as well as the command-line when they're at a terminal with access t their Git repo, etc...
@gmj Btw... You _should_ read my Hacktober Blog Post, if you're any good with programming and/or Go we could use the help! That post also outlines some interesting things we want to do, for example Git integration so that one could primarily keep their twtxt.txt file in a Git repo somewhere, but still have say a twtxt.net account and use the Web App, API and Mobile apps as well as the command-line when they're at a terminal with access t their Git repo, etc...