GM = @grimoire Magic 🌟

Now that we have @grimoire , I know that at least the devs won't ever leave this :nostr: place. Wut is this beast!? Lmao, lesgoooo :catDance:.

The satisfactory moments of the novice woodworker 🔨

Your spec is as lean as the # of new event kinds it introduces View article →

All Nostr long form should be Nostrified Markdown. Wikis, Articles, Books, Docs, ... No #asciidoc, #djot, ... MD is the standard, despite its few flaws. Just need to also parse and handle: - nostr event and profile references - custom emoji - double square bracket links (wiki-style) And for :book: Books and :documentation: Docs and the like you then only need an index event kind that brings :article: Articles or :wiki: Wikis together in a tree. The 30040 events already get that kind of right, except that different content types (books, docs, ...) need to be **different** kinds, not just differentiated in a tag somewhere.

My time away gave me some perspective on :Nostr: Nostr things. The #communikeys spec being one of them. So I made it better (I think 😉):

NostrHub

NostrHub | Discover and Publish NIPs

Explore official NIPs and publish your own custom NIPs on NostrHub.

Or View article → The right to publish content types is now 100% :badge: Badge based (no more fees or other complexity). For this, Badges just need a one tag update that lets people request the badge from the author with a Form they fill in, which I think is useful for Badges in general. View article → Business, Brands and Apps that want to embrace Nostr already have: - a pubkey by default - very often some kind of members or subscriptions categories for their users/customers So I believe this spec maps onto that really well. Little complexity (relative to other community specs) and tons of flexibility, all while keeping transparency to the users.

Doing some of my best design work yet rn. Feels like it, at least. Way too excited 🤩. All other Nostr stuff on the backburner. #sorrynotsorry

How is not every software company looking for Designers that code rn? Especially, start-ups. I quit my Figma subscription because I can do things faster, better and more standardized **in the code**. Why bother with 'translating' mock ups anymore, honestly? Even the AI tooling in Figma (and the like) loses to the flexibility, collab and performance benefits you have from working in the code of apps directly.

Code = Liability Community = Asset #Nostrepreneurshio