# 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 11
# self = https://watcher.sour.is/conv/eiv2qka
@shreyan Thanks for your encouraging words 🤗
I also agree that buckket's twtzt dlient makes a terrible Yarn client -- I would even go so far as to say it's not very well maintained either as it has been broken for some time 😢
Yes we can raise a PR against the original reference client -- But I'm not convinced it'll get accepted 😢
@shreyan Thanks for your encouraging words 🤗
I also agree that buckket's twtzt dlient makes a terrible Yarn client -- I would even go so far as to say it's not very well maintained either as it has been broken for some time 😢
Yes we can raise a PR against the original reference client -- But I'm not convinced it'll get accepted 😢
@shreyan Thanks for your encouraging words 🤗
I also agree that buckket's twtzt dlient makes a terrible Yarn client -- I would even go so far as to say it's not very well maintained either as it has been broken for some time 😢
Yes we can raise a PR against the original reference client -- But I'm not convinced it'll get accepted 😢
@prologic I also feel it's not well maintained, when I tried to use it a lot of things felt pretty broken - no public nick, config not in the twtxt.txt, following list stored separately, etc...
might even be best to just create a fork
@shreyan I am actually seriously considering forking the spec and putting this to the community.
One of the motivating reasons to do this (besides to avoid the continued hostility) is we don't share the same goals or visions.
Decentralized microBlogging is for all (not just retro enthusiasts and hackers)
@shreyan I am actually seriously considering forking the spec and putting this to the community.
One of the motivating reasons to do this (besides to avoid the continued hostility) is we don't share the same goals or visions.
Decentralized microBlogging is for all (not just retro enthusiasts and hackers)
@shreyan I am actually seriously considering forking the spec and putting this to the community.
One of the motivating reasons to do this (besides to avoid the continued hostility) is we don't share the same goals or visions.
Decentralized microBlogging is for all (not just retro enthusiasts and hackers)
@prologic it does feel odd that public nicks and metadata are in an extension and not the main spec /cc @shreyan
@funbreaker The original spec was very lax on specifics and details. I guess it was never intended to be used as a decentralized social media ecosystem 😆 Which has been made quite clear by the few that are strongly outspoken and don't want this. 🤦♂️ and/or unsupportive of any other uses (despite the open spec and "fork me" badge 🤣)
@funbreaker The original spec was very lax on specifics and details. I guess it was never intended to be used as a decentralized social media ecosystem 😆 Which has been made quite clear by the few that are strongly outspoken and don't want this. 🤦♂️ and/or unsupportive of any other uses (despite the open spec and "fork me" badge 🤣)
@funbreaker The original spec was very lax on specifics and details. I guess it was never intended to be used as a decentralized social media ecosystem 😆 Which has been made quite clear by the few that are strongly outspoken and don't want this. 🤦♂️ and/or unsupportive of any other uses (despite the open spec and "fork me" badge 🤣)