# 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 9
# self = https://watcher.sour.is/conv/nrp4ywq
> It is optional as well - so if one does not want it - just not turn that feature on.
If we decide that the benefits outweigh the risks and accept that differences (even though we'll do our best to bridge the gaps) -- we'll have to make "Enabling" / "Disabling" an actual thing. being an experimental feature flag is not enough, feature flags are designed to be short-lived until promoted, or decided against.
The question then becomes more along the lines of:
- Do we want a toggle for Activity Pub at the Pod level? (I assume yes)
- Do we want a toggle for Activity Pub discovery at the User level?
> It is optional as well - so if one does not want it - just not turn that feature on.
If we decide that the benefits outweigh the risks and accept that differences (even though we'll do our best to bridge the gaps) -- we'll have to make "Enabling" / "Disabling" an actual thing. being an experimental feature flag is not enough, feature flags are designed to be short-lived until promoted, or decided against.
The question then becomes more along the lines of:
- Do we want a toggle for Activity Pub at the Pod level? (I assume yes)
- Do we want a toggle for Activity Pub discovery at the User level?
> It is optional as well - so if one does not want it - just not turn that feature on.
If we decide that the benefits outweigh the risks and accept that differences (even though we'll do our best to bridge the gaps) -- we'll have to make "Enabling" / "Disabling" an actual thing. being an experimental feature flag is not enough, feature flags are designed to be short-lived until promoted, or decided against.
The question then becomes more along the lines of:
- Do we want a toggle for Activity Pub at the Pod level? (I assume yes)
- Do we want a toggle for Activity Pub discovery at the User level?
> It is optional as well - so if one does not want it - just not turn that feature on.
If we decide that the benefits outweigh the risks and accept that differences (even though we'll do our best to bridge the gaps) -- we'll have to make "Enabling" / "Disabling" an actual thing. being an experimental feature flag is not enough, feature flags are designed to be short-lived until promoted, or decided against.
The question then becomes more along the lines of:
- Do we want a toggle for Activity Pub at the Pod level? (I assume yes)
- Do we want a toggle for Activity Pub discovery at the User level?
@prologic personally I think it should be there at user level for sure - that way ActivityPub-averse yarn users can join any pod and then decide for themselves whether they want ActivityPub or not, without requiring a pod owner to turn it off for everyone in the pod.