# 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 7
# self = https://watcher.sour.is/conv/g7eelyq
QOTD: What are your thoughts on nostr?
@mckinley full of crypto spam. Slow. Bad UI’s.
@mckinley Brings up a few interesting points. But I fear it's a rather complicated protocol. I read through a few pages on that site, but I haven't seen a real specification for it. I immediately thought that you can't really change your keys without losing your identity. Basically the same as with changing feed URLs over here. Maybe slightly better, but not much.
@lyse
>I fear it’s a rather complicated protocol.
The core protocol looks very simple but I'm sure you can get in the weeds with extensions.
>you can’t really change your keys without losing your identity
I think you're right but that seems reasonable to me. Your public key *is* your identity, similar to certain cryptocurrencies or Tor hidden services. Why would you want to change your key without changing your identity?
Something I've noticed about the Nostr people is that they aren't the same as the software minimalism people. It seems like it's all JavaScript, Go, and Rust with dependency counts in the hundreds.
@mckinley My goodness, 99 specifications!? I'm out.
Maybe some people want to periodically change their keys or if your private key is lost or leaked, you also need a new one. But yeah, you're right. You have to draw a line somewhere.