@bender@twtxt.net I just couldnāt resist the temptation, now that my usal setup has started acting funny. But Iāll keep that in mind
@aelaraji@aelaraji.com was it hard to set up for you?
@aelaraji@aelaraji.com Still improving things š¤
@aelaraji@aelaraji.com do not use twtxt.app yet. It has issues that @prologic@twtxt.net will fix soon.
@aelaraji@aelaraji.com At least your feed works as well your avatar š
@prologic@twtxt.net it is weeds, not really grass. The first was fairly green, but camera turned it more yellow than it is. The short one is brownish/yellow, yes.
I donāt know why, but either Jennyās behaving different after the last update, or I Fucked up something and I have no Idea how to fix it.
Symptoms:
- I donāt have copies of my New Posts in my Maildir after posting them (as in I donāt see them in neomuttās inbox).
- Nor fetch or fetch context (if they get replied to) seem to fech them auto-magically.
- I had to do a full whipe (~/Maildir/twtxt and ~/.cache/jenny) in order to get them fetched back.
Host header is sent by the client. And donāt even think about serving UTF-8 or even just putting utf-8 in the content type. š
And for the JPEG thumbnails I pass a special flag to ImageMagick so that IBM Web Explorer from OS/2 wonāt trip. 𤣠And always use link rel="stylesheet" for CSS, because some browsers render inlined CSS as literal text. And ⦠probably more that I forgot by now. š
@bender@twtxt.net Oh my god! š Thatās worth a small fortune on eBay. š¤£
Host header is sent by the client. And donāt even think about serving UTF-8 or even just putting utf-8 in the content type. š
And for the JPEG thumbnails I pass a special flag to ImageMagick so that IBM Web Explorer from OS/2 wonāt trip. 𤣠And always use link rel="stylesheet" for CSS, because some browsers render inlined CSS as literal text. And ⦠probably more that I forgot by now. š
@movq@www.uninformativ.de see anything you like here? š¤

@GabesArcade@gabesarcade.comās Arcade@gabesarcade.com nice! TIL about āPlanet of Lanaā, and I think it will be the very first game I will buy on iOS. Thank you for sharing!
@bender@twtxt.net Thanks! I wanted that to never end as well. :-)
@movq@www.uninformativ.de Even way lower than that.
@aelaraji@aelaraji.com can atest, feed is now reachable! Thanks mate!
@prologic@twtxt.net @bender@twtxt.net @movq@www.uninformativ.de @aelaraji@aelaraji.com Success!
@arne@uplegger.eu Iāve tried Matrix before, it was all good and dandy until servers started getting spammed with stuff no sane human being should see (if you know what I men). So, I took down my server and never looked back.
@prologic@twtxt.net My bad. It has been a while since the last time I poked around my mystery box, and I must have Effed up something yesterday. Is it fixed now? (Also, Iāve noticed that access to my avatar is, somehow, still denied. Still poking at it. š¤¦)
Wow! @arne@uplegger.eu isnāt kidding! See: https://rz.uni-greifswald.de/dienste/allgemein/instant-messaging-chat/
@prologic@twtxt.net hear hear! IRC all the way. š
@movq@www.uninformativ.de Welcome to the University Computer Centre Greifswald, where we like FLOSS and have never known fear or money!
@movq@www.uninformativ.de LOL. I canāt imagine a workplace using Matrix. It simply⦠boggles my mind.
@arne@uplegger.eu You have Matrix at work? No Teams, Google Chat, Slack, Discord, whatever, but Matrix? Really? Where do you work, is this Socialist Russia?!
@movq@www.uninformativ.de I donāt. but i do use IRC so hmmm š§
@aelaraji@aelaraji.com At work we used to have XMPP/Jabber Chat-Clients but now they are obsolete, due to the introduction of Matrix.
@lyse@lyse.isobeef.org How many people are still using XMPP? š¤ Iād expect the number to just as low as IRC users? š¤
@prologic@twtxt.net Neither can I. š±
@prologic@twtxt.net neither can I. Very well protected!
@aelaraji@aelaraji.com I cannot view your raw feed š§ 

@balloonfu-sen@yarn.girlonthemoon.xyz LOL 𤣠Too late! I already saw it and replied š
@balloonfu-sen@yarn.girlonthemoon.xyz That depends on the display configuration and preferences.
@bender@twtxt.net Danke š
@prologic@twtxt.net will open an issue, yup.
@david@daiwei.me I agree! Letās get them back into the fold š¤
@bender@twtxt.net Please create an issue for this too! Probably against twtd right? We should validate new fetchers and see if they are real clients or not. I think yarnd already does ybis quite well? š§
@bender@twtxt.net Thank you! š
@lyse@lyse.isobeef.org simplified it a little bit. Using only *bot* will bring collateral damage I want to avoid (there are, still some āgoodā bots):
@aibots {
header_regexp User-Agent (?i)(GPTBot|ChatGPT|OAI-Search|anthropic|Claude|Google-Extended|FacebookBot|CCBot|Perplexity|Applebot-Extended|cohere|Omgili|Bytespider)
}
abort @aibots
@prologic@twtxt.net I linked you some of my findings on the twtxt.app on IRC. The main problem is the hashing. Totally broken. But you have got to give it some thought, because GitHub hosting of the feed is tricky (even more so if they are CNAMEing their domain to it). It is also finicky because Pages is auto-enabled on username.github.io, so actions must run each time you twt.
@prologic@twtxt.net done: https://git.mills.io/yarnsocial/feeds/issues/41
And if we can compile a list and file issues for feeds, twtxt.app and anything else as issues for when i get back š feature requests, bug reports. etc š¤
@bender@twtxt.net Danke š
@prologic@twtxt.net I will.
@GabesArcade@gabesarcade.com Thanks for reporting! I will fix this š Soon!
@lyse@lyse.isobeef.org 07, right there, is my favourite. Thatās not to say I donāt like the rest. I love them all! I donāt think I would ever get tired of enjoying that view, each and every day. š
@david@daiwei.me Some entries can be probably simplified with just *bot*. :-) (But I donāt use Caddy, so no idea about case (in)sensitivity.
That reminds me, I should do something similar with my Nginx.
@aelaraji@aelaraji.com I do use XMPP. But only the text chat part. ;-)
@movq@www.uninformativ.de Hier hab ich zum Glück überhaupt gar nichts davon mitbekommen.
@bender@twtxt.net Iām glad to announce that Lyseās Free Nose Cleaning Service is now internationally available.
@movq@www.uninformativ.de Congrats! :-)
@movq@www.uninformativ.de There is nothing like that on Linux, because you donāt need it. Everything just works!
@bender@twtxt.net Haha! Thanks. The broken avatar was a Me and my Hotlinking policy problem, It should be fixed by now. And I Freaking love the twtxt.app by the way. Cheers!
@GabesArcade@gabesarcade.com Thatās Halo? I donāt think I ever saw that in person ⦠š¤
@lyse@lyse.isobeef.org I got coffee coming out of my nose on this one. š¤£
One day, @lyse@lyse.isobeef.org, one day!
@prologic@twtxt.net Very nice! Which boat is yours? :-)
@aelaraji@aelaraji.com wow, look who the cat dragged in! š I was thinking about you just yesterday, when testing the twtxt.app, and seeing your avatar photo broken. And today, here you are! Nice to āseeā you mate!
@rdlmda@rdlmda.me THIS! ⦠has been my daily mantra, for at least 8 months; and Iām still waiting for some Magic⢠to happen.
@prologic@twtxt.net Oohhhhhhhh, lovely. š
@movq@www.uninformativ.de Right now it 16C and 8.30PM
@prologic@twtxt.net That looks nice! Whatās the temperature?
@arne@uplegger.eu Really?! Wow! š³
@prologic@twtxt.net You have trees at the campsites Down Under? Thatās really luxur! š©
Everywhere Iāve been (Europe) they chopped down the trees - no shadow - nowhere.
Just a couple of shots of where were staying š

FYi š Iām aware of an optimist precomputed hashing bug on the new twtxt.app 𤯠Trying to work with @bender@twtxt.net remotely on my vacation yo fix it š¤£
@GabesArcade@gabesarcade.com The no-JS part is one thing, but you also have to disable the (nowadays common) forced-HTTP-to-HTTPS-redirect, because those old browsers canāt do modern crypto. And make sure that your webserver serves the correct page even if no Host header is sent by the client. And donāt even think about serving UTF-8 or even just putting utf-8 in the content type. š
And for the JPEG thumbnails I pass a special flag to ImageMagick so that IBM Web Explorer from OS/2 wonāt trip. 𤣠And always use link rel="stylesheet" for CSS, because some browsers render inlined CSS as literal text. And ⦠probably more that I forgot by now. š
@david@daiwei.me Not sure, actually. Letās see. Those are the ones where I still have the original disks (or have bought them on eBay again):
- SuSE Linux 6.4 (itās a massive 7 CD distro with a huge manual, best thing ever)
- OS/2 2.1
- OS/2 Warp 3 (red and blue spine because
$reasons)
- OS/2 Warp 4
- PC DOS 7
- MS-DOS 6.22
- Windows 3.1
- Windows for Workgroups 3.11
- Windows 95 C
- Windows 98
- Windows NT 4 Workstation (still in the mail, though š
)
- Windows 2000
- Windows XP Professional (last Windows I ever used on my private PCs)
(Plus a few āclassicā office products as can be seen here: https://movq.de/blog/postings/2024-05-23/0/POSTING-en.html )
As an example, this is a thread @GabesArcade@gabesarcade.comās Arcade@gabesarcade.com and @david@daiwei.me carried all on twtxt.app, no issues: https://twtxt.net/conv/r4uf52ggwseh
@movq@www.uninformativ.de I figure there is a bug somewhere, but where?

@lyse@lyse.isobeef.org Oh yeah, few people are as persistent as her. That said, itās really easy to give up. This shit is overwhelming.
@david@daiwei.me as you alter ego, I seriously recommend you stop creating feeds left and right. But whom am I kidding, right?! š
I wonder how long will it take to show a follower on twtd. It only shows the feedās owner, so far.
@citizenalex@citizenalex.envs.net Correct.
@arne@uplegger.eu Whoah! āSchaffung eines Aufenthaltsraumes für Nichtraucher!ā Irre, dass es einen solchen vor dem 1. Mai 1975 nicht gab. Kann man sich heute überhaupt nicht vorstellen.
Cool, schƶnes Heftchen hast Du da gesetzt. :-) Die Lochkartenanzahlen sind auch der absolute Wahnsinn.
I know whatās happening. Will come back later to explain (for @prologic@twtxt.net).
@itsericwoodward@itsericwoodward.com @bender@twtxt.net Oh, I missed that. Whoopsy daisy!
@kiwu@twtxt.net Hanging on by a thread is plenty good enough for many spiders, so it should be sufficient for you, too!!1!
@arne@uplegger.eu Das āalteā RechenzentrumsgebƤude wurde 2020 leer gezogen und einige Jahre spƤter abgerissen. Einen kleinen Einblick ins Innere gibt es in der URZ-Chronik von 2009.
@movq@www.uninformativ.de we found a bug. @prologic@twtxt.net loves it!
@bender@twtxt.net āTwt could not be foundā š¢
@bender@twtxt.net I, too, should take a nap now.
@bender@twtxt.net For forkās sake!
@david@raw.githubusercontent.com your fork worked, and this is a fork, of your fork. Letās forkāem!
Congratulations! I am using twtxt.app, and it rocks!
Hmmm the Twtxt App isnāt grouping threads correctly š§
Set/GetDisabled(ā¦) and PasteHandler(), tt starts up fine and seems to work without issues.
@movq@www.uninformativ.de @bender@twtxt.net Indeed! No idea why this isnāt the default in the first place.
@itsericwoodward@itsericwoodward.com Twtxthashgeddon, hahahaha, brilliant. :-D
@itsericwoodward@itsericwoodward.com Haha! Iām glad you like it! 𤣠I ummed and arrred over the set of publishing backends it should support, and in the end decided to support Yarn, Github/Gitea and twtd. I hope thatās enough and flexible enough for most folks š¤
@itsericwoodward@itsericwoodward.com Ahh youāre welcome bud! š
Adding support for forking, forked conversations and navigating back to the root of a thread for the Twtxt App š¤
lleeypvkzbw2? That Twt was never ingested by twtxt.net (and likely the search engine) so umm hmmm threading breaks š¤£
@GabesArcade@gabesarcade.com Youāre welcome! āŗļø
lleeypvkzbw2? That Twt was never ingested by twtxt.net (and likely the search engine) so umm hmmm threading breaks š¤£
Oh if weāre talking about the twtxt.app client, thatās a different story. I still consider that alpha/beta quality. Lemme look into that. It has itās own cache of course (using IndexDB) and itās entirely possible some behaviours are still not quite right yetā¦
lleeypvkzbw2? That Twt was never ingested by twtxt.net (and likely the search engine) so umm hmmm threading breaks š¤£
I see the same thing, @prologic@twtxt.net. They will eventually disappear.
lleeypvkzbw2? That Twt was never ingested by twtxt.net (and likely the search engine) so umm hmmm threading breaks š¤£
@GabesArcade@gabesarcade.com Wiath what client? š¤
@bender@twtxt.net I donāt see it š
It was showing twice in my timeline. Both twtxts.
lleeypvkzbw2? That Twt was never ingested by twtxt.net (and likely the search engine) so umm hmmm threading breaks š¤£
@GabesArcade@gabesarcade.com Yes, because if you edit/delete a Twt after the ecosystem has ingested it, well there then are two versions š Just be aware of edits/deletes, especially if someone has already replied to said Twt š¤£
@GabesArcade@gabesarcade.com Did you by change edit or otherwise delete the Twt you replied to (2nd last in your feed) with the reply/thread id lleeypvkzbw2? That Twt was never ingested by twtxt.net (and likely the search engine) so umm hmmm threading breaks š¤£



