# 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 13
# self = https://watcher.sour.is/conv/pqhbula
@doesnm finally someone read my blogpost ;)
@doesnm finally someone read my blogpost ;)
@doesnm finally someone read my blogpost ;)
@doesnm finally someone read my blogpost ;)
@doesnm like OP, that will not work, as it has wrong/incomplete information.
Well, as for a new UUID it's a thought to combine the timestamp+username or timestamp+url to create a unique id. In this scenario I think the first would probably be favourable. This way if someone decides to use a different url (most likely they will stick to their nickname) UUID's will still hold up.
Adding to that, we could implement a version variable in the meta, adapt code to either read the old or new format UUID, so older threads won't break.
@Codebuzz I really like this idea of just using the Feed's # nick as a sort of "identifier". This gets us out of this mess of when feeds move locations or authors decide to host on 3 or 4 different protocols 🤣 Downside? Something picks the same nick? (_they'll still hash differently, so that's fine_).
@Codebuzz I really like this idea of just using the Feed's # nick as a sort of "identifier". This gets us out of this mess of when feeds move locations or authors decide to host on 3 or 4 different protocols 🤣 Downside? Something picks the same nick? (_they'll still hash differently, so that's fine_).
@prologic yeah short Nick is going to be unique enough. There is always olong Nick that adds the domain for differentiation.