# 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 19
# self = https://watcher.sour.is/conv/nc6duqq
@jlj Your ctrl-c.club email doesn't sppear to be working and I have no other way to reach a private message to you 🤣 -- We need to get private inter-pod messaging working, it's really a missing features in my opinion that use it's own set of merits, like reaching someone without blasting out a public social media Yarn or two 🤣
@jlj Your ctrl-c.club email doesn't sppear to be working and I have no other way to reach a private message to you 🤣 -- We need to get private inter-pod messaging working, it's really a missing features in my opinion that use it's own set of merits, like reaching someone without blasting out a public social media Yarn or two 🤣
@prologic Yeah, slowly coming to that realisation, re email. Think it's been down for a few weeks. Sent you a replacement. In the meantime, yeah, I'm stepping back from my original opposition to the private messaging... Well, I think it was @adi who really didn't like it, wasn't it? Anyway, yeah, agreed: there are certainly use cases.
@jlj Nope can't reply to that email either :/
> 524 5.2.4 Mailing list expansion problem
@jlj Nope can't reply to that email either :/
> 524 5.2.4 Mailing list expansion problem
@jlj Nope can't reply to that email either :/\n\n> 524 5.2.4 Mailing list expansion problem
@prologic @jlj I've been opposing adding DM/chat to yarn, because there already are sooo many chat services out there, so no need to reinvent the wheel. Also having to stay on top of yet another inbox is something i would like to avoid. Though if we can come up with some way of relaying/forwarding the DMs to whatever service you prefer, like just sending a email to the users existing account seem like a good option or to build in support for delta.chat that just uses email for chat.
@prologic @jlj I've been opposing adding DM/chat to yarn, because there already are sooo many chat services out there and having to stay on top of yet another inbox is something i would like to avoid. Though if we can come up with some way of relaying/forwarding the DMs to whatever service you prefer, like just sending a email to the users existing account seem like a good option or to build in support for delta.chat that just uses email for chat.
@darch @jlj Yes well what we initially build isn't complete. But when I get around to polishing it off we'll more than likely integrate with something, it may very well stay as SMTP/POP3 based services with mbox/Maildir backend formats for messages. I can't think of anything else that is more prevalent that works or can be made to work with other things? At least this way you _could_ just pull messages into whatever favourite Mail client you prefer to use.
@darch @jlj Yes well what we initially build isn't complete. But when I get around to polishing it off we'll more than likely integrate with something, it may very well stay as SMTP/POP3 based services with mbox/Maildir backend formats for messages. I can't think of anything else that is more prevalent that works or can be made to work with other things? At least this way you _could_ just pull messages into whatever favourite Mail client you prefer to use.
@prologic That's some grisly dogfood. ;-) Third time's a charm?
@darch Ah, right; knew someone coherently objected. ;-) Yeah, I hear you; some relaying / forwarding would be nice.\n\n(I love Delta Chat!)
The issue I have with any kind of forwarding/relay is I wish to avoid storing and kind of PII on Yarn pods. So much like how Twtxt clients work in the first place, I'd err on the side of "pulling" messages rather than forwarding to something stored on a user's account.
The issue I have with any kind of forwarding/relay is I wish to avoid storing and kind of PII on Yarn pods. So much like how Twtxt clients work in the first place, I'd err on the side of "pulling" messages rather than forwarding to something stored on a user's account.
@prologic Ah, yes, excellent point; love that about pods.