Considering it was just yesterday we learned how trivial it can be to "jailbreak" most of the models we have today [1], I can't imagine any possible path forward to allowing AI live-generated sexual content ... pretty much ever.

It'll be literally hours or days from the moment they allow such a thing that we'll learn about the ingenious ways folks are "jailbreaking" game models to enable all manner of rape fantasy, child abuse, and everything in between by simply punching in the LLM equivalent of the Konami code when they're prompted to name their rival Gary (or ... their Charmander ... oh god....)

[1]: https://news.ycombinator.com/item?id=38934513

It triggers me a little when folks complain about HTTPS. Nowadays you have a wealth of tools to trivialize TLS certificate tasks.

Public TLS cert? LetsEncrypt + certbot (or any of the other zillion great ACME clients/libraries out there).

Self-hosted PKI for private/test use? Smallstep CLI (https://smallstep.com/docs/step-cli/) is good. And honestly, the raw `openssl` commands to barf out a root selfsigned cert aren't that difficult and number as less than 5 shell invocations that you could have in your history or a bash function or something.

Self-hosted PKI with extra steps that you already did because you have a Kubernetes cluster for some other reason? cert-manager will take care of pretty much everything.

These days the "hardest" part is sneaking your CA chain into the appropriate browsers / services you're using/testing, but even that is a few moments of inconvenience at best.

At least in Australia, a lot of beaches are eroding. Fast. Like, the Gold Coast is basically completely artificial at this point, they truck the sand in from somewhere else on a regular basis to keep the tourism and Schoolies dickheads constantly flowing through: https://www.abc.net.au/news/2023-02-20/the-gold-coast-ever-d...

In that very same Gold Coast (and in many beaches in Australia, and I believe other parts of the world), they erect literal "shark nets" to fence off the parts of the coast that people frequently swim in: https://en.wikipedia.org/wiki/Shark_net

So my point is, we already engage in a terrific amount of ... I kinda wanna call it "shitty terraforming" ... in our coastal areas. Turning a few kilometer stretch of beach into a jacuzzi doesn't sound so bad to me when framed in that context :)

This one, IIRC: https://news.ycombinator.com/item?id=16233336

As someone who chose for personal and ethical reasons not to reproduce, and also struggles to maintain lasting relationships, I sure am glad I'm not Japanese at least! :)

Fair point, but the context here is your original comment:

> Great idea, but not a fan of the timing yielding a legacy (ARM) SoC.

So you're talking about the main processing cores of the SoC, the one(s) that are responsible for running the Linux kernel + OpenWRT user space, right?. Not the random other 8/16/32-bit MCUs...

You're asking yjftsjthsd-h to furnish data to make a slam dunk conclusion that ARM-licensed CPU designs will out-sell RISC-V.

You realize Apple Silicon is ARM, right? And 99% of all smartphones that have been sold in the last decade, and indeed in 2023, are based on ARM cores?

We are talking hundreds of millions of devices being built and sold each year, just in the phone+PC space. That's ignoring all other verticals where ARM designs can be scaled up/down to meet.

I mean, gosh, even if virtually EVERY company in the world, EXCEPT Apple, chose to drop all ARM IP tomorrow and switch to RISC-V, there'd still be a good chance the statement "There will be more new ARM CPUs shipped next year than RISC-V CPUs." would still hold true in 2025: Apple sell a lot of computers in various sizes, you know :)

A century of progress in domestic automotive sector would disagree with your opinion, here.

If it wasn't for the gub'ment infringing on the liberties of the little guys (corporations), we'd still be driving cars without airbags, seatbelts, and proper fuel tank safety regulations.