# 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 44
# self = https://watcher.sour.is?uri=https://gbmor.dev/twtxt.txt&offset=44
@jlj right now the getwtxt-ng source is in a private repo on github, though I may move it to sr.ht for its primary home (and just mirror it to github)
rewrite of getwtxt (as getwtxt-ng) is going okay. i'm much happier with sqlite for storage.
I've started a ground-up rewrite of getwtxt, my twtxt registry server.
Dealing with date/time in code is so annoying...
I think I'll resurrect this football pool generator site I used to run
working on an http api for tilde.institute, to query packages and uptime, and some other things
Been a while since I wrote any twtxt-related code. I should fix that ...
Started working on a twtxt library in Rust. Once it's further along I'll make the repo public so folks can hack on it.
Two interviews this coming week! Things are looking up for me.
@freemor oof, looks like I should avoid e-commerce sites using Magento then ...
job interview on tuesday for a dev position ... kinda nervous!
I've switched from Vim to VSCode ... it's very nice, but I feel strange using it.
@freemor I'm reading that now. I use links and w3m occasionally, but perhaps I should use them more often...
Working on a tildecoin (currency simulation for the tildeverse) implementation. This should be fun! If any Rustaceans want to join in: https://github.com/tildecoin
@mdosch I also use #IRC extensively. Much more than any other digital communication medium.
ughhh .... what should I work on .... I want to program but I don't know what to do.
It seems like every time I try to use a different editor, I always end up back using the SpaceVim vim distribution. It's just so ... good
@mushmouth your twtxt.txt file looks good with the metadata at the top!
Hey @deepend! There's a few of us who are active :)
@quite I'm glad we were able to figure this out!
@quite After doing various tests of the fetchers change along with making tweetsch buffered, it seems to be working perfectly. On my fork, it's the 'bugfix-tweetsch-deadlock' branch, so you can test it yourself.
@quite I've been testing a few iterations of a fix. It appears that the simplest is making tweetsch a buffered channel of len(sources), which allows the ratelimiting (fetchers) to function without blocking indefinitely on tweetsch<- sends
@quite Ah, I see now. I have an idea for a patch to mitigate this. I'm testing it now and will submit a PR shortly. :)
@quite I've done a little bit of testing and haven't experienced deadlock yet. Just a bit of a delay from the fetch ratelimiter.
@quite Hmm. Where exactly is the deadlock happening?
Just finished a long day at work, then ate dinner and got a patch/PR written out. I feel productive! And sleepy ...
@quite thanks for the kind words! I'm trying out #twet right now. I like it, it's a nice alternative to the original client.
@von Good luck! I hope you find a job you love!
@mdosch it looks like liberapay needs some public relations consulting lol
finally got sqlite working in getwtxt! wooo!
Ooooof debugging the sqlite functions in getwtxt is giving me a headache
Feels like there's always more work to do on my projects...
@kas sure, feel free! I'm new to twtxt so I'm not sure what other resources are out there.
Weird bugs coming out of the woodwork in getwtxt. The fun of a project in its infancy!
Refactored a section of getwtxt. Now time to do more code challenges while I test it ...
@kas Thanks for letting me know! I fixed it and added you to the registry.
Hey @von - join the twtxt.tilde.institute registry already :-p
The TripleByte interview was stressful. Hoping for the best, and decompressing by doing some coding challenges...
I have the first of two interviews with TripleByte on Tuesday. I'm nervous! #ohsnap
I've gotten getwtxt into a usable state. Time for the running beta!