# 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 61074
# self = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=45091
# next = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=45191
# prev = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=44991
@carsten It is not 🤣 Far from it 😅
@carsten It is not 🤣 Far from it 😅
@carsten It is not 🤣 Far from it 😅
@carsten It is not 🤣 Far from it 😅
@carsten C# ?! 😱 Why for the love of god would anyone in their right mind develop something in C#?! 😅
@carsten C# ?! 😱 Why for the love of god would anyone in their right mind develop something in C#?! 😅
@carsten C# ?! 😱 Why for the love of god would anyone in their right mind develop something in C#?! 😅
@carsten C# ?! 😱 Why for the love of god would anyone in their right mind develop something in C#?! 😅
My silence initially was not an invitation of my position on this. Both my wife and I read through the material, the (_not to be linked_) twt, and IRC backlog. Making fun (_humour_) of any protected class is NOT OK. I agree 👌
My silence initially was not an invitation of my position on this. Both my wife and I read through the material, the (_not to be linked_) twt, and IRC backlog. Making fun (_humour_) of any protected class is NOT OK. I agree 👌
My silence initially was not an invitation of my position on this. Both my wife and I read through the material, the (_not to be linked_) twt, and IRC backlog. Making fun (_humour_) of any protected class is NOT OK. I agree 👌
My silence initially was not an invitation of my position on this. Both my wife and I read through the material, the (_not to be linked_) twt, and IRC backlog. Making fun (_humour_) of any protected class is NOT OK. I agree 👌
@thecanine Wow ! 😱 I certainly didn't want to try it before, and certainly don't nw 😅
@thecanine Wow ! 😱 I certainly didn't want to try it before, and certainly don't nw 😅
@thecanine Wow ! 😱 I certainly didn't want to try it before, and certainly don't nw 😅
@thecanine Wow ! 😱 I certainly didn't want to try it before, and certainly don't nw 😅
@bender @bender Oh man that was months ago, when Ullarah was still around 🤦‍♂️
@bender @bender Oh man that was months ago, when Ullarah was still around 🤦‍♂️
@bender @bender Oh man that was months ago, when Ullarah was still around 🤦‍♂️
@bender @bender Oh man that was months ago, when Ullarah was still around 🤦‍♂️
@lyse Very lovely pics as always 👌 What's with all the logs that were cut down and left in.a neat pile? 🤔
@lyse Very lovely pics as always 👌 What's with all the logs that were cut down and left in.a neat pile? 🤔
@lyse Very lovely pics as always 👌 What's with all the logs that were cut down and left in.a neat pile? 🤔
@lyse Very lovely pics as always 👌 What's with all the logs that were cut down and left in.a neat pile? 🤔
@movq @lyse yeah I will never work in a centralised place every again, ever. It's just insane.
@movq @lyse yeah I will never work in a centralised place every again, ever. It's just insane.
@movq @lyse yeah I will never work in a centralised place every again, ever. It's just insane.
@movq @lyse yeah I will never work in a centralised place every again, ever. It's just insane.
@dfaria Short answer: NO
@dfaria Short answer: NO
@dfaria Short answer: NO
@dfaria Short answer: NO
🤙 Yarn.social weekly call

- When: Saturday 4th Feb @ 0500 UTC and 1200 UTC
- Where: https://meet.mills.io/call/Yarn.social

Please indicate which time-slot you'd like to come hang on in 🙏
🤙 Yarn.social weekly call

- When: Saturday 4th Feb @ 0500 UTC and 1200 UTC
- Where: https://meet.mills.io/call/Yarn.social

Please indicate which time-slot you'd like to come hang on in 🙏
🤙 Yarn.social weekly call

- When: Saturday 4th Feb @ 0500 UTC and 1200 UTC
- Where: https://meet.mills.io/call/Yarn.social

Please indicate which time-slot you'd like to come hang on in 🙏
🤙 Yarn.social weekly call

- When: Saturday 4th Feb @ 0500 UTC and 1200 UTC
- Where: https://meet.mills.io/call/Yarn.social

Please indicate which time-slot you'd like to come hang on in 🙏
@linux_gizmos bloody hell that thing is small and cheap 😳
@linux_gizmos bloody hell that thing is small and cheap 😳
@linux_gizmos bloody hell that thing is small and cheap 😳
@linux_gizmos bloody hell that thing is small and cheap 😳
@bender Distributed Network.
@bender Distributed Network.
@bender Distributed Network.
@bender Distributed Network.
actually from my reading and understanding I think it's even worse than this.

They claim that the platform runs on a distributed network protocol of relay servers that I believe are managed by Nostr/

so basically, this is very much centralized and you have to place trust in both the app and relay service.
actually from my reading and understanding I think it's even worse than this.

They claim that the platform runs on a distributed network protocol of relay servers that I believe are managed by Nostr/

so basically, this is very much centralized and you have to place trust in both the app and relay service.
actually from my reading and understanding I think it's even worse than this.

They claim that the platform runs on a distributed network protocol of relay servers that I believe are managed by Nostr/

so basically, this is very much centralized and you have to place trust in both the app and relay service.
actually from my reading and understanding I think it's even worse than this.

They claim that the platform runs on a distributed network protocol of relay servers that I believe are managed by Nostr/

so basically, this is very much centralized and you have to place trust in both the app and relay service.
@slashdot it's not a fucking decentralized network 🤦‍♂️ it's a goddamn distributed not work 🤬

Fucking Web3 garbage 😱
@slashdot it's not a fucking decentralized network 🤦‍♂️ it's a goddamn distributed not work 🤬

Fucking Web3 garbage 😱
@slashdot it's not a fucking decentralized network 🤦‍♂️ it's a goddamn distributed not work 🤬

Fucking Web3 garbage 😱
@slashdot it's not a fucking decentralized network 🤦‍♂️ it's a goddamn distributed not work 🤬

Fucking Web3 garbage 😱
So baxk to Yarn.social ? 😆
So baxk to Yarn.social ? 😆
So baxk to Yarn.social ? 😆
So baxk to Yarn.social ? 😆
@github_blog ClickOps, ChatOps, DevOps, Ops... What's next?! 😱
@github_blog ClickOps, ChatOps, DevOps, Ops... What's next?! 😱
@github_blog ClickOps, ChatOps, DevOps, Ops... What's next?! 😱
@github_blog ClickOps, ChatOps, DevOps, Ops... What's next?! 😱
@axodys Interesting app and "social platform", too bad it's built on a centralised distributed network of relays 😅
@axodys Interesting app and "social platform", too bad it's built on a centralised distributed network of relays 😅
@axodys Interesting app and "social platform", too bad it's built on a centralised distributed network of relays 😅
@axodys Interesting app and "social platform", too bad it's built on a centralised distributed network of relays 😅
@abucci Thank you 🙏
@abucci Thank you 🙏
@abucci Thank you 🙏
@abucci Thank you 🙏
@abucci I _think_ so. The backend already knows how to measure "inactive feeds" so that shouldn't be too hard to build, just have to build an interface around it "somehow" -- I think I recall telling you about a weekly email you'd get, but if you haven't gotten one, then you've been nuking these *zit(s) before that 😅*
@abucci I _think_ so. The backend already knows how to measure "inactive feeds" so that shouldn't be too hard to build, just have to build an interface around it "somehow" -- I think I recall telling you about a weekly email you'd get, but if you haven't gotten one, then you've been nuking these *zit(s) before that 😅*
@abucci I _think_ so. The backend already knows how to measure "inactive feeds" so that shouldn't be too hard to build, just have to build an interface around it "somehow" -- I think I recall telling you about a weekly email you'd get, but if you haven't gotten one, then you've been nuking these *zit(s) before that 😅*
@abucci I _think_ so. The backend already knows how to measure "inactive feeds" so that shouldn't be too hard to build, just have to build an interface around it "somehow" -- I think I recall telling you about a weekly email you'd get, but if you haven't gotten one, then you've been nuking these *zit(s) before that 😅*
@abucci Really don't need to store the _real_ email at all, just a token, using the same reset password jwt flows. Let it expire after like a few minutes. Click the link, verify token, cool, redirect to login, Otherwise, drop it on the floor.
@abucci Really don't need to store the _real_ email at all, just a token, using the same reset password jwt flows. Let it expire after like a few minutes. Click the link, verify token, cool, redirect to login, Otherwise, drop it on the floor.
@abucci Really don't need to store the _real_ email at all, just a token, using the same reset password jwt flows. Let it expire after like a few minutes. Click the link, verify token, cool, redirect to login, Otherwise, drop it on the floor.
@abucci Really don't need to store the _real_ email at all, just a token, using the same reset password jwt flows. Let it expire after like a few minutes. Click the link, verify token, cool, redirect to login, Otherwise, drop it on the floor.
@abucci Well if you recall, we don't actually store it either and never will. So maybe it's pointless? 🤔
@abucci Well if you recall, we don't actually store it either and never will. So maybe it's pointless? 🤔
@abucci Well if you recall, we don't actually store it either and never will. So maybe it's pointless? 🤔
@abucci Well if you recall, we don't actually store it either and never will. So maybe it's pointless? 🤔
@abucci Okay 👌 Maybe file a feature request(s) as per above, and we'll try to build this 🤞
@abucci Okay 👌 Maybe file a feature request(s) as per above, and we'll try to build this 🤞
@abucci Okay 👌 Maybe file a feature request(s) as per above, and we'll try to build this 🤞
@abucci Okay 👌 Maybe file a feature request(s) as per above, and we'll try to build this 🤞
@abucci Oh 🤣
@abucci Oh 🤣
@abucci Oh 🤣
@abucci Oh 🤣
I should als note that the Email field is optional. Will making that mandatory slow things down? 🤔 Be interesting to see what these bots are using? 🤔 Make email verification before creation a thing? 🤔
I should als note that the Email field is optional. Will making that mandatory slow things down? 🤔 Be interesting to see what these bots are using? 🤔 Make email verification before creation a thing? 🤔
I should als note that the Email field is optional. Will making that mandatory slow things down? 🤔 Be interesting to see what these bots are using? 🤔 Make email verification before creation a thing? 🤔
I should als note that the Email field is optional. Will making that mandatory slow things down? 🤔 Be interesting to see what these bots are using? 🤔 Make email verification before creation a thing? 🤔
@abucci So like just block some known patterns of user/feed names? 🤔
@abucci So like just block some known patterns of user/feed names? 🤔
@abucci So like just block some known patterns of user/feed names? 🤔
@abucci So like just block some known patterns of user/feed names? 🤔
@abucci I'm open to some feature flagged ideas? 🤔
@abucci I'm open to some feature flagged ideas? 🤔
@abucci I'm open to some feature flagged ideas? 🤔
@abucci I'm open to some feature flagged ideas? 🤔