# 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=38391
# next = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=38491
# prev = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=38291
@justamoment l'd pretry much do the same thing 👌 Teach by example 👌
@justamoment l'd pretry much do the same thing 👌 Teach by example 👌
@justamoment l'd pretry much do the same thing 👌 Teach by example 👌
@justamoment l'd pretry much do the same thing 👌 Teach by example 👌
what the hell is that last column? 🤔😳
what the hell is that last column? 🤔😳
what the hell is that last column? 🤔😳
what the hell is that last column? 🤔😳
@xuu Haha 🤣 I always use the first way to embed a version string or commit hash in any daemon or cli I write in Go -- Using the -ldflags option.
@xuu Haha 🤣 I always use the first way to embed a version string or commit hash in any daemon or cli I write in Go -- Using the -ldflags option.
@xuu Haha 🤣 I always use the first way to embed a version string or commit hash in any daemon or cli I write in Go -- Using the -ldflags option.
@xuu Haha 🤣 I always use the first way to embed a version string or commit hash in any daemon or cli I write in Go -- Using the -ldflags option.
Done 👌 by the time you read this the update should have gone out 🤞
Done 👌 by the time you read this the update should have gone out 🤞
Done 👌 by the time you read this the update should have gone out 🤞
Done 👌 by the time you read this the update should have gone out 🤞
@marado I think the fact that you used two at symbols probably tells me that maybe we should support both forms? 🤔
@marado I think the fact that you used two at symbols probably tells me that maybe we should support both forms? 🤔
@marado I think the fact that you used two at symbols probably tells me that maybe we should support both forms? 🤔
@marado I think the fact that you used two at symbols probably tells me that maybe we should support both forms? 🤔
@carsten Its kind of horrifying really when you think about it. Your own personal identity not even in your fucking control 🤦♂️ Disgusting business practises 🤬
@carsten Its kind of horrifying really when you think about it. Your own personal identity not even in your fucking control 🤦♂️ Disgusting business practises 🤬
@carsten Its kind of horrifying really when you think about it. Your own personal identity not even in your fucking control 🤦♂️ Disgusting business practises 🤬
@carsten Its kind of horrifying really when you think about it. Your own personal identity not even in your fucking control 🤦♂️ Disgusting business practises 🤬
@marado @mckinley and anyone else interested. This PR is merged and rolled out to the Feeds service/instance I run 👌
@marado @mckinley and anyone else interested. This PR is merged and rolled out to the Feeds service/instance I run 👌
@marado @mckinley and anyone else interested. This PR is merged and rolled out to the Feeds service/instance I run 👌
@marado @mckinley and anyone else interested. This PR is merged and rolled out to the Feeds service/instance I run 👌
@xuu looks like we don't parse mentions with a non-whitespace in front of the at symbol? 🤔
@xuu looks like we don't parse mentions with a non-whitespace in front of the at symbol? 🤔
@xuu looks like we don't parse mentions with a non-whitespace in front of the at symbol? 🤔
@xuu looks like we don't parse mentions with a non-whitespace in front of the at symbol? 🤔
@lyse Yup for some reason I can see the root of this yarn now 🤗
@lyse Yup for some reason I can see the root of this yarn now 🤗
@lyse Yup for some reason I can see the root of this yarn now 🤗
@lyse Yup for some reason I can see the root of this yarn now 🤗
I think it's the way I red the comment from one of the core dead? nightpool? 🤔
I think it's the way I red the comment from one of the core dead? nightpool? 🤔
I think it's the way I red the comment from one of the core dead? nightpool? 🤔
I think it's the way I red the comment from one of the core dead? nightpool? 🤔
Yup 👌 As much as I don't like ActivityPub I think it's the way to go too 👌
Should we file an issue for someone to explore building the out? 🤔
Yup 👌 As much as I don't like ActivityPub I think it's the way to go too 👌
Should we file an issue for someone to explore building the out? 🤔
Yup 👌 As much as I don't like ActivityPub I think it's the way to go too 👌
Should we file an issue for someone to explore building the out? 🤔
Yup 👌 As much as I don't like ActivityPub I think it's the way to go too 👌
Should we file an issue for someone to explore building the out? 🤔
@eaplmx Yes but that won't matter as the Feeds service will basically poll the RSS feed and track it over time writing new Twts into the Twtxt feed 👌 -- This _would_ already work as-is if you just shove in the .rss URI, but I'm going to add first-class support for this with something like: mastodon:user@server
@eaplmx Yes but that won't matter as the Feeds service will basically poll the RSS feed and track it over time writing new Twts into the Twtxt feed 👌 -- This _would_ already work as-is if you just shove in the .rss URI, but I'm going to add first-class support for this with something like: mastodon:user@server
@eaplmx Yes but that won't matter as the Feeds service will basically poll the RSS feed and track it over time writing new Twts into the Twtxt feed 👌 -- This _would_ already work as-is if you just shove in the .rss URI, but I'm going to add first-class support for this with something like: mastodon:user@server
@eaplmx Yes but that won't matter as the Feeds service will basically poll the RSS feed and track it over time writing new Twts into the Twtxt feed 👌 -- This _would_ already work as-is if you just shove in the .rss URI, but I'm going to add first-class support for this with something like: mastodon:user@server
So with the help of a good 'ol friend (no longer active on Yarn.social / Twtxt, we miss you buddy 😅) I've figured out how Mastodon RSS works and it looks pretty reasonable as a 1-way Mastodon -> RSS -> Twtxt which we can then use in any valid Twtxt client. Seems to work rather nicely 👌
So with the help of a good 'ol friend (no longer active on Yarn.social / Twtxt, we miss you buddy 😅) I've figured out how Mastodon RSS works and it looks pretty reasonable as a 1-way Mastodon -> RSS -> Twtxt which we can then use in any valid Twtxt client. Seems to work rather nicely 👌
So with the help of a good 'ol friend (no longer active on Yarn.social / Twtxt, we miss you buddy 😅) I've figured out how Mastodon RSS works and it looks pretty reasonable as a 1-way Mastodon -> RSS -> Twtxt which we can then use in any valid Twtxt client. Seems to work rather nicely 👌
So with the help of a good 'ol friend (no longer active on Yarn.social / Twtxt, we miss you buddy 😅) I've figured out how Mastodon RSS works and it looks pretty reasonable as a 1-way Mastodon -> RSS -> Twtxt which we can then use in any valid Twtxt client. Seems to work rather nicely 👌
@eaplmx At this point I'm just curious. Do you know how to access/view the RSS feed of a Mastodon user? 🤔
@eaplmx At this point I'm just curious. Do you know how to access/view the RSS feed of a Mastodon user? 🤔
@eaplmx At this point I'm just curious. Do you know how to access/view the RSS feed of a Mastodon user? 🤔
@eaplmx At this point I'm just curious. Do you know how to access/view the RSS feed of a Mastodon user? 🤔