Going for the minimal, nuanced vector #logodesign that LLMs can't dream up. Has the <>, the ⭐, the G of @grimoire and looks like some kind of portal. @verbiricha wdyt?

Pretty weird to :90percent: of people to display a bunch of content types in your :nostr: Nostr app, for which you don't give a route to create them. Not saying your app has to enable creation of all of them, but it should at least point to other apps that do. And yes, there's Nip-89, I know. But it says nothing about whether the proposed apps handle the CREATION for the :AirQuoteLeft: supported :AirQuoteRight: kinds, so in the majority of cases it's sending users to another app (that they don't know) just to SEE the same content type over there and be like "What now?". It also has some weird base assumptions and seems to be thought out mostly from the web app perspective. I think :app: App events could be the better solution here. If we find a neat way to specify what content types the app lets you READ vs what types it's lets you WRITE, you'd have a general solution for all platforms (APK, Mac, iOS, Linux, cli, etc...) and for content tires that can even go beyond Nostr stuff (MP3, MP4, DOC, ....). Would make building a great search UX in apps like @Zapstore easier too, ngl 😉.

Expanding the #foodforest today: Paw-Paw, Mulberry, Nashis, Kakis, Sorbus, Grapes, ...

Kind 1s should stop where the :thread: Thread stops and the :reply: Comments start.

Badges for community moderation are neat because the key that awards the badges can be any key you want: Your own community key, a hot-key on a server, someone else that already did/does the work of curating acceptable people in a way you like, .... Communities can start by manually awarding Badges (I.e. access to parts of their community) and switch to a more automated hot-key signing flow later, if needed. The only missing part for Badges in the current NIP is a way to request them. For this, I think Forms are the way.

Android icons are a wild-west mess of different sizes and transparent backgrounds, etc... But I think I found a good way of making 'em look consistent and beautiful. Thank you bluuuuuur :PepeLaugh:

GM = @grimoire Magic 🌟

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.