You can tell Open Interpreter to run commands based on you human-language input. If you want local only LLM, you can pair it with Ollama. It works for “interactive” use where you’re asked for confirmation before a command is run.

I set this up in a VM because I wanted a full automatic coding “agent” which can run commands without my intervention and I did not want it to blow up main system. It did not really work though because as far as I know Open Interpreter does not have a way to “pipe” a command’s output back into the LLM so that it could create feedback with linters and stuff.

Another issue was that Starcoder2, which is the only LLM trained on permissive licensed code I could find, only has a 15B “human-like” model. The smaller models only speak code so I don’t know how that would work for agentic usage and the 15B is really slow running on DDR4 CPU. I think agents are cool though so I would like to try Aider which is a supposedly good open source agent and unlike Open Interpreter is not abandonware.

Thanks for coming to my blabering talk, hope this might be useful for someone.

Fair enough. I guess I imagined someone hosting all the selfhosted web apps that get posted to this forum, when most people likely just host only the few they need on the go, so it isn’t really that burdensome.

Edit: Forgot to add: I always though that it could be useful to just set up Apache Guacamole, so that instead of the hosted services, my family members could just use remote desktop apps but I never got around to it.

Yep my thoughts. New selfhosters think the hard part of selfhosting is command line but that’s “kinda” like thinking that the hard part of math is writing numbers on paper. Terminal is just the medium, not the complex part. Navigating filesystem and editing files is easier on the desktop but changing permissions and managing services would be be extremely difficult for a newbie without using the terminal because (almost) every online tutorial uses terminal. OP would have to learn how to translate the terminal command to its desktop counterpart at which point they might as well use the terminal.

OP also has an XY problem. They asked for a system which does not require terminal usage but they should have actually asked for an easy to set up system. People are recommending things like Yunohost though, so it’s fine in the end.

It’s nice there’s a front end for all these tools but I kinda don’t get why is everything “hosted”. This could have just been a desktop app. I guess it can be useful when you want to convert something on your phone but to me it just seems like unnecessary server maintenance burden.

I used to selfhost on a core 2 duo thinkpad R60i. It had a broken fan so I had to hide it into a storage room otherwise it would wake up people from sleep during the night making weird noises. It was pretty damn slow. Even opening proxmox UI in the remotely took time. KrISS feed worked pretty well tho.

I have since upgraded to… well, nothing. The fan is KO now and the laptop won’t boot. It’s a shame because not having access to radicale is making my life more difficult than it should be. I use CalDAV from disroot.org but it would be nice to share a calendar with my family too.

It sounded like you got annoyed that I was guessing and it sounded like you tried to make it clear to me that the guess was not helpful to you with the use of sarcasm. I guess I misunderstood, sorry.

Regarding the actual questions: You asked how does it compare to Coreboot. Canoeboot is actually coreboot, just slightly modified to work with Free Software Foundation’s rules but these rules are kind of absurd. See [1]. Libreboot is also modified Coreboot but one that’s actually good. The difference between them is that Libreboot should be a bit easier to install and that they support different hardware.

In terms of battery life the same laptop with or without Coreboot should perform the same. Coreboot really only handles the booting. Battery life should depend on the “EC firmware”, which is like a second chip on your motherboard that handles stuff like blinking LEDs or checking if your lid is opened or closed. It also depends on the OS itself so Linux vs Windows will make a difference. Canoeboot is an exception because it does not include “microcode updates” for ideological reasons. Microcode is code that runs on a “CPU inside of your CPU”. Not updating it will A) make your CPU buggy and vulnerable to attacks like Spectre [2] and B) maybe even have worse battery life because Microcode can control the voltage your CPU runs at. More voltage -> more power (P ~ V^2)

[1] https://libreboot.org/news/policy.html

[2] https://en.wikipedia.org/wiki/Spectre_(security_vulnerability)

Well if it were closed source, it would be harder to repackage proprietary apps because you would not know how the snap “root filesystem” translates to $DISTRO root filesystem.

Because some apps are only packaged as snaps so if you want them to be accessible to users, you have to install snapd. Flatpak can still be the default which on non-Canonical distros already is. Which why I don’t even worry about snap becoming the standard.

You simply use a different packaging format as I said in the previous comment.

I’m not arguing whether snap or flatpak is better. Flatpak is better.

But your arguments are going against each other. You disagree that FSF should tell you what software you can use but then you want to tell other users what software they can use. If you use flatpak despite of FSF’s opinions, you should let people use snap despite of your opinion.

You are confused and mean. You cannot compare 2 different laptops and say that one has worse battery management because of coreboot. You would need to have the same laptop with and without coreboot to do any comparison.

I don’t really get what you are trying to say in the second paragraph but Canoeboot is not a good daily driver because it’s basically a “drug substitute” for GNU dummies. The author of it does not recommend using it. Use Libreboot instead as it does not break your CPU.

My guess: Generally it should not be that different since most of it is handled by the EC firmware. (Proprietary is OK in FSF’s eyes if it’s baked into the hardware) But Canoeboot does not include microcode updates which could affect the CPU’s power management. (Clocks speed, Vcore, etc.)

Ok but KDE has official Snap packages so they already are “legitimizing it”. Also snap won’t be able to entshittify anything. Snapd is still open source, so you can just repackage the software for different package system.

This is a stupid argument. In FSF’s eyes even having nonfree repository (ie. for drivers) is bad so this is completely irrelevant for anyone considering flatpak or snap. Both have nonfree stuff in there.

mainly hobbyists or some very specific feature. For example antiX for old hardware or Spiral Linux for the better installer, gaming specific distros for gaming etc. Also there are protest distros which advertise not having something - usually SystemD.

Don’t introduce proprietary crap just so companies can profit off of it.

I agree but I think it’s the user who should be able to make the informed choice (ie. during installation)

in case you have not solved it, it’s easy on Sway. man sway-output (kinda) tells you how to do it. Here’s an example sway config line:

output HDMI-1 res --custom 1921x1081@61Hz

You can even change CRT timings like front porch, if you want that.

DEs need to embrace tiling functionality and transparent windows (eg. playing a YT video under your LibreOffice window). It’s the only proper way to use a tablet. Obviously KDE’s Windows-like taskbar is a nightmare for tablets but even Android’s “deck of window cards” is crappy for anything that you couldn’t just as well do on a smartphone.