Isildur: BTW I’m selling these cool new One Ring™ limited edition rings, forged in darkness and bound to the One Ring…we’ve got sizes for men, women, elves, and dwarves!
Elrord: O shit gimme 5 of those bad boys
Isildur: BTW I’m selling these cool new One Ring™ limited edition rings, forged in darkness and bound to the One Ring…we’ve got sizes for men, women, elves, and dwarves!
Elrord: O shit gimme 5 of those bad boys
A while back, one of the image generation AIs (midjourney?) caught flack because the majority of the images it generated only contained white people. Like…over 90% of all images. And worse, if you asked for a “pretty girl” it generated uniformly white girls, but if you asked for an “ugly girl” you got a more racially-diverse sample. Wince.
But then there reaction was to just literally tack “…but diverse!” on the end of prompts or something. They literally just inserted stuff into the text of the prompt. This solved the immediate problem, and the resulting images were definitely more diverse…but it led straight to the sort of problems that Google is running into now.
You can label your devices. When formatting, do mkfs.ext4 -l my-descriptive-name /dev/whatever
. Now, refer to it exclusively by /dev/disk/by-label/my-descriptive-name
. Much harder to mix up home
and swap
than sdc2
and sdc3
(or, for that matter, two UUIDs).
Another problem: legislation like this cements the status quo. It’s easy enough for large incumbents to add features like this, but to a handful of programmers trying to launch an app from their garage, this adds another hurdle into the process. Remember: Signal and Telegram are only about a decade old, we’ve seen new (and better) apps launch recently. Is that going to stop?
It’s easy to say “this is just a simple hash lookup, it’s not that big a deal!”, but (1) it opens the door to client-side requirements in legislation, it’s unlikely to stop here, (2) if other countries follow suit, devs will need to implement a bunch of geo-dependant (?) lookups, and (3) someone is going to have to monitor compliance, and make sure images are actually being verified–which also opens small companies up to difficult legal actions. How do you prove your client is complying? How can you monitor to make sure it’s working without violating user privacy?
Also: doesn’t this close the door on open software? How can you allow users to install open source message apps, or (if the lookup is OS-level) Linux or a free version of Android that they’re able to build themselves? If they can, what’s to stop pedophiles from just doing that–and disabling the checks?
If you don’t ban user-modifiable software on phones, you’ve just added an extra hurdle for creeps: they just need to install a new version. If you do, you’ve handed total control of phones to corporations, and especially big established corporations.
So fewer downloads, which is a very different thing.
First, why is every post on this forum -1? Somebody must be holding a grudge.
Second: it doesn’t matter. ECC just prevents bit flips in RAM, once data leaves a system it’s irrelevant whether it had ECC or not.
I’ve been running servers of various kinds for decades. There is a difference between running servers on hardware with ECC vs none, but it’s not a big deal. Unless you’re running, like, banking software or something where accuracy or uptime is critical…I wouldn’t sweat it. You may just have to reboot cuz of a kernel panic once or twice a year.
And a big bowl of rice! Yeah, that seems like a lot of food to me…
Title game on point tho