I’ll take FOSS over the proprietary software we can be sure will do malicious things to us any day.

I don’t know anything really about Stormux or HomeAssistantOS, but ArchLinuxARM is honestly going down the tubes. I use it a lot, but I’m pretty well decided to switch away from it.

The ArchLinuxARM package repos are constantly ridiculously out of date, and the folks in charge of ArchLinuxARM a) aren’t doing anything to fix it and b) won’t let the community help or even talk about the issue. (They lock threads and otherwise shut down conversation on the topic.)

It’s a bummer. Arch is a great OS (coughasidefromsystemdcough) and it’s nice to be able to run it on a Raspberry Pi. But as it is, it’s hard to see it as usable for real-world use cases. Maybe someone someday will create a new Arm-focused version of Arch (maybe Arch proper will even decide to start supporting Arm) unrelated to the existing ArchLinuxARM project. But for now, it’s terrible.

Pewdiepie is a Nazi.

Nazis still deserve punches.

Are you thinking of AlternativeTo?

My solution is scp with termux. I can’t suggest any better alternative.

Uninstall it and make the world a slightly better place?

The GPL family of licenses was designed to cover code specifically. AI engines are code and are covered in most jurisdictions by copyright. (Disclaimer: I know a lot less about international intellectual property law than about U.S. intellectual property law. But I’m pretty confident what I’ll say here is at least true of the U.S…) But you don’t really have a functional generative AI system without weights. And it’s not clear that weights are covered by any particular branch of intellectual property in any particular jurisdiction. (And if they are, it’s not clear that the legal entity who trained the engine owns those rights on those weights rather than the rights holders who hold rights to the materials being used as training data.) It’s the weights that would make for any biases or purposefully nefarious output. Nothing that isn’t covered by intellectually property can meaningfully be said to be “licensed”, really. Under the AGPLv3 or any other license. To speak of something not covered by any intellectual (or non-intellectual, I suppose) property as “licensed” is just kindof nonsensical.

Like, since Einstein’s General Relativity isn’t covered by any intellectual property, it’s not possible for General Relativity to be “licensed”. Similarly, unless some law is passed making LLM weights covered by, say, copyright law, one can’t speak of those weights being “licensed”.

By the way, there are several high-profile cases of companies like Meta releasing LLMs that you can run locally and calling them “Open Source” when there’s nothing “Open Source” about them. As in, they don’t distribute the source code of LLaMa at all. That’s exactly the opposite of “Open Source” and the weights aren’t code and can’t really be said to be “Open Source”. More info here.

Now, all that said, I don’t think there’s actually any inherent benefit to LLMs, AGPLv3 or otherwise, so I don’t have any interest even in AGPLv3 engines. But I’m all for more software being licensed AGPLv3. I just don’t think AGPLv3 is a concept that applies to any portion of LLMs aside from the engine.

AnySoftKeyboard does. And it’s under an Apache 2.0 license which is fully foss.

FUTO Keyboard was forked from another project which is Open Source. But the license FUTO keyboard itself is under, by restricting modifications to for non-commercial purposes and forbidding removal of functionality that allows the user to make payments to FUTO, fails to qualify as “Open Source”.

FUTO keyboard is not Open Source.

FizzyOrange got it right. “Screen grab” is nicely asking a graphical system (X11/xorg-server or a Wayland compositor or whatever) via an api to give you an image of either the whole desktop or some particular rectangular part of it. And you can do it 30 times every second (or more) to get a video. OBS uses such APIs to get video from the screen for saving to a file or streaming to Twitch or whatever. Various tools can be used to get screenshots and save them to files. Etc.

Heck. On my work machine, because they require us to meticulously log the time we spend on individual tasks, I’ve got a script running that uses ImageMagick’s import command to grab screenshots of my desktop and save them to files once every 5 minutes so I can refer back to them while logging my time.

And as FizzyOrange said, various Wayland compositors have workarounds for the fact that there isn’t (or rather wasn’t until recently) a way to do screen grab in a standard way that would work across all compositors which properly and comprehensively implement the Wayland protocol. I use Sway on my personal machines and it’s based on something called wlroots which has built-in a nonstandard extension to the Wayland protocol that allows screen grab. But once wlroots adopts the new standard way of doing screen grabbing, the nonstandard extension will be unneeded/obsolete.

Oh shit! I hadn’t heard they’d finally added that. That’s awesome.

Maybe that means FFMPEG and Zoom will start supporting it soon.

On my personal systems, I use Sway (a Wayland compositor). And I sometimes wish I could do screen grab with FFMPEG, but so far I haven’t wanted that enough to actually switch to X11 or use wl-screenrec.

On my work machine, I’m on Ubuntu and I have to use Zoom and screen sharing is kindof a non-negotiable thing. (Plus, FFMPEG screen grab is nice to have on my work machine as well.) So I use i3-gaps on xorg-server. Except for those two things, I’d rather use Sway.

Wake me when they add screen grab.

We have to go deeper.

I like IceWM pretty well… for a non-tiling WM, that is. 😉

It’s very lightweight.

The README in the repo indicates it’s based on the NEO-PI, which is kindof the gold standard in personality tests at least right now from what I understand.

Book recommendation for folks who might want to know more about the topic of personality psychology. Me, Myself, and Us: The Science of Personality and the Art of Well-Being by Dr. Brian Little.

I write Java for a paycheck, but I really hate it.

It feels like everything is layers and layers of overengineered cruft, each added to the precarious tower for something extremely minor. But every subsequent card in the house of cards makes it more precarious. “But look, I don’t have to write accessors.” “But look, I eliminated the need for the web.xml file.” “But look, I don’t have to understand SQL now.” But look, the codebase depends on a shit-ton of completely opaque Automagic™ that you have no hope of understanding the moment something goes wrong – which it will if you even think of changing your Java version. And since it’s practically impossible to understand what’s going on under-the-hood of whichever dependency is fubar’d this week, you have to resort to a mixture of trial-and-error and copy-pasting shit (that you also don’t understand) from StackOverflow and praying to Cthulhu something works – which is also trial-and-error because Java questions in particular have tons of just straight up wrong answers.

To be fair, I’m the guy on my team who people come to when they run into those sorts of “I bumped up one subminor version of Mockito to fix a bug that was preventing my unit test from working but now literally half of our unit tests won’t build” or “I added the war plugin to the build.gradle and now SwaggerUI is broken.” So maybe I see more than my fair share of “well shit, I guess I’ll just spend the next three hours hunting down which magical combination of Jar version numbers will fix things” kind of problems. But damn. This shit didn’t ever happen back when I was doing Python for a paycheck.

I don’t use Java if I don’t have to. If I have to use Java, I prefer to just use Servlets (mostly I do web development) and absolutely as few dependencies as I can possibly get away with. Fewer moving parts mean less that can break.

Mo’ unit tests, mo’ problems.

To be fair, the team at the time was all business majors. (Is “Computer Information Systems” what they call that degree most places or just at my alma mater?) I think I was the only computer science major there.

They’d done a surprisingly admirable job of cobbling together a working e-commerce, loss prevention, customer sercvice portal, orderfulfillment, and CMS suite. And their schooling was in, like, finance, MS Office, and maybe one semester on actual programming.

None of them had ever learned how to count in binary. Let alone been exposed to 2’s compliment. And there were no QA engineers.

Oh, there was the sysadmin. He had a temper and was a cowboy. If you asked him to do something, it’d be fuckin’ done, man. But you did not want to know how he made sausage. The boss asked him to set up a way for us to do code reviews and he installed Atlassian Fisheye/Crucible on a laptop under his desk. We used that for years. And a lot of the business logic of the customer-facing e-commerce site lived in the rewrite rules in the Apache config that only he had access to and no one else could decipher if they did have access.

Those were good times. Good times.