# 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/grghd3a
It's ok for most encrypted protocols (In salty you can fetch other messages but can't decrypt). Btw i think recipient can be removed so if someone seen message they tried to decypt, if can't - its not message to you
@doesnm That's _actually_ not true, because you'd have to know the target you're interested in, in the first place. Inboxes in Salty.IM are deliberately shahed for this reason. So whilst you _may_ know your own inbox address, etc, I (_as an arbitrary bad actor_) wouldn't easily be able to guess (_let alone brute force_) my way to another inbox address of an interested party.
@doesnm That's _actually_ not true, because you'd have to know the target you're interested in, in the first place. Inboxes in Salty.IM are deliberately shahed for this reason. So whilst you _may_ know your own inbox address, etc, I (_as an arbitrary bad actor_) wouldn't easily be able to guess (_let alone brute force_) my way to another inbox address of an interested party.
It is not possible to remove it, otherwise you do not know that the message is for you. With that information you can't decrypt.
It is not possible to remove it, otherwise you do not know that the message is for you. With that information you can't decrypt.
I made a draft of an "encrypted public messenger", which was basically a Feed for an address derivate from the public ket, let's say 'abcd..eaea'
Anyone could check, "are there any messages for my address?" and you get a whole list of timestamps and encrypted stuff.
Inside the encrypted message is a signature from the sender. That way you 'could' block spam.
Only the owner of the private key could see who sent what, and so...
And even with that my concussion was that users expectations for a private IM might be far away from my experiment.
I made a draft of an "encrypted public messenger", which was basically a Feed for an address derivate from the public ket, let's say 'abcd..eaea'
Anyone could check, "are there any messages for my address?" and you get a whole list of timestamps and encrypted stuff.
Inside the encrypted message is a signature from the sender. That way you 'could' block spam.
Only the owner of the private key could see who sent what, and so...
And even with that my concussion was that users expectations for a private IM might be far away from my experiment.
It's nice to see we're all largely thinking along the same lines. e.g: Salty.im 😅
It's nice to see we're all largely thinking along the same lines. e.g: Salty.im 😅