I just hit the big red PUBLISH button on NDK 2.4.

(well, actually, I did it from the command line, the big red button is imaginary)

## Codename: Safely Embrace the Chaos

Nostr is a, mostly, friendly environment with not too many developers and no ill-intent among them.

But this will not always be the case. Compatibility issues, mistakes, and all kinds of chaos is to be expected.

This version of NDK introduces validation at the library-level so that clients built using NDK can rely on some guarantees on handled-kinds that events they are consuming comply with what is defined on their respective NIPs.

An example?

NIP-88, recurring subscriptions, defines that Tier events should have amount tags of what subscribers are expected to pay and the cadence.

Prior to NDK 2.4 some malformed events would render like this:

But with NDK 2.4 the malformed parts of the events don't reach the client code.

This is just a beginning, but event-validation is now moving into the library!

That's kind of what my impression was.

That's kind of what my impression was.

#AbstractArt #Artstr

"Windows to a Nothingview"

got an idea for jack, if one of you want to pass it along, a bitkey wallet that filters water....two birds one stone

What does the error say?

What I want is not really "Linux APIs". I want a headset that I can configure as a 12k by 2k pixel screen and connect it via HDMI. The headset should then simulate that screen at a configurable size and distance. Oh and yeah, it should not phone home.

Wrong answer. The correct answer is NIP-29.