# 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/a5kjj2q
I didn’t express myself very well earlier when mentioning muting abucci. I muted to stop myself from saying anything regretful (which would be a waste of my time and theirs). Also, I try to make all mutes temporary.
@brasshopper Noted. On slightly different note, I'm very happy with the tools we've built and the fact we've managed to avoid "moderation" really. I hope it stay that way 🤞
@brasshopper Noted. On slightly different note, I'm very happy with the tools we've built and the fact we've managed to avoid "moderation" really. I hope it stay that way 🤞
Not to mention that "moderation" in a 'decentralised" system is kind of silly IMO 😅
Not to mention that "moderation" in a 'decentralised" system is kind of silly IMO 😅
@prologic This is something I really like about this model. Your twts are still your own. You can at-mention whoever you like however much you like. They just don’t have to listen. Of course, if you’re on someone else’s instance, then it gets a bit more complicated. But at least it’s _possible_ to move to your own.
@brasshopper Same functionality exists for users on pods too 👌 -- You can either Unfollow or Mute or both -- You can even Hide Twts and entire threads too!
@brasshopper Same functionality exists for users on pods too 👌 -- You can either Unfollow or Mute or both -- You can even Hide Twts and entire threads too!
@prologic yeah I gotcha. I was saying that ownership of one’s twts are a bit more complicated when they’re one someone else’s instance. The instance owner could, for example, delete the feed of someone who was behaving badly. If they hadn’t backed up their feed, might be game over for all those twts.
@brasshopper Ahh yea I see: But like you said you can download it, mode it or run your own pod 👌 Nothing proprietary or closed source here 🤗 -- Speaking of which... I'm open to ideas that make taking your feed with you easier and what not ...
@brasshopper Ahh yea I see: But like you said you can download it, mode it or run your own pod 👌 Nothing proprietary or closed source here 🤗 -- Speaking of which... I'm open to ideas that make taking your feed with you easier and what not ...
@prologic That’s why I was so excited about search the other day. I was thinking about the possibility of hosting my twtxt on IPFS which would mean effectively hosting it on no machine in particular. (It would change over time and could be multiple at the same time.) However, this would prevent me from knowing my own followers because the request log would be spread out across many nodes which most definitely wouldn’t share their user agent logs with me. That’s not great but perhaps it doesn’t matter. I personally only care about knowing my own followers so that I find people who mention me that I don’t happen to also follow. This is where search/registries would be really valuable. I could just periodically search various indexes/registries for mentions. I feel like this could have a benefit of keeping trolls at a distance. If I only search once an hour and put them in a separate queue, I can handle people outside my circle differently.
@brasshopper Makes sense, and something I plan to improve upon. Know anyone that could contribute some Go code to improve the search engine I built? 🤔
@brasshopper Makes sense, and something I plan to improve upon. Know anyone that could contribute some Go code to improve the search engine I built? 🤔