(#kqqd2ha) @quark@ferengi.one Yes, keep em coming. :-)
@prologic@twtxt.net Just start off the experiment now and see how far you get. :-D
#qkhpmwq
If this user/feed is violating this Pod's (yarn.meff.me) community guidelines as set out in the Abuse Policy, please report them immediately!
You are also free to Unfollow or Mute this user or feed. Muting will also remove that user/feed's content from your view and you will no longer see content from that user/feed anywhere.
@lyse does not follow you (they may not see your replies!)
(#kqqd2ha) @quark@ferengi.one Yes, keep em coming. :-)
@prologic@twtxt.net Just start off the experiment now and see how far you get. :-D
That’s a very entertaining talk about mining and analyzing radio station playlists: https://media.ccc.de/v/38c3-radiomining-playlist-scraping-und-analyse It’s in German, not sure how good the English translation or subtitles are.
Man, @quark@ferengi.one has an absolute gold mine. Having dealt again with different clocks and all sorts of strange time things at work today, this made my day! https://netbros.com/1755172401/ :‘-D
(#ixka6ca) @bender@twtxt.net Hahahahahaahaaa, you’re right, it can’t be anything else! :‘-D Must have been one of these manmade objects. Let’s hope they will become a full member of the Grant Wishes Council soon. In any case, I will keep trying.
(#bfbkxpq) @bender@twtxt.net I wished my mate would see it, too. But he turned his head a second too late. :-(
On today’s night walk I came across an absolutely giant shooting star. With it being visible for three seconds, it’s my second largest I’ve ever seen so far.
The sky picked up a few colors for just a few minutes: https://lyse.isobeef.org/abendhimmel-2025-11-13/
(#hnbf6ta) @movq@www.uninformativ.de Yup, it’s been some days here, too.
(#n7g6uxq) @movq@www.uninformativ.de Haha, you were spot on! It took me a bit to figure this out on my own. I’m actually very surprised to have gotten this wrong. Oh well.
(#3neip4q) No, I was using an empty hash URL when the feed didn’t specify a url metadata. Now I’m correctly falling back to the feed URL.
Hmmm, looks like my twt hash algorithm implementation calculates incorrect values. Might be the tilde in the URL that throws something off. :-? At least yarnd and jenny agree on a different hash.
(#uhwlufa) @bender@twtxt.net Hmm, didn’t find anything. But you mean a giant bucketload of access_log /home/$USER/logs/access.log if=… where the condition matches the requested path for said user? Yeah, that gets annoying very quickly. :-D
(#tqjqvwa) @movq@www.uninformativ.de Uuuhhh, beautiful! <3
(#dnzwh6a) @bender@twtxt.net Sounds about right.
I had a brainfart yesterday, though. For whatever reason I thought of subdomains, which are modeled with server entries in nginx. So, each could define its own access_log location. However, there are no subdomains in place! Searching around, I didn’t find any solution to give each user their own access log file.
One way would be a cronjob, aeh, systemd timer as I learned the other day, that greps the main access log and writes all user access log files with only the relevant stuff.
(#unjam3a) @movq@www.uninformativ.de Haha, right. :-D
Ah, it’s this famous font. :-) I already thought so, but wasn’t sure if it’s actually the same.
(#agua34q) @bender@twtxt.net Wasn’t that transferred to somebody else?
(#sxlpyva) @movq@www.uninformativ.de Oh, fuck them!
(#onzfgpa) @bender@twtxt.net Hahaha! :-D But I actually do like their approach. I don’t know what staff should do differently when they are not involved in the channel topic. At least in the general case. Maybe in this specific scenario here they could have cross-checked domains, git repos and stuff like that. But I also reckon that it’s only fair if they treat everybody the same.
(#vihysca) @bender@twtxt.net Of course, I didn’t do anything yet at all. Maybe I will find some time next weekend. Let’s see.
(#ulrmviq) @movq@www.uninformativ.de Wow, that’s a hell lot of food! If it doesn’t spoil, it’s easily enough for the rest of your life and all your neighbors and surrounding cities, probably more. :-D
That’s a great font. I like it. It just suits the print style incredibly well. No offence, to the absolute contrary, I would not have thought that you actually designed that. It looks just so right. Hats off! :-)
(#wswlm2q) @movq@www.uninformativ.de Have we reached peak enshittification yet?
YouTube is completely broken for me for a week or more. The player doesn’t even load anymore. Trying to limit the search results to real videos doesn’t do shit, etc. It’s useless. But downloading the videos with yt-dlp still works like a dream.
(#bwrwbdq) @movq@www.uninformativ.de Actually, @threatcat@tilde.club popped up in my own access log first. That’s how I discovered the feed. :-) So I figured that this feed author actually sees my reply. The hope is that with the next mention of my feed in threatcat’s feed, the other tilde users, who are following threatcat, are then also informed of my existence. :-)
I don’t know how tilde.club is set up. But it should be relatively easy to give all users access to their nginx access logs. Not sure if somebody already requested that or not. But I’d encourage tilde users to ask for that. Maybe also just for twtxt.txt and/or in a custom, reduced log format.
(#goq5brq) @lafe@tilde.club Hahaha! :-D That surely helps. What kind of plant are we talking about here?
Thank you for https://www.uninformativ.de/blog/postings/2025-11-09/0/POSTING-en.html, @movq@www.uninformativ.de! I never configured systemd timers, but I would have gotten it wrong, too. Good to know when I eventually stumble across that in the future. I’m still using cron. Yeah, its field order sucks and I always have to look it up (because I don’t deal with that all that often). Indeed, systemd’s order sounds more reasonable.
I should work on my client again and add some new features. Like adding a new feed directly in the client and not having to go to the config first. And showing a preview of a feed before actually adding it. Also, a search would be something to add. And finally combining my User-Agent analyzer with my subscription list to spot new feeds automatically.
(#7c3dhmq) @prologic@twtxt.net I’m all for it!
(#5ara5ka) Welcome to the party, @threatcat@tilde.club! I reckon it’s totally fine what you’re doing. Over time, message counts naturally drop anyway. :-D And this is fine, too.
(#5dyjtqa) @prologic@twtxt.net @movq@www.uninformativ.de Same here, I give each service a dedicated e-mail address. It’s very interesting to see how e-mail addresses are transferred to other actors. Luckily, this only happens rarely. But it does happen. In surprising ways.
Aliases not only help to fight spam, but are also a great way to specify filter rules to sort e-mails.
(#jxpe2iq) Tada, and it’s back! \o/
(#jxpe2iq) @quark@ferengi.one Very sad indeed! :-(
@eldersnake@we.loveprivacy.club Unfortunately, it’s back down again. But my hopes are high as it is a 503 this time and not a connection error anymore. :-)
(#dyyssga) @movq@www.uninformativ.de Brilliant, thank you! I didn’t know about that.
(#mok2vtq) Double congrats, @thecanine@twtxt.net! \o/
I’m not a fan of the gemtext limits. This being only a single page (which probably doesn’t get updated a whole lot), the efforts of having two dedicates files are not all that big, or so I’d at least naively imagine.
I always recommend checking the W3C validator results, even though I’m very guilty of not doing that myself. It just doesn’t occur to me in the heat of the moment. I reckon if I were writing HTML on a more regular basis, I would pick up on making that a real habit. Anyway, your HTML being generated, you probably can’t address the findings, though. So, might not be even worth the time heading over to the validator.
From a privacy point of view, personally, I would definitely host the CSS myself. Other than that, nice link collection. :-)
(#es2jiwq) @prologic@twtxt.net He’ll be probably back in a few days or weeks I reckon. It’s not the first time that his raspi (or what hardware does he use again?) is down. :-)
(#34cy36q) @movq@www.uninformativ.de Great writeup! It’s just missing a section on burning down the planet.
(#ikbmtja) @movq@www.uninformativ.de Ah, I see.