Ahkshually 🤓 the advent of Olas precipitated a paradigm shift within the Nostr protocol by pioneering the deployment of an entirely unprecedented event taxonomy: kind 20. This event classification was wholly absent from the preexisting Nostr event schema, rendering Olas the vanguard in its implementation. Consequently, Pablo, in his infinite wisdom, architected Olas to instantiate dual-modality event propagation—supporting both canonical kind 1 notes with inline media embeddings **as well as the novel kind 20 dispatches.

But why? My hypothesis posits that kind 20, in its embryonic state, lacked the infrastructural ubiquity requisite for self-sustaining viability within the broader Nostr ecosystem. Ergo, a symbiotic relationship with the more entrenched kind 1 paradigm was imperative to bootstrap its adoption. However, in a remarkable turn of events, the proliferation of client-side compatibilities and the meteoric ascension of the #Olas365 challenge catalyzed a re-evaluation of this dual-support strategy. As discourse intensified among protocol cognoscenti, an emergent consensus suggested the deprecation of legacy kind 1 media notes in favor of an unambiguous prioritization of the avant-garde kind 20 framework, thereby streamlining the ecosystem and solidifying its evolutionary trajectory.

That’s the fixed version already 😅

cc nostr:npub16c0nh3dnadzqpm76uctf5hqhe2lny344zsmpm6feee9p5rdxaa9q586nvr nostr:npub1zga04e73s7ard4kaektaha9vckdwll3y8auztyhl3uj764ua7vrqc7ppvc

Kind 1 maximalism at its finest