# 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 6525
# self = https://watcher.sour.is?uri=https://lyse.isobeef.org/twtxt.txt&offset=134
# next = https://watcher.sour.is?uri=https://lyse.isobeef.org/twtxt.txt&offset=234
# prev = https://watcher.sour.is?uri=https://lyse.isobeef.org/twtxt.txt&offset=34
@vain Did your hygrometer break?
@vain Great bookmark, I'll have a deeper look. Thank you!
@thewismit Ha, I got caught in the cronjob PATH trap again last night. ;-)
@jlj @vain @prologic Thanks! Nice, at least the -ntpl flags in ss are the same as in netstat.
@vain Welcome back and happy catching up!
@vain Ah, alright, cool. I need to have a closer look then.
@xuu Oh this is brilliant! \o/
@xuu Oh this is brilliant! \\o/
@jlj Yes, I had been using netstat ever since, too. So, ss is better than netstat in your opinion?
@prologic @eldersnake Uuuhhh, very cool! Didn't know about this either, but I actually was never on a system without ip or ifconfig.
I accidentally typed ss rather than ls and look what's coming up – another utility to investigate sockets! Nice, I didn't know about it.
@prologic :-D I try to do some packaging research next week.
@prologic Sounds good! Which part are you agreeing on here? The "Lyse needs to learn packaging (before the analyzer is more usable)" or the "create a Handy Twtxt Tools page"? Probably both. ;-)
@kt84 I always knew that tomatos are weed!!
@prologic Yes you are at least for twtd/twxt.net! :-D If you want to replace the current component in twtd, go ahead and feel free to use it in any form you want to. I probably need to read on the library/packaging of Go code. What do you reckon, where would be a suitable place to put a link to my subproject? Create a new "Handy Twtxt Tools" page on dev.twtxt.net?
@prologic Olé, worky, worky! After fixing it, you have deserved a nice Sunday brekkie. Enjoy!
@prologic Sure, of course! Whatever you like. :-) I should probably add fetching and including the Who Follows Resource, too. Optionally with a flag.
@prologic Thanks! Wow, the sky is crazy yellow here, but my camera isn't capable of capturing the colors at all. :-( Saharan air layer is back.
@prologic Yeah, an off-by-one error seems very likely for the page counter bug. Though, the number of results is probably something else. Or I just don't know how it's calculated, maybe it's the total number of search term occurrences, so one result can have several literal matches.
@prologic @jos Thank you proxylogic! 8-) Works perfectly now, thanks jos.
Hey @jos, I hope this twt reaches you. Please configure your Apache to include the charset in the Content-Type response header of your twtxt.txt. The twtxt client somehow guesses the wrong one and then fails.
29 days ago, @prologic asked me to participate in an experiment: switching search engines. I have to say this worked out really good so far. The only things I noticed right away, is, that with DuckDuckGo I need to search more specifically and provide a bit more context than it would have taken for a Google search (even without an account) to dig up the relevant results, I believe.
@thewismit @jlj I like regex a lot, they're so powerful. But sometimes they can go a bit overboard.
@jlj I can only tell you, that at least your twtxt.txt file works flawlessly.
@thewismit Oh yeah, this is bloody awesome! \\o/ Need to remember this channel.
@thewismit Oh yeah, this is bloody awesome! \o/ Need to remember this channel.
On the way to the woods I came across a kestrel (?) today. Moving twigs in the wind and full zoom don't make for the highest quality photos. Everything had melted days ago, but we got snow overnight again, some forest glades were covered in 15-20 cm snow. https://lyse.isobeef.org/schnee-im-wald-2021-01-25/
@off_grid_living I suspect this is not enough to move that amount of air. But I don't have any data nor have I even tried this. Just some gut feeling.
@vain Cool! I like the twt hash test suite. ;-) You could extend the feed fetch with ETag or If-Modified-Since headers.
@niplav I first thought my client had a bug.
@jlj Excellent! ;-) Yep, just let Nginx terminate the HTTPS session and pass everything over HTTP to twtd.
@jlj Your redirect on twtxt.net is missing the /twtxt.txt. :-) Don't you want to add TLS support, now that you're moving? Since people move around lately, I need to add a "mark all twts read" option to my client, because all the hashes are now different and show up again as unread.
@off_grid_living Green looking good, mate. Doing something the first time always takes much longer than anticipated and you also encounter plenty of surprises. Even the second time you learn something new. At least that's my experience.
@vain Ah nice reference! I was already wondering when I saw jenny appearing in my access log. :-)
@prologic @xuu Cool, lextwt to the rescue! With retwt it looks like this: https://lyse.isobeef.org/retwt-broken-code-rendering.png My own twtxt parser handles subjects too freely and treats the first parentheses – no matter where in the twt the appear – as subjects which happens to be my example subject hash tag in markdown inline code. Since I hide the subject to save space, the code block is empty.
@adi @thewismit @vain @prologic Yes, so do I. I don't feel any overhead, even for the most basic stuff. But I also have a single repository for all my super tiny stuff of various sorts.
@birb It's about time! Welcome back mylord.
@thewismit @prologic For a start we could teach twtd to show all its cached external feeds, too, not just the internal ones.
Since I lately see technically invalid twt subject hash tags for machine-parsable conversation grouping every now and then, I just taught the twtxt parser of my client to recover these (#1234567) subjects. Now they are grouped back into the proper conversations and do not form new root/single twts. Note, that the offending clients did not expand the hash tag in the subject to a proper (#<hash url>) form prior to publishing the twts. (Let's see whether my first markdown code will be expanded by twtd to a linked hash tag or not.)
@thewismit Well, English is not my mother tongue, I just made "diffability" up as it sounded good and seemed likely to exist. Though, turns out, its meaning is a bit different. What I meant to say is the "possibility to create a diff". Glad that be both learned something new today. :-D
@thewismit I don't think this is possible right now. In fact this doesn't work for any external feeds and is not just limited to other twtd instances. That's what I experienced as an anonymous twtxt.net visitor. But I use twtd hardly at all, just to fool around locally, so take this with a grain of salt.
@adi @thewismit Sure, you don't need to have one, but does it really hurt you? Even for small stuff it's an easy way have distributed backups. I also wouldn't want to miss the quick and easy diffability, which comes in very handy if I accidentally hit the wrong keys in vim without immediately noticing. The particular hosting is debatable, no question, but I certainly wouldn't want to loose the version control aspect in general.
@prologic I thought, that vain was a made up nickname and not a real word.
@vain @prologic Up until now I didn't know that this is even an English adjective. What future nick are you thinking about?
@anth What window manager are you using and what did your daughter teach you? :-)
@vain Absolutely! When reading through the back log prior to this invention, it was horrible.
@deadguy Any success with the coding otter yet? ;-)
@vain Yeah, over the time it feels like there's less time to do useful stuff. It's even worse since I started twtxting. :-D
@prologic @xuu Yeah, documenting them would be great. Maybe we don't even need a separate meta data file and can handle everything using special comments.
What the fuck, it took systemd up to release 240 to implement append:/my/stdout.log for StandardOutput and -Error! Of course this Ubuntu box runs version 237… I was joking to my mates that they added file:path in version 236, not knowing that this evil insinuation is actually true! O_o Who needs files anyways? There's this Über-Pötterlog. Holy mother! Back to good old /bin/sh -c '… >> /my/stdout.log'.
@off_grid_living Fair enough. I just thought, that QLD would be quite humid and therefore provide perfect conditions for oxidation. I often heard, that once the thing is sealed up and the corrosive stuff inside used up, it won't rust any further. But it needs to be sealed, if there are leaks, oxidation continues.
@pbatch Cool solution! The one time I had to implement such custom ordering I went with holey integers and recompute, because items were rearragned only very rarely.
@vain Oh, this is wonderful! I just started reading it.
@prologic No doubt about that, but sadly this is not one of them. One record summer follows the next. Decades ago, winter used to be much cooler, too.
@off_grid_living I'm no material expert, but this looks fine. If you cap off the square tubes, you'll probably stop the oxidation starting from inside. I wouldn't want to paint the inside.
@vain Yes, cities make a difference. Some photos were taken around 450-500m NHN, much higher than where you are. @adi Still nice, though.
@adi How much did you get? Here it will be gone on Wednesday, temperatures are supposed to rise from tomorrow on.
@vain Oh yeah, we got five centimeters over night.
@vain Looks like you haven't sacrificed enough cats, have you? 2021 is the year when Linux finally prevails the desktops!
@adi In my case I had trouble to get the overall idea on how to work with several files. My initial expection simply wasn't met. However, your HOWTO is the missing link, thanks mate! You definitely have to link this somewhere prominent. Maybe also publishing the raw mkws website sources (or a subset of it, probably without the tarballs) would also helpful to get one or two tricks. Ah, unprocessed, makes sense.
@adi Yes, good idea! A little bit more complex example would certainly also help. It took me quite long to wrap my head around on how to use this properly (maybe I was just too tired). What does the "upp" in "upp{html,xml,css,…}" stand for? "pp" references the preprocessor, but the "u"? At the moment I don't have a usecase for mkws, but I'll keep it in mind. Btw, the "man" directory in the File Hierarchy section misses the "" in the tree.
@adi Yes, good idea! A little bit more complex example would certainly also help. It took me quite long to wrap my head around on how to use this properly (maybe I was just too tired). What does the "upp" in "upp{html,xml,css,…}" stand for? "pp" references the preprocessor, but the "u"? At the moment I don't have a usecase for mkws, but I'll keep it in mind. Btw, the "man" directory in the File Hierarchy section misses the "" in the tree.2021-01-15T20:45:00+01:00\t@https://twtxt.net/user/adi/twtxt.txt> (#u6jmita) In my case I had trouble to get the overall idea on how to work with several files. My initial expection simply wasn't met. However, your HOWTO is the missing link, thanks mate! You definitely have to link this somewhere prominent. Maybe also publishing the raw mkws website sources (or a subset of it, probably without the tarballs) would also helpful to get one or two tricks. Ah, unprocessed, makes sense.
@adi I reckon you should make the pp docs more prominent on the front page. I'll take a deeper look into it tomorrow.
@xuu @vain @prologic Thanks, great analyses! Ha, I have 42 twts! Well, now not anymore. Using the target URL of a redirect and not the original one should get rid of at least some of the duplicates. I would have expected some of the EMPTY flagged ones as FAILED instead, esp. all the ones with the invalid TLDs (see mine for example). But I need to have a deeper look at the code. Cool project nevertheless!
@off_grid_living I'm pretty sure you – as someone with a lot of gardening experience – will also find a solution to cover up the looks. :-)
@prologic @vain @xuu Wow! Did you account for duplicates such as the twtxt.net URL change?
@vain Thanks, but in reality it was of course much nicer.
@adi @prologic My tt client uses the conversation URLs in the twt subjects when creating a reply, because I think this makes more sense, too. This is also covered by the Twt Subject Extension Spec. This client is still in a terrible state right now – hence "tt" as in "terrible tui" rather than "twtxt tui". :-P
@vain Cool. I believe for experiments it's a totally valid approach to go with cheap stuff. No need to spend tons of money.