# 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 17
# self = https://watcher.sour.is/conv/4to7qbq
@prologic just an off the wall question about hashes. why not use the time+message as it was in the original twtxt.txt file? is it because it's just not store anyplace?
also how set in stone is using user+url? vs user@domain? the latter would mean the url could change without invalidating the hash.
@xuu Hmmm The problem with using the domain is there’s no standardization around where you can host your feed
@xuu Hmmm The problem with using the domain is there’s no standardization around where you can host your feed
@xuu Hmmm The problem with using the domain is there’s no standardization around where you can host your feed
also it’s worth noting but the hush of previously created content doesn’t actually change so if you change your feed URL it only affects you post going forward
also it’s worth noting but the hush of previously created content doesn’t actually change so if you change your feed URL it only affects you post going forward
also it’s worth noting but the hush of previously created content doesn’t actually change so if you change your feed URL it only affects you post going forward
or in other words it’s only a content post addressing not an identity of the user
or in other words it’s only a content post addressing not an identity of the user
or in other words it’s only a content post addressing not an identity of the user
@prologic I see.. so using an ec25519 key as identity? and some kind of certificate to define the location of a feed? or maybe a DHT like Kademlia? TwTorrent ;)
@prologic I see.. so using an ec25519 key as identity? and some kind of certificate to define the location of a feed? or maybe a DHT like Kademlia? TwTorrent ;)
@prologic I see.. so using an ec25519 key as identity? and some kind of certificate to define the location of a feed? or maybe a DHT like Kademlia? TwTorrent ;)
@prologic I see.. so using an ec25519 key as identity? and some kind of certificate to define the location of a feed? or maybe a DHT like Kademlia? TwTorrent ;)
@xuu Haha let’s keep it simple ! I always have two goals in mind a) compatibility with plain old Twtxt or simple enough to adopt and b) easy for the average non-technical person
@xuu Haha let’s keep it simple ! I always have two goals in mind a) compatibility with plain old Twtxt or simple enough to adopt and b) easy for the average non-technical person
@xuu Haha let’s keep it simple ! I always have two goals in mind a) compatibility with plain old Twtxt or simple enough to adopt and b) easy for the average non-technical person