Here is the NKBIP-01 spec for curated publications, for anyone interested. We publish our docs on the implementation we wrote to publish docs. Because, of course, we do. 🧠 https://next-alexandria.gitcitadel.eu/publication?d=gitcitadel-project-documentation-curated-publications-specification-7-by-stella-v-1 And here's a preview in dark mode, cuz y'all like that. https://image.nostr.build/cae110f13bf9a59e1cd0c307d2eb517e15d60e8ecbc68f705e13ee943c412213.png

It has been up there, forever. They've all seen it and refused to merge or just responded with why it's a stupid concept, or whatever. The number is listed in the ReadMe.md and leads to the spec we have on the wiki. https://wikistr.com/nkbip-01*fd208ee8c8f283780a9552896e4823cc9dc6bfd442063889577106940fd927c1

Okay, NIP-62 is now "Right to Vanish" and "Curated Publications" will apparently not be merged, so never mind then. Removing the reference to the NIP number in the NKBIP-01 documents. Sorry, for any confusion. @npub1m3xdppkd0njmrqe2ma8a6ys39zvgp5k8u22mev8xsnqp4nh80srqhqa5sf @npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsyn I think that's a wrap. We tried. 🤷‍♀️ https://github.com/nostr-protocol/nips/blob/master/62.md

NIPs のコミットのキャッチアップ https://github.com/nostr-protocol/nips/commits/master/?since=2025-02-28&until=2025-03-12 * NIP-73: External Content IDs * URLs の `k` タグの値が変更された。"<scheme-host, normalized>" -> "web" * README * NKBIP-03 の kind が追加された * NKBIP-01 の kind の名前が変更された * NIP-23: Long-form Content * `kind: 30023` への返信には NIP-22: Comment を使用することが明記された * NIP-01: Basic protocol flow description * 置き換え可能なイベント (Replaceable event) の `a` タグの説明にメモが追加された。末尾にコロン (:) を含める * NIP-66: Relay Discovery and Liveness Monitoring * 新しく追加された NIP。イベントとしてのリレーの情報 * NIP-55: Android Signer Application * 「Usage for Web Applications」に UX に関する事柄が追加された #キャッチアップ #nips

@nprofile1qqs8a474cw4lqmapcq8hr7res4nknar2ey34fsffk0k42cjsdyn7yqqppemhxue69uhkummn9ekx7mp0qyghwumn8ghj7mn0wd68ytnhd9hx2tcpzemhxue69uhk2er9dchxummnw3ezumrpdejz7gzjcuq I also think you'd have a field day with neo4j. You should check out NKBIP-01 & 04 Kind 30040s are the root of the tree, where contained 30040's are branch points, letting you crawl down to the leaves Kind 30041s are the leaf nodes, to which NKBIP-04 (not yet implemented) lets you crawl back to the root https://wikistr.com/nkbip-01*fd208ee8c8f283780a9552896e4823cc9dc6bfd442063889577106940fd927c1/nkbip-04*dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319

We're just hosting our specs on Wikistr and Alexandria. We're still going through the PR motions, but it's hopeless getting anything merged. Example: https://wikistr.com/nkbip-01*fd208ee8c8f283780a9552896e4823cc9dc6bfd442063889577106940fd927c1 https://next-alexandria.gitcitadel.eu/publication?d=gitcitadel-project-documentation-curated-publications-specification-7-by-stella-v-1

I don't get it, too much talk about 30042 and 30041 events and "a" tags without any explanation of what it actually does or how its actually used... I tried reading NKBIP-01 but I still don't understand how its supposed to be used nostr:naddr1qvzqqqrcvgpzplfq3m5v3u5r0q9f255fdeyz8nyac6lagssx8zy4wugxjs8ajf7pqyghwumn8ghj7mn0wd68ytnhd9hx2tcpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcqpphxkcnfwqknqvg9xm7pr

Okay, we're trying out proposing a #NIP. We've renamed it "Collections", to clarify the content of the spec, but it's the revamped and streamlined NKBIP-01 NUD, containing the 30040 and 30041 events. @nevent1qvzqqqqqqypzplfq3m5v3u5r0q9f255fdeyz8nyac6lagssx8zy4wugxjs8ajf7pqydhwumn8ghj7argv4nx7un9wd6zumn0wd68yvfwvdhk6tcpr3mhxue69uhhg6r9vd5hgctyv4kzumn0wd68yvfwvdhk6tcqyqf5w2sfpuumlvdxk7zam9tfeg2jpaut56wjzndrndj4l5jggce4xe2s9th

@npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z Stripped it down, simplified it, and removed everything specific to some particular use case. https://wikistr.com/nkbip-01*fd208ee8c8f283780a9552896e4823cc9dc6bfd442063889577106940fd927c1

Fine. We'll submit NKBIP-01 for review, since it's been implemented in multiple clients, covers something very basic, and people keep asking us where the spec is because they want to use it, and see how it goes.

30040s? That's what they're used for, yes. For creating note collections and hierarchies. We allow for optional tags, including labels. Already listed a bunch in the spec, but you could add labels. #Alexandria just ignores whatever additional tags it doesn't utilize. We didn't bother including labels, as we're going for embeddings, with the 1987 kinds. https://wikistr.com/nkbip-01*70122128273bdc07af9be7725fa5c4bc0fc146866bec38d44360dc4bc6cc18b9 https://wikistr.com/nkbip-02*dc4cd086cd7ce5b1832adf4fdd1211289880d2c7e295bcb0e684c01acee77c06

You can see the 30040/41 events in the NIP repo ReadMe.md. Here's the spec. https://wikistr.com/nkbip-01*70122128273bdc07af9be7725fa5c4bc0fc146866bec38d44360dc4bc6cc18b9

Kind 1111 is the new comment event for NIP-29. Should be merged soon. https://github.com/nostr-protocol/nips/pull/1233 We have a NUD called NKBIP for a Nostr Knowledge Base, that also works for publishing anything hierarchical and sectionable, like a book or a magazine or audiobook, etc. https://wikistr.com/nkbip-01*70122128273bdc07af9be7725fa5c4bc0fc146866bec38d44360dc4bc6cc18b9

Project #Alexandria wiki page is updated, with the latest alpha-version screenshots. Once we get to a beta version (will take a few more weeks), we'll host a public instance of Alexandria on https://gitcitadel.eu, so that you can all start uploading your books and articles. As you can see, you have quite a bit control, of what the final Nostr document looks like, by utilizing the standard Asciidoc markup, for formatting and adding metadata. Our Alexandria parser is a NKBIP-01-specific extension of the Asciidoctor parser. https://wikistr.com/gc-alexandria*dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319/nkbip-01*70122128273bdc07af9be7725fa5c4bc0fc146866bec38d44360dc4bc6cc18b9

>>The index MUST also be uniquely identifiable using a combination of the d tag's first value (usually containing the title), the pubkey, and the kind fields.<< This is the part in the NKBIP-01 that pertains to the d tag. We could change the text to read >>The index MUST also be uniquely identifiable using a combination of the d tag's values (at least including the first value, usually the title), the pubkey, and the kind fields.<<

It looks like you've made author a required field, but NKBIP-01 says it's optional. On the uploader, I have a construct_d_tag function with a fall-through statement, that adds on each additional available variable, ending with $dTagTitle . "-by-" . $dTagAuthor . "-v-" . $dTagVersion So, something like The-fox-and-the-hound-by-Aesop-v-fourth-revised

We listed our NKBIP-01 and NKBIP-02 specs in the NIP repo. That should make them easier to find. https://github.com/nostr-protocol/nips/blob/master/README.md

That already exists, with kind 30041. https://wikistr.com/nkbip-01*dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319/nkbip-01*70122128273bdc07af9be7725fa5c4bc0fc146866bec38d44360dc4bc6cc18b9

Yup. 😊 We're reformatting the wiki pages to asciidoc. We already got NKBIP-01 updated.

Could NKBIP 01 or 02 offer an attack vector?

Working on it with out knowledge base and ebook reader Alexandria. Everything you know regarding interacting with nostr notes, but "sections" or chapters are their own notes that compose into modular articles, also semantically searchable through embeddings. https://wikifreedia.xyz/nkbip-01/npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsyn https://wikifreedia.xyz/nkbip-02/npub1m3xdppkd0njmrqe2ma8a6ys39zvgp5k8u22mev8xsnqp4nh80srqhqa5sf https://gitworkshop.dev/r/naddr1qq9yzmr90pskuerjd9ssz9rhwden5te0wfjkccte9ejxzmt4wvhxjmczyr7jprhgeregx7q2j4fgjmjgy0xfm34l63pqvwyf2acsd9q0mynuzqcyqqq80xg9h3fj2

https://wikistr.com/nkbip-01*dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319

Take a look at Liminal's spec here: https://wikistr.com/nkbip-01*dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319 Perhaps things that should be immutable can stay in the proposal, while comments and other things that should be editable are referenced.

This is progress, believe me 🤣 Per @npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl's suggestion, I've added filters that pare down the fetched kind 30040 events to just events that comply with the NKBIP-01 specification (Wikistr link below). From this I learned that we haven't yet uploaded any test events that comply with the new specification! I used the opportunity to improve the app's loading states, and to add a message in the case no matching events show up in the feed. Article display functionality is almost complete; next I'll be working on an article writer interface. I'd love to hear y'all's suggestions on the article writer UX! #alexandria #gitcitadel #development #otherstuff https://image.nostr.build/7cc3bb741785cb05d24fb3bd62c816492d6a7bfe70047dd1162fc9be0a992774.png https://wikistr.com/nkbip-01*dc4cd086cd7ce5b1832adf4fdd1211289880d2c7e295bcb0e684c01acee77c06 https://geyser.fund/project/gitcitadel

And, like, whatever happened to the NUD idea? Should we publish one for NKBIP-01 and -02, or did everyone lose interest? https://github.com/nostr-protocol/nips/pull/1214

https://wikifreedia.xyz/nkbip-01

@nprofile1qqsd6ejdteqpvse63ntf7qz6u9yqspp4z7ymt8094urzwm0x2ceaxxgprdmhxue69uhhg6r9vehhyetnwshxummnw3erztnrdakj7qguwaehxw309a6xsetrd96xzer9dshxummnw3erztnrdakj7qgcwaehxw309anxjmr5v4ezumn0wd68ytnhd9hx2tcn2pqw8 @nprofile1qqs8qy3p9qnnhhq847d7wujl5hztcr7pg6rxhmpc63pkphztcmxp3wgpzemhxue69uhkwun9v4h8xmm4dsh8xurpvdjj7qgswaehxw309ahx7um5wghx6mmd9uq35amnwvaz7tmwdaehgu3ww35x2umpd4jkxct59e5k7tckquc5r might be something to consider for nkbip-01, any potential incompatabilities?

Modular articles: https://i.nostr.build/QCzgEahFqxjK3LbT.png https://wikifreedia.xyz/nkbip-01/npub1m3xdppkd0njmrqe2ma8a6ys39zvgp5k8u22mev8xsnqp4nh80srqhqa5sf

Ahh, nkbip not nkbib. nkbip-01 and -02 are trending wiki topics, according to my grapevine on brainstorm.ninja! They’re probably also trending according to YOUR grapevine, although you never know until you check!

Maybe a stretch, but here's a wall of an idea: (1) Let's move from relay pools as the town square, where everyone sharing an intersection of relays shares the same town square and move to relays as islands, closed off rooms etc. Similar to Reddit, but a theme is assigned to the relay, curated by the moderator(s) and community. More closed than what Satelite.earth has. (2) find better ways to aggregate notes and surface older content - diminishing the recency bias. Why (1)? With the wide perspectives we see from everyone, groups are not able to maintain a stable set of values. A permissionless wiki or community is not going to bring in specialized groups for fear of vandalism or being lost in the sea of other unrelated notes. Of course you have relay selection, but this is an afterthought in the town square model. How is a segregated nostr going to help with ingroup behavior? It doesn't explicitly, but it creates an environment at the base level that disincentivizes negative & reactionary behaviors between tribes because now you can choose to not have in your face if you don't care to see it. Set it in your community rules. Also, the real interesting stuff happens at the boundaries between communities - where relays don't need to be so strict with a specific theme. Where you can share relevant content across communities. Curation at the level of the user, dictated by what room they choose to be in at any given moment. (2) Now nostr is more segregated, what about visibility? How can we surface old content? Searching through tags and labels work, but in a very limited way because you want tags to be specific. If you don't have a defined term ontology for whatever topic it is care about, you're stuck with a resolution problem. You need to balance between trying to find the most relevent tags for a topic and throwing tangentially related tags to increase reach. Current functionality to share content is boosting, forking articles/notes and quote posting. Quoting, while used to change the context of a conversation or to aggregate multiple posts comes with its own set of problems. Similar to citations in papers, you're stuck temporally. Seeing the top level post means you see the new context, but you're going to have a problem finding where others have taken the conversation if you only see the bottom level. I've also seen quoting as a method for grouping notes together, but argue that its pretty ineffective for the previous reason. What makes this worse is that many clients are __feed based__. Meaning unless you see it in your feed, you're not going to find it without some text search, which is very limited if you're trying to explore a general topic. Two problems now, which many if not all clients face: Search resolution in text, tags/labels, and a temporal bias toward recency - incentivizing you to join in on the current conversation. Here are two specs. a) Modular articles, aka note collections, note collages, aka renderable lists with context: Originally developed to help search and segregate focused context within a larger article, modular articles group events together as its core functionality. Take a set of related events, group them together, and now they're all searchable under a single context. "Opinions on integrating alt coins for tips" "Vegetarian recipes" "Cool notes and events that happened this week on nostr" https://wikifreedia.xyz/nkbip-01/npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl https://highlighter.com/laeserin/1719204947236 b) Embedded content: Without going into detail about the how, embedding models are a computational approximation of __meaning__ where you can compute distances between concepts. You want to find content that wasn't labeled or grouped and you don't know the exact words being said? Your best chance is through embeddings. Expensive, but effective and ideally used for content to be "caught" later like knowledge content or relevant notes. It makes little sense to embed everything someone shouts out their window. https://wikifreedia.xyz/nkbip-02/npub1m3xdppkd0njmrqe2ma8a6ys39zvgp5k8u22mev8xsnqp4nh80srqhqa5sf Relays-as-islands helps users stay in their echo chamber if they'd like: Good for community security, but individuals pick the communities they want to participate in. Broadcasting, boosting and quoting now functions as a cross pollination mechanism, rather than a "hey followers check this out" Note collections help aggregate and surface old content as prescribed by the user given some context. Embedding models help for search resolution, with the optional capacity to throw in for a recommendation algorithm.

Welcome back 🤝 Yes, nested json is yucky 😂 We're also putting our specs on wikifreedia for faster iteration and feedback https://wikifreedia.xyz/nkbip-01/npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl https://wikifreedia.xyz/nkbip-02/npub1m3xdppkd0njmrqe2ma8a6ys39zvgp5k8u22mev8xsnqp4nh80srqhqa5sf

Hey there, I took a break for a while, but am back now 👋 @npub1m3xdppkd0njmrqe2ma8a6ys39zvgp5k8u22mev8xsnqp4nh80srqhqa5sf I saw your nkbip-01 and @npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl post about project Alexandria. Congrats to what you are planning and thinking about! So putting json in content tags is now officially forbidden by the nostr dads (and I guess for the right reasons). So we put everything in tags now? If you don't mind I will propose something for my use case to the nkbip repo or is there another place for discussing this stuff now? I want to apologize for being such a bad discussion partner when you came up with your initial idea. Hello again Nostr 🚀

I'm new to the database space, let alone creating one for nostr. where could I get started? I do think we'd need some special permissions for kind 30041 (modular content - publishing multiple sections of an article) because of publishing notes at high frequency and 1986 (embeddings), of which the vectors could get quite large. Maybe we can iterate on best practices and specs for both perspectives relay and events? https://wikifreedia.xyz/nkbip-01/npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl https://wikifreedia.xyz/nkbip-02/npub1m3xdppkd0njmrqe2ma8a6ys39zvgp5k8u22mev8xsnqp4nh80srqhqa5sf

Our whole Operating Function / OS is premised on the concept of closures. Take typed functional programming and create a closure of the highest loop and you end up with the full state of a running machine (homoiconic data _and_ code) as a single serializable and portable value. I think our tech compliments many of the ideas in NKBIP-01 very well. What you are describing is basically Supercombinators for ideas, what we provide is supercombinators for compute 🤝 https://www.youtube.com/watch?v=pQzeYhSp1pw

The specs we've formalized so far: Modularizing content - chunking. Helps with navagibility and encapsulating ideas, https://wikifreedia.xyz/nkbip-01/npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl Embeddings on nostr - you find a piece of text worth embedding? Put the embedding on nostr for anyone to grab and use. https://wikifreedia.xyz/nkbip-02/npub1m3xdppkd0njmrqe2ma8a6ys39zvgp5k8u22mev8xsnqp4nh80srqhqa5sf

Alexandria and the eBook uploader are not going to change any of the current functionality, but just so everyone knows, we are going to adopt the Asciidoc standard going forward, to 1. match the direction Wikistr is headed, 2. utilize the Asciidoc toolset @npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 is working on, 3. facilitate more advanced formatting options for writers (including myself 🤩 ), and 4. make displaying/publishing to other formats (ePUB, PlantUML, and LaTeX, especially) more smooth. We are in the process of moving our hosted wiki from Wikinostr to the more-advanced Wikistr, and my wiki pages will be reformatted to display best in that environment. Your current markdown documents should still display well, so long as you kept to the basic markup set and didn't do anything too fancy. https://i.nostr.build/bcWFCHMFg7NOnbVb.png NKBIP-01 has been updated accordingly. nostr:naddr1qvzqqqrcvgpzphtxf40yq9jr82xdd8cqtts5szqyx5tcndvaukhsvfmduetr85ceqyw8wumn8ghj7argv43kjarpv3jkctnwdaehgu339e3k7mf0qqyxu6mzd9cz6vp3z00ste

Because we prefer to ask for forgiveness, rather than permission, we're going to write Gherkin scripts for NKBIP-01 and -02, and use them to release Alexandria. @nevent1qvzqqqqqqypzphtxf40yq9jr82xdd8cqtts5szqyx5tcndvaukhsvfmduetr85ceqydhwumn8ghj7argv4nx7un9wd6zumn0wd68yvfwvdhk6tcpr3mhxue69uhhg6r9vd5hgctyv4kzumn0wd68yvfwvdhk6tcqypz65trn9llg8789lg4j57txh0dyy6pak9up38xmrnaxq69ch763wuf63ff

Newest version of the spec. https://next.nostrudel.ninja/#/wiki/topic/nkbip-01?pubkey=dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319

NKBIP-01 Alexandria client coming soon, but test events are already out there.

Here's one of my more-complex Markdown docs under Asciidoc. Hardly any difference. I think we're overthinking this. Asciidoc is fine. https://wikistr.com/nkbip-01*dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319/nkbip-01*dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319

I would just reference it from NKBIP-01, name the spec NKBIP-02, but the Kind 1986. Then it shows up under 1984 and 1985 on the event register. So, people will be more likely to find it and less-likely to recreate it.

Same in nosey https://nosey.vercel.app/?q=NKBIP-01+

Here are all of the notes containing a reference to our new NKBIP-01 spec. You can use the identifier to read through the historical conversation. https://nos.today/search?q=NKBIP-01

You can also (maybe) see it on Wikifreedia. https://wikifreedia.xyz/nkbip-01/laeserin@getalby.com

Update to NKBIP-01, the NIP for modular articles and eBooks. https://next.nostrudel.ninja/#/wiki/topic/nkbip-01?pubkey=dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319

Liminal's original spec had no e tag in the 30040, so we thought you were just pointing out that he'd forgotten it. https://wikifreedia.xyz/nkbip-01/liminal@nostrplebs.com

https://wikifreedia.xyz/nkbip-01/npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl I have the "d" tag in the examples, but I can add it to the text and make it more explicit.

Here's the spec. @npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft wants to change the stringified content to tags, I think. @npub1m3xdppkd0njmrqe2ma8a6ys39zvgp5k8u22mev8xsnqp4nh80srqhqa5sf agreed to it, yesterday, but they haven't had time to update it. I'll fork it and correct it, after lunch, if they don't get to it, first. https://wikifreedia.xyz/nkbip-01

https://wikifreedia.xyz/nkbip-01

And I'm wondering what the benefit of the 30041 event kind is, over 30023. I could use either with the 30040 header event, right? https://wikifreedia.xyz/nkbip-01/ naddr1qvzqqqrcvgpzphzv6zrv6l89kxpj4h60m5fpz2ycsrfv0c54hjcwdpxqrt8wwlqxqythwumn8ghj7un9d3shjtnwdaehgu3wvfskuep0qqyxu6mzd9cz6vp33hcqlp

We need closed communities, they'd probably appreciate top-down moderation, exclusive access. I'm thinking of interoperable academic knowledge bases compared to siloed academic journals. PDF's don't make sense anymore with hyperlinked knowledge. Lets link ideas semantically where every party has agency to curate and work on their ideas without risking being invaded by toxicity and spam, but at the meta level because of nostr, anyone can listen to their relays being broadcasted and mix it in with other knowledge bases. just to start you off 😉 https://wikifreedia.xyz/nkbip-01/npub1m3xdppkd0njmrqe2ma8a6ys39zvgp5k8u22mev8xsnqp4nh80srqhqa5sf

I think every client could probably benifit from a knowledgebase/tutorials on their client and related ideas. But have them nostr native events enabling interoperability and remixability https://wikifreedia.xyz/nkbip-01/liminal@nostrplebs.com

Feel weird attaching these notes as a comment, but trying to keep a hold over a specific group of notes. Feels a little intrusive, but its a way to keep the idea and its linked notes together. Doing so gets cumbersome with lots of notes though. - (solution) modular articles: think full wiki's, but the atomic unit are (sub) sections of them. Written about them here: https://wikifreedia.xyz/nkbip-01/dc4cd086cd7ce5b183 - what i actually wanted to comment, but its all related anyway. Communities, KB's, curation mechanisms etc. @nevent1qqsdej8tz55tya5jt9kmd77k4nzuvpn227ya2h3sm0nc34va3dhakwspr3mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmqzyrwye5yxe47wtvvr9t05lhgjzy5f3qxjcl3ft09su6zvqxkwua7qvqcyqqqqqqgjc79hf

Been thinking about colaborative decentralized wikis. And how to organize content. https://wikifreedia.xyz/nkbip-01/dc4cd086cd7ce5b183 I have other ideas regarding network effects and our bias to wide open relays, so i'm putting a pin in this and will come back to it.