These articles display properly in Njump, Habla, Coracle, and Nostrudel, but if you check the tags, they refer to an article that is previous/next with "a" tags.
So that a long-form client could add paging through the articles, and 30040 can be auto-created that contains all of the articles in a series, in the correct order, so that they could be displayed in #Alexandria, as a magazine.
My Sybil client is going to do this @Sebastix, but I wanted to check that the resulting articles aren't rejected by the other clients.
So, I'm writing a loooooonnnnnggg article on building Sybil and you'll know the MVP is complete, when the article is visible as a series, under my @Silberengel npub.
Cool. So this perhaps can also be used for documenting content like how it’s published on nostr-php.dev for example?
Well, the idea is that writers often start off with one, long, markdown file and scaffold it into sections and then they fill in the sections, like I'm doing below. And then they end up with one gigantic document.
They would have the choice to publish that as a serialized article and auto-generate a matching 30040. Then a client that only does 30023s could add a button or breadcrumb at the bottom, for "next" and "previous" (like on a blog, but only for this particular series), and a more advanced tool like Alexandria could display the entire thing as an eBook with chapters that you can navigate over a ToC.
So, it's a linked-list that is delivered with a matching index.
https://github.com/SilberWitch/Sybil/blob/main/BuildingSybil/BuildingSybil.md
@Sebastix do you know how I can generate a naddr?
I'm calling nak from shell to do encoding and decoding, so far, but I was thinking it might make sense in the PHP Helper.
https://m.primal.net/LTZz.png
Its not in the library yet (NIP-19)
Okay, then I'll stick with the shell scripting, for now, and then switch it out in a later increment. No rush, just thought that would be a nice addition. Fiddling with identifiers is a PITA. 😅
It’s on the roadmap, I need it too for my Drupal modules 🤓
Yeah, know the feels. Had to add serial articles to Sybil because my article about Sybil is too long to post to most relays. 😂
Just curious, what 'logic' or mechanism do you use to generate the d-tags?
looks like there's a bug, that event has a bech32 on the event address in the place where the pubkey should be
It's not a bug. Articles don't usually have `a` tags. I was trying them out, to see how the clients would respond. Since no clients use `a` tags, I'm considering using them for something novel.
The pubkey is contained in the naddr.
ah ok, it's just very different to how all other tags are used (no bech32 encoding) so supporting that would require changing libraries and querying for two types of indexed values (i.e. the way NIP-01 describes it and this new encoding)
Okay, I was trying to avoid adding another tag, but I guess I should avoid single-letter tags. I could call it "navigation", or something.
it's not the a tag, it's the encoding of the tag that is very non-standard (i.e. doesn't follow NIP-01); I'm guessing some relays might bark at the non-standard format
Yeah, I need the eventID in there, unfortunately. Can't go with pubkey.
Oddbean new post about login | logout 
