# 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=40891
# next = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=40991
# prev = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=40791
prologic
twtxt.net
View Thread
@justamoment @eaplmx You _might_. be bit right here... But you have to understand the history of how this happened in the first place... When I first came across Twtxt I t started out by building a "web" client. I called it at _that_ time github.com/prologic/twtxt (I no longer use Github) because "naming is hard". -- The project quickly picked up some interest and traction and so things kind of stuck for a while (naming wise), I'd already by this stage purchased the domain twtxt.net and hosted my "web" client by then....

Anyway... playing devil's advocate here this is also a double-edge sword, on one hand its helped promote Twtxt itself, on the other yeah, things have gotten a it confusing (but less so as we continue to improve documentation and communications).
prologic
twtxt.net
View Thread
@justamoment @eaplmx You _might_. be bit right here... But you have to understand the history of how this happened in the first place... When I first came across Twtxt I t started out by building a "web" client. I called it at _that_ time github.com/prologic/twtxt (I no longer use Github) because "naming is hard". -- The project quickly picked up some interest and traction and so things kind of stuck for a while (naming wise), I'd already by this stage purchased the domain twtxt.net and hosted my "web" client by then....

Anyway... playing devil's advocate here this is also a double-edge sword, on one hand its helped promote Twtxt itself, on the other yeah, things have gotten a it confusing (but less so as we continue to improve documentation and communications).
prologic
twtxt.net
View Thread
@justamoment @eaplmx You _might_. be bit right here... But you have to understand the history of how this happened in the first place... When I first came across Twtxt I t started out by building a "web" client. I called it at _that_ time github.com/prologic/twtxt (I no longer use Github) because "naming is hard". -- The project quickly picked up some interest and traction and so things kind of stuck for a while (naming wise), I'd already by this stage purchased the domain twtxt.net and hosted my "web" client by then....

Anyway... playing devil's advocate here this is also a double-edge sword, on one hand its helped promote Twtxt itself, on the other yeah, things have gotten a it confusing (but less so as we continue to improve documentation and communications).
prologic
twtxt.net
View Thread
B
prologic
twtxt.net
View Thread
B
prologic
twtxt.net
View Thread
B
prologic
twtxt.net
View Thread
B
prologic
twtxt.net
View Thread
@win0err If you're referring to the original twtxt, then yes, it left a lot of things out and quite a bit of it is ambitious 😢 -- It _might_ be worthwhile one day either:

1. rewriting the spec (which @mckinley has done a nice job of, but I still want to host that at https://dev.twtxt.net in Markdown 😅)
2. start writing "client recommendations" (like what we did with extensions)
prologic
twtxt.net
View Thread
@win0err If you're referring to the original twtxt, then yes, it left a lot of things out and quite a bit of it is ambitious 😢 -- It _might_ be worthwhile one day either:

1. rewriting the spec (which @mckinley has done a nice job of, but I still want to host that at https://dev.twtxt.net in Markdown 😅)
2. start writing "client recommendations" (like what we did with extensions)
prologic
twtxt.net
View Thread
@win0err If you're referring to the original twtxt, then yes, it left a lot of things out and quite a bit of it is ambitious 😢 -- It _might_ be worthwhile one day either:

1. rewriting the spec (which @mckinley has done a nice job of, but I still want to host that at https://dev.twtxt.net in Markdown 😅)
2. start writing "client recommendations" (like what we did with extensions)
prologic
twtxt.net
View Thread
@win0err If you're referring to the original twtxt, then yes, it left a lot of things out and quite a bit of it is ambitious 😢 -- It _might_ be worthwhile one day either:

1. rewriting the spec (which @mckinley has done a nice job of, but I still want to host that at https://dev.twtxt.net in Markdown 😅)
2. start writing "client recommendations" (like what we did with extensions)
prologic
twtxt.net
View Thread
@win0err Maybe you can help us with that part of the spec? 🤔 It was added to honestly squelch really only one grumpy Twtxt user at the time, so we did it 😅 But really a well behaving client will periodically fetch a feed but respect HTTP headers like Last-Modified and so the hit on a web server is minimal at best. -- And as you just found, _many_ clients don't yet actually even respect this field, only really yarnd does (I believe). -- And if you set it too big well then maybe nobody sees your post for a while 😅

I would offer documentation on our use of the WebSub protocol, however this is not possible to implement for feed authors in _all_ cases, especially on multi-user hostrs like many of the tilde(s) I think... -- Is this something we _should_ document as an optional client feature? (I feel most feed authors probably wouldn't care all that much)
prologic
twtxt.net
View Thread
@win0err Maybe you can help us with that part of the spec? 🤔 It was added to honestly squelch really only one grumpy Twtxt user at the time, so we did it 😅 But really a well behaving client will periodically fetch a feed but respect HTTP headers like Last-Modified and so the hit on a web server is minimal at best. -- And as you just found, _many_ clients don't yet actually even respect this field, only really yarnd does (I believe). -- And if you set it too big well then maybe nobody sees your post for a while 😅

I would offer documentation on our use of the WebSub protocol, however this is not possible to implement for feed authors in _all_ cases, especially on multi-user hostrs like many of the tilde(s) I think... -- Is this something we _should_ document as an optional client feature? (I feel most feed authors probably wouldn't care all that much)
prologic
twtxt.net
View Thread
@win0err Maybe you can help us with that part of the spec? 🤔 It was added to honestly squelch really only one grumpy Twtxt user at the time, so we did it 😅 But really a well behaving client will periodically fetch a feed but respect HTTP headers like Last-Modified and so the hit on a web server is minimal at best. -- And as you just found, _many_ clients don't yet actually even respect this field, only really yarnd does (I believe). -- And if you set it too big well then maybe nobody sees your post for a while 😅

I would offer documentation on our use of the WebSub protocol, however this is not possible to implement for feed authors in _all_ cases, especially on multi-user hostrs like many of the tilde(s) I think... -- Is this something we _should_ document as an optional client feature? (I feel most feed authors probably wouldn't care all that much)
prologic
twtxt.net
View Thread
@win0err Maybe you can help us with that part of the spec? 🤔 It was added to honestly squelch really only one grumpy Twtxt user at the time, so we did it 😅 But really a well behaving client will periodically fetch a feed but respect HTTP headers like Last-Modified and so the hit on a web server is minimal at best. -- And as you just found, _many_ clients don't yet actually even respect this field, only really yarnd does (I believe). -- And if you set it too big well then maybe nobody sees your post for a while 😅

I would offer documentation on our use of the WebSub protocol, however this is not possible to implement for feed authors in _all_ cases, especially on multi-user hostrs like many of the tilde(s) I think... -- Is this something we _should_ document as an optional client feature? (I feel most feed authors probably wouldn't care all that much)
prologic
twtxt.net
View Thread
@lyse Ahh 😅
prologic
twtxt.net
View Thread
@lyse Ahh 😅
prologic
twtxt.net
View Thread
@lyse Ahh 😅
prologic
twtxt.net
View Thread
@lyse Ahh 😅
prologic
twtxt.net
View Thread
@lyse Clearly I don't know how to do footnotes 🤯
prologic
twtxt.net
View Thread
@lyse Clearly I don't know how to do footnotes 🤯
prologic
twtxt.net
View Thread
@lyse Clearly I don't know how to do footnotes 🤯
prologic
twtxt.net
View Thread
@lyse Clearly I don't know how to do footnotes 🤯
prologic
twtxt.net
View Thread
@eaplmx Good points. I personally like to call Yarn.social (and have been for a while now) an "ecosystem'. I'm pretty sure it says this on the Landing Page too somewhere... At some point (also) in the near future (when funds are available, because apparently its both complex and expensive to setup a not-for-profit / foundation 🤦‍♂️), there will also be a foundation (maybe be a different name?)

None of this however will have any effect on anything as long as we continue to:

- listen to the community
- adhere to the Twtxt specifications and Extensions
- keep specifications and client up-to-date[^1]


[^1]: There is _some_ contention over the use of Markdown in Twts (the Unicode newline literal is documented), however there is no agreement on this. It's a bit of a tough one. Really there are some useful parts of Markdown we all like to use, and other parts that we don't use nor need.
prologic
twtxt.net
View Thread
@eaplmx Good points. I personally like to call Yarn.social (and have been for a while now) an "ecosystem'. I'm pretty sure it says this on the Landing Page too somewhere... At some point (also) in the near future (when funds are available, because apparently its both complex and expensive to setup a not-for-profit / foundation 🤦‍♂️), there will also be a foundation (maybe be a different name?)

None of this however will have any effect on anything as long as we continue to:

- listen to the community
- adhere to the Twtxt specifications and Extensions
- keep specifications and client up-to-date[^1]


[^1]: There is _some_ contention over the use of Markdown in Twts (the Unicode newline literal is documented), however there is no agreement on this. It's a bit of a tough one. Really there are some useful parts of Markdown we all like to use, and other parts that we don't use nor need.
prologic
twtxt.net
View Thread
@eaplmx Good points. I personally like to call Yarn.social (and have been for a while now) an "ecosystem'. I'm pretty sure it says this on the Landing Page too somewhere... At some point (also) in the near future (when funds are available, because apparently its both complex and expensive to setup a not-for-profit / foundation 🤦‍♂️), there will also be a foundation (maybe be a different name?)

None of this however will have any effect on anything as long as we continue to:

- listen to the community
- adhere to the Twtxt specifications and Extensions
- keep specifications and client up-to-date[^1]


[^1]: There is _some_ contention over the use of Markdown in Twts (the Unicode newline literal is documented), however there is no agreement on this. It's a bit of a tough one. Really there are some useful parts of Markdown we all like to use, and other parts that we don't use nor need.
prologic
twtxt.net
View Thread
@eaplmx Good points. I personally like to call Yarn.social (and have been for a while now) an "ecosystem'. I'm pretty sure it says this on the Landing Page too somewhere... At some point (also) in the near future (when funds are available, because apparently its both complex and expensive to setup a not-for-profit / foundation 🤦‍♂️), there will also be a foundation (maybe be a different name?)

None of this however will have any effect on anything as long as we continue to:

- listen to the community
- adhere to the Twtxt specifications and Extensions
- keep specifications and client up-to-date[^1]

[^1]: There is _some_ contention over the use of Markdown in Twts (the Unicode newline literal is documented), however there is no agreement on this. It's a bit of a tough one. Really there are some useful parts of Markdown we all like to use, and other parts that we don't use nor need.
prologic
twtxt.net
View Thread
@eaplmx Good points. I personally like to call Yarn.social (and have been for a while now) an "ecosystem'. I'm pretty sure it says this on the Landing Page too somewhere... At some point (also) in the near future (when funds are available, because apparently its both complex and expensive to setup a not-for-profit / foundation 🤦‍♂️), there will also be a foundation (maybe be a different name?)

None of this however will have any effect on anything as long as we continue to:

- listen to the community
- adhere to the Twtxt specifications and Extensions
- keep specifications and client up-to-date[^1]


[^1]: There is _some_ contention over the use of Markdown in Twts (the Unicode newline literal is documented), however there is no agreement on this. It's a bit of a tough one. Really there are some useful parts of Markdown we all like to use, and other parts that we don't use nor need.
prologic
twtxt.net
View Thread
Finally... Even if Yarn.social and yarnd instances (Pods) tomorrow were to suddenly be spawned in the thousands, with thousands of users or more, nothing much would change I don't think. We would have scalability problems with the search engine (pretty sure), and at that point _some_ of those pods _might_ be "Hosted Pods" (for a fee), which I'm _hoping_ by then would go back into a "foundation" (yet to be named, TBD) to continue to fund the "foundation" (TBD).
prologic
twtxt.net
View Thread
Finally... Even if Yarn.social and yarnd instances (Pods) tomorrow were to suddenly be spawned in the thousands, with thousands of users or more, nothing much would change I don't think. We would have scalability problems with the search engine (pretty sure), and at that point _some_ of those pods _might_ be "Hosted Pods" (for a fee), which I'm _hoping_ by then would go back into a "foundation" (yet to be named, TBD) to continue to fund the "foundation" (TBD).
prologic
twtxt.net
View Thread
Finally... Even if Yarn.social and yarnd instances (Pods) tomorrow were to suddenly be spawned in the thousands, with thousands of users or more, nothing much would change I don't think. We would have scalability problems with the search engine (pretty sure), and at that point _some_ of those pods _might_ be "Hosted Pods" (for a fee), which I'm _hoping_ by then would go back into a "foundation" (yet to be named, TBD) to continue to fund the "foundation" (TBD).
prologic
twtxt.net
View Thread
Finally... Even if Yarn.social and yarnd instances (Pods) tomorrow were to suddenly be spawned in the thousands, with thousands of users or more, nothing much would change I don't think. We would have scalability problems with the search engine (pretty sure), and at that point _some_ of those pods _might_ be "Hosted Pods" (for a fee), which I'm _hoping_ by then would go back into a "foundation" (yet to be named, TBD) to continue to fund the "foundation" (TBD).
prologic
twtxt.net
View Thread
... and build what I believe (and have always believed now for the past few years) the best kind of social media. The slow kind, the truly decentralised kind and the one that is easy to reason about and build against.

It's just a freka'n text file 🤣
prologic
twtxt.net
View Thread
... and build what I believe (and have always believed now for the past few years) the best kind of social media. The slow kind, the truly decentralised kind and the one that is easy to reason about and build against.

It's just a freka'n text file 🤣
prologic
twtxt.net
View Thread
... and build what I believe (and have always believed now for the past few years) the best kind of social media. The slow kind, the truly decentralised kind and the one that is easy to reason about and build against.

It's just a freka'n text file 🤣
prologic
twtxt.net
View Thread
... and build what I believe (and have always believed now for the past few years) the best kind of social media. The slow kind, the truly decentralised kind and the one that is easy to reason about and build against.

It's just a freka'n text file 🤣
prologic
twtxt.net
View Thread
@movq I agree with @lyse very well said. I guess I can also understand the "worries" (as unfounded as they are) too, especially coming from your perspective. As you say though (thank you 🙏) Yarn.social is a far cry from this situation.

All along we started out with:

> What is the community doing now, what has it always done, what does it want to do.

And we formalised that.

At the same time we built what is now called yarnd, or Yarn.social Pod(s). Aside from the fact it is both decentralised and distributed and uses Twtxt, and all the Extensions, as well as IndieAuth, Atom, WebMentions and WebSub (all open source protocols and specifications, most of which are from the "Small Web") there's nothing special going on -- yarnd is just a multi-user client and implementation of the specs.

My only goal has always been (and unlikely to change) to bring the simplicity of Twtxt to the masses (I think you all remember this). Hide the complexities of hosting a feed (as simple as that is for tech savvy folks)...
prologic
twtxt.net
View Thread
@movq I agree with @lyse very well said. I guess I can also understand the "worries" (as unfounded as they are) too, especially coming from your perspective. As you say though (thank you 🙏) Yarn.social is a far cry from this situation.

All along we started out with:

> What is the community doing now, what has it always done, what does it want to do.

And we formalised that.

At the same time we built what is now called yarnd, or Yarn.social Pod(s). Aside from the fact it is both decentralised and distributed and uses Twtxt, and all the Extensions, as well as IndieAuth, Atom, WebMentions and WebSub (all open source protocols and specifications, most of which are from the "Small Web") there's nothing special going on -- yarnd is just a multi-user client and implementation of the specs.

My only goal has always been (and unlikely to change) to bring the simplicity of Twtxt to the masses (I think you all remember this). Hide the complexities of hosting a feed (as simple as that is for tech savvy folks)...
prologic
twtxt.net
View Thread
@movq I agree with @lyse very well said. I guess I can also understand the "worries" (as unfounded as they are) too, especially coming from your perspective. As you say though (thank you 🙏) Yarn.social is a far cry from this situation.

All along we started out with:

> What is the community doing now, what has it always done, what does it want to do.

And we formalised that.

At the same time we built what is now called yarnd, or Yarn.social Pod(s). Aside from the fact it is both decentralised and distributed and uses Twtxt, and all the Extensions, as well as IndieAuth, Atom, WebMentions and WebSub (all open source protocols and specifications, most of which are from the "Small Web") there's nothing special going on -- yarnd is just a multi-user client and implementation of the specs.

My only goal has always been (and unlikely to change) to bring the simplicity of Twtxt to the masses (I think you all remember this). Hide the complexities of hosting a feed (as simple as that is for tech savvy folks)...
prologic
twtxt.net
View Thread
@movq I agree with @lyse very well said. I guess I can also understand the "worries" (as unfounded as they are) too, especially coming from your perspective. As you say though (thank you 🙏) Yarn.social is a far cry from this situation.

All along we started out with:

> What is the community doing now, what has it always done, what does it want to do.

And we formalised that.

At the same time we built what is now called yarnd, or Yarn.social Pod(s). Aside from the fact it is both decentralised and distributed and uses Twtxt, and all the Extensions, as well as IndieAuth, Atom, WebMentions and WebSub (all open source protocols and specifications, most of which are from the "Small Web") there's nothing special going on -- yarnd is just a multi-user client and implementation of the specs.

My only goal has always been (and unlikely to change) to bring the simplicity of Twtxt to the masses (I think you all remember this). Hide the complexities of hosting a feed (as simple as that is for tech savvy folks)...
prologic
twtxt.net
View Thread
@eaplmx You are right on both counts and yes I did say this and of course I still believe its true 👌 That aside, calling our community and project (what should become a foundation when I have the money, with you guys driving it!) is not right though 🤗
prologic
twtxt.net
View Thread
@eaplmx You are right on both counts and yes I did say this and of course I still believe its true 👌 That aside, calling our community and project (what should become a foundation when I have the money, with you guys driving it!) is not right though 🤗
prologic
twtxt.net
View Thread
@eaplmx You are right on both counts and yes I did say this and of course I still believe its true 👌 That aside, calling our community and project (what should become a foundation when I have the money, with you guys driving it!) is not right though 🤗
prologic
twtxt.net
View Thread
@eaplmx You are right on both counts and yes I did say this and of course I still believe its true 👌 That aside, calling our community and project (what should become a foundation when I have the money, with you guys driving it!) is not right though 🤗
prologic
twtxt.net
View Thread
@eaplmx Sadly the simple fact here is; We can debate this part of the spec until the cows come home (_a silly English/Australian expression_). There is just no way to agree on this at all. IMO it should be removed from the spec entirely. yarnd (as one client) for example just makes this configurable, ful-stop, with a reasonable default value that has been discussed and widely agreed upon by the community at least twice now.
prologic
twtxt.net
View Thread
@eaplmx Sadly the simple fact here is; We can debate this part of the spec until the cows come home (_a silly English/Australian expression_). There is just no way to agree on this at all. IMO it should be removed from the spec entirely. yarnd (as one client) for example just makes this configurable, ful-stop, with a reasonable default value that has been discussed and widely agreed upon by the community at least twice now.
prologic
twtxt.net
View Thread
@eaplmx Sadly the simple fact here is; We can debate this part of the spec until the cows come home (_a silly English/Australian expression_). There is just no way to agree on this at all. IMO it should be removed from the spec entirely. yarnd (as one client) for example just makes this configurable, ful-stop, with a reasonable default value that has been discussed and widely agreed upon by the community at least twice now.
prologic
twtxt.net
View Thread
@eaplmx Sadly the simple fact here is; We can debate this part of the spec until the cows come home (_a silly English/Australian expression_). There is just no way to agree on this at all. IMO it should be removed from the spec entirely. yarnd (as one client) for example just makes this configurable, ful-stop, with a reasonable default value that has been discussed and widely agreed upon by the community at least twice now.
prologic
twtxt.net
View Thread
No. I eat the whole thing.
prologic
twtxt.net
View Thread
No. I eat the whole thing.
prologic
twtxt.net
View Thread
No. I eat the whole thing.
prologic
twtxt.net
View Thread
No. I eat the whole thing.
prologic
twtxt.net
View Thread
@lyse Yeah me neither. Will have to sleep on that one 😅 😴
prologic
twtxt.net
View Thread
@lyse Yeah me neither. Will have to sleep on that one 😅 😴
prologic
twtxt.net
View Thread
@lyse Yeah me neither. Will have to sleep on that one 😅 😴
prologic
twtxt.net
View Thread
@lyse Yeah me neither. Will have to sleep on that one 😅 😴
prologic
twtxt.net
View Thread
@lyse Something the feeds service is doing or just poorly designed Atom output from PixelFeed? 🤔
prologic
twtxt.net
View Thread
@lyse Something the feeds service is doing or just poorly designed Atom output from PixelFeed? 🤔
prologic
twtxt.net
View Thread
@lyse Something the feeds service is doing or just poorly designed Atom output from PixelFeed? 🤔
prologic
twtxt.net
View Thread
@lyse Something the feeds service is doing or just poorly designed Atom output from PixelFeed? 🤔
prologic
twtxt.net
View Thread
@lyse Ooops 😅 Although I am wondering how really useful this refresh field really is hmm 🤔 It was only added to squelch some grumpy feed authors, but I do wonder about its utility and downside if you declare an exceedingly large value 🤔
prologic
twtxt.net
View Thread
@lyse Ooops 😅 Although I am wondering how really useful this refresh field really is hmm 🤔 It was only added to squelch some grumpy feed authors, but I do wonder about its utility and downside if you declare an exceedingly large value 🤔
prologic
twtxt.net
View Thread
@lyse Ooops 😅 Although I am wondering how really useful this refresh field really is hmm 🤔 It was only added to squelch some grumpy feed authors, but I do wonder about its utility and downside if you declare an exceedingly large value 🤔
prologic
twtxt.net
View Thread
@lyse Ooops 😅 Although I am wondering how really useful this refresh field really is hmm 🤔 It was only added to squelch some grumpy feed authors, but I do wonder about its utility and downside if you declare an exceedingly large value 🤔
prologic
twtxt.net
View Thread
_meh_ the Atom output is a bit *meH but it works 🤣*
prologic
twtxt.net
View Thread
_meh_ the Atom output is a bit *meH but it works 🤣*
prologic
twtxt.net
View Thread
_meh_ the Atom output is a bit *meH but it works 🤣*
prologic
twtxt.net
View Thread
_meh_ the Atom output is a bit *meH but it works 🤣*
prologic
twtxt.net
View Thread
Here we go @win0err-on-pixelfed
prologic
twtxt.net
View Thread
Here we go @win0err-on-pixelfed
prologic
twtxt.net
View Thread
Here we go @win0err-on-pixelfed
prologic
twtxt.net
View Thread
Here we go @win0err-on-pixelfed
prologic
twtxt.net
View Thread
@bender Ahh as a non-user of PixelFeed I didn't know it has an Atom feed 😅 Let's throw it in feeds.twtxt.net and see what happens 🤔
prologic
twtxt.net
View Thread
@bender Ahh as a non-user of PixelFeed I didn't know it has an Atom feed 😅 Let's throw it in feeds.twtxt.net and see what happens 🤔
prologic
twtxt.net
View Thread
@bender Ahh as a non-user of PixelFeed I didn't know it has an Atom feed 😅 Let's throw it in feeds.twtxt.net and see what happens 🤔
prologic
twtxt.net
View Thread
@bender Ahh as a non-user of PixelFeed I didn't know it has an Atom feed 😅 Let's throw it in feeds.twtxt.net and see what happens 🤔
prologic
twtxt.net
View Thread
Also there is no way to tell yarnd to hard-refresh or ignore this either 🤣
prologic
twtxt.net
View Thread
Also there is no way to tell yarnd to hard-refresh or ignore this either 🤣
prologic
twtxt.net
View Thread
Also there is no way to tell yarnd to hard-refresh or ignore this either 🤣
prologic
twtxt.net
View Thread
Also there is no way to tell yarnd to hard-refresh or ignore this either 🤣
prologic
twtxt.net
View Thread
@win0err And FWIW, a single pod will only fetch your feed once per cache refresh interval, regardless of how many users on that pod (pods are by default multi-user pods) follow you.
prologic
twtxt.net
View Thread
@win0err And FWIW, a single pod will only fetch your feed once per cache refresh interval, regardless of how many users on that pod (pods are by default multi-user pods) follow you.
prologic
twtxt.net
View Thread
@win0err And FWIW, a single pod will only fetch your feed once per cache refresh interval, regardless of how many users on that pod (pods are by default multi-user pods) follow you.
prologic
twtxt.net
View Thread
@win0err And FWIW, a single pod will only fetch your feed once per cache refresh interval, regardless of how many users on that pod (pods are by default multi-user pods) follow you.
prologic
twtxt.net
View Thread
@lyse Oh boi. I was wondering why I couldn't see @win0err's Twt you were clearly replying to ! 🤣 @lyse Looks like your client tt isn't respecting the # refresh interval of a feed? @win0err has this set to:


# refresh = 14400


Which yarnd will hard respect and so I and anyone on my pod (and basically any other pod, there's like some ~20 or so now) will only see updates twice per day 😅 -- You _might_ want to reconsider this value...? 🤣~
prologic
twtxt.net
View Thread
@lyse Oh boi. I was wondering why I couldn't see @win0err's Twt you were clearly replying to ! 🤣 @lyse Looks like your client tt isn't respecting the # refresh interval of a feed? @win0err has this set to:


# refresh = 14400


Which yarnd will hard respect and so I and anyone on my pod (and basically any other pod, there's like some ~20 or so now) will only see updates twice per day 😅 -- You _might_ want to reconsider this value...? 🤣~
prologic
twtxt.net
View Thread
@lyse Oh boi. I was wondering why I couldn't see @win0err's Twt you were clearly replying to ! 🤣 @lyse Looks like your client tt isn't respecting the # refresh interval of a feed? @win0err has this set to:


# refresh = 14400


Which yarnd will hard respect and so I and anyone on my pod (and basically any other pod, there's like some ~20 or so now) will only see updates twice per day 😅 -- You _might_ want to reconsider this value...? 🤣~
prologic
twtxt.net
View Thread
@lyse Oh boi. I was wondering why I couldn't see @win0err's Twt you were clearly replying to ! 🤣 @lyse Looks like your client tt isn't respecting the # refresh interval of a feed? @win0err has this set to:


# refresh = 14400


Which yarnd will hard respect and so I and anyone on my pod (and basically any other pod, there's like some ~20 or so now) will only see updates twice per day 😅 -- You _might_ want to reconsider this value...? 🤣~
prologic
twtxt.net
View Thread
Which btw is my first ever Twt: https://twtxt.net/twt/o6dsrga 😅
prologic
twtxt.net
View Thread
Which btw is my first ever Twt: https://twtxt.net/twt/o6dsrga 😅
prologic
twtxt.net
View Thread
Which btw is my first ever Twt: https://twtxt.net/twt/o6dsrga 😅
prologic
twtxt.net
View Thread
Which btw is my first ever Twt: https://twtxt.net/twt/o6dsrga 😅
prologic
twtxt.net
View Thread
@win0err Yeah, fair. I should probably mention (if not already obvious) by just preserving the already-existing subject hash, its pretty easy to participate in a thread (assuming the same folks follow your feed). But yeah without a client its a. bit harder I suppose, one of the reasons we added a hash sub-command to the yarnc command-line tool/client.


  $ yarnc hash -u https://twtxt.net/user/prologic/twtxt.txt -t 2020-07-18T12:39:52Z "Hello World! 😊"
  o6dsrga
prologic
twtxt.net
View Thread
@win0err Yeah, fair. I should probably mention (if not already obvious) by just preserving the already-existing subject hash, its pretty easy to participate in a thread (assuming the same folks follow your feed). But yeah without a client its a. bit harder I suppose, one of the reasons we added a hash sub-command to the yarnc command-line tool/client.


  $ yarnc hash -u https://twtxt.net/user/prologic/twtxt.txt -t 2020-07-18T12:39:52Z "Hello World! 😊"
  o6dsrga
prologic
twtxt.net
View Thread
@win0err Yeah, fair. I should probably mention (if not already obvious) by just preserving the already-existing subject hash, its pretty easy to participate in a thread (assuming the same folks follow your feed). But yeah without a client its a. bit harder I suppose, one of the reasons we added a hash sub-command to the yarnc command-line tool/client.


  $ yarnc hash -u https://twtxt.net/user/prologic/twtxt.txt -t 2020-07-18T12:39:52Z "Hello World! 😊"
  o6dsrga
prologic
twtxt.net
View Thread
@win0err Yeah, fair. I should probably mention (if not already obvious) by just preserving the already-existing subject hash, its pretty easy to participate in a thread (assuming the same folks follow your feed). But yeah without a client its a. bit harder I suppose, one of the reasons we added a hash sub-command to the yarnc command-line tool/client.


  $ yarnc hash -u https://twtxt.net/user/prologic/twtxt.txt -t 2020-07-18T12:39:52Z "Hello World! 😊"
  o6dsrga
prologic
twtxt.net
View Thread
@lyse Yeah! I _used_ to think I was pretty decent at making paper air planes, but after watching this guy, no way! 🤦‍♂️
prologic
twtxt.net
View Thread
@lyse Yeah! I _used_ to think I was pretty decent at making paper air planes, but after watching this guy, no way! 🤦‍♂️
prologic
twtxt.net
View Thread
@lyse Yeah! I _used_ to think I was pretty decent at making paper air planes, but after watching this guy, no way! 🤦‍♂️
prologic
twtxt.net
View Thread
@lyse Yeah! I _used_ to think I was pretty decent at making paper air planes, but after watching this guy, no way! 🤦‍♂️