The “annoying” thing about hardware these days is that it basically keeps working “forever”. At least much, much longer that you’d expect.
Now that I think about it … I only remember one PC of mine actually dying because of a hardware failure – and that was probably because I did too much overclocking. 😂 If it wasn’t for changes in software, I could probably still use them all. I mean, why not, my Pentium 133 still works and I use it for gaming regularly.
So … my little NAS probably won’t die any time soon. Hmmm.
@mckinley@twtxt.net Not really sure, to be honest. Probably a couple hundred GB … ? 🤔 With the changed data, it might be half a TB to transfer? I’m just guessing.
Let’s see how it goes next time. I don’t expect to add much data any time soon. (On the other hand, I’ll swap the USB disks for the next run, so it’ll take the same ~9 hours, again. Meh.)
I think the solution is to have less data. 😈
@movq@www.uninformativ.de That’s no fun at all. I don’t like to throw away working hardware either, but I wouldn’t wait 7 hours (CPU-bound!) for my manual backup to complete if it could be done faster on a 10 year old laptop with AES-NI. How much data did you add?
@lyse@lyse.isobeef.org Yeah, only ~30 of the ~133 feeds I’m following have had a twt in the last month … 56 in the last year. Some had their last twt in 2016. 🫤
@aelaraji@aelaraji.com Ahh no worries! 😉 I hope the docs are okay 👌
@slashdot@feeds.twtxt.net Good, those US congressmen are fucking idiots I swear to god 🤣 They don’t know the difference between China, Taiwan, Singapore or Thailand if they fell over those countries backwards 😅 Bunch of old farts 💨
I think I found the bug 🐛
twtxt.net
), I'm going to be deleting 235 accounts today: https://gist.mills.io/prologic/0381c79977384051bb0b4afc89b4893d
I just dropped another 124 useless accounts 🥳
@movq@www.uninformativ.de I did indeed edit a Twt just now 🤣 probably from this thread IIRC (typo) 😅
@movq@www.uninformativ.de I know right 😅 This can’t be true, I must be over reacting and something else is fucked up with some code somewhere 🤣
Ninguém pode obrigar PS ou AD a ir a debates. Mas é de todo inaceitável que a sua indisponibilidade sirva de chantagem, que se resolva discriminando todas as outras candidaturas para colocar estas duas em posição de destaque.
Fica bem o Bloco, que ameaça com uma providência cautelar se as televisões insistirem nessa ideia:
@EsquerdaNet@EsquerdaNet https://masto.pt/@EsquerdaNet/112395601755516016
@prologic@twtxt.net From the DOM? That can’t be right. 😳😳😳
@prologic@twtxt.net It always fetches the canonical feed URL and, when it can’t find the latest twt hash (that it saw in the previous run) it traverses the archived feeds until it does find it. Something along those lines.
I just got one such notification:
Date: Tue, 07 May 2024 15:56:01 +0200
From: me@pinguin
To: me@pinguin
Subject: [regularly] jenny
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/1 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/2 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/3 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/4 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/5 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Now, your feed did not get archived, as far as I can tell. So why am I getting this then? Have you edited a twt just now? That would explain it. 😅
Or maybe someone added some janky javascript into the codebase I can’t find 🤔
@movq@www.uninformativ.de No it’s stripping it from the DOM. The server is sending a document with fragments in the URI(s) of links that are ‘Inreply-to” links (for context). Chrome is stripping them!
@lyse@lyse.isobeef.org Fair enough, I mean I have the same sets of problems too.
@prologic@twtxt.net Strip it from what? From requests being sent to the server? That’s always been the case, afaik. 🤔
~/go/bin
to your $PATH
, at least I did. I’m not sure what to do about it, though. 🤔 This doesn’t really belong into Yarn’s setup guide and it’s mentioned as one of the first things in the Arch wiki, for example, but still … To newcomers this might look a bit like a broken build process:
@movq@www.uninformativ.de Noice 👌
@movq@www.uninformativ.de Oh, and then it switches to the new active feed? 🤔
@movq@www.uninformativ.de It appears to strip the #fragment
🤦♂️
@prologic@twtxt.net Huh? What does that look like in Chrome? 🤔 (I only have Chromium.)
👋 Okay folks, let’s startup the Yarn.social calls again.
- Event: Yarn.social Online Meetup
- When: 25th May 2024 at 12:00pm UTC (midday)
- Where: Mills Meet : Yarn.social
- Cadence: 4th Saturday of every Month
Agenda:
Anything we want to talk about. Twtxt, Yarn, self hosting, cool stuff you’ve been working on. chit-chat, whatever 😅
@prologic@twtxt.net My client tells me when it fetches archived feeds. That’s all.
~/go/bin
to your $PATH
, at least I did. I’m not sure what to do about it, though. 🤔 This doesn’t really belong into Yarn’s setup guide and it’s mentioned as one of the first things in the Arch wiki, for example, but still … To newcomers this might look a bit like a broken build process:
@prologic@twtxt.net Ah, yes, that’s better! 👍
~/go/bin
to your $PATH
, at least I did. I’m not sure what to do about it, though. 🤔 This doesn’t really belong into Yarn’s setup guide and it’s mentioned as one of the first things in the Arch wiki, for example, but still … To newcomers this might look a bit like a broken build process:
@movq@www.uninformativ.de Fixed 👌
yarnd setup
look like to anyone? 🤔 Let's say it exists, and it helps you setup a Yarn pod in seconds. What does it do? Of course I'd have to split out yarnd
itself into yarnd run
to actually run the server/daemon part.
@lyse@lyse.isobeef.org Anyway fixed 👌
I just realized something that’s completely fucked up.
$ curl -qssL https://twtxt.net/ | grep -E 'In-reply-to' | head
<a href="https://twtxt.net/conv/2tjsjuq?p=1#rlsxhsq" title="Show conversation for #2tjsjuq">In-reply-to</a>
<a href="https://twtxt.net/conv/bghmkra?p=1#dfnrbyq" title="Show conversation for #bghmkra">In-reply-to</a>
<a href="https://twtxt.net/conv/e24exeq?p=1#itft6wa" title="Show conversation for #e24exeq">In-reply-to</a>
For some reason the latest version of Chrome is stripped #fragment
(s) from the HTML body being served.
da fuq?! When did this change, in what version? Did we (W3C and the community) agree that this behavior should change?! 😱 Fark’n hell Google™ Chrome 🤬
yarnd setup
look like to anyone? 🤔 Let's say it exists, and it helps you setup a Yarn pod in seconds. What does it do? Of course I'd have to split out yarnd
itself into yarnd run
to actually run the server/daemon part.
@prologic@twtxt.net Oh, was I? I don’t recall any of that. But who knows. ;-)
@movq@www.uninformativ.de Wut?! 🧐 How do you get notified? 🤔
@prologic@twtxt.net I won’t see any activity again, unless somebody else I follow interacts with them. Yep, fetching the feeds still happens with a patched version of the original twtxt client. tt is just a viewer of the database contents.
(Hmmm, I think I could add the time of the last twt to the output of jenny -l
. 🤔 Currently it only shows the last successful retrieval time.)
@prologic@twtxt.net Every now and then, I get a notification about Yarn feeds getting archived/rotated. 😅 Appears to work without issues. 👍