# 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 15
# self = https://watcher.sour.is/conv/vc6fcta
🤔 Q: Should yarnd impose a limit of four or five posts per minute, either from the Web App or the API?
🤔 Q: Should yarnd impose a limit of four or five posts per minute, either from the Web App or the API?
🤔 Q: Should yarnd impose a limit of four or five posts per minute, either from the Web App or the API?
🤔 Q: Should yarnd impose a limit of four or five posts per minute, either from the Web App or the API?
@prologic to combat spam and badly implement clients? Is the issue really that big? Also I cloud be turn on/off under the poderator settings, maybe as a feature flag
@prologic to combat spam and badly implement clients? Is the issue really that big? Also it cloud be turned on/off under the poderator settings, maybe as a feature flag
@darch All good questions, in order:
- no
- yes
@darch All good questions, in order:
- no
- yes
@darch All good questions, in order:
- no
- yes
@darch All good questions, in order:
- no
- yes
@darch Oh it is a future problem we _will_ eventually have. It _would_ be considered an abuse of a pod and a disruption to others to "post too fast", but I _think_ yarnd should have a configurable hard limit of what this _should be_ with a sensible default.
I'll write up an issue referencing this Yarn and implement it as a feature flag at some point (_no rush on this one, we're still quite small_).
@darch Oh it is a future problem we _will_ eventually have. It _would_ be considered an abuse of a pod and a disruption to others to "post too fast", but I _think_ yarnd should have a configurable hard limit of what this _should be_ with a sensible default.
I'll write up an issue referencing this Yarn and implement it as a feature flag at some point (_no rush on this one, we're still quite small_).
@darch Oh it is a future problem we _will_ eventually have. It _would_ be considered an abuse of a pod and a disruption to others to "post too fast", but I _think_ yarnd should have a configurable hard limit of what this _should be_ with a sensible default.
I'll write up an issue referencing this Yarn and implement it as a feature flag at some point (_no rush on this one, we're still quite small_).
@darch Oh it is a future problem we _will_ eventually have. It _would_ be considered an abuse of a pod and a disruption to others to "post too fast", but I _think_ yarnd should have a configurable hard limit of what this _should be_ with a sensible default.
I'll write up an issue referencing this Yarn and implement it as a feature flag at some point (_no rush on this one, we're still quite small_).