# 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/w4chkna
mckinley
twtxt.net
View Thread
@falsifian TLS won't help you if you change your domain name. How will people know if it's really you? Maybe that's not the biggest problem for something with such low stakes as twtxt, but it's a reasonable concern that could be solved using signatures from an unchanging cryptographic key.

This idea is the basis of Nostr. Notes can be posted to many relays and every note is signed with your private key. It doesn't matter where you get the note from, your client can verify its authenticity. That way, relays don't need to be trusted.
falsifian
www.falsifian.org
View Thread
@mckinley Yes, changing domains is be a problem if you tie your identity to an https url. But I also worry about being stuck with a key I can't rotate. Whatever gets used, it would be nice to be able to rotate identities. I like @lyse's idea for that.
prologic
twtxt.net
View Thread
@falsifian You mean the idea of being able to inline # url = changes in your feed?

> Whatever gets used, it would be nice to be able to rotate identities. I like @lyse’s idea for that.
prologic
twtxt.net
View Thread
@falsifian You mean the idea of being able to inline # url = changes in your feed?

> Whatever gets used, it would be nice to be able to rotate identities. I like @lyse’s idea for that.
falsifian
www.falsifian.org
View Thread
@prologic

> (#w4chkna) @falsifian You mean the idea of being able to inline # url = changes in your feed?

Yes, that one. But @lyse pointed out suffers a compatibility issue, since currently the first listed url is used for hashing, not the last. Unless your feed is in reverse chronological order. Heh, I guess another metadata field could indicate which version to use.

Or maybe url changes could somehow be combined with the archive feeds extension? Could the url metadata field be local to each archive file, so that to switch to a new url all you need to do is archive everything you've got and start a new file at the new url?

I don't think it's that likely my feed url will change.
prologic
twtxt.net
View Thread
@falsifian I like this idea too as a completing solution to the "identify problem":

> Or maybe url changes could somehow be combined with the archive feeds extension? Could the url metadata field be local to each archive file, so that to switch to a new url all you need to do is archive everything you’ve got and start a new file at the new url?

👌
prologic
twtxt.net
View Thread
@falsifian I like this idea too as a completing solution to the "identify problem":

> Or maybe url changes could somehow be combined with the archive feeds extension? Could the url metadata field be local to each archive file, so that to switch to a new url all you need to do is archive everything you’ve got and start a new file at the new url?

👌