# 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 13
# self = https://watcher.sour.is/conv/oyvxhoa
The /metrics endpoint is there for the operator, so you can monitor/measure your pod's performance and adjust accordingly, or file bug reports for me to fix broken shit™ 🤣 -- It is never pushed anywhere, only pulled. And I only ever pull two key pieces out dao and mao of known single and multi-user pods, but I ASK beforehand 🤣 -- For example I'm not pulling DAU and MAO stats from @kaniyama_t 's Twitter2 pod because I never got a response to whether I could or not 😅
The /metrics endpoint is there for the operator, so you can monitor/measure your pod's performance and adjust accordingly, or file bug reports for me to fix broken shit™ 🤣 -- It is never pushed anywhere, only pulled. And I only ever pull two key pieces out dao and mao of known single and multi-user pods, but I ASK beforehand 🤣 -- For example I'm not pulling DAU and MAO stats from @kaniyama_t 's Twitter2 pod because I never got a response to whether I could or not 😅
The /metrics endpoint is there for the operator, so you can monitor/measure your pod's performance and adjust accordingly, or file bug reports for me to fix broken shit™ 🤣 -- It is never pushed anywhere, only pulled. And I only ever pull two key pieces out dao and mao of known single and multi-user pods, but I ASK beforehand 🤣 -- For example I'm not pulling DAU and MAO stats from @kaniyama_t 's Twitter2 pod because I never got a response to whether I could or not 😅
The /metrics endpoint is there for the operator, so you can monitor/measure your pod's performance and adjust accordingly, or file bug reports for me to fix broken shit™ 🤣 -- It is never pushed anywhere, only pulled. And I only ever pull two key pieces out dao and mao of known single and multi-user pods, but I ASK beforehand 🤣 -- For example I'm not pulling DAU and MAO stats from @kaniyama_t 's Twitter2 pod because I never got a response to whether I could or not 😅
@prologic I will play devil’s advocate. The telemetry being proposed for the go tool chain is opt-out. I think opt-out is better that being “based on honour”. It is also meant to “see, and fix broken shit” 😜😂

Also, I bet most running Yarn do not even know about it. 😬😂
@bender You make an excellent point. I might just put it behind an --enable-metrics flag 🤔
@bender You make an excellent point. I might just put it behind an --enable-metrics flag 🤔
@bender You make an excellent point. I might just put it behind an --enable-metrics flag 🤔
@bender You make an excellent point. I might just put it behind an --enable-metrics flag 🤔
Although performance metrics that measure CPU, Memory and such aren't really the same thing as "telemetry"
Although performance metrics that measure CPU, Memory and such aren't really the same thing as "telemetry"
Although performance metrics that measure CPU, Memory and such aren't really the same thing as "telemetry"
Although performance metrics that measure CPU, Memory and such aren't really the same thing as "telemetry"