Sounds quite similar to Markov chains which made me think of this story:

https://thedailywtf.com/articles/the-automated-curse-generator

Still gets a snort out of me every time Markov chains are mentioned.

Oh, they’re putting a lot of thought into it I’m sure.

That thought being “Money, Money, Money, Profit, Profit” of course.

That feature is right on the border between real neat tech and deeply unsettling.

“Hey, my phone uses its last few electrons to turn into a bluetooth beacon to stay findable” sounds like sci-fi “reserve power emergency mode”

“I can’t turn off the locator chip in a device that holds half my life and memories” is just dystopian.

I’m wondering if there would be a way to keep it useful while minimizing impact for people who stay off the grid. A hardware switch would probably be a good start but they won’t fly with current all-touch designs.

Is that a reference to Angleton?

Decent writeup by Charles Stross:

https://www.antipope.org/charlie/blog-static/2024/01/worldcon-in-the-news.html

The mode of operation of WorldCon/the Hugos seems interesting as in “May you live in interesting times”

Edit: fixed auto-co-wrecked spelling of Charles Stross

Teenagers and a dog sound like Scooby Doo. No idea how specific the rest is.

B stands for Billion (Parameters) IIRC

I’m hopeful that reencoding on the fly or even merging preencoded files into a single stream is too expensive because it needs a lot of compute power and invalidates caches .

Funnily enough, wikipedia has the answer

https://en.m.wikipedia.org/wiki/Wikipedia:Database_download

IT changes usually affect management as well, while “cost saving” in production doesn’t.

Stopping AWS instances would be handy, but your idea to slag the drives is unnecessary.

Just set up full disk encryption for everything.

You die -> no key -> no data

I run a 2 node k3s cluster. There are a few small advantages over docker swarm, built-in network policies to lock down my VPN/Torrent pod being the main one.

Other than that writing kubernetes yaml files is a lot more verbose than docker-compose. Helm does make it bearable, though.

Due to real-life my migration to the cluster is real slow, but the goal is to move all my services over.

It’s not “better” than compose but I like it and it’s nice to have worked with it.

You’re asolutely right, IP addresses are kind of a grey area since the are needed for lot of troubleshooting and debugging.
Nevertheless, you can always strive to reduce the stored data.
For your application, you wouldn’t even need to store the historic IP adresses, just a rough geo-location and maybe a mobile/landline/whatever-flag and comparing the current login attempt to that. Even saves you some performance by not repeating the geo-lookups everytime.
Implement your failed-login counter separately by account and source IP and you’ve got decent security without linking an account to an IP.

Because collecting data that is not strictly necessary is almost always a bad move. IP addresses might be relatively harmless, but might link you to other activities.

You personally might be okay with reddit knowing your IP addresses, but some people might get into trouble.

Take the insane anti-abortion laws in some US states. If an IP address from those states accesses pro-choice subreddits, that might be enough for law enforcement to start harassing someone.