Login to reply
Replies (23)
Awesome.
Could we get search by kind number?
I love easy access to NIPs.
We need touse this more. NIPs github repository is centralized as fuck.
View quoted note →
Make it editable and we will replace github
Duh... I should have logged in 🤦
Hello Vitor
Need a more straightforward, less in your face design to consume/read things. Seeing just 4 nips at a time is bad. :)
I posted my new documentation/wiki NIP draft there now.
Cool.
1) Asciidic is more suited for Nips, since they literally are wikis in the end
2) All nips are custom nips
3) We want to start referencing the Nips used IN the app releases (events). How would do that?
We need a way to group / index selected Nips.
Missed opportunities aside.
Big step up from GH 👏
We've been putting them into normal 30818s.
Any tag that makes it easy to filter for NIPs?
30818 is superior and can be used for any spec system (BUSs, MLS, ...).
Buuuut, you need the ability to filter.
Beyond just indexing them together.
Asciidoc is harder to #vibe I guess 🙈
Which is a valid point tbh.
Asciidoc is optomized for presentation of content, not ease of vibe-coding, yes.
We're using it to publish books, and we know how to code, so okay.
We can display their content, but they can't display ours. Their loss.
All irrelevant, really. We're building an intelligent wiki search (not just another tiresome chatbot, but rather something truly engineered and smart) and more complex and configurable visual navigation.
Then we work on labeling and vector embeddings.
True. Thought about it after writing and tag is a silly idea.
Any APi like things other apps can tap into?
For that search for example?
The search will eventually become an #Aedile component, but you can just use #NFDB and piggy-back on the functionality he's building for us.
Great 👌.
A kind is also a silly idea. I'm over it.
i'm looking forward to when someone sics an AI to analyse the nip activity and identifies the social structure and whose *ahem* you have to *ahem* to get the quickest merge