# 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 12
# self = https://watcher.sour.is/conv/sfzohfq
prologic
twtxt.net
View Thread
Also thinking, in order to solve (_for consistency and UX_) "Followers" and "Following" counts in the app, I _might_ just publish those numbers directly in each feed in the preamble metadata (_respecting user privacy settings of course_). What y'all think? cc @lyse Thinking something basica like:


# followers = N


Pods already publish a list of # following = url already, so we can just _count_ that as-is.
prologic
twtxt.net
View Thread
Also thinking, in order to solve (_for consistency and UX_) "Followers" and "Following" counts in the app, I _might_ just publish those numbers directly in each feed in the preamble metadata (_respecting user privacy settings of course_). What y'all think? cc @lyse Thinking something basica like:


# followers = N


Pods already publish a list of # following = url already, so we can just _count_ that as-is.
prologic
twtxt.net
View Thread
It's actually a really simple patch:



Which looks like this:

prologic
twtxt.net
View Thread
It's actually a really simple patch:



Which looks like this:

prologic
twtxt.net
View Thread
It's actually a really simple patch:\n\n \n\nWhich looks like this:\n\n
lyse
lyse.isobeef.org
View Thread
@prologic Doesn't sound too bad to me. :-)
prologic
twtxt.net
View Thread
@lyse Also thinking about another approach following_url and followers_url but this adds extra round-trips on pods to go fetch these rather then just trust the feed authors published numbers. What do you think? 🤔
prologic
twtxt.net
View Thread
@lyse Also thinking about another approach following_url and followers_url but this adds extra round-trips on pods to go fetch these rather then just trust the feed authors published numbers. What do you think? 🤔
lyse
lyse.isobeef.org
View Thread
@prologic Just a number is way good enough. I mean you don't have any possibility to verify these numbers anyway. The author could just provide a forged file at this URL, so just include it in the feed directly, if that's something important. (Personally I don't care about numbers too much.)
prologic
twtxt.net
View Thread
@lyse

> Personally I don’t care about numbers too much

I don't much either in this case, but folks will expect this and it looks kind of bland/empty on the mobile view the way it's presented. Thanks for the opinion, I'm learning to towards an optional set of kv pairs:


# following = N
# followers = N


If blank, clients _shoudl_ display a ?? in place of a number, otherwise display the number as-is.
prologic
twtxt.net
View Thread
@lyse \n\n> Personally I don’t care about numbers too much\n\nI don't much either in this case, but folks will expect this and it looks kind of bland/empty on the mobile view the way it's presented. Thanks for the opinion, I'm learning to towards an optional set of kv pairs:\n\n
\n# following = N\n# followers = N\n
\n\nIf blank, clients _shoudl_ display a ?? in place of a number, otherwise display the number as-is.
prologic
twtxt.net
View Thread
@lyse

> Personally I don’t care about numbers too much

I don't much either in this case, but folks will expect this and it looks kind of bland/empty on the mobile view the way it's presented. Thanks for the opinion, I'm learning to towards an optional set of kv pairs:


# following = N
# followers = N


If blank, clients _shoudl_ display a ?? in place of a number, otherwise display the number as-is.