l'empathie mécanique @dpwiz@qoto.org

@0x17 good luck, have fun

@tao It's in their published threat model / security assumptions:

> Attackers do not have access to private keys referenced within the C2PA ecosystem (e.g., claim signing private keys, Time-stamping Authority private keys, etc.). They may, however, attempt to access these keys via exploitation techniques...

And later, in the spoofing section.

Proper key handling is notoriously difficult. And with incentives like here, attackers would be motivated to hit it even more than some DRM system.

And anyway, no need for a breakthrough if you can walk in with a gag order and do what you need.

@tao The cryptography infrastructure would be broken܍ in no time and then the courts would have to face "cryptographically secure" fakes.

܍ Knowing ahem.. state actors, the thing would be backdoored through and through so the services could do their thing whenever they need.

@DetersHenning @Sherifazuhur @simon_brooke I have a feeling that the post is intended to specifically* support "the court ordered a ceasefire" narrative, with a follow up of "Israel violates the court decision".

*) Given how the first point is phrased and then amended.

@DetersHenning @Sherifazuhur @simon_brooke

Well, "There’s a new version of this post."

https://twitter.com/QudsNen/status/1750868389516513304

But who cares, as long as one can spread the original.

@mjg59 @archiloque @aeva x86 is basically the same. Vendors add extras to prop their benchmark numbers. Then the extras get either adopted or abandoned.

Ditto with software "distributions".

We can live with that, as we have alternatives and not blobs are required for mainstream ops.

@redmp

Evil haskell tips:

```
case
quotRem n d
of
(q, r) -> ...
```

@redmp @BoydStephenSmithJr I started to use `where`-like `let`:

```
let
z = bar x
w = zip y
in
whatevs z w
```

This way it better preserves layout when shuffling things around.

@danilo > Give me a week and you can have plans for a scalable fusion reactor design.

Oh... Trading "decades" of building AI for finally getting fusion after a week instead of perennial "in 20 more years" is so, so, so worth the deal.

Even if it burns out after that single miracle, having cheap clean energy will solve any climate-related problems in no time. We have solutions already, the problem is they aren't particularly energy-efficient.
With a few more hints at efficiency geoengineering can be achieved to marvelous results.

@danilo Incremental improvement in carbon capture is all it has after all the time? Did it even have "Engines of creation" in its corpus? We are a living proof of programmable nanotechnology being possible. Even humans can solve it on their glacial bureaucratic timescales given incentives. With AIs, this step is basically unavoidable due to its omni-useful nature. Whatever the task you can postulate "brb, inventing nanotech" will be one of the first replies from a truly capable AI.

If the story is about a chatbot instantiated for hype, then yeah, everything checks out. But if the "1000 person-years compressed into 1 hour" is the real deal then the ending doesn't make any sense.

send purr requests on mewhub

@leobm The key point for me was understanding what "type A is inhabited by values x, y, z" is about.
Next, if types are some propositions in logic, then values are their proofs.
So, by writing code that compiles you're proving that some logical statement holds.

Interestingly, if you can't say something with types, no way you can write actual code that gonna work.

And of course, if a type system admits bullshit, then you can bullshit compiler with your code.
Every industrial language admits BS, but some of them make it easy to lie, cheat, AND steal (esp. with dynamic types), while the others make that painful.

A good type system can review your design before you have committed to implementing something unrealistic, being a net positive on effort spent pinning down all the important stuff.

@ebel 🌈, if you squint hard enough

@boilingsteam whatever, as long as it runs Steam. Preferably SteamOS.

Windows multi-store schiso-tablets... No thanks.

@arialdo There's [Void#](https://hackage.haskell.org/package/base-4.19.0.0/docs/GHC-Exts.html#t:Void-35-), for the times when you really want to a-void something

@arialdo What do you want to understand? The function ignores its argument to produce String. It may as well be `f :: a -> String`.

The `error` argument isn't evaluated and so no actual errorirng happens.

@reidrac@social.sdf.org @doragasu Just use Cop-s Lock, like Google does on chromebooks.

@pmidden Even better: commas are whitespace (clojure)