@movq@www.uninformativ.de Huh, this is the first time I heard of IBM WebExplorer.
I’m out of shape. I decided to walk up the local mountain to watch the sunset, but I arrived five minutes late, even though I sped up at the end. Should have started my journey ten or fifteen minutes earlier. I saw the setting sun at foot, but the photos were total disasters.
On the way there I picked two handful of blackberries in the forest. Delicious!
Today was the second time in my life that I saw a grass snake in the wild. They can easily be recognized by the yellow “ears”. Unfortunately, this one was run over. :-( But I jumped at the opportunity to photograph it as it didn’t escape in a fraction of a second like my first encounter three years ago. Still, poor fellow. :-(
On the way home, a deer jumped out of the brush in front of me and headed down the forest road before it went back in the other side. As always, that’s nice.
I also had to slow down a bunch of times because of frogs or toads on the paths. Not sure which ones, it was already after dark. I guesstimate it must have been 60-70 amphibians in total, maybe more. Some of them did not move to the wayside but rather into the middle of the track, right in front of me. Crazy suicide frogs! There were four reeeeaaaallly close calls. I could just avoid stepping on them after they tried to hop right under my boot. Not a centimeter to spare. No toads were harmed during my trip. Phew!
Once I had to stop completely because of the large activity ahead of me. A larger (about the size of half a palm) individual surrounded my foot and then jumped against my heel. Twice! What the heck!? :-D But suuuper cool experience. I’m very glad I actually went out. Totally worth it. I met so many amazing animals. Don’t care about the missed sunset a single bit.
@bender@twtxt.net Nope, still don’t have a mobile one. Works extremely well for me. :-)
Temperatures begin to drop a bit for the night, phew. https://lyse.isobeef.org/abendhimmel-2024-08-30/01.jpg
@movq@www.uninformativ.de @bender@twtxt.net Haha, great! :-)
Just returned from an evening walk. We met a young slow worm, a bunch of small frogs, about the width of a pointing finger and a bucket load of sweat. It’s bloody hot and humid. Also, heaps of ripped trash bags in the forest and lake. :-( No photos, it was too exhausting to even carry my pocket camera.
@movq@www.uninformativ.de Lol, someone just showed me this brilliant German (Saxon, actually) song. The title Hitzetodcheck translates to “heat death check”. Sorry to all non-German speakers. https://www.youtube.com/watch?v=1qHH3RO_X34
I’m also ready absolutely ready for winter.
yarnd --help
currently says (for me):
@abucci@anthony.buc.ci Yep, --open-registrations=false
has to also use the equal sign, just like the short form, otherwise it’s activated. At least that’s consistent. But, is has no effect, if the settings.yaml claims something different.
I have the impression that command line flags only take effect the first time you start yarnd. Unless the option has no pendant in the config file, such as -A/--admin-user $user
. Since -A
is not a boolean, but takes a string, you are free to use a blank or an equal sign…
It’s this package: https://github.com/spf13/pflag?tab=readme-ov-file#command-line-flag-syntax
I also noticed and fixed the typo. 8-)
-R=false
on the command line or leave it out entirely. When explicitly stating -R=false
, there has to be an equal sign. With a space (-R false
) it's somehow parsed as -R
which is equivalent to -R=true
. O_o Very weird. I'd really like to see an error instead.
Yeah, user error on my end, never mind. The persisted settings.yaml overrides the command line arguments. That’s surprising to me. I expected the command line options to overrule the config file. Oh well.
@aelaraji@aelaraji.com Hmmm, so it is permanent damage. Damn! :-( I’m no electronics guy, but I’d suspect it to be broken, if unplugging it and plugging it in again doesn’t fix it. Kinda doubt that a repair shop will get it going again. I have no idea where I would bring it over here. The best I can think of is to ask the volunteers at the repair café if they have any suggestions, I reckon they’re not able to fix it either. But that place is only open once a month.
How much of your screen is gone by now? Looks like a lot.
Wow, crazy. A decade ago, I think I only experienced power outages three or maybe four times in my entire life. Since then, they became a bit more frequent. Probably five or six, maybe more. Not sure how many of these events are attributed to construction incidents, where an excavator ripped a power line apart. Last time, loggers threw a tree in an overhead power line, so the power company had to disconnect my area from the grid.
@abucci@anthony.buc.ci You can also use -R=false
on the command line or leave it out entirely. When explicitly stating -R=false
, there has to be an equal sign. With a space (-R false
) it’s somehow parsed as -R
which is equivalent to -R=true
. O_o Very weird. I’d really like to see an error instead.
I still have to figure out the precedence of the settings.yaml or command line arguments. I’m probably holding it wrong, but it seems to give me different results…
vim
cursor at the end of the first line on replies, and forks. I have tried adding to this to jenny
's configuration:
@quark@ferengi.one @movq@www.uninformativ.de A general workaround in these cases is to wrap the command in a shell script and reference said script instead.
@aelaraji@aelaraji.com Oh, shoot! The broken rows are permanent? Looks like you’re the king of power outages. :-( How frequent do you experience blackouts?
@movq@www.uninformativ.de Phew, that was a close call.
@quark@ferengi.one Enjoy! :-)
@aelaraji@aelaraji.com Bwhahaha! :‘-D
@mckinley@twtxt.net Wow, I was not aware, that there are different kinds of blackberries. But of course there are. Everything has all sorts of different species, why would it be different with these tasty guys? :-)
I just read up on them and – surprise, surprise – it turns out, the Himalayans are not native to most of Europe either. Doh! It gets even more interesting, their origin is unclear. Maybe Armenia and the Caucasus region. Fascinating!
@movq@www.uninformativ.de @prologic@twtxt.net Right, what can possibily go wrong!? ;-)
It’s funny that you mention it, too. We also were quite surprised that it was incredibly quiet in nature. Not just no man-made noise (we obviously avoided the crowds), not even in the distance, but also hardly any birds. We joked they’re still exhausted from the heat of the days before and still resting.
@abucci@anthony.buc.ci Thank you for using Lyse’s Unofficial Yarnd Help Desk: https://lyse.isobeef.org/tmp/yarnd-disable-registrations.png
@prologic@twtxt.net Or c) you click on a link somebody gave you. My brain is a bit dead now, but that might be a problem when you’re logged in.
vim
cursor at the end of the first line on replies, and forks. I have tried adding to this to jenny
's configuration:
Today, I learned about vim "+normal $"
, how cool! :-) Thanks @quark@ferengi.one!
I just learned from a German documentary that there is goldbeating. Never heard of that term before. Super interesting.
@prologic@twtxt.net Great! Git knowledge is helpful in a lot of situations. What’s the website about? You both had some fun writing HTML by hand? :-)
@prologic@twtxt.net No worries, all good. :-)
@bender@twtxt.net Wasn’t too terrible, I just watched a video in the background. ;-)
It cooled off to 20°C today, but mid week is supposed to be crazy hot again. It was a nice walk, also plenty of people around, though. So we decided against going up our backyard mountain to avoid the masses. We finally took a path that we haven’t checked out for years. That was pretty cool. I couldn’t remember anything on that.
More scenery: https://lyse.isobeef.org/waldspaziergang-2024-08-25/
Neither of us has ever seen such a marmelade bun mushroom:
@prologic@twtxt.net @movq@www.uninformativ.de You can just GET /twt/<HASH>
with Accept: application/json
:
$ curl -sH 'Accept: application/json' https://twtxt.net/twt/fgthxaq | jq
{
"twter": {
"nick": "prologic",
"uri": "https://twtxt.net/user/prologic/twtxt.txt",
"avatar": "https://twtxt.net/user/prologic/avatar#gdoicerjkh3nynyxnxawwwkearr4qllkoevtwb3req4hojx5z43q"
},
"text": "(#tkjafka) @<falsifian https://www.falsifian.org/twtxt.txt> @<movq https://www.uninformativ.de/twtxt.txt> You actually only really want the missing root Twt. You could just fetch this from any Yarn pod. There are scripts I built way back when yo do this 😅",
"created": "2024-08-23T00:54:04Z",
"markdownText": "(#tkjafka) [@falsifian](https://www.falsifian.org/twtxt.txt#falsifian) [@movq](https://www.uninformativ.de/twtxt.txt#movq) You actually only really want the missing root Twt. You could just fetch this from any Yarn pod. There are scripts I built way back when yo do this 😅",
"hash": "fgthxaq",
"tags": [
"tkjafka"
],
"subject": "(#tkjafka)",
"mentions": [
"@<falsifian https://www.falsifian.org/twtxt.txt>",
"@<movq https://www.uninformativ.de/twtxt.txt>"
],
"links": []
}
@prologic@twtxt.net I returned way later. Maybe next time. :-)
@prologic@twtxt.net Noone around. :-)
@movq@www.uninformativ.de The second one is at least discouraged. https://dev.twtxt.net/doc/twtsubjectextension.html#format
[…] Putting mentions before the hash is still supported but discouraged. […]
@movq@www.uninformativ.de It’s a very low-traffic channel. At least when I usually idle around. :-)
It is really cool to watch this guy building a crossbow: https://www.youtube.com/watch?v=K-ogGdXTGkM
@prologic@twtxt.net Cool, simplification is gold. Non-existent code is the best code. :-)
@movq@www.uninformativ.de @quark@ferengi.one Look at all the nice branching! :-)
twtxt
client by buckket to actually fetch and fill the cache. I think one of of the patches played around with the error reporting. This way, any problems with fetching or parsing feeds show up immediately. Once I think, I've seen enough errors, I unsubscribe.
@quark@ferengi.one It’s a giant mess at the moment. I started rewriting it from scratch in January last year. But that’s also a big undertaking. And that’s why I stopped. I should proceed, though. Let’s see.
@quark@ferengi.one Bwahahahahaha, yeah! :-D Well, birds can be considered descendants.
@movq@www.uninformativ.de Oder gar ±inf Grad! Bibber, schwitz. Naja, passt auf jeden Fall zum Ortsnamen. :-) Mittlerweile haben sie ihr kaputtes JS repariert.
So, by “evolve” you actually mean “remove”, @prologic@twtxt.net? :-?
twtxt
client by buckket to actually fetch and fill the cache. I think one of of the patches played around with the error reporting. This way, any problems with fetching or parsing feeds show up immediately. Once I think, I've seen enough errors, I unsubscribe.
Let me take this opportunity to recommend something to @bmallred@staystrong.run: https://staystrong.run/user/bmallred/twtxt.txt returned 200 but no Last-Modified header - can’t cache content
:-)
Another modification I made is to actually cache it anyways. Otherwise, tt
wouldn’t show anything. I implemented that for some other feed that doesn’t exist anymore.
Correct, @bender@twtxt.net. Since the very beginning, my twtxt flow is very flawed. But it turns out to be an advantage for this sort of problem. :-) I still use the official (but patched) twtxt
client by buckket to actually fetch and fill the cache. I think one of of the patches played around with the error reporting. This way, any problems with fetching or parsing feeds show up immediately. Once I think, I’ve seen enough errors, I unsubscribe.
tt
is just a viewer into the cache. The read statuses are stored in a separate database file.
It also happened a few times, that I thought some feed was permanently dead and removed it from my list. But then, others mentioned it, so I resubscribed.
To get this going, I implemented the easiest, next best option I could think of. Happy to get some feedback. Yes, it should be improved in the future, no doubt about that. Although, I have changed a few things in yarnd in the past, I’m not really familiar with the code base, so beware of bugs and other undesired side effects.
@falsifian@www.falsifian.org @bender@twtxt.net I’d certainly hate my client for automatic feed unsubscription, too.
Hmm, bissel kalt… https://lyse.isobeef.org/tmp/null-grad.png
@prologic@twtxt.net Yeah, I’ve noticed that as well when I hacked around. That’s a very good addition, ta! :-)
Getting to this view felt suprisingly difficult, though. I always expected my feeds I follow in the “Feeds” tab. You won’t believe how many times I clicked on “Feeds” yesterday evening. :-D Adding at least a link to my following list on the “Feeds” page would help my learning resistence. But that’s something different.
Also, turns out that “My Feeds” is the list of feeds that I author myself, not the ones I have subscribed to. The naming is alright, I can see that it makes sense. It just was an initial surprise that came up.
159-196-9-199.9fc409.mel.nbn.aussiebb.net
Righto, I cobbled something together here: https://git.mills.io/yarnsocial/yarn/pulls/1172 It needs a bunch more work, though. Screen time is up for today.
@movq@www.uninformativ.de Mr. Watson for the doping test please.
159-196-9-199.9fc409.mel.nbn.aussiebb.net
Yeah, the ErrDeadFeed
is never actually checked anywhere. It’s only set and that’s it.