# 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 20
# self = https://watcher.sour.is/conv/ljne7oq
That metadata I keep seeing at the top of some twtxt feeds ("nick = ", "url = ", etc.) is not formalized anywhere, is it? Where does it come from? The actual question is: Should I stick to a certain format? 🤔
That metadata I keep seeing at the top of some twtxt feeds ("nick = ", "url = ", etc.) is not formalized anywhere, is it? Where does it come from? The actual question is: Should I stick to a certain format? 🤔
That metadata I keep seeing at the top of some twtxt feeds ("nick = ", "url = ", etc.) is not formalized anywhere, is it? Where does it come from? The actual question is: Should I stick to a certain format? 🤔
@vain I have seen it pop up on a few feeds around and adopted it into the new parser I built. \n\nThe format I have followed has been '# ' :whitespace: '=' :whitespace: :text-before-newline: keys can be repeated and accessed like an array of values.
@vain I have seen it pop up on a few feeds around and adopted it into the new parser I built. \n\nThe format I have followed has been '# ' :whitespace: :key-name: '=' :whitespace: :value: keys can be repeated and accessed like an array of values.
@vain I have seen it pop up on a few feeds around and adopted it into the new parser I built.
The format I have followed has been '# ' :whitespace: :key-name: :whitespace: '=' :whitespace: :value: keys can be repeated and accessed like an array of values.
@vain I have seen it pop up on a few feeds around and adopted it into the new parser I built. \n\nThe format I have followed has been '# ' :whitespace: :key-name: :whitespace: '=' :whitespace: :value: keys can be repeated and accessed like an array of values.
@vain I have seen it pop up on a few feeds around and adopted it into the new parser I built.
The format I have followed has been '# ' :whitespace: :key-name: :whitespace: '=' :whitespace: :value: keys can be repeated and accessed like an array of values.
@vain I have seen it pop up on a few feeds around and adopted it into the new parser I built. \n\nThe format I have followed has been '# ' :whitespace: :key-name: :whitespace: '=' :whitespace: :value: keys can be repeated and accessed like an array of values.
@vain I have seen it pop up on a few feeds around and adopted it into the new parser I built.
The format I have followed has been '# ' :whitespace: :key-name: :whitespace: '=' :whitespace: :value: keys can be repeated and accessed like an array of values.
We plan to formalize it real soon Right @lyse ?
We plan to formalize it real soon Right @lyse ?
We plan to formalize it real soon Right @lyse ?
@lyse Alrighty! Better change my client to match those. :) (I use totally custom stuff at the moment.)
@lyse Alrighty! Better change my client to match those. :) (I use totally custom stuff at the moment.)
@lyse Alrighty! Better change my client to match those. :) (I use totally custom stuff at the moment.)