# 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/uthooyq
htwtxt maybe, but i can't built it (broken?)
@doesnm it's five years old, no updates (abandon-ware, really). I will give it a try to see if I can get it to compile.
@bender + a 9 years old container image by the good ol' buckket himself ... not sure what to expect from that but will give it a quick spin and report back
@bender + a 9 years old container image by the good ol' buckket himself ... not sure what to expect from that but will give it a quick spin and report back
Alright, I gave #htwtxt container a quick spin. The thing lives and feels dead simple, like, echo -e "`date -Im`\\tHello world!" >> twtxt.txt kind of simple but with a GUI. and I LOVE IT! Now let's see if we can rebuild the image with the latest version of htwtxt.
Alright, I gave #htwtxt container a quick spin. The thing lives and feels dead simple, like, echo -e "`date -Im`\tHello world!" >> twtxt.txt kind of simple but with a GUI. and I LOVE IT! Now let's see if we can rebuild the image with the latest version of htwtxt.
Cool! Max 140 characters, LOL.
@bender Yep! Twtxt spec by the letter I guess 🥲
@bender Yep! Twtxt spec by the letter I guess 🥲
@aelaraji you will have to compute hashes by hand, right? How is the timeline, to read from those you follow? I figure it was a nice exercise to raise the dead, but with very little practical purposes, wouldn't you agree? ;-)
@bender highly probably, unless I learn go and implement it myself (or someone else more capable does) ... but I'm so lazy I'd just copy them from twtxt.net and call it a day xD and yeah, it's kinda rough the way things are...
- I don't see a way to follow others, all I can do is go to the /feeds URI for a list of the server's users/feeds.
- I still couldn't figure out how to get a direct link to a user's twtxt file, curling /feeds/usernick spits out a list of the user usernick twts, so I guess you could use that to follow them.
- no way to add in your # nick = usernick / # url = proto://domain.ltd/path/to/twtxt.txt ...etc. Probably because that wasn't part of the spec back then?
So yeah, it would make for a nice project while learning Go. :P
@bender highly probably, unless I learn go and implement it myself (or someone else more capable does) ... but I'm so lazy I'd just copy them from twtxt.net and call it a day xD and yeah, it's kinda rough the way things are...
- I don't see a way to follow others, all I can do is go to the /feeds URI for a list of the server's users/feeds.
- I still couldn't figure out how to get a direct link to a user's twtxt file, curling /feeds/usernick spits out a list of the user usernick twts, so I guess you could use that to follow them.
- no way to add in your # nick = usernick / # url = proto://domain.ltd/path/to/twtxt.txt ...etc. Probably because that wasn't part of the spec back then?
So yeah, it would make for a nice project while learning Go. :P
@aelaraji hehehehe! Being a nine years old container, the first thing to do is to bring the code complaint to the latest Go release. :-P
Yeah, metadata is an extension, and not part of the original spec.
@bender I built my own, a much smaller one with a multi stage build... shouldn't that do the trick? 🤔
@bender I built my own, a much smaller one with a multi stage build... shouldn't that do the trick? 🤔