# 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/2io2uxq
@prologic I just like to see everything that's happening in the twtverse. Although, if the current trends keep up, I'll probably have to switch to the boring old timeline.
Actually, I just had an idea. Would it be feasible to add a configuration option to exclude followed feeds from Discover? That way, we wouldn't have to filter through all the posts we've already read to find new feeds.
Hmm actually I think this may be possible...
Let me have a look 👌
Hmm actually I think this may be possible...
Let me have a look 👌
Yes it actually is possible to do this looking at the way the code and views are constructed. There is actually a per-User "Discover" view that is built on every Cache/Fetch cycle. This _could_ be modified with another "FilterFunc".
What should this User Preference be called? 🤔 How should it behave? 🤔
Yes it actually is possible to do this looking at the way the code and views are constructed. There is actually a per-User "Discover" view that is built on every Cache/Fetch cycle. This _could_ be modified with another "FilterFunc".
What should this User Preference be called? 🤔 How should it behave? 🤔
Maybe is can be called "Filter out Followed"