# 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/ecbxzkq
We:

- Drop # url= from the spec.
- We don't adopt # uuid = -- Something @anth also mentioned (_see below_)

We instead use the @nick@domain to identify your feed in the first place and use that as the identify when calculating Twt hashes <id> + <timestamp> + <content>. Now in an ideal world I also agree, use WebFinger for this and expect that for the most part you'll be doing a WebFinger lookup of @user@domain to fetch someone's feed in the first place.

The only problem with WebFinger is should this be mandated or a recommendation?
We:

- Drop # url= from the spec.
- We don't adopt # uuid = -- Something @anth also mentioned (_see below_)

We instead use the @nick@domain to identify your feed in the first place and use that as the identify when calculating Twt hashes <id> + <timestamp> + <content>. Now in an ideal world I also agree, use WebFinger for this and expect that for the most part you'll be doing a WebFinger lookup of @user@domain to fetch someone's feed in the first place.

The only problem with WebFinger is should this be mandated or a recommendation?
Can i change identify without ruining federation? it is important because i can change server and want migrate all my data
Wait, webfinger? Mandate this ruin philosophy "twtxt is just text file"
@doesnm Like now?
@doesnm Like now?
@prologic How is nick@domain any better than a feed URL? Changing the nick now also breaks threading. That's even worse than the current approach. Also, there might be multiple feeds with same nicks on one domain, e.g. on free hosters.
@lyse Yup you're right, it's s terrible idea 💡
@lyse Yup you're right, it's s terrible idea 💡
Probably the best idea I've heard/seen si far is @anth's idea of a feed having a uuid # uuid = (_if present_) otherwise just falling back to the URL you fetched it from and dropping the idea of a feed # url = entirely.
Probably the best idea I've heard/seen si far is @anth's idea of a feed having a uuid # uuid = (_if present_) otherwise just falling back to the URL you fetched it from and dropping the idea of a feed # url = entirely.