Did GitHub Copilot really increase my productivity?
Yuxuan Shui, the developer behind the X11 compositor picom (a fork of Compton) published a blog post detailing their experiences with using GitHub Copilot for a year. I had free access to GitHub Copilot for about a year, I used it, got used to it, and slowly started to take it for granted, until one day it was taken away. I had to re-adapt to a life without Copilot, but it also gave me a chance to look back at how I used Copilot, … ⌘ Read more

It’s a beautiful day in the neighborhood.

@movq@www.uninformativ.de sounds like a very good place to start! 😊

@Rob@jsreed5.org you forgot to add “said no one”. 🤭

How To Efficiently Copy Files To Multiple Destinations: https://mckinley.cc/notes/20240508-copy-multiple-destinations.xhtml

I suspect that people who came to Gemini from Gopher are more satisfied with the protocol than people who came to Gemini from HTTP.

@prologic@twtxt.net Doesn’t matter. Far, far away! From everything! That’s where I’d go. 😂

Ran a few tests.

Copying data from the NAS’s encrypted ZFS pool to the USB disk’s encrypted btrfs runs at ~20 MByte/s. That is for a single 1 GB file of random data. Cold caches, sync included.

That same USB disk with the same btrfs can sustain ~75 MByte/s when I use it on my workstation (i7-3770).

And indeed, the aes flag does not show up in the output of lscpu on the NAS.

I’ll try to tweak some things about this, but it might be time for an upgrade … 🫤 (Or I’ll have to re-think the entire thing somehow.)

@lyse@lyse.isobeef.org Where to? 🤔

What’s that thing called when everyone on a social media platform (hardly matters which one) all post the same sort of thing. It all sounds oh so wonderful, or all so dramatic, everyone claps and cheers and thumbs up or whatever. What’s that thing called? There’s a term for it hmmm 🧐

All packed, ready to go.

Use your energy 💪

@mckinley@mckinley.cc That’s a cool idea!

we’ll just have to run another one in early June just for you 😅

@bender@twtxt.net LOL well I’ve scheduled it for the end of the month 😆

@dbucklin Nice quote 👌

I don’t pretend to have all the answers. I don’t pretend to even know what the questions are. Hey, where am I? - wigums

@prologic@twtxt.net I can’t recommend it enough.

@prologic@twtxt.net towards the end of the month.

@mckinley@twtxt.net looks nice! 👌

When do you get back from your holiday? 🤔

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! 😊

@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. 🥴

@prologic@twtxt.net Kehrwoche! :-)

@movq@www.uninformativ.de

$ 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. :-)

@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. 🫤

@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 💨

TikTok Sues US Government Over Law Forcing Sale or Ban
Less than two weeks after President Biden signed a bill that will force TikTok’s Chinese owner, ByteDance, to sell the popular social media app or face a ban in the United States, TikTok said it sued the federal government on Tuesday, arguing the law was unconstitutional. From a report: TikTok said that the law violated the First Amendment by effectively removing an … ⌘ Read more

I think I found the bug 🐛

I just dropped another 124 useless accounts 🥳

Image

@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 🤔

@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. 🤔

@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.)