# 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 7
# self = https://watcher.sour.is/conv/tb66tsq
How's the protocol licensed? MIT right?
@adi I _think_ the Twtxt spec and the TBD Twtxtv2 specs _should_ be licensed differently. I'm not even sure what the original Twtxt spec is licensed under in the first place. What is the common licensing for open specs / protocols like RFC(s) in the first place? 🤔\n\n> Also we should refer to what Yarn.social uses as the Twtxt or Twtxtv2 spec, the **protocol** is strictly HTTP over TLS / HTTPS (_in fact we kind of enforce this to a certain degree_).
@adi I _think_ the Twtxt spec and the TBD Twtxtv2 specs _should_ be licensed differently. I'm not even sure what the original Twtxt spec is licensed under in the first place. What is the common licensing for open specs / protocols like RFC(s) in the first place? 🤔
> Also we should refer to what Yarn.social uses as the Twtxt or Twtxtv2 spec, the **protocol** is strictly HTTP over TLS / HTTPS (_in fact we kind of enforce this to a certain degree_).
@adi I _think_ the Twtxt spec and the TBD Twtxtv2 specs _should_ be licensed differently. I'm not even sure what the original Twtxt spec is licensed under in the first place. What is the common licensing for open specs / protocols like RFC(s) in the first place? 🤔
> Also we should refer to what Yarn.social uses as the Twtxt or Twtxtv2 spec, the **protocol** is strictly HTTP over TLS / HTTPS (_in fact we kind of enforce this to a certain degree_).