# 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 14
# self = https://watcher.sour.is/conv/vle23sa
> In case of conflict, consider users over authors over implementors over specifiers over theoretical purity.
โ W3C, HTML Design Principles ยง 3.2 Priority of Constituencies
> In case of conflict, consider users over authors over implementors over specifiers over theoretical purity.
โ W3C, HTML Design Principles ยง 3.2 Priority of Constituencies
Good quote to remember and use in your engineering career ๐
Good quote to remember and use in your engineering career ๐
@prologic Yes! Sadly, I have the feeling that this is rarely adhered to in the wild.
@lyse Well it should be ๐คฃ
@lyse Well it should be ๐คฃ
I like this quote. I also like a new term I've learned recently called "Complexity Budget".
I like this quote. I also like a new term I've learned recently called "Complexity Budget".
@prologic Soooooooo โฆ what wins? Users or the Complexity Budget? ๐
@prologic Soooooooo โฆ what wins? Users or the Complexity Budget? ๐
@prologic Soooooooo โฆ what wins? Users or the Complexity Budget? ๐
@prologic Soooooooo โฆ what wins? Users or the Complexity Budget? ๐
@prologic I like this part better: โOf course, it is preferred to make things better for multiple constituencies at once.โ That should be the aim.
It is worth noting that this comes from a 2007 working draft.