# 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 11
# self = https://watcher.sour.is/conv/zsblufa
@darch Isn't that basically the same argument as @fastidious had just now? 🤔
> 100% agreed. Let’s not be apprentice of many, master of none.
I'm not sure 😂
@darch Isn't that basically the same argument as @fastidious had just now? 🤔\n\n> 100% agreed. Let’s not be apprentice of many, master of none.\n\nI'm not sure 😂
@darch Isn't that basically the same argument as @fastidious had just now? 🤔
> 100% agreed. Let’s not be apprentice of many, master of none.
I'm not sure 😂
@prologic not sure I understand what you mean here...?!
@darch Let me explain then... I've often had discussions with colleagues about "decentralised" social media and how you could also incorporate things like "events". The problem though is that if you want it to be a closed event, with you know sensitive information like "let's all meet at this address for xyz" it becomes quite hard and borderline dangerous.
Bottom line is I (_after much convncing_) do tend to think the same way as the other folks here, "less is more" and "focus" on the things you're good at that are of "high quality". Perhaps events can be an external?
@darch Let me explain then... I've often had discussions with colleagues about "decentralised" social media and how you could also incorporate things like "events". The problem though is that if you want it to be a closed event, with you know sensitive information like "let's all meet at this address for xyz" it becomes quite hard and borderline dangerous.
Bottom line is I (_after much convncing_) do tend to think the same way as the other folks here, "less is more" and "focus" on the things you're good at that are of "high quality". Perhaps events can be an external?
@darch Let me explain then... I've often had discussions with colleagues about "decentralised" social media and how you could also incorporate things like "events". The problem though is that if you want it to be a closed event, with you know sensitive information like "let's all meet at this address for xyz" it becomes quite hard and borderline dangerous.\n\nBottom line is I (_after much convncing_) do tend to think the same way as the other folks here, "less is more" and "focus" on the things you're good at that are of "high quality". Perhaps events can be an external?
We have to remember as well that this isn't just about the web interface that most of you see and interactive with. There is a mobile app I'm hard at work with improving and getting "production ready". There is a command-line client/app too. And all the while we're trying very hard to maintain as much compatibility with Twtxt itself without breaking "old" clients too badly.
We have to remember as well that this isn't just about the web interface that most of you see and interactive with. There is a mobile app I'm hard at work with improving and getting "production ready". There is a command-line client/app too. And all the while we're trying very hard to maintain as much compatibility with Twtxt itself without breaking "old" clients too badly.
Gotcha, my idea was only to provide announcement about the events. All the rspv data should not be part of the yarn/twtxt ecosystem. I would link to something like gath.io or facebook events for this
