# 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 8
# self = https://watcher.sour.is/conv/5g3aloq
@slashdot Yhe solution to “social media” is still to have no algorithms at all.
@slashdot Yhe solution to “social media” is still to have no algorithms at all.
@slashdot Yhe solution to “social media” is still to have no algorithms at all.
@slashdot @prologic Reminds me of one of the ssb devs saying "ssb does have an algorithm: chronological ordering"
@will @slashdot Yeah! We do too 🤣 Technically (_I guess?_) we have two? Chronological ordering and Twts will eventually fall off the active global cache once we reach MaxCacheTTL or MaxCacheItems... This serves two purposes:

* Keeps pod's memory utilisation at a steady constant depending on no. of active pod users.
* Provides a minimal "plausible deniability" in that Twts do not remain hanging around permanently._
@will @slashdot Yeah! We do too 🤣 Technically (_I guess?_) we have two? Chronological ordering and Twts will eventually fall off the active global cache once we reach MaxCacheTTL or MaxCacheItems... This serves two purposes:\n\n* Keeps pod's memory utilisation at a steady constant depending on no. of active pod users.\n* Provides a minimal "plausible deniability" in that Twts do not remain hanging around permanently._
@will @slashdot Yeah! We do too 🤣 Technically (_I guess?_) we have two? Chronological ordering and Twts will eventually fall off the active global cache once we reach MaxCacheTTL or MaxCacheItems... This serves two purposes:

* Keeps pod's memory utilisation at a steady constant depending on no. of active pod users.
* Provides a minimal "plausible deniability" in that Twts do not remain hanging around permanently._
@will @slashdot Yeah! We do too 🤣 Technically (_I guess?_) we have two? Chronological ordering and Twts will eventually fall off the active global cache once we reach MaxCacheTTL or MaxCacheItems... This serves two purposes:\n\n* Keeps pod's memory utilisation at a steady constant depending on no. of active pod users.\n* Provides a minimal "plausible deniability" in that Twts do not remain hanging around permanently._