What do you think nostr:nprofile1qqs8lft0t45k92c78n2zfe6ccvqzhpn977cd3h8wnl579zxhw5dvr9qpzemhxue69uhkvun9deejumn0wd68yvfwvdhk6qgdwaehxw309ahx7uewd3hkcqghwaehxw309anxjmr5v4ezumn0wd68ytnhd9hx2aezugp , nostr:nprofile1qqs8qy3p9qnnhhq847d7wujl5hztcr7pg6rxhmpc63pkphztcmxp3wgpz9mhxue69uhkummnw3ezuamfdejj7qgmwaehxw309a6xsetxdaex2um59ehx7um5wgcjucm0d5hsz9nhwden5te0dehhxarjv4kxjar9wvhx7un89uqaujaz and nostr:nprofile1qqs2js6wu9j76qdjs6lvlsnhrmchqhf4xlg9rvu89zyf3nqq6hygt0spz9mhxue69uhkummnw3ezuamfdejj7qghwaehxw309aex2mrp0yhxummnw3ezucnpdejz7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uygje4n? I'd give it some elegant Asciidoc and then we could hone the .CSS in our clients, to make it look pretty.

Reply to this note

Please Login to reply.

Discussion

YES! I'm working on improved book support and rendering so this would be perfect to test.

Yeah, that's motivating test data, since lots of Nostriches would click on it.

Let's maybe wait to announce until all three renderings are done and then make a joint announcement. Maybe add a screencast of each display in the announcement.

Proof of interop.

First rule of #bookclub:

Interop 💪

There needs to be at least one topic where the stuff actually works.

I think this is the first intra-project team that actually manages to successfully coordinate.

We're trying to get the same for relays, but it's been a bit like herding cats. 😅

Sounds good!

Working on the pretty #asciidoc part today 🫡

Book widget is for next week.

This would be a good test case for our styling.

The license brings up an interesting point. Is there a way we can link the license to every event that makes up the book? If users can work with individual sections of the book in isolation, the license should be attached to those as well as to the whole.

Ah, like a citation event for licenses?

Yeah something like that. Probably a distinct event kind from citations, but similar in concept.

You could attach the license to books, music, code, etc.

I'll write something up.