# 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 196263 # self = https://watcher.sour.is?offset=181358 # next = https://watcher.sour.is?offset=181458 # prev = https://watcher.sour.is?offset=181258
Bush fire sunsets are the nicest
[0]). A syntax like the following could help to know what public key you used to encrypt the message, and which private key the client should use to decrypt it:
!<nick url> <encrypted_message> <public_key_hash_7_chars>
[0] https://www.brandonchecketts.com/archives/its-2023-you-should-be-using-an-ed25519-ssh-key-and-other-current-best-practices
twtxt (for now), although I see the community could be interested in.timeline https://github.com/sorenpeter/timeline/discussions
Some people send "get better" messages, but someone sent me some flowers, so I have something to look at during recovery. This picture shows a white and a pink flower from that bunch.
Some people send "get better" messages, but someone sent me some flowers, so I have something to look at during recovery. This picture shows a white and a pink flower from that bunch.