# 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/3vcgitq
Even if I don’t think JavaScript should go concurrent, because it is great the way it is (and the even loop works well) and if we need concurrency there are others languages, here a great article about the subject: https://webkit.org/blog/7846/concurrent-javascript-it-can-work/
@tkanos JavaScript has been going concurrent, in a way, via web workers for awhile now. Web workers are not standardized and are a glaring security hole, so I block them in my browsers where possible. But a good 1/3 of the web stops working when you do that.

It should have been made truly concurrent long ago, in my opinion, if only to bring ^^ that stuff back under some sort of standard.
true
@abucci Agreed
@abucci Agreed