Do you mind, if I port your stuff over to Alexandria?

Reply to this note

Please Login to reply.

Discussion

Like, publish 21 Lessons as a book?

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.

Please do!

21 Lessons is published under the Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license, as is my other work. That means that you are free to share, adapt, and translate the material as you see fit. The only requirement is that you must distribute your contributions under the same license. https://21lessons.com/translations

I'd love to help.

Hey, sure. I'm going to need someone to proofread the upload, to make sure I didn't skip a chapter, by accident, or screw up the formatting or something wonky like that.

We're still building the automated, intelligent proof-reader. It's still completely manual. Someone just scrolling down the page and looking to see if something looks strange. 🙈

I'll @ you with the draft upload, later today.

About â…” of the way through. Should be done, tomorrow. I see, now, that it really would be nearly impossible to get it all straight with Markdown. Need finer granularity on the tags.

I think some of the hyperlinks are broken. Probably all need to be tested. Maybe you could do that, too.

GN, for now.

This will be a great test case for improving our stylesheets!

The formatting is a real doozy. 😅 Gigi decided to not make this easy on us. But, it will be very elegant, I think, once we get it all straightened out.

I tried to maintain the linkage, but with less "jumping out" of the flow of the main passages, so that it isn't distracting on an e-paper reader.

(((converting my shit to nostr)))

We're going to make it look 🤌

Competition is on 😉

I've got some time today and so will take a run.

How best to feedback?

I also need to learn more about the approach here as seems NOSTR adjacent. Seems to remember a parallel NIP repo or something?

If you click on the embedded note with my "Testerin" pic on it, the nevent json opens.

The two links in the main issue will always go to the newest nevent, so each draft will have a new one, but the top links won't change because the d-tag and the naddr don't change.

I can just include your license version in the Title Page event.

I was planning on doing this, anyway, as I know it would be popular for Nostriches to highlight and stuff.