# 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 61083
# self = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=38191
# next = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=38291
# prev = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=38091
@slashdot Oh this is really cool 👌 Too bad I'm not at my Desktop right now 🤔 Will check out later (doesn't work on mobile)
@slashdot Oh this is really cool 👌 Too bad I'm not at my Desktop right now 🤔 Will check out later (doesn't work on mobile)
@slashdot Oh this is really cool 👌 Too bad I'm not at my Desktop right now 🤔 Will check out later (doesn't work on mobile)
@slashdot Oh this is really cool 👌 Too bad I'm not at my Desktop right now 🤔 Will check out later (doesn't work on mobile)
@eaplmx What will happen now _I think_ is all your Twts will change their Hashes maybe 😅 Changing your feed's "Hashing URL" is not something you _really_ want to do too often I think 🤣 But let's see...
@eaplmx What will happen now _I think_ is all your Twts will change their Hashes maybe 😅 Changing your feed's "Hashing URL" is not something you _really_ want to do too often I think 🤣 But let's see...
@eaplmx What will happen now _I think_ is all your Twts will change their Hashes maybe 😅 Changing your feed's "Hashing URL" is not something you _really_ want to do too often I think 🤣 But let's see...
@eaplmx What will happen now _I think_ is all your Twts will change their Hashes maybe 😅 Changing your feed's "Hashing URL" is not something you _really_ want to do too often I think 🤣 But let's see...
@rsdoiel Don't worry, I've used IRC for over 25years and counting now 😅 Its still the best open communications medium around really 🤣 Just head over to Yarn.social#collaboration and follow the links. I _tried_ to make it easy by linking the Libera Web Chat client 👌
@rsdoiel Don't worry, I've used IRC for over 25years and counting now 😅 Its still the best open communications medium around really 🤣 Just head over to Yarn.social#collaboration and follow the links. I _tried_ to make it easy by linking the Libera Web Chat client 👌
@rsdoiel Don't worry, I've used IRC for over 25years and counting now 😅 Its still the best open communications medium around really 🤣 Just head over to Yarn.social#collaboration and follow the links. I _tried_ to make it easy by linking the Libera Web Chat client 👌
@rsdoiel Don't worry, I've used IRC for over 25years and counting now 😅 Its still the best open communications medium around really 🤣 Just head over to Yarn.social#collaboration and follow the links. I _tried_ to make it easy by linking the Libera Web Chat client 👌
@eaplmx I'm _actually_ not sure if that'll work. Can you test it and let us know, then submit a PR to amend the spec if it does? 😅 It just affects the Twt Hash(es), and we take the first one as the "Hashing URI".
@eaplmx I'm _actually_ not sure if that'll work. Can you test it and let us know, then submit a PR to amend the spec if it does? 😅 It just affects the Twt Hash(es), and we take the first one as the "Hashing URI".
@eaplmx I'm _actually_ not sure if that'll work. Can you test it and let us know, then submit a PR to amend the spec if it does? 😅 It just affects the Twt Hash(es), and we take the first one as the "Hashing URI".
@eaplmx I'm _actually_ not sure if that'll work. Can you test it and let us know, then submit a PR to amend the spec if it does? 😅 It just affects the Twt Hash(es), and we take the first one as the "Hashing URI".
The AT Protocol – notizBlog -- Actually, can someone that speaks/rads German natively please translate this blog post for the rest of us that don't understand German 😅 Thank you! 🙏
The AT Protocol – notizBlog -- Actually, can someone that speaks/rads German natively please translate this blog post for the rest of us that don't understand German 😅 Thank you! 🙏
The AT Protocol – notizBlog -- Actually, can someone that speaks/rads German natively please translate this blog post for the rest of us that don't understand German 😅 Thank you! 🙏
The AT Protocol – notizBlog -- Actually, can someone that speaks/rads German natively please translate this blog post for the rest of us that don't understand German 😅 Thank you! 🙏
So I discovered (get it? 🤣) that there is a Twtxt feed out there that is otherwise identical but are served as two different feeds with a different # url = field for some strange reason, even though the content is literally identical 😅
You can see what I mean by poking around these two twts: #jbsw56q and #bekvqja
Basically if you're going to serve your feed over different protocols or a different URL on the same protocol/scheme, you _really_ should use the same # url = (Hashing URI as per the spec) 🤗
So I discovered (get it? 🤣) that there is a Twtxt feed out there that is otherwise identical but are served as two different feeds with a different # url = field for some strange reason, even though the content is literally identical 😅
You can see what I mean by poking around these two twts: #jbsw56q and #bekvqja
Basically if you're going to serve your feed over different protocols or a different URL on the same protocol/scheme, you _really_ should use the same # url = (Hashing URI as per the spec) 🤗
So I discovered (get it? 🤣) that there is a Twtxt feed out there that is otherwise identical but are served as two different feeds with a different # url = field for some strange reason, even though the content is literally identical 😅
You can see what I mean by poking around these two twts: #jbsw56q and #bekvqja
Basically if you're going to serve your feed over different protocols or a different URL on the same protocol/scheme, you _really_ should use the same # url = (Hashing URI as per the spec) 🤗
So I discovered (get it? 🤣) that there is a Twtxt feed out there that is otherwise identical but are served as two different feeds with a different # url = field for some strange reason, even though the content is literally identical 😅
You can see what I mean by poking around these two twts: #jbsw56q and #bekvqja
Basically if you're going to serve your feed over different protocols or a different URL on the same protocol/scheme, you _really_ should use the same # url = (Hashing URI as per the spec) 🤗
@lyse Actually you are _somewhat_ right about and I empathise with your point of view. As much as I believe in what we've built here, I also recognise its not for everyone. The "masses" (as we call 'em) are (as you say) truly lost. It is next to impossible to pry them away from all this centralised privacy eroding garbage as they almost just "don't get it".
I've found myself saying in conversations with my wife and friends and family, with the increase in data branches, that we will only start to question the way things are and where our data is stored and with whom, only (and only if) it started to hurt a lot more than it already is.
With the recent branches of Optus and Medibank here in Australia, Australians are starting to feel the pain of identity fraud, theft, increased difficulty in dealing with institutions (like taking your own money out of a bank!) and so on...
@lyse Actually you are _somewhat_ right about and I empathise with your point of view. As much as I believe in what we've built here, I also recognise its not for everyone. The "masses" (as we call 'em) are (as you say) truly lost. It is next to impossible to pry them away from all this centralised privacy eroding garbage as they almost just "don't get it".
I've found myself saying in conversations with my wife and friends and family, with the increase in data branches, that we will only start to question the way things are and where our data is stored and with whom, only (and only if) it started to hurt a lot more than it already is.
With the recent branches of Optus and Medibank here in Australia, Australians are starting to feel the pain of identity fraud, theft, increased difficulty in dealing with institutions (like taking your own money out of a bank!) and so on...
@lyse Actually you are _somewhat_ right about and I empathise with your point of view. As much as I believe in what we've built here, I also recognise its not for everyone. The "masses" (as we call 'em) are (as you say) truly lost. It is next to impossible to pry them away from all this centralised privacy eroding garbage as they almost just "don't get it".
I've found myself saying in conversations with my wife and friends and family, with the increase in data branches, that we will only start to question the way things are and where our data is stored and with whom, only (and only if) it started to hurt a lot more than it already is.
With the recent branches of Optus and Medibank here in Australia, Australians are starting to feel the pain of identity fraud, theft, increased difficulty in dealing with institutions (like taking your own money out of a bank!) and so on...
@lyse Actually you are _somewhat_ right about and I empathise with your point of view. As much as I believe in what we've built here, I also recognise its not for everyone. The "masses" (as we call 'em) are (as you say) truly lost. It is next to impossible to pry them away from all this centralised privacy eroding garbage as they almost just "don't get it".
I've found myself saying in conversations with my wife and friends and family, with the increase in data branches, that we will only start to question the way things are and where our data is stored and with whom, only (and only if) it started to hurt a lot more than it already is.
With the recent branches of Optus and Medibank here in Australia, Australians are starting to feel the pain of identity fraud, theft, increased difficulty in dealing with institutions (like taking your own money out of a bank!) and so on...
@eaplmx Haha 🤣 But it's so true right 😅 it's nothing to do with "tech", it is everywhere. As we build more and more complicated "things" we lose our understanding of how anything _actually_ works 😅 -- We (as a human race) would be so royally screwed if the Sun was to hit us with a south facing solar flare, or an asteroid were to strike the earth again 🤣
@eaplmx Haha 🤣 But it's so true right 😅 it's nothing to do with "tech", it is everywhere. As we build more and more complicated "things" we lose our understanding of how anything _actually_ works 😅 -- We (as a human race) would be so royally screwed if the Sun was to hit us with a south facing solar flare, or an asteroid were to strike the earth again 🤣
@eaplmx Haha 🤣 But it's so true right 😅 it's nothing to do with "tech", it is everywhere. As we build more and more complicated "things" we lose our understanding of how anything _actually_ works 😅 -- We (as a human race) would be so royally screwed if the Sun was to hit us with a south facing solar flare, or an asteroid were to strike the earth again 🤣
@eaplmx Haha 🤣 But it's so true right 😅 it's nothing to do with "tech", it is everywhere. As we build more and more complicated "things" we lose our understanding of how anything _actually_ works 😅 -- We (as a human race) would be so royally screwed if the Sun was to hit us with a south facing solar flare, or an asteroid were to strike the earth again 🤣
@slashdot Good 👌 Facial Recognition absolutely should be banned 🤬
@slashdot Good 👌 Facial Recognition absolutely should be banned 🤬
@slashdot Good 👌 Facial Recognition absolutely should be banned 🤬
@slashdot Good 👌 Facial Recognition absolutely should be banned 🤬
I _think_ sadly we saw a bunch of spam/bot accounts created on various pods throughout the network 😢 besides up and coming "invite system" we plan to build, not sure there is much more we can do 🤣 Oh well 🤷♂️
I _think_ sadly we saw a bunch of spam/bot accounts created on various pods throughout the network 😢 besides up and coming "invite system" we plan to build, not sure there is much more we can do 🤣 Oh well 🤷♂️
I _think_ sadly we saw a bunch of spam/bot accounts created on various pods throughout the network 😢 besides up and coming "invite system" we plan to build, not sure there is much more we can do 🤣 Oh well 🤷♂️
I _think_ sadly we saw a bunch of spam/bot accounts created on various pods throughout the network 😢 besides up and coming "invite system" we plan to build, not sure there is much more we can do 🤣 Oh well 🤷♂️
@abucci Hah 😅 Never, I know you're a fan of Scala 🤣 But cool little project l 👌
@abucci Hah 😅 Never, I know you're a fan of Scala 🤣 But cool little project l 👌
@abucci Hah 😅 Never, I know you're a fan of Scala 🤣 But cool little project l 👌
@abucci Hah 😅 Never, I know you're a fan of Scala 🤣 But cool little project l 👌
It would be pretty easy to take the same code and write a CLI that generates static HTML like I'm doing with twtxt2html 👌
It would be pretty easy to take the same code and write a CLI that generates static HTML like I'm doing with twtxt2html 👌
It would be pretty easy to take the same code and write a CLI that generates static HTML like I'm doing with twtxt2html 👌
It would be pretty easy to take the same code and write a CLI that generates static HTML like I'm doing with twtxt2html 👌
@tel Hey! 👋 Nice to still see you around 🙇♂️
@tel Hey! 👋 Nice to still see you around 🙇♂️
@tel Hey! 👋 Nice to still see you around 🙇♂️
@tel Hey! 👋 Nice to still see you around 🙇♂️
@akoizumi I _think_ this is true of just about any non-trivial "tech" these days, for example cars.
@akoizumi I _think_ this is true of just about any non-trivial "tech" these days, for example cars.
@akoizumi I _think_ this is true of just about any non-trivial "tech" these days, for example cars.
@akoizumi I _think_ this is true of just about any non-trivial "tech" these days, for example cars.
@algorifer I'm working on an integrated full text and keyword search engine directly into yarnd which will replace the current (crappy) tag-only search. This will allow us to index an archive (optional, as some archives are rather large) and give us full search capability and do interesting things like pull up old conversations (yarns) from the index (but explicitly as we'll likely continue to use the cache model with limited size and ttl for good reasons).
@algorifer I'm working on an integrated full text and keyword search engine directly into yarnd which will replace the current (crappy) tag-only search. This will allow us to index an archive (optional, as some archives are rather large) and give us full search capability and do interesting things like pull up old conversations (yarns) from the index (but explicitly as we'll likely continue to use the cache model with limited size and ttl for good reasons).
@algorifer I'm working on an integrated full text and keyword search engine directly into yarnd which will replace the current (crappy) tag-only search. This will allow us to index an archive (optional, as some archives are rather large) and give us full search capability and do interesting things like pull up old conversations (yarns) from the index (but explicitly as we'll likely continue to use the cache model with limited size and ttl for good reasons).
@algorifer I'm working on an integrated full text and keyword search engine directly into yarnd which will replace the current (crappy) tag-only search. This will allow us to index an archive (optional, as some archives are rather large) and give us full search capability and do interesting things like pull up old conversations (yarns) from the index (but explicitly as we'll likely continue to use the cache model with limited size and ttl for good reasons).
@carsten Hmmm maybe give me some days to think about how to do this properly 🤗
@carsten Hmmm maybe give me some days to think about how to do this properly 🤗
@carsten Hmmm maybe give me some days to think about how to do this properly 🤗
@carsten Hmmm maybe give me some days to think about how to do this properly 🤗
@algorifer Sure so archived Twts are not indexed at the moment....
@algorifer Sure so archived Twts are not indexed at the moment....
@algorifer Sure so archived Twts are not indexed at the moment....
@algorifer Sure so archived Twts are not indexed at the moment....
@rsdoiel Are you able to join our IRC channel so we can talk through this? 🤔