# 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 25
# self = https://watcher.sour.is/conv/pdlvy3q
I dunno π€·ββοΈ But this guy/gal is π€£ I had to double-check time zones and his/her feed file/uri to be sure, but I'm 99.9% sure they are writing to their twtxt.txt feed file with a timestamp in the future π€£
I dunno π€·ββοΈ But this guy/gal is π€£ I had to double-check time zones and his/her feed file/uri to be sure, but I'm 99.9% sure they are writing to their twtxt.txt feed file with a timestamp in the future π€£
I dunno π€·ββοΈ But this guy/gal is π€£ I had to double-check time zones and his/her feed file/uri to be sure, but I'm 99.9% sure they are writing to their twtxt.txt feed file with a timestamp in the future π€£
But they don't follow me, so we'll never know for sure π\n\n 
But they don't follow me, so we'll never know for sure π
But they don't follow me, so we'll never know for sure π\n\n
But they don't follow me, so we'll never know for sure π
@prologic but how do they control when they write?
@prologic but how do they control when they write?
Hahaha π€£ I _know_ you're just being funny here, but I _believe_ they are literally just writing a timestamp/date that is in the future to their feed twtxt.txt file π
Hahaha π€£ I _know_ you're just being funny here, but I _believe_ they are literally just writing a timestamp/date that is in the future to their feed twtxt.txt file π
Hahaha π€£ I _know_ you're just being funny here, but I _believe_ they are literally just writing a timestamp/date that is in the future to their feed twtxt.txt file π
@prologic I'm not. I seriously want to know how
@prologic I'm not. I seriously want to know how
itβs a really good way of pinning a Twt at the top of the timeline bar isnβt it? π€£
itβs a really good way of pinning a Twt at the top of the timeline bar isnβt it? π€£
itβs a really good way of pinning a Twt at the top of the timeline bar isnβt it? π€£
@prologic but seriously. How do people write custom timestamps on twtxt or goryon? Or are they using a custom client? I actually honestly don't know, and I'm probably missing something extremely obvious here.
@prologic but seriously. How do people write custom timestamps on twtxt or goryon? Or are they using a custom client? I actually honestly don't know, and I'm probably missing something extremely obvious here.
@lyxal Yeah they are using their own "client" -- Or client here is a rather loose term, since Twtxt itself is just _really_ a twtxt.txt file hosted somewhere. What you you use here is a multi-user backend with API and a nice Mobile App (Goryon) to go along with. But under the hood it still manages a set of twtxt.txt files in /data/feeds/<username>. But no, you're right it would not be possible for any user to artificially go and post something in the future here, that would be silly, since you don't have _direct_ access to the file per se. Although...
@lyxal Yeah they are using their own "client" -- Or client here is a rather loose term, since Twtxt itself is just _really_ a twtxt.txt file hosted somewhere. What you you use here is a multi-user backend with API and a nice Mobile App (Goryon) to go along with. But under the hood it still manages a set of twtxt.txt files in /data/feeds/<username>. But no, you're right it would not be possible for any user to artificially go and post something in the future here, that would be silly, since you don't have _direct_ access to the file per se. Although...
@lyxal Yeah they are using their own "client" -- Or client here is a rather loose term, since Twtxt itself is just _really_ a twtxt.txt file hosted somewhere. What you you use here is a multi-user backend with API and a nice Mobile App (Goryon) to go along with. But under the hood it still manages a set of twtxt.txt files in /data/feeds/<username>. But no, you're right it would not be possible for any user to artificially go and post something in the future here, that would be silly, since you don't have _direct_ access to the file per se. Although...
... That _might_ change with some upcoming changes to the API and the twt command-line client where I will probably add things like twt sync that can sync between a local twtxt.txt file and your Twt.social account on the pod where your account lives.
... That _might_ change with some upcoming changes to the API and the twt command-line client where I will probably add things like twt sync that can sync between a local twtxt.txt file and your Twt.social account on the pod where your account lives.
... That _might_ change with some upcoming changes to the API and the twt command-line client where I will probably add things like twt sync that can sync between a local twtxt.txt file and your Twt.social account on the pod where your account lives.