There’s an enforcement component. It’s designed to punish the producer so it hurts so it won’t do it again.
jdw
joined 2 weeks ago
Many moons ago I used heartbeat for this, but you’d need both servers in the same cidr range. I assume that’s not the case here.
In your case you could probably use a dynamic DNS service to move the IP around, but the challenge would be knowing when to kick it off.
You could write scripts to determine when the live one goes down, but we’re probably already more complicated than you were looking for.
Federated DNA data storage service. My bad.
That’s LLM bullshit, sir.
You never really think there’s people behind these things.
Hells yeah.
WP had a time, but there are a ton of better options now.
The WP plugin gatekeeping is terrible, it lacks cyclical review which allows abandoned plugins to be converted to malware; its target audience is people who have no business running their own internets and have no idea what updates are, thus scattering the landscape with outdated WP installs ripe for conversion into botnets; it uses an unreasonable amount of resources, primarily due to encouraging users to install every plugin the can find; and finally, who the hell is Dolly?
We need a federated DNA service.
The problem, of course, is distinguishing between harmless and harmful use. There are painfully few things that are objectively good or bad.
I recently had a Kona loaner with that. It was so dumb.