# 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 196262
# self = https://watcher.sour.is?offset=180731
# next = https://watcher.sour.is?offset=180831
# prev = https://watcher.sour.is?offset=180631
Wow. Thanks to comp.misc for pointing this place.
š§® USERS:1 FEEDS:2 TWTS:1213 ARCHIVED:84163 CACHE:2968 FOLLOWERS:17 FOLLOWING:14
@doesnmppsflt It looks like it... Although they shouldn't be empty since Timeline took care of sending those. I believe I have an idea as to why that happened, but will have to test before filing an issue.
@doesnmppsflt It looks like it... Although they shouldn't be empty since Timeline took care of sending those. I believe I have an idea as to why that happened, but will have to test before filing an issue.
@lyse HAHA! A forever stable major release eh? That's brilliant š ...
@lyse HAHA! A forever stable major release eh? That's brilliant š ...
My webmention script are the same as Timeline
Your mention is... empty?
@doesnm.p.psf.lt I don't know if you have already noticed, but your Twtxt/Webmention script outputs Timestamps from the future š¤ I wonder if Timeline's does the same ...
I'm sitting in official cabal.club with nicknames doesnm and doesnm-seed from vps because can't install cli in Termux
[47Ā°09ā²48ā³S, 126Ā°43ā²05ā³W] Transfer aborted
Noice! 
Mention sent successfully
I've been using nile, my alternative WM for #plan9, for over a decade now. I just made some additional improvements and finally gave it a web page: http://a.9srv.net/src/nile/
I've been using nile, my alternative WM for #plan9, for over a decade now. I just made some additional improvements and finally gave it a web page: http://a.9srv.net/src/nile/
[47Ā°09ā²05ā³S, 126Ā°43ā²10ā³W] Transfer 25% complete...
curl: (3) URL rejected: Malformed input to a URL function. Writing sender in bash was BAD idea
@prologic I say we should find a way to support mentions with only url, no nick, as per the original spec.
- For @<nick url> we already got support
- For @<nick> the posting client should expand it to @<nick url>, if not then the reading client should just render it as @nick with no link.
- For @<url> the sending client should try to expand it to @<nick url>, if not then the reading client should try to find or construct a nick base on:
1. Look in twtxt.txt for a nick =
2. Use (sub)domain from URL
3. Use folder or file name from URL
@prologic I say we should find a way to support mentions with only url, no nick, as per the original spec.
- For @<nick url> we already got support
- For @<nick> the posting client should expand it to @<nick url>, if not then the reading client should just render it as @nick with no link.
- For @<url> the sending client should try to expand it to @<nick url>, if not then the reading client should try to find or construct a nick base on:
1. Look in twtxt.txt for a nick =
2. Use (sub)domain from URL
3. Use folder or file name from URL
@prologic I say we should find a way to support mentions with only url, no nick, as per the original spec.
- For @<nick url> we already got support
- For @<nick> the posting client should expand it to @<nick url>, if not then the reading client should just render it as @nick with no link.
- For @<url> the sending client should try to expand it to @<nick url>, if not then the reading client should try to find or construct a nick base on:
1. Look in twtxt.txt for a nick =
2. Use (sub)domain from URL
3. Use folder or file name from URL
@prologic I say we should find a way to support mentions with only url, no nick, as per the original spec.
- For @<nick url> we already got support
- For @<nick> the posting client should expand it to @<nick url>, if not then the reading client should just render it as @nick with no link.
- For @<url> the sending client should try to expand it to @<nick url>, if not then the reading client should try to find or construct a nick base on:
1. Look in twtxt.txt for a nick =
2. Use (sub)domain from URL
3. Use folder or file name from URL
[47Ā°09ā²42ā³S, 126Ā°43ā²01ā³W] Waiting for carrier
Pinellas County Running: 5.03 miles, 00:09:19 average pace, 00:46:55 duration
easy five to complete the first week of marathon training. my left glute/hip had some twinges
#running
Pinellas County Running: 5.03 miles, 00:09:19 average pace, 00:46:55 duration
easy five to complete the first week of marathon training. my left glute/hip had some twinges
#running
Pinellas County Running: 5.03 miles, 00:09:19 average pace, 00:46:55 duration
easy five to complete the first week of marathon training. my left glute/hip had some twinges
#running
@prologic This is fricking amazing, congratulations! :-) \\o/
@prologic This is fricking amazing, congratulations! :-) \o/
@lyse Just watched this too! Not too bad š
@lyse Just watched this too! Not too bad š
[47Ā°09ā²00ā³S, 126Ā°43ā²58ā³W] Carrier too weak
@lyse That was great! š Now I need to go back and watch the other videos by that guy. š
@lyse That was great! š Now I need to go back and watch the other videos by that guy. š
@lyse That was great! š Now I need to go back and watch the other videos by that guy. š
@lyse That was great! š Now I need to go back and watch the other videos by that guy. š
I am now fully off Cloudflare š„³
I am now fully off Cloudflare š„³
[47Ā°09ā²00ā³S, 126Ā°43ā²14ā³W] Bad satellite signal -- switching to analog communication
So Go lang is at a funny version huh' v1.23.4 will there ever be a v1.23.45678? š« š¤”
So Go lang is at a funny version huh' v1.23.4 will there ever be a v1.23.45678? š« š¤”
@lyse ahhh thank you so so much!!!! i've heard of shellcheck but haven't checked it out properly - will try it for my scripts :D i really appreciate it
@lyse ahhh thank you so so much!!!! i've heard of shellcheck but haven't checked it out properly - will try it for my scripts :D i really appreciate it
@shreyan Yeah the guy seems quite mad and hell bent on destroying his reputation and his project š¤¦āāļø
@shreyan Yeah the guy seems quite mad and hell bent on destroying his reputation and his project š¤¦āāļø
@ no. It is jest. Just like The Onion, but exclusively for a fictitious company. š
@slashdot Matt really is a fucking idiot š¤¦āāļø Right? š¤
@slashdot Matt really is a fucking idiot š¤¦āāļø Right? š¤
š§® USERS:1 FEEDS:2 TWTS:1212 ARCHIVED:84140 CACHE:2965 FOLLOWERS:17 FOLLOWING:14
That's a well done mapping of computer time scale to human time scale: https://youtu.be/PpaQrzoDW2I Matt Godbolt is also a guy that I just enjoy listening to.
@movq Hmm yeah, you're right. I should have checked for our location prior to getting too excited.
@aelaraji Yeah, a sore neck is always a win. :-P Here's nothing really to see, all cloudy. And also a bit cold at -2Ā°C. I don't feel like standing still all that long outside at the moment. :-D
Couldn't see shi_, but enjoyed observing the moon light slipping trough the fast moving clouds! I'll take that as a win š
> /Me came back with a soar neck ..._
Couldn't see shi_, but enjoyed observing the moon light slipping trough the fast moving clouds! I'll take that as a win š
> /Me came back with a soar neck ..._
@lyse /Me throws his keyboard off to the side, grabs his camera just in case and runs upstairs screaming "Yeah! Science B_ !"_
@lyse /Me throws his keyboard off to the side, grabs his camera just in case and runs upstairs screaming "Yeah! Science B_ !"_
@lyse Hmm, their illustration looks pretty optimistic. š¤ When I look at it in Stellarium, the cluster around Saturn is pretty close to the Sun. Not sure you can see them. š¤ Saturn is even closer to the Sun than Mercury ā and Mercury is notoriously hard to observe.
But I hope Iām wrong!
January looks pretty interesting, too, btw.
@lyse Hmm, their illustration looks pretty optimistic. š¤ When I look at it in Stellarium, the cluster around Saturn is pretty close to the Sun. Not sure you can see them. š¤ Saturn is even closer to the Sun than Mercury ā and Mercury is notoriously hard to observe.
But I hope Iām wrong!
January looks pretty interesting, too, btw.
@lyse Hmm, their illustration looks pretty optimistic. š¤ When I look at it in Stellarium, the cluster around Saturn is pretty close to the Sun. Not sure you can see them. š¤ Saturn is even closer to the Sun than Mercury ā and Mercury is notoriously hard to observe.
But I hope Iām wrong!
January looks pretty interesting, too, btw.
@lyse Hmm, their illustration looks pretty optimistic. š¤ When I look at it in Stellarium, the cluster around Saturn is pretty close to the Sun. Not sure you can see them. š¤ Saturn is even closer to the Sun than Mercury ā and Mercury is notoriously hard to observe.
But I hope Iām wrong!
January looks pretty interesting, too, btw.
[47Ā°09ā²52ā³S, 126Ā°43ā²11ā³W] --bad checksum--
Your code apparently works just fine. Until it @doesnm't. ;-) The shell languages are weird and having some strange properties that one is just not used to when coming from other languages.
PSA: Yarnd operators might want to define code { white-space: pre } in their CSS themes to render things as they're supposed to look like.
@andros I love how this is coming together! :-)
@kat To improve you shell programming skills, I highly recommend to check out shellcheck: https://github.com/koalaman/shellcheck It points out common errors and gives some suggestions on how to improve the code. Some details in shell scripting are very tricky to get right at first. Even after decades of shell programming, I run into "corner cases" every now and then.
E.g. in getlyr's line 7 it warns:
echo -e $(gum style --italic --foreground "#f4b8e4" "'$artist', '$song'")
^-- SC2046: Quote this to prevent word splitting.
For more information:
https://www.shellcheck.net/wiki/SC2046 -- Quote this to prevent word splitt...
Most likely not all that problematic in this application, but it's good to know about this underlying concept. Word splitting is basically splitting tokens on whitespace, this can lead to interesting consequences as illustrated by this little code:
$ echo $(echo "Hello World")
Hello World
$ echo "$(echo "Hello World")"
Hello World
In the first case the shells sees two whitespace-separated tokens or arguments for the echo command. This basically becomes echo Hello World. So, echo joins them by a single space. In the second one it sees one argument for the echo command, so echo simply echos this single argument that contains three spaces.
[47Ā°09ā²45ā³S, 126Ā°43ā²34ā³W] Saalmi, retransmit, please
@prologic Oh yeah, that's terrible, yuck! Let's not do it then. :-)
@prologic As written in IRC, several things turned me off. I don't have the energy at the moment to wrestle through. :-(
After I stripped off my clothes and turned around, I came to the conclusion that the plan to shower was cancelled at this moment. The faucet had broken right off and was laying in the tub. I noticed that the diameters of the hot and cold water pipes were surprisingly small, didn't expect that. Since the pipes were broken flush with the wall, I couldn't even determine if I had to remove the inner our outer threads, well, remains thereof, in order to attempt to repair this mess. Luckily, I was going to see a plumber mate at the christmas tree collection later anyway.
The first thing that came to mind when I woke up was that I didn't catch the logical flaw in my dream: absolutely no water was coming out of the burst pipes. The whole scenario took place in summer, so the water couldn't be frozen either.