Just today I heard someone whining about how in LinkedIn and other recruitment sites there’s like five bazillion profile tag options for RDMBSes and various dialects of SQL… when in actuality the recruiters are probably only concerned if the developer can do a bloody SELECT and stuff.

You Chrome folks need extensions to use non-Google search engines?

Firefox uses just bog standard OpenSearch definitions. No shenanigans. Ships with both Google and Bing if you’re into that sort of things. And you can add arbitrary search URLs, no probalo.

deleted by creator

NOP is $EA, of course, and… um…

…sorry, I’m just a Commodore 64 scrub, I don’t know nothing about this high and mighty Intel 8086 nonsense.

[looking up]

…it’s 0x90 on IA-32? WHAT? Someone told me every processor used 0xEA because that was commonly agreed and readily apparent. …guess I was wrong

Scrivener!

The frustrating thing is that, at least for me, there are no perfect word processors geared for novels and other scenarios where you manage large text masses.

Scrivener is one of those cases where you have a pretty excellent software that doesn’t have a lot of problems OSS alternatives have. I have smooth time with it. But at the same time, the software always could be better.

Probably the best OSS novel writing software I’ve used is Org-Mode for Emacs. But, you know, it’s based on Emacs, so it squeaks around the edges and gives the impression that it’s a miracle it runs as brilliantly as it does.

They recently added some unlockable graphics for the widget. Nothing major.

Guess they changed the icon just for the hell of it while they were at it.

Yeah, I just tried upgrading my Gitea Windows instance to Forgejo via Docker, and it actually works pretty much as easily as it did before. Fantastic! Might just leave it here instead of shoving it all in the VM - I can always do that later if it’s necessary. Having a full VM does have upsides, but in this particular instance this is definitely good enough.

Heh, your comment actually made me finally go and resolve a problem I’ve had since I got this laptop in 2020. I didn’t have SVM virtualisation acceleration enabled because that made Windows unable to boot somehow. A bit of twiddling after, it finally did! VirtualBox runs! Docker runs!

…but why would I use Docker for something like this. Might as well blow the dust off of my FreeBSD virtual machine and run Forgejo there!

What’s the latest on Forgejo’s Windows builds? Last I checked there was no Windows build due to no volunteers for build/test - Gitea’s old build stuff should still be good.

Which is a mild shame because Gitea’s Windows version was an insanely simple way to run it if you are a solo dev on Windows and need a private Git site. Drop the binary on an USB hard drive, run it on terminal, boom, done.

(Currently contemplating just setting up a Raspberry Pi server.)

I’m going to just say that I’m exteremely sceptical on how this will turn out, just because there has been quite a few Wikipedia forks that have not exactly worked out despite the best interests and the stated objectives they had.

Now - Wikipedia isn’t exactly an entity that doesn’t have glaring problems of its own, of course - but I’m just saying that the wiki model has been tried out a lot of times and screwed up many times in various weird ways.

There’s exactly two ways I can see Wikipedia forks to evolve: Crappily managed fork that is handled by an ideological dumbass that attracts a crowd that makes everything much worse (e.g. Conservapedia, Citizendium), or a fork that gets overrun by junk and forgotten by history, because, well, clearly it’s much more beneficial to contribute to Wikipedia anyway.

I was about to respond with a copy of the standard Usenet spam response form with the “sorry dude I don’t think this is going to work” ticked, but Google is shit and I can’t find a copy of that nonsense anymore, so there.