Vibe coded with history obfuscated behind a million-line initial commit:
For anyone considering touching this intentionally-misleading radioactive garbage fire with a 10-foot pole:
You should never, ever use cryptographic or security tools that do not come from reliable, reputable sources.
I was really curious about the possibilities here for a re-usable “saved hibernation state”, and did a lot of digging around and testing in exploration of that idea. Please note that the following is wacky as hell and is not a good way to run a server at all, but is possible:
The next time you boot, the kernel will load the saved hibernation state from the partition specified in the resume= parameter, as if it had just been hibernated instead of halted.
Now for the downsides:
Anyway, now that we know it’s possible, if you really can’t suspend/resume in a non-wacky way I recommend instead just booting normally and trying to make the boot process as fast as possible. A good guide here: https://wiki.archlinux.org/title/Improving_performance/Boot_process
If booting quickly to a static state is the goal, alpine diskless mode might be a good option: https://wiki.alpinelinux.org/wiki/Diskless_Mode
What a beautiful idea. I love it.
Nothing too fancy! Mostly just designing a lot of thickness and buttressing into the part, and then slicing with thick walls, dense triangle infill, and an orientation that puts the layer lines perpendicular to the highest stresses.
I built a friction drive for my bike with a load-bearing PLA motor mount (cheap crappy PLA, too), since I don’t have the equipment or ventilation for much else. With a bit of overengineering, it’s been doing great for almost a year now, despite all the heat and force thrown at it.
I suspected as much, but I’ll need to consult a journalist to be sure
The post title and body don’t make this clear, but “AI authentication tools” in this context refers to tools that verify the authenticity of journalistic image and video media to confirm they’re not AI-generated.
Tl;dr: one project written by one person that does everything on every platform.
(edit - this is a huge red flag, if that wasn’t obvious)
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.
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.
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.
Does the motor/pump work at all, spraying water around inside? If yes, and there are no clogs, check the drain solenoid - it should actuate a valve that directs the pumped flow of water through the drain pipe instead of the sprayers.