TehPers

Surely you have an example where it’s appropriate for a service to generate nonconsensual deepfakes of people then? Because last I checked, that’s what the post’s topic is.

And yes, children are people. And yes, it’s been used that way.

Edit: as for guardrails, yes any service should have that. We all know what Grok’s are though, coming from Elon “anti-censorship” Musk. I mentioned ChatGPT also generating images, and they have very strict guardrails. They still make mistakes though, and it’s still unacceptable. Also, any amount of local finetuning of these models can delete their guardrails accidentally, so yeah.

When someone clicks the “edit” button, I guess.

Ok yes you’re right. “Grok generate me some CSAM” is the same as opening up a photo editor and drawing a new real looking body onto someone’s child and putting it in a new body position. Same exact thing. No different at all. Twitter has no responsibility for running a service that can do this.

Grok, put this “small adult” into a bikini and have her bend over.

Creating nudes without consent, especially CSAM (even with consent), can be extremely illegal. Doing it in photo editor software makes you responsible and only leaves it on your device. ChatGPT will attempt to filter it, and their filters lean on the aggressive side, but that’s also between you and OpenAI. Grok will post it publicly.

Modern* protect children bills would be more accurate.

The playbook these days is to use children, terrorism, etc to justify something that fails to address that problem and pushes some other agenda.

This has been true anyway in the US and UK. I have no clue how true this is in France and I won’t pretend to know, but from some other comments on the potential implementation could be better than what we’ve seen so far. I hope so, anyway.

Yes, actually. Data centers are designed to cool down components pretty efficiently. They aren’t cooking the RAM at 500°C.

500°C would be way above the safe operating temps, but most likely yes.

Server memory is probably reusable, though likely to be either soldered and/or ECC modules. But a soldering iron and someone sufficiently smart can probably do it (if it isn’t directly usable).

My experience, having actually tried this on a huge codebase: my time was better spent looking at file names and reading source code myself to answer specific questions about the code.

Using it to read a single file or a few of them might go better. If you can find the right files first, you might get decent output.

Spouting bullshit? If so, I agree.

Codebases in the 100k+ to 1m+ sloc can be very difficult for a LLM (or human) to answer detailed questions about. A LLM might be able to point you in the right direction, but they don’t have enough context size to fit the code, let enough the capability to actually analyze it. Summarize? Sure, but it can only summarize what it has in context.

Apple stores are the embodiment of wasted space.

Otherwise, there are ways to use negative space to help direct the user to important information. It’s just often abused to direct them away from it to sell something, sadly.

TLDR: data is something you collect over time from users, so you shouldn’t let the contracts for it mindlessly drift, or you might render old data unusable. Keeping those contracts in one place helps keep them organized.

But that explanation sucks if you’re actually five, so I asked ChatGPT to do that explanation for you since that would be hard for me to do:

Here’s a super-simple, “explain it like I’m 5” version of what that idea is trying to say:

🧠 Imagine your toys

You have a bunch of toys in your room — cars, blocks, stuffed animals.

Now imagine this:

• You put some cars in the toybox.

• You leave other cars on the floor in another place.

• You keep some blocks in a bucket… and some blocks on the shelf.

• And every time you want a toy, you have to run to a different spot to find its matching pieces.

That would be really confusing and hard to play with, right? Because things are spread out in too many places for no good reason.

🚧 What the blog is really warning about

In software (computer programs), “state” is like where toys are stored — it’s important information the program keeps track of. For example, it could be “what level I’m on in a game” or “what’s in my cart when I shop online.”

The article says the biggest mistake in software architecture is:

Moving that important stuff around too much or putting it in too many places when you don’t need to.

That makes the program really hard to understand and work with, just like your toys would be if they were scattered all over the place. (programming.dev)

🎯 Why that matters

If the important stuff is all over the place:

• People get confused.

• It’s harder to fix mistakes.

• The program gets slower and more complicated for no reason.

So the lesson is:

👉 Keep the important information in simple, predictable places, and don’t spread it around unless you really need to. (programming.dev)

I mean, my car is an older Corolla, so almost entirely physical buttons. My phone, however…

Wow, i immediately installed flickboard, thanks!

There have been touch-specific keyboard layouts, but not really for English or other languages with Latin characters. You can probably imagine that CJK touch KBs can be pretty creative sometimes though.

They also just don’t work at all when they get wet. This tends to be a problem when your car is covered in snow and ice, of course.

I want the power button on my phone to protrude like an actual button so I can actually press it. The thing’s like 4mm wide and I’m supposed to somehow push this thing through the gap in the side of my case with my thumb that’s 5x ~10x (just checked) the width of the button.

As for other buttons, I wouldn’t mind physical buttons for the Android controls at the bottom, but not really a huge deal to me tbh.

wouldn’t it be smart for these companies to bid a bit more if they could, to make these builds with more resellable parts instead of using these crazy server rack combo platters?

Their customers don’t care about if they are resellable. They just want GPUs.

We aren’t their customers, and I mean this in the most literal sense possible. You can’t buy these. They only sell them to big companies.

Yes, it’s shit.

Nvidia sold many of their data center GPUs as full server racks. The GPUs aren’t in a form factor to use with a traditional PC and simply cannot slot into a PCIe slot because they don’t have that kind of interface. Look up the DGX B200, which is shipped in a form factor intended for rack mounting and has 8 GPUs alongside two CPUs and everything else needed to run it as a server. These GPUs don’t support video output. It’s not that they just don’t have an output port. They don’t even have the software for it because these GPUs are not capable of rendering graphics (which makes you wonder why they are even called “GPU” anymore). They cannot be plugged into a PCIe slot because there is no interface for it.

To be more specific here, GPUs are really, really good at linear algebra. They multiply matrices and vectors as single operations. CPUs can often do some SIMD operations, but not nearly as well or as many.

Video games do a lot of LA in order to render scenes. At the bare minimum, each model vertex is being multiplied by matrices to convert from world space to screen space, clip space, NDC, etc which are calculated based on the properties of your camera and projection type.

ML also does a lot of LA. Neural nets, for example. are literally a sequence of matrix multiplications. A very simple neural net works by taking a vector representing an input (or matrix for multiple inputs), multiplies that by a matrix representing a node’s weights, then passes the result to an activation function. Then does that a bunch more times.

Both functions want GPUs, but both need different things from it. AI wants GPUs with huge amounts of memory (for these huge models) which are optimized for data center usage (using cooling designed for racks). Games want GPUs that don’t need to have terabytes of VRAM, but which should be fast at calculating, fast at transferring data between CPU and GPU, and capable of running many shader programs in parallel (so that you can render more pixels at a time, for example).