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.
I’ve been lucky to have them overwinter, and I see larvae throughout the year. Haven’t had to bring new ones in since the first couple of releases, but I’d imagine that might have a lot to do with the climate here.
I haven’t tried predatory mites yet but I’m planning to soon, since my new nemesis is thrips, and the ladybugs can’t control those. Tough spot though, since I assume the ladybugs will eat the predatory mites…
I struggled with spider mites every season for a few years, until I built up a latent population of ladybugs, initally bought at my local nursery. My balcony garden (between 40 and 100 plants depending on the season) has been big enough to support this, not sure if this will be applicable to yours but I’ll share what worked for me.
The key for me was not using any pesticides and letting the population of mites and aphids swell so there was plenty for the ladybugs to eat - it’s all about getting them to lay eggs, because it’s the ladybug larvae that stick around (can’t fly yet!) and do the most eating, and ladybugs lay eggs where they think there will be enough food for their babies to eat. You want to start a multi-generational war on those mites.
Water the garden heavily at sunset and mist all the foliage so the ladybugs have plenty to drink as well as eat. Make sure it’s dark so they are less likely to fly away. Release them all over the garden, let them eat and lay eggs and begin the war, and keep an eye out for the larvae after a week or so. Don’t use pesticides, and hopefully the cycle continues on and on and keeps all your soft-bodied pests in check indefinitely.
I think the existence of a chain linking arbitrary whatsapp input to arbitrary host code execution using a fucking LLM as the intermediary is the real flaw here, not just the wonky openclaw guardrails…
There is a specific location permission option “Allow all the time” that an app can request - I use GPSLogger, and it has this option available. Osmand might not work, in this case.
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.
35-50mph is motorcycle territory, and you should get a motorcycle helmet (Snell-rated are the most safe, DOT-rated are less safe, anything unrated is trash). Helmets are the one piece of gear I take seriously, so here’s my spiel:
For a motorcycle helmet to work properly, you really need it to fit properly, and the only way to tell is to put it on and test it out. If it’s too loose, too tight, slightly wrong shape for your head, etc, that could negate most of the protection the helmet offers.
I urge you to make that trip to a shop that sells helmets and get a proper fit. Or at least order several models and sizes from the links others have posted and return anything that doesn’t fit perfectly.
I had a very dainty motorcycle crash in the rain once at no more than 10mph, and still ended up with a concussion because my helmet wasn’t the right fit. Made me realize how easily I could have died if I’d had a different crash, since I’d been relying on a helmet that was never going to protect me properly in the first place.