# 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 1
# self = https://watcher.sour.is/conv/zc4awna
Ask HN: How to study for system design that doesn't include front end/back end?**
I got a system design interview where I was asked to build a pricer for a financial product, then expand it to multiple pricers that might share inputs.
This was not the typical system design interview where you have to deal with APIs / load balancers / latency / etc
I have studied that a lot, but what about these type of general interviews?
* * *
Comments URL: [https://news.ycombinator.com/item?id=43358293](https://news.ycombinator.com/it ... ⌘ Read more*