# 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 4
# self = https://watcher.sour.is/conv/z5ucsza
prologic
twtxt.net
View Thread
Speaking of Git hosting / forges / thingies... I just realised that the way in which sr.ht manages patches is _actually_ very similar to what I had in mind, at least conceptually. And... it looks like they somehow have figured out a way to represent whether or not the patches were applied in this nifty Web UI -- If you follow the link to a proposed patch for example you also get another nice interface explaining how to deal with the patch -- As well as a nifty (if you expand it out) little CLI snippet you can paste into your Terminal like:


$ curl -s https://lists.sr.ht/~migadu/alps-devel/patches/36196/mbox | git am -3


Neat! 👌 Some good inspiration to draw from there... (even if I still don't like the idea of using Email).
prologic
twtxt.net
View Thread
Speaking of Git hosting / forges / thingies... I just realised that the way in which sr.ht manages patches is _actually_ very similar to what I had in mind, at least conceptually. And... it looks like they somehow have figured out a way to represent whether or not the patches were applied in this nifty Web UI -- If you follow the link to a proposed patch for example you also get another nice interface explaining how to deal with the patch -- As well as a nifty (if you expand it out) little CLI snippet you can paste into your Terminal like:


$ curl -s https://lists.sr.ht/~migadu/alps-devel/patches/36196/mbox | git am -3


Neat! 👌 Some good inspiration to draw from there... (even if I still don't like the idea of using Email).
prologic
twtxt.net
View Thread
Speaking of Git hosting / forges / thingies... I just realised that the way in which sr.ht manages patches is _actually_ very similar to what I had in mind, at least conceptually. And... it looks like they somehow have figured out a way to represent whether or not the patches were applied in this nifty Web UI -- If you follow the link to a proposed patch for example you also get another nice interface explaining how to deal with the patch -- As well as a nifty (if you expand it out) little CLI snippet you can paste into your Terminal like:


$ curl -s https://lists.sr.ht/~migadu/alps-devel/patches/36196/mbox | git am -3


Neat! 👌 Some good inspiration to draw from there... (even if I still don't like the idea of using Email).
prologic
twtxt.net
View Thread
Speaking of Git hosting / forges / thingies... I just realised that the way in which sr.ht manages patches is _actually_ very similar to what I had in mind, at least conceptually. And... it looks like they somehow have figured out a way to represent whether or not the patches were applied in this nifty Web UI -- If you follow the link to a proposed patch for example you also get another nice interface explaining how to deal with the patch -- As well as a nifty (if you expand it out) little CLI snippet you can paste into your Terminal like:


$ curl -s https://lists.sr.ht/~migadu/alps-devel/patches/36196/mbox | git am -3


Neat! 👌 Some good inspiration to draw from there... (even if I still don't like the idea of using Email).