# 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 14
# self = https://watcher.sour.is/conv/pftowua
Whay if instead of a static “Your timeline is empty try the Discover tab…” We just build an automated bot that greets new users on a pod then goes away? 🤔
Whay if instead of a static “Your timeline is empty try the Discover tab…” We just build an automated bot that greets new users on a pod then goes away? 🤔
@prologic Funny you should say that because I when I was first bringing https://we.loveprivacy.club to life I had a similar thought, but then with the new static discovery thing and also the option to switch on public viewing of the cached posts I didn't think of it any more, thinking it would probably just be extra complexity at the time. I guess the question is how difficult (or not) would it be to implement? I like the idea personally.
@eldersnake From a technical perspective it would require adding a new model to the internal database so users can store/create lists of feeds and group them, giving them a name, etc. Then it would simply be a matter of for each list, pulling up all entries out of the feed cache matching the uri(s) in the list and constructing a "custom" timeline. So really not hard at all, the hardest part is actually building the new UI and Model to store the list of feeds and naming the list in the first place 😂
@eldersnake From a technical perspective it would require adding a new model to the internal database so users can store/create lists of feeds and group them, giving them a name, etc. Then it would simply be a matter of for each list, pulling up all entries out of the feed cache matching the uri(s) in the list and constructing a "custom" timeline. So really not hard at all, the hardest part is actually building the new UI and Model to store the list of feeds and naming the list in the first place 😂
@prologic I was referring to the automated bot, not the custom lists 😁
@eldersnake D’oh 🤦♂️ Serves me right trying to respond with 5hrs sleep 😴
@eldersnake D’oh 🤦♂️ Serves me right trying to respond with 5hrs sleep 😴
To answer your question though on new account creation I could just inject a bunch of Twts into the user’s timeline that would disappear the moment their timeline gets populated.
To answer your question though on new account creation I could just inject a bunch of Twts into the user’s timeline that would disappear the moment their timeline gets populated.