This is a week-old repo with a 163,000-line initial commit, and the test repo that init was dumped in from is filled with hundreds of claude/codex co-author commits. Regardless of whether it’s to hide the ai co-authoring, it’s shady to obscure a repo’s initial work like that.
I could be wrong, of course, but this smells like yet another overambitious ai-slop project that’ll get abandoned in a month.
I’ve always hated the gap in cumbersomeness between creating cronjobs and systemd timers, and always wished I could set a timer up as easily as I can stick a new line in the crontab. Having something bridge that gap would be the best of both worlds.
Very very cool! Would love to see it all in the case once you design and print it.
I’m working on this exact problem at home now, and finding 24GB of ddr4, a 6th-gen i7, and an old 8GB rx580 is more than enough to run pretty capable models up to ~35B parameters just fine, and equivalent MoE models shockingly fast. Not exactly cheap, with the price of everything so crazy right now, but certainly cheaper altogether than I’d imagined.
The one recurring unsolveable problem I run into is not being able to kill a process that’s stuck in D state. If something has broken in the layers between that process and hardware (not uncommon when working with old cheap “box of scraps” hardware, as I like to do), it can get stuck forever and you have to kill the whole system, sometimes forcibly. Not the end of the world, but it sucks when it happens.
735 is definitely just the number of devices that can boot postmarketos. The list of mature, well-supported devices (with enough working features to be considered as such) is much smaller, though still pretty great. Making phone calls seems to be especially spotty, unfortunately.
The full list, with matrices showing working features on each device, is here: https://wiki.postmarketos.org/wiki/Devices
This is a community for asking actual questions for discussion, not screaming personal rants into the void.
Of course the secondary opt-in user repo with unvetted package maintainers is infected with malware, it’d be a miracle if it weren’t! They warn as much in the docs. Use at your own risk, or package and maintain it yourself, because you’re likely not finding it packaged more reliably elsewhere.
And I love Debian, but if you think the Debian repos with 30,000+ packages and 1000+ community maintainers aren’t also infected with malware…
The demo video is the most ridiculous thing I’ve ever seen, I love it
Been a rough few weeks to be a linux sysadmin, I tell ya
I run the immich container stack on a vm with 4GiB memory and 2 cores, with db on local disk and external libraries over smb, and it runs perfectly fine. I offload the machine learning jobs to another sometimes-on machine, sometimes, but don’t really need to unless I’m dumping thousands of new images into the external library at a time and want it all to process quickly.
Looks like both of your vms probably have the same mac address - the 172 ip address is likely a self-assigned fallback when the dhcp server replies to the second vm that it can’t give it an address. Double-check and make sure the mac address in each vm’s proxmox network adapter settings match your pfsense dhcp reservations, and let me know if that resolves it.
Private until apple gets a subpoena from a prosecutor in some medieval christo-fascist red state trying to turn a miscarriage into a murder charge.
The grub command line options at the beginning of this article might help get your system booted without the memory deadlock, and then you can make further adjustments as needed: https://tierhive.com/blog/tierhive-howto/debian-13-minimal-guide-reduce-ram-to-38mb-and-disk-to-275mb
Alpine is great for exactly this kind of thing, though, and I use it often in embedded environments where resources are at a premium. Just do some good reading up on it beforehand, since can be very different if you’re used to debian and systemd.
The ongoing maintenance for this would be a bit of a pain, since you’d need to recompile every update on a separate machine with enough memory to do so, package it up into a .deb, and distribute and install it everywhere.
I do this on a little raspberry pi cluster and it works, but it’s work.
Too true. And good on you.
I mean, it’s basically an optional gecos field. That feels a bit like writing off *nix as a whole because /etc/passwd has a place to put your phone number.
Government thugs interrogating me in a Project 2027 concentration camp cell: “we know you gave someone named ‘homeassistant’, born on 1970-01-01, access to your server, now tell use where they are!”
You’re interacting with a server managed by someone else - everything that flows through it is ultimately under their control, and you’re trusting them with it. They could log everything, or nothing. Even if storing passwords hashed is the default, an admin can replace any part of the code they want, so they could grab and store raw passwords if they really wanted to, or take over your account and impersonate you, or any number of other unlikely but possible things.
So use a unique password, and only provide data (your real source ip, your saved posts, views, votes, etc) that you trust the admins of your server with.