@prologic@twtxt.net will miss the first couple, but will sure join when we return from vacations! 😊
$ units -t '500 gigabytes per 9 hours' 'megabytes per second'
15.432099
That’s a very unfortunate speed in the year 2024.
@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?
@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 🤣
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.
~/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
🤦♂️
👋 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 😅
~/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 🤬
@movq@www.uninformativ.de Wut?! 🧐 How do you get notified? 🤔
twtxt.net
), I'm going to be deleting 235 accounts today: https://gist.mills.io/prologic/0381c79977384051bb0b4afc89b4893d
I think the next cleanup I’ll do is to delete any account that was created, and then used within some time window and never used again. Does that make sense? 🤔
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 I think you were the one that originally came up with this BUIDL
thing. Was it always suppose to be the commit timestamp? 🤔
@lyse@lyse.isobeef.org What if they see traffic again at some point? 🤔 How do you fetch feeds again? You fork/exec out to the Python twtxt
client right? 🤔
@lyse@lyse.isobeef.org Since some time ago I automated the same feature in yarnd
; I haven’t really noticed when it happens. But I went and had a look just now, looks like it “just works”™ and no-one notices 🤣
$ dke -t f3fe6f03902e /bin/sh
/ # cd /data/feeds
/data/feeds # ls -lah prologic*
-rw-r--r-- 1 yarnd yarnd 7.9K May 7 05:16 prologic
-rw-r--r-- 1 yarnd yarnd 877.8K May 3 23:32 prologic.1
-rw-r--r-- 1 yarnd yarnd 515.1K Mar 24 2023 prologic.2
-rw-r--r-- 1 yarnd yarnd 963.7K Nov 19 2022 prologic.3
-rw-r--r-- 1 yarnd yarnd 995.6K Mar 10 2022 prologic.4
-rw-r--r-- 1 yarnd yarnd 1.9M Nov 7 2021 prologic.5
@aelaraji@aelaraji.com I think you’ll find it simpler to use zs