BoofStroke

Don’t like it? Spin up your own node. Run it as you see fit. That’s what’s different. Personally I’d prefer we go back to Usenet.

Human sales droids do that all the time too. “Why yes, we’ll do a full vulnerability assessment on a class B network for you for less than $1000”

Different charge controllers are needed. If the ups manual doesn’t specifically support LiFePO4 the answer is no. You’d likely also need to configure it for that charge cycle if supported.

Everyone knows it’s jelly in the middle, peanut butter on each slice of bread.

It’s been raining. Taking the kayak to the local class III creek. Did that yesterday too. Gotta play while there is water.

This white house app?

https://thereallo.dev/blog/decompiling-the-white-house-app

The official White House Android app:

Injects JavaScript into every website you open through its in-app browser to hide cookie consent dialogs, GDPR banners, login walls, signup walls, upsell prompts, and paywalls.

Has a full GPS tracking pipeline compiled in that polls every 4.5 minutes in the foreground and 9.5 minutes in the background, syncing lat/lng/accuracy/timestamp to OneSignal’s servers.

Loads JavaScript from a random person’s GitHub Pages site (lonelycpp.github.io) for YouTube embeds. If that account is compromised, arbitrary code runs in the app’s WebView.

Loads third-party JavaScript from Elfsight (elfsightcdn.com/platform.js) for social media widgets, with no sandboxing.

Sends email addresses to Mailchimp, images are served from Uploadcare, and a Truth Social embed is hardcoded with static CDN URLs. None of this is government infrastructure.

Has no certificate pinning. Standard Android trust management.

Ships with dev artifacts in production. A localhost URL, a developer IP (10.4.4.109), the Expo dev client, and an exported Compose PreviewActivity.

Profiles users extensively through OneSignal - tags, SMS numbers, cross-device aliases, outcome tracking, notification interaction logging, in-app message click tracking, and full user state observation.

Domino’s pizza turned itself around.

I believe more Tlds is generally stupid. But instead of all the protect the children bullshit, I’d be good with a .kids tld that requires certification to own. Then you can just whitelist that for your precious crotch goblins and leave the rest of us alone.

For camping out of signal range or Halloween I still rock a SanDisk sansa with a rockbox rom.

Moved to action launcher after the sale. Enshittification was inevitable.

God dammit. All the whining they do about needing donations to keep developing and this is what they come up with.

Sure for physical things that need prototypes and materials. That is not a thing with software.

Software and business method patents have always been bullshit.

Patent the machine, not how you use it. Software is just instructions to a machine.

Which goes against the do one thing and do it well philosophy that helps to keep things stable and secure.

I’m doing my part

I think a birthday field in Pam or passwd would be fine. It’d be cool to have a happy birthday motd on login.

But it doesn’t belong in what should be an init system. Much of the scope of systemd beyond an init system is the real issue. Resolved for example. Fuck poettering.

“For the children” tech laws should all be abolished. Why should I be burdened because you can’t be bothered to raise your own damned kids properly?

It’s a shame webos got bought and turned into a tv os. It would shine on modern hardware and was ‘rooted’ out of the box.

Specifically in Linux you can just use iperf assuming you have a box on the other end.

You both make good points, but prevention is better than de-escalation or alerting. Being known as protected is a preventative measure.

Of course alarms/monitoring and response (de-escalation) are very important. But stopping it before it starts should get attention as well.