kp1197

Hello! Have you ever felt like too important to answer questions? Guess what! This one weird trick will turn you into a French General in the boardroom!

I kind of regret calling it Straussian because of the baggage that comes with that label. The key differentiator here compared to exoteric/esoteric is the stabilization mechanism: social costs to either upgrading one’s own understanding, or upgrading someone else’s understanding. That’s what keeps the readings differentiated and therefore the tiered structure stable. Keeping the structure encourages the memes survival, because it widens the acceptability of the message to meet audiences where they are. I think I need a few more examples and I ought to make this point a little more explicit.

Soon he may be making vanity license plates

Isn't the post more about the interesting capabilities of the language rather than an engineering context?

I remember the days of countless insane, boutique javascript libraries. React's ubiquity is a victory - let's not encourage throwing something away in the name of some vague notion of "innovation".

Does performing gradient descent on token input embeddings lead to interpretable results? And if not, why?

After working pretty closely with vLLM and SGLang over the past few months, this is EXACTLY what I had envisioned what a successor project would look like - analyzing an operation dependency graph and then fusing (or, at a minimum, scheduling tasks smarter). Congrats to the team.

It is unclear to me is whether Kent recovered his cognitive ability or not. He says he has, "thanks to the genie" (which seems to be his name for coding LLMs). Does this mean that with a genie, he is now able to produce like he was before? Or that he used a genie to help "re-train" himself?

Robots that can do anything.

Is it though? He's perfectly positioned to do so.

As I've posted elsewhere in the comments here, I think there are good solutions, but it will take some cooperation to get them off the ground (adoption of standards, licenses, etc.). Here is what I've proposed, which comes pretty close to what the CAI (Content Authenticity Initiative) is doing: https://dev.to/kylepena/addressing-the-threat-of-deep-fakes-...

I've got some good solutions on this front, I think: https://dev.to/kylepena/addressing-the-threat-of-deep-fakes-...

Watermarking is not the way to go. It relies on the honesty of the producers, and watermarks can be easily stripped. With images, the way to go is detect authentic images, not fake ones. I've written about this extensively: https://dev.to/kylepena/addressing-the-threat-of-deep-fakes-...

I don't buy the argument that merely because solutions exist, they can spontaneously be "chosen" by the system, even if such choosing doesn't break rules. We are talking about an idealized setup using disproven physics, so it's weird to talk about correctness. But I think the author is invoking a variety of Murphys law: Anything that can happen, might happen spontaneously. If that's true in idealized Newtonian physics world, maybe we should "fix" that? Or maybe the question of what to do about weird multiple solution sotuations is simply not in the scope of Newtons theory.

The article is asking us to consider an idealized situation

Great point on the analogue hack. But I think it's a perfect-is-enemy-of-good situation. There is currently no such thing as digitally verifiable media. If such a thing existed, it would at least partially shove the cat back into the bag (maybe people would abuse the cameras with the HSMs in this way, but its one step better than having all images with no verifiability). Whats more, Photoshop has existed for 25 years - and convincing Hollywood SFX for 30+ - so clearly it is deep fakes specifically that are the nascent threat. Doesn't HSM at least help address low effort deep fakes from people without HSM enabled cameras? Also, you could put in a depth range sensor and make the depth reading part of the signed payload.

This seems like an obvious solve. Produce cameras with HSM (hardware security modules) that cryptographically sign the image using the existing certificate infrastructure. Get browser vendors to visually indicate signed images. Now you have a "class" of images that are known to be produced by taking a photo with a verified device.