

I’ve found this one: https://codeberg.org/polyphony/slopscore
By its own metrics, it was made without AI (and the source is on Codeberg, which iirc has strict rules about AI code).


I’ve found this one: https://codeberg.org/polyphony/slopscore
By its own metrics, it was made without AI (and the source is on Codeberg, which iirc has strict rules about AI code).
You should be able to just fork it normally, then reset (or is it revert?) to the commit you want.


I think there are three main issues (though I might be overlooking something):
However, it’s not entirely unprecedented for a computer to provide a proof that we don’t completely understand. I forgot the details (and I’ll edit them in if I can find it), but there was at least one problem that was solved using a computer and brute force trying millions of cases. That produces a proof much longer than any human could read in a lifetime, and iirc there where quite a few mathematicians unhappy about it at the time too.


Debian is the OS.
Proxmox builds on Debian to turn it into a hypervisor. That’s an OS for managing VMs and containers. Proxmox (like most hypervisors) gives you a handy webinterface.
There are easier hypervisors to use, but Proxmox is great for learning, and allows you to expand well later.
tbh, except for gaming and AI, you don’t need nearly as much processing power as you might think. I run most of my stuff on a (fairly new, can’t remember which one exactly) i5, and it sits at an average 2-3% CPU usage, with the maximum its recorded being 10.9% (there’s two VMs and 8 containers running on it). 11th gen i5 will probably be more than enough to start with.
In my non-professional opinion, what you really want to look at is how much power your system is going to use when idle, since that’s what (small) servers are doing most of the time. This is not something specified by manufacturers, and it depends on all the parts going into the computer (CPU, mainboard, PSU, fans, how the BIOS is set up, …).
I would also recommend getting at least 16 GB of RAM (honestly I would say 32, if not for the current prices). Containers don’t use too much, but if you want to set up VMs for services, each VM will want at least 2-4 GB for itself.
LXC-Containers (https://en.wikipedia.org/wiki/LXC) are like extremely lightweight and slightly less secure Linux VMs. They are similar to Docker, but while Docker is containerizing applications, LXC containerizes Linux distros.


Running Docker inside a VM is the recommended way to run Docker on Proxmox.
Personally, I just run Docker inside LXC containers. Aparently, this is supposed to be not entirely stable, but its never given me any problems. (I commit an entirely different sin against efficiency, by keeping each service in its own LXC container, each with its own Docker host.)
I also run Immich (in Docker inside a container), and haven’t noticed any performance issues. But I’m the only user, and I don’t use it heavily, so ymmv.


Well, if its unbreakable, then its either snake oil, or some variation on the one-time-pad (really depends on your definition of unbreakable).
But having read the article, this is definetly snake oil.
Yes, TinyCore-Core comes without a GUI (like the commenter above said, headless). When they say 28 MB RAM, that might even be overestimating it a bit. All of TinyCore-Core fits into just 17 MB. Of course that goes up if you need to install things, and I don’t know if it comes with an ssh-Server out-of-the-box. So for a proper server setup, 28 MB sounds pretty reasonable.
It blows my mind, that there is an entire Linux Distro, that fits into a modern processor’s cache. Who needs RAM anyways? (unfortunately, because of how cache works, we can’t actually use it without RAM)
If you run your services off of a homelab rack that dims the lights whenever you power it on
If you are in this situation, then you definetly should get some more power, or at least a UPS to make sure you don’t trip a breaker.
It would (hopefully) have less attack surface. Electron is, after all, a whole browser, and needs to be able to do all the things a browser can do, while a native implementation can limit itself to just the very limited network interactions needed. (e.g. while XSS attacks are quite hard to do on a modern browser, a native app would make them impossible)