# 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 60813
# self = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=53880
# next = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=53980
# prev = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=53780
@lyse Ahh yea! I'll setup some CD for it this weekend 👌
@lyse Ahh yea! I'll setup some CD for it this weekend 👌
@lyse Ahh yea! I'll setup some CD for it this weekend 👌
@movq
> If you all were to clear your caches, would your clients fetch archived feeds?
No.
And I'm also thinking of nuking my pod at some point and starting over. But maybe after we refactor a few important things.
@movq
> If you all were to clear your caches, would your clients fetch archived feeds?
No.
And I'm also thinking of nuking my pod at some point and starting over. But maybe after we refactor a few important things.
@movq
> If you all were to clear your caches, would your clients fetch archived feeds?
No.
And I'm also thinking of nuking my pod at some point and starting over. But maybe after we refactor a few important things.
@bender I _think_ it comes down to one of the principles Yarn.social was founded on, which is to say, users should have choices and what they "see" is not driven by "algorithms". The "Discover" view in and of itself has utility/value to others, and is otherwise just a "view" of a pod's cache, but I agree with you. It was even getting noisey for me 🤣
@bender I _think_ it comes down to one of the principles Yarn.social was founded on, which is to say, users should have choices and what they "see" is not driven by "algorithms". The "Discover" view in and of itself has utility/value to others, and is otherwise just a "view" of a pod's cache, but I agree with you. It was even getting noisey for me 🤣
@bender I _think_ it comes down to one of the principles Yarn.social was founded on, which is to say, users should have choices and what they "see" is not driven by "algorithms". The "Discover" view in and of itself has utility/value to others, and is otherwise just a "view" of a pod's cache, but I agree with you. It was even getting noisey for me 🤣
In other words, there isn't anything _specifically_ wrong with the Twtxt spec (+extensions), but if you for example use a client and server combination that never considered the User-Agent header and check logs or intercept requests for your feed, than you end up missing an important part of the whole flow (unless you are of course deliberating ignoring that, e.g: 1-way feeds, news feeds, etc).
In other words, there isn't anything _specifically_ wrong with the Twtxt spec (+extensions), but if you for example use a client and server combination that never considered the User-Agent header and check logs or intercept requests for your feed, than you end up missing an important part of the whole flow (unless you are of course deliberating ignoring that, e.g: 1-way feeds, news feeds, etc).
In other words, there isn't anything _specifically_ wrong with the Twtxt spec (+extensions), but if you for example use a client and server combination that never considered the User-Agent header and check logs or intercept requests for your feed, than you end up missing an important part of the whole flow (unless you are of course deliberating ignoring that, e.g: 1-way feeds, news feeds, etc).
In my opinion, this _can_ all be solved by a "better standard client".
In my opinion, this _can_ all be solved by a "better standard client".
In my opinion, this _can_ all be solved by a "better standard client".
For example I noticed in this thread, someone, me, and you, and now it's just a bad -mention mentioned Soren Peter with a bad link :/
For example I noticed in this thread, someone, me, and you, and now it's just a bad -mention mentioned Soren Peter with a bad link :/
For example I noticed in this thread, someone, me, and you, and now it's just a bad -mention mentioned Soren Peter with a bad link :/
This also just reminds me of the other problems that exist:
- bad mentions.
- knowing whether someone will you've -mentioned will even see your reply at all.
This also just reminds me of the other problems that exist:
- bad mentions.
- knowing whether someone will you've -mentioned will even see your reply at all.
This also just reminds me of the other problems that exist:
- bad mentions.
- knowing whether someone will you've -mentioned will even see your reply at all.
@mckinley I think we just need a way of surfacing this information better for both users and operators? 🤔
@mckinley I think we just need a way of surfacing this information better for both users and operators? 🤔
@mckinley I think we just need a way of surfacing this information better for both users and operators? 🤔
@mckinley Yeah this is what was being "cleaned up"
Yo be honest I don't think there is a good solution IMO
@mckinley Yeah this is what was being "cleaned up"
Yo be honest I don't think there is a good solution IMO
@mckinley Yeah this is what was being "cleaned up"
Yo be honest I don't think there is a good solution IMO
You're right we should
never be like Microshit 😆
You're right we should
never be like Microshit 😆
You're right we should
never be like Microshit 😆
@mckinley I think "posting to the void" was/is a poor choice of words hete.
@mckinley I think "posting to the void" was/is a poor choice of words hete.
@mckinley I think "posting to the void" was/is a poor choice of words hete.
Today in the news
> Microsoft is a security risk
Today in the news
> Microsoft is a security risk
Today in the news
> Microsoft is a security risk
@slashdot Oh boi! 😆 Gotta take a screenshot of this in case Microsoft demand the article be taken down 🤣
@slashdot Oh boi! 😆 Gotta take a screenshot of this in case Microsoft demand the article be taken down 🤣
@slashdot Oh boi! 😆 Gotta take a screenshot of this in case Microsoft demand the article be taken down 🤣
@dfaria Also, I don't really care whether you continue to use my pod or not frankly.
> One more reason not to use https://twtxt.net/
negative comments like this are completely unconstructive and have no basis in merit. If you have issues with the way I administer my pod, speak up, provide alternatives. If you have good technical suggestions for Twtxt/Yarn, we're all ears. We are only trying (or attempt to try) to make things better for all, which as you can appreciate is a hard thing to do.
Next time, please leave your constructive criticisms at home. No-one forces you to use my pod (for free).
@dfaria Also, I don't really care whether you continue to use my pod or not frankly.
> One more reason not to use https://twtxt.net/
negative comments like this are completely unconstructive and have no basis in merit. If you have issues with the way I administer my pod, speak up, provide alternatives. If you have good technical suggestions for Twtxt/Yarn, we're all ears. We are only trying (or attempt to try) to make things better for all, which as you can appreciate is a hard thing to do.
Next time, please leave your constructive criticisms at home. No-one forces you to use my pod (for free).
@dfaria Also, I don't really care whether you continue to use my pod or not frankly.
> One more reason not to use https://twtxt.net/
negative comments like this are completely unconstructive and have no basis in merit. If you have issues with the way I administer my pod, speak up, provide alternatives. If you have good technical suggestions for Twtxt/Yarn, we're all ears. We are only trying (or attempt to try) to make things better for all, which as you can appreciate is a hard thing to do.
Next time, please leave your constructive criticisms at home. No-one forces you to use my pod (for free).
Oh never mind! 🤦♂️ That's your other feed that you syndicate some stuff to? 🤔 Research?
Oh never mind! 🤦♂️ That's your other feed that you syndicate some stuff to? 🤔 Research?
Oh never mind! 🤦♂️ That's your other feed that you syndicate some stuff to? 🤔 Research?
@dfaria And btw, even if I block a feed or whole domain, it doesn't stop you from following. it just removes it from the "Discover" view.
@dfaria And btw, even if I block a feed or whole domain, it doesn't stop you from following. it just removes it from the "Discover" view.
@dfaria And btw, even if I block a feed or whole domain, it doesn't stop you from following. it just removes it from the "Discover" view.
@dfaria And here I thought you never or we're not capable (client?) of interacting with other users? 🤣
@dfaria And here I thought you never or we're not capable (client?) of interacting with other users? 🤣
@dfaria And here I thought you never or we're not capable (client?) of interacting with other users? 🤣
@eapl.me We went out for nice breakfast and put the camper trailer away 😅
@eapl.me We went out for nice breakfast and put the camper trailer away 😅
@eapl.me We went out for nice breakfast and put the camper trailer away 😅
@mckinley Yeah pretry by hand at the moment.I only backup what I cannot reproduce.
@mckinley Yeah pretry by hand at the moment.I only backup what I cannot reproduce.
@mckinley Yeah pretry by hand at the moment.I only backup what I cannot reproduce.
@mckinley I use Restic and backup to another machine on my network as well as Backblaze B2
@mckinley I use Restic and backup to another machine on my network as well as Backblaze B2
@mckinley I use Restic and backup to another machine on my network as well as Backblaze B2
@mckinley Do you have an alternate proposal? What we _want_ to avoid really (if possible) is the idea of "1-ay posting" or "posting to the void". As an obvious example, the idea of syncing your Mastoon toots to Twtxt twts that you never see replies to is well umm just silly 🤣 and thus creates unwanted noise as it's just like talking to a "brick wall" 😥
@mckinley Do you have an alternate proposal? What we _want_ to avoid really (if possible) is the idea of "1-ay posting" or "posting to the void". As an obvious example, the idea of syncing your Mastoon toots to Twtxt twts that you never see replies to is well umm just silly 🤣 and thus creates unwanted noise as it's just like talking to a "brick wall" 😥
@mckinley Do you have an alternate proposal? What we _want_ to avoid really (if possible) is the idea of "1-ay posting" or "posting to the void". As an obvious example, the idea of syncing your Mastoon toots to Twtxt twts that you never see replies to is well umm just silly 🤣 and thus creates unwanted noise as it's just like talking to a "brick wall" 😥
@rrraksamam You must live in the southern hemisphere? 🤔 It doesn't ever snow here in Brisbane 🤣
@rrraksamam You must live in the southern hemisphere? 🤔 It doesn't ever snow here in Brisbane 🤣
@rrraksamam You must live in the southern hemisphere? 🤔 It doesn't ever snow here in Brisbane 🤣
@bender This is what I fell over and bunged up my shin 😱 
@bender This is what I fell over and bunged up my shin 😱
@bender This is what I fell over and bunged up my shin 😱