In-reply-to » ROFL 🤣 I've found myself a new insult: :diffoff a vim command...

@prologic@twtxt.net it offends someone with a different opinion? 🤣

No, seriously… :diffoff is used to disable vim’s diff mode that’s usually started running vim -d someFile someOtherFile or by having both files on a split window and applying :diffthis on both panes. (just learned this this morning)

⤋ Read More

So I joined Stacker.news a few weeks ago. It’s like HackerNews if you consider a hot air balloon to rival a MiG-35 fighter jet.
And it turned out to be exactly what I expected.

⤋ Read More
In-reply-to » That FAT12 implementation is very naive and unoptimized. You can see in this video that it takes about 7 seconds to copy a ~10 kB file: https://movq.de/v/fbf2b90ce1/los86-fat12-copy.mp4 🥴 I kind of like that, though, because it feels a little bit like an old machine. 😅🤪

@prologic@twtxt.net Indeed, I’ve gained a lot more respect for Linux/BSD and DOS. 😃

⤋ Read More
In-reply-to » That FAT12 implementation is very naive and unoptimized. You can see in this video that it takes about 7 seconds to copy a ~10 kB file: https://movq.de/v/fbf2b90ce1/los86-fat12-copy.mp4 🥴 I kind of like that, though, because it feels a little bit like an old machine. 😅🤪

@prologic@twtxt.net Something along those lines, yeah. And/or some generic cache for disk sectors.

⤋ Read More
In-reply-to » That FAT12 implementation is very naive and unoptimized. You can see in this video that it takes about 7 seconds to copy a ~10 kB file: https://movq.de/v/fbf2b90ce1/los86-fat12-copy.mp4 🥴 I kind of like that, though, because it feels a little bit like an old machine. 😅🤪

@prologic@twtxt.net Lots, I guess. 😅 The kernel keeps almost no state between syscalls, so when you want to read the next byte from a file, it has to do all the work from scratch: Locate the file in the directory and traverse the cluster chain until you’ve reached the next byte. It’s easier to code this way, but obviously much slower. And the userspace program cp could read/write in multiples of 512 – it currently does not do that, intentionally, because if everything is a multiple of 512, you’re less likely to discover bugs. 😅

⤋ Read More
In-reply-to » 3°C today, it was quite nice in the sun. A lot of hunting and tree felling going on in the forest. And we met the heron again, that was very cool: https://lyse.isobeef.org/waldspaziergang-2024-12-28/

@movq@www.uninformativ.de All my cameras have an optical zoom. The current one even reaches 18x optical magnification. This feller was very relaxed as we snuck up on him. We didn’t want to scare him off, so we stopped at around four meters. Still, some zoom factor was used to caputure him. :-)

The last few days were very sunny, so is today and the next couple days. One just has to keep moving, or it gets too cold.

⤋ Read More
In-reply-to » That FAT12 implementation is very naive and unoptimized. You can see in this video that it takes about 7 seconds to copy a ~10 kB file: https://movq.de/v/fbf2b90ce1/los86-fat12-copy.mp4 🥴 I kind of like that, though, because it feels a little bit like an old machine. 😅🤪

(This issues a lot of BIOS calls, that’s why it’s so slow.)

⤋ Read More
In-reply-to » @emmanuel oh! Nice! You've now got a nice avatar 👌

@prologic@twtxt.net It’s hosted at home on an computer I didn’t use anymore. It worked well for a few months, and since maybe the beginning of December, it begun to be very slow. But like I said, I have no time for that now, but if I have questions when I’ll look, I’ll think of you 😅 (but I was thinking about installing a new OS before these problems, I may just do that).

⤋ Read More

After taking a short break for Christmas business, I’ve worked on my little toy operating system for the 8086 again.

It understands the basics of FAT12 now. I’ve actually never sat down before to learn how FAT works. 🤦 Well, better late than never, I guess.

It can’t do subdirectories nor timestamps and I probably won’t implement that. One flat directory is good enough for my purposes and the OS has no notion of time, yet, anyway.

It’s really cool to be able to exchange files with the Linux host or other DOS VMs. 🥳

https://movq.de/v/21e91bafdb/los86-fat12.mp4

⤋ Read More
In-reply-to » 3°C today, it was quite nice in the sun. A lot of hunting and tree felling going on in the forest. And we met the heron again, that was very cool: https://lyse.isobeef.org/waldspaziergang-2024-12-28/

@lyse@lyse.isobeef.org Have you got a zoom on your camera now? That looks very close for a heron. 🤯

Looks like a lovely day indeed. We only had fog all day and I was too lazy to go outside. 😂

⤋ Read More
In-reply-to » I’m currently writing a tutorial (in French) to learn the basics of groff + mom to typeset generalist PDF (not manpages). It’s my nerdy project for the time being, and it grew quite larger than I anticipated (it probably will have 40 pages when finished)… not because groff is hard, but because my goal is people who never touched a formatting language, so I have to cover the basics.

@emmanuel@wald.ovh Oh, that’s going to be interesting. It’s been a moment since I’ve used groff.

⤋ Read More

I’m currently writing a tutorial (in French) to learn the basics of groff + mom to typeset generalist PDF (not manpages). It’s my nerdy project for the time being, and it grew quite larger than I anticipated (it probably will have 40 pages when finished)… not because groff is hard, but because my goal is people who never touched a formatting language, so I have to cover the basics.

⤋ Read More
In-reply-to » Ghostly is available now. In the past I have used iTerm, but this time around I am going to try keeping as much vanilla tools as possible on macOS (thus will use Terminal, and see how it goes). Yet, this one looks interesting!

@emmanuel@wald.ovh good to know, thanks! I don’t think I will dabble with it, but it is good to know it exists. Considering its author, it is bound to get better.

⤋ Read More
In-reply-to » @eapl.me A way to have a more bluesky'ish handles in twtxt could be to take inspiration from Bridgy Fed and say: If NICK = DOMAIN then only show @DOMAIN So instead of @eapl.me@eapl.me it will just be @eapl.me

@doesnm@doesnm.p.psf.lt So the user should then set nick = _@domain.tld in the twtxt.txt?

It seems more intuitive and userfriendly to just use: nick = domain.tld and have then convention for clients to render the handle as @domain.tld instead of @domain.tld@domain.tld

For a feed with no nick defined (eg. https://akkartik.name/twtxt.txt) it will also be simpler and make more sense to just use the domain as the nick and render it as @domain.tld

⤋ Read More
In-reply-to » For Example:

@eapl.me@eapl.me A way to have a more bluesky’ish handles in twtxt could be to take inspiration from Bridgy Fed and say: If NICK = DOMAIN then only show @DOMAIN
So instead of @eapl.me@eapl.me it will just be @eapl.me

And it event seem that it will not break webfinger lookup: https://webfinger.net/lookup/?resource=%40darch.dk (at least not for how I’ve implemented webfinger on my sever for a single user;)

⤋ Read More