# 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 5
# self = https://watcher.sour.is/conv/thst6wq
@prologic The current state is not perfect, no doubt. Only very few things in fact are. Breaking compatibility doesn't make it a ton better. So I wouldn't bother. :-) I'm convinced that hard forking only increases the barrier of entry.
@lyse I am too. Breaking compatibility or coming up with something completely different to what we already have, and what is already pretty simple would just makes things harder for ordinary folks. What I _think_ we need to largely continue with is hiding much of the complexities away we have today without any new (or very few) additions in terms of specs/extensions or modifications thereof. For example, maybe yarnd (as one client) doesn't have to care about "managing feed aliases" for what a user follows. Maybe we can just automagically work that shit out and not worry about this whole mess of having to rename a feed you follow or unfollow/refollow it just because someone decided to change their # nick = field 😅
@lyse I am too. Breaking compatibility or coming up with something completely different to what we already have, and what is already pretty simple would just makes things harder for ordinary folks. What I _think_ we need to largely continue with is hiding much of the complexities away we have today without any new (or very few) additions in terms of specs/extensions or modifications thereof. For example, maybe yarnd (as one client) doesn't have to care about "managing feed aliases" for what a user follows. Maybe we can just automagically work that shit out and not worry about this whole mess of having to rename a feed you follow or unfollow/refollow it just because someone decided to change their # nick = field 😅
@lyse I am too. Breaking compatibility or coming up with something completely different to what we already have, and what is already pretty simple would just makes things harder for ordinary folks. What I _think_ we need to largely continue with is hiding much of the complexities away we have today without any new (or very few) additions in terms of specs/extensions or modifications thereof. For example, maybe yarnd (as one client) doesn't have to care about "managing feed aliases" for what a user follows. Maybe we can just automagically work that shit out and not worry about this whole mess of having to rename a feed you follow or unfollow/refollow it just because someone decided to change their # nick = field 😅
@lyse I am too. Breaking compatibility or coming up with something completely different to what we already have, and what is already pretty simple would just makes things harder for ordinary folks. What I _think_ we need to largely continue with is hiding much of the complexities away we have today without any new (or very few) additions in terms of specs/extensions or modifications thereof. For example, maybe yarnd (as one client) doesn't have to care about "managing feed aliases" for what a user follows. Maybe we can just automagically work that shit out and not worry about this whole mess of having to rename a feed you follow or unfollow/refollow it just because someone decided to change their # nick = field 😅