Viddy, a modern watch(1) alternative with paging, visual diffs, and history: https://github.com/sachaos/viddy
@prologic@twtxt.net will miss the first couple, but will sure join when we return from vacations! 😊
New at #SEP: The Incommensurability of Scientific Theories https://plato.stanford.edu/entries/incommensurability/
@mckinley@twtxt.net It’s probably a bit faster, but not much. Maybe 20-30 MByte/s (I watched one 40 GB file being copied and it took 20-30 minutes or something like that.)
I need to optimize this. 🥴
twtxt.net
), I'm going to be deleting 235 accounts today: https://gist.mills.io/prologic/0381c79977384051bb0b4afc89b4893d
$ units -t '500 gigabytes per 9 hours' 'megabytes per second'
15.432099
That’s a very unfortunate speed in the year 2024.
@prologic@twtxt.net I noted it in my calendar, looking forward to it. :-)
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 Cool!
@movq@www.uninformativ.de I’m subscribed to 48 feeds at the moment. And only a fraction is actually active.
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. 🫤
New at #SEP: Vienna Circle https://plato.stanford.edu/entries/vienna-circle/
@aelaraji@aelaraji.com Ahh no worries! 😉 I hope the docs are okay 👌
@prologic@twtxt.net Checking it out right away! Thanks!
New at #SEP: Miracles https://plato.stanford.edu/entries/miracles/
@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 🤣
@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 🤔