Michael J

https://geyser.fund/project/gitcitadel

Building the library of Alexandria

Public Key

npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsyn

NIP-05 Address

buttercat1791@gitcitadel.com

NIP-57 Address

gitcitadel@geyser.fund

Profile Code

nprofile1qqs8qy3p9qnnhhq847d7wujl5hztcr7pg6rxhmpc63pkphztcmxp3wgpz4mhxue69uhkummnw3ex2mrfw3jhxtn0wfnszxnhwden5te0w35x2en0wfjhxapwdehhxarjxyhxxmmdr5qzes

Publishing to

nostrelites.org

theforest.nostr1.com

nostr.wine

Author Public Key

npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsyn

Show more details

Last Notes

2024-10-05 23:39:18

We just had our first #GitCitadel quarterly project meeting this morning. It was great to hear each other's voices after text chatting about the project on and off Nostr every day for several months.
We've got some exciting things on the way, but the running theme of the meeting was Stability. Our project supporters want it, and we think Nostr desperately needs it. Reflecting that theme, our testing strategy for Alexandria and Aedile was our biggest point of discussion. FOSS code is cheap, but reliability is valuable, and reliability is what we'll deliver.
Our first priority for Q4 is to deliver an alpha version of Alexandria with basic writing and viewing functionality for people to begin to explore. Once y'all have a chance to try it out, we'll begin to collect feedback and determine what features to prioritize next.
As Alexandria begins to mature, we'll turn some of our attention back towards Aedile, our Nostr Development Kit. Aedile will be a fast and reliable product built by developers, for developers, and we're excited to give it some attention again.
Thanks to everyone who has supported us thus far, and stay tuned! I'm stoked to see what our team can create.

2024-10-01 15:06:10

- reply

We've discussed putting knowledge base content on one relay and the social context for those events on a different relay.

2024-10-01 13:18:56

- reply

That's actually pretty much exactly what I'm doing right now. 🤣

2024-10-01 13:17:58

- reply

And what are they to do when they have tried other means of redress unsuccessfully?
Our country was founded on a rebellion, we ought to understand those who resort to protest when they believe their voices are not being heard.

2024-10-01 05:53:01

Today on #Alexandria I'm working on the Compose view.
Compose will be the second step after Edit. Once you've copy-pasted, uploaded, or typed your AsciiDoc document, you'll be able to fine-tune it with Compose. The document is broken down into the form of zettel and index events which will be published to Nostr. Before publishing, you'll be able to edit the events in-place or rearrange them in the published event hierarchy.
This is just the start. In the future, I expect Compose to be one of the most feature-rich pages, since index composition is a core part of Alexandria's value proposition.
#GitCitadel
https://image.nostr.build/c445d0426451418d8dd483981827f9b3fd04bb2c935f8cf9cdf83b26bf27c891.png

2024-10-01 04:25:14

Defrauding workers of their wages is a sin that cries out to heaven for vengeance. I don't blame the dock workers for doing what they need to do to provide for themselves and their families.
#nevent1q…f2y0

2024-09-29 04:57:21

Love of money is the root of all evil.
Yes, that includes Bitcoin.
Stay humble and seek eternal things first.

2024-09-29 03:32:05

For my new fad diet, just drink a gallon of milk every day and see what happens.

2024-09-25 14:36:17

Some UX wisdom 👀
#nevent1q…0ah0

2024-09-24 21:43:43

- reply

Yes! If you want it to be cushy lay down a rug. A nice rug on wood looks beautiful.

2024-09-24 21:18:56

If you are a homeowner, I implore you, please don't paint over brick!
Brick is a perfect good natural material. Work with it, rather than imposing your whims on its color.
One day painted brick will be as dated as shag carpet and wood paneled walls.

2024-09-24 20:39:57

- reply

Yes! And I think Alexandria can be that for people who want real answers, not just news and blog posts.

2024-09-24 20:21:26

- reply

Well we are only doing this part time.

2024-09-24 20:18:34

- reply

Yeah that's the one I was thinking of.

2024-09-24 20:15:32

- reply

Dangit I can't find the original notes.
A bunch of people joked they were reply guy.
Anyway the reason was the same as emoji guy: it was a black hat attack test to force devs to up their game.

2024-09-24 20:11:11

- reply

Just wait till we add in the fun features.
Wikilinks, point-and-click reorganization of zettels, remixing, commenting...
The goal is to make it feel natural. What you see is just the beginning.

2024-09-24 20:00:57

- reply

I *think* they're still around but I don't remember where.

2024-09-24 19:57:14

- reply

I like that. Is there a specific reason why? I want to understand the design logic.

2024-09-24 19:55:31

- reply

ReplyGuy used throwaway npubs, I think. Like burner phones.

2024-09-24 19:11:57

- reply

The lettering all comes out of the box with Flowbite's Svelte components.
We can switch to a serif font at some point, and we can use a different font to make the document summary/overview right below the title pop out.

2024-09-24 14:45:32

#Alexandria update:
Recent work on this project has focused on extending Asciidoctor's converter to organize an AsciiDoc document into individual indices and zettels according to the Nostr Knowledge Base specification. This is now working on a basic level (though we will add additional features to this parser as the project continues), so I can turn to the editor preview.
Since this is UI-focused work, I have screenshots!
First, we have an editor area into which you can type or paste AsciiDoc content.
https://image.nostr.build/73cee7c0bcaf8e1afa09f7ea85e7d4662cdb02c9097d304952c3543aca32c1e4.png
Clicking the eye icon shows a preview.
https://image.nostr.build/50ecf75dc242af4491f103fda58db4d9294a6bc2ac93e266bab2bdec362be3fe.png
Hovering the mouse cursor over the preview highlights each discrete section. Each paragraph will become a kind 30041 zettel, and each section with a header will become a kind 30040 index that references the zettel events produced for the paragraphs it contains.
https://image.nostr.build/e8268c6df06907459754ada9260ea69c6ede44d1a228b2d78d3a6b17048f5c9e.png
https://image.nostr.build/d92e9d1be4a16a5394b689791b749aa577b2817f0fc4a3a1e7360ce0a93bccdb.png
Images, tables, code blocks, and other entities will all be published as unique Nostr events so that they may be easily remixed and referenced in other index events.
Once the preview works, my next effort will be to write the actual upload functionality to turn Alexandria into an honest-to-goodness Nostr Knowledge Base publisher app. Stay tuned!
#GitCitadel

2024-09-23 14:00:01

- reply

Yay! Thanks for confirming that; glad auth is working, at least on Amethyst.

2024-09-23 13:43:54

- reply

Maybe Nostr needs more teams and fewer lone wolves.

2024-09-21 14:20:11

My brother sent me this:
```
C is Latin, the root of all modern languages, the whole universe used to speak it.
C++ is French, it’s Latin with fancy rules, used by the elite around the world & in specific circles.
JavaScript is English, everybody speaks it, most speakers speak it poorly and others don’t bother learning another language.
Java is German, it’s verbose, over-complicated and it made me cry several times. I won’t elaborate.
Python is Esperanto, it was created to be so easy everyone could speak it. Its speakers could benefit from a shower once in a while.
Rust is Russian, most speakers have an authoritarian left background and want to spread it worldwide.
```

2024-09-20 19:50:16

- reply

Desktop apps for all my friends!

2024-09-20 19:10:11

- reply

Nope that's exactly it. Why do I need to rent software? My computer can run it.
Browsers have made everyone lazy. Even desktop apps run in WebView now (I'm looking at you Electron).

2024-09-20 14:43:33

Some people are submitting questions to this work meeting asking what the company is gonna do about Covid cases.
Bruh it's 2024 💀
Sometimes I encounter a mindset so different it might as well be another dimension. Who are these people? Where do they live?

2024-09-19 22:34:27

- reply

I have a ton of home improvement todos that keep getting in front of my Nostr project compdos 😅

2024-09-18 04:55:22

- reply

We can use kind 1111 for Alexandria from the get-go.

2024-09-18 01:45:59

- reply

Nah we just have Bitcoiners bombing their own messages.

2024-09-17 21:59:22

- reply

The same principle applies to mainstream topics on Nostr, tbh. https://image.nostr.build/46515078ed1d4579c31dbb770084f0b3923a50817c84d166ec01ffd58874db88.jpg

2024-09-17 20:47:02

- reply

This makes so much sense.

2024-09-17 14:21:23

- reply

I'm thinking that clients should handle this npub evaluation and issue confirmation events. Relays can then determine which npubs to allow or block based on these confirmations. We can have high- or low-trust relays based on each relay's threshold for allowing an npub. New npubs would necessarily start on only a few relays before getting whitelisted to others as they have more verifiable interactions.
Onboarding becomes key here. If I'm operating a private relay and I manually whitelist my friend's new npub, that speaks well of that npub when other relays evaluate it.

2024-09-17 14:09:17

- reply

Even a fresh clone is failing. Here is the output:
```
git clone nostr://npub1m3xdppkd0njmrqe2ma8a6ys39zvgp5k8u22mev8xsnqp4nh80srqhqa5sf/Alexandria?relayhint=thecitadel.nostr1.com alexandria
Cloning into 'alexandria'...
nostr: fetching...
✔ wss://wheat.happytavern.co/ new events: 1 user profile
✘ wss://nostr.thesamecat.io/ connection timeout
✔ wss://nostr.wine/ new events: 1 user profile
✔ wss://greensoul.space/ no new events
✔ wss://nos.lol/ new events: 2 announcement updates, 7 proposals
✔ wss://nostr.mom/ new events: 1 user profile
✔ wss://relay.damus.io/ new events: 2 announcement updates, 7 proposals
✘ wss://theforest.nostr1.com/ timeout
✔ wss://thecitadel.nostr1.com/ new events: 2 announcement updates, 7 proposals
✔ wss://relay.nostr.band/ new events: 2 announcement updates, 6 proposals nostr updates: 2 announcement updates, 7 proposals, 1 user profile
WARNING: failed to fetch from git@github.com:limina1/indextr-client.git error:early EOF; class=Net (12); code=Eof (-20)
and using alternative protocol https://git@github.com/limina1/indextr-client.git: early EOF; class=Net (12); code=Eof (-20)
Error: failed to fetch objects in nostr state event from:
git@github.com:limina1/indextr-client.git: early EOF; class=Net (12); code=Eof (-20) and using alternative protocol https://git@github.com/limina1/indextr-client.git: early EOF; class=Net (12); code=Eof (-20)
```

2024-09-17 14:02:01

- reply

This is a change from previous versions, yes.
I will try a fresh clone to see if that helps. My configuration may have gotten borked.

2024-09-16 12:25:33

- reply

There's a whole discussion to be had there about how to best understand modesty.
I've come to find that modesty is best formulated as an outward expression of humility. However, that doesn't always mean "cover up all the skin." Dressing or acting differently from those around us always draws attention, so it's better for humility to try to blend in a little.
St. Francis de Sales says that we should be the best-dressed but least obtrusive person in the room, and I think about that almost daily.

2024-09-16 12:13:14

- reply

How tho?

2024-09-16 01:52:37

- reply

How do you handle window organization?

2024-09-14 22:47:17

- reply

Man I want to try that now.

2024-09-14 20:29:32

- reply

That sounds good. It gives us flexibility, but maintains basic compatibility with standard event identification by d tag.

2024-09-14 20:28:26

- reply

I've started reading through the article. I'll post thoughts as I go.
First is that, part of the reason Google retired their "don't be evil" slogan is because they didn't define "evil." For almost any situation, you can find someone who thinks a given course of action is evil. This leads to a moralistic paralysis.
The subsequent discussion on making "supervise" AI runs into the same problem. It can try to respond to the values of its users, but it is virtually guaranteed that there are contradictions in the different value systems such an AI would have to balance.
In short, we can't have ethical AI unless we chose an ethical system for it to adhere to, and no one wants to make that decision.

2024-09-14 20:05:30

So...wen notes over carrier pigeon?

2024-09-14 19:41:30

- reply

The app in general probably shouldn't have its own DB, but our instance, on our website, could easily have its own DB, server, etc. to provide premium features.

2024-09-14 16:40:41

- reply

The wiki spec uses a title-like format because it can be used to build human-readable URLs within the client.

2024-09-14 16:40:08

- reply

Now my question is how relays handle it. If they index the whole d tag array, rather than just the first value, than an event which, for whatever reason, has multiple values in the d tag array would be impossible to access via parameterized lookup.

2024-09-14 16:37:51

- reply

Maybe using `[[author:leo-tolstoy]]` should link to a search page showing results with that `author` tag. We can use a similar format for wikilinks to search results or tag-based feeds. Perhaps you want to link to a feed of literature on a specific topic.

2024-09-14 15:02:30

- reply

The formal spec may have been removed amid edits and shuffling. Some event kinds have specific d tag usage defined, but there's no formal standard for all events, that I could find.

2024-09-14 14:44:24

Hey @nprofile…0d52, question for my curiosity:
How does GRAIN handle event indexing by d tag? Specifically, does it index the whole d tag array blindly, or does it index just the first value?

2024-09-14 14:38:21

Y'all the `d` tag isn't defined anywhere in the NIPs repo 🙃
#nostrdev

2024-09-14 14:37:37

- reply

I see the error on both `ngit push` and `ngit pull`.

2024-09-14 14:36:13

- reply

Y'all I searched and the NIPs repo doesn't formally define the `d` tag anywhere.
That means no one can tell us we can't extend it lol.
I was thinking we use positional values to extend the `d` tag array. Something like:
```json
"tags": [
["d", "war-and-peace", "leo-tolstoy", "penguin-classics-edition"]
]
```
The general format would be `["d", <title>, <author>, <edition>]` where edition is a human-readable edition name (as opposed to just a number).
The event _should_ still be addressable by `#d` and the title, just like other event kinds' d tags, but we can increase address specificity for the Nostr Knowledge Base use case. Then we can bake this specificity into wikilinks (see NIP-54 for an existing wikilinks specification). A document might contain `[[War and Peace. Leo Tolstoy. Penguin Classics Edition.]]` and we can specify that clients should split that at the periods and normalize it into a d tag array reference, so it becomes `["#d", "war-and-peace", "leo-tolstoy", "penguin-classics-edition"]`. The client can then use this tag array to search its relays, find the closest match, and display to the user a hyperlink to the referenced event.
Basically, we define a citation format for NKB events.
Since the event ID is derived from a serialization of the whole event, including tags, increasing identifier specificity will always generate a unique event ID.
We'll have to experiment with how relays index events by d tag, and how they respond to queries for such events. Maybe Stella's PHP utilities can help us with that. Worst case, relays only support searching by the first `d` tag value and return a bunch of matching results, and then we have Alexandria walk through the results and find matches by author and edition.

2024-09-14 14:04:45

- reply

Relay AUTH for closed groups is just the beginning.
Imagine running a small, authenticated relay on your laptop. You could sit down in a coffee shop, turn the relay on, and have your project group sit down with you, log on and share notes and documents over the local wifi. Maybe the relay could use your local filesystem as a backend store for documents and images. Other members of your group might use the same setup, and everyone's respective local relays could use negentropy to stay in sync. Now you have a self-hosted collaboration network that you can pop up anywhere and that requires no central servers.
Relays used to exchange git events for Git over Nostr could run alongside a push notification service. When one of your contributors opens a new patch proposal, you can get notified instantly on your phone. You can even connect to that relay and comment on the proposal while you're on the go.
Attach a relay to a small server that imports calendar events to a shared calendar. Anyone who has access to that calendar can run a small utility that uploads calendar files, such as .ical, to the server. The server transforms those into a Nostr event and drops it onto the relay. A push notification then goes out to every device in the calendar group to tell the clients to fetch the new event.
So far all of our innovation has focused on making better clients, but a smart client will only get you so far. Nostr's secret sauce is its relays; when we realize that, it will open up whole new horizons.

2024-09-14 13:45:28

Y'all we're sleeping on relay capabilities.
#MakeBackendGreatAgain

2024-09-14 13:44:52

- reply

Trying it out now, but I get this:
> Error: git should set GIT_DIR when remote helper is called
> Caused by:
> environment variable not found
Do I need to set the `GIT_DIR` env var a certain way?

2024-09-14 12:52:26

- reply

I think so? You might be thinking in PHP-specific terms I'm not familiar with.
As an example, though, I recently wrote a class for my day job that had a public `value` prop and a private `_value` state. Changes to `value` updated `_value`, but not vice-versa, because the public one had a change listener and I needed a way to change it without triggering the listener.
However, were it not for that case, I would have just used a single class property `value` with no explicit getters or setters, because TypeScript defines get and set behavior by default on classes, without the need for developer code.

2024-09-14 12:37:03

- reply

CLI dev is still dev

2024-09-14 12:36:21

- reply

I only use them when my get or set needs to do something non-standard. Using them everywhere when the language supports default getters and setters on class properties just creates unnecessary clutter.

2024-09-14 03:54:28

- reply

Did you read the except from the Summa? It addresses that very question.

2024-09-14 03:00:45

- reply

If you cook a meal, do you not have both the power and right to share it with whom you please, or to not share it at all?

2024-09-14 02:22:00

- reply

While searching I also read the suggestion that the commands we see to put all the Canaanites to the sword was a Hebrew idiomatic hyperbole; indeed we see examples of hyperbole throughout Scripture ("If your eye causes you to sin,..." etc.).
If this is the case, then, as you suggested earlier, perhaps we are not to take it absolutely literally, in which case the moral or spiritual meaning becomes primary in governing our understanding of such passages.

2024-09-14 02:19:21

- reply

A bit of searching brought this up; Article 5 is especially pertinent:
https://www.newadvent.org/summa/2094.htm
Thomas asserts God's absolute sovereignty over life and death, saying:
"All men alike, both guilty and innocent, die the death of nature: which death of nature is inflicted by the power of God on account of original sin, according to 1 Samuel 2:6: "The Lord killeth and maketh alive." Consequently, by the command of God, death can be inflicted on any man, guilty or innocent, without any injustice whatever."
All the objections and replies are worth a read, though.

2024-09-13 22:18:55

- reply

That last point is why I led with the moral/allegorical interpretation of the passage. Frankly, I don't fully understand why God would command the Israelites to kill all of the Canaanites, but I do understand that when I read it today, I can understand it as an admonition to aggressively root out all the things in my life that will draw me away from God.
Yet, we can't simply discard the literal meaning of the text, and those passages are definitely among the most difficult to understand literally, at least from a moral framework shaped by the incarnation, death, and resurrection of God.
God also allowed divorce in ancient Israel, but Jesus forbids it to Christians. Is this a contradiction? It sure can feel that way sometimes. Is God "allowed" to command what he pleases? Yes.
Now, this goes back to the ancient question: "Does God commands something because it is just, or is it just because he commands it?" I tend towards the Medieval view of divine simplicity—that God is identical with all of his attributes. So God and justice are the same thing. Which suggests to me that if these passages of Scripture don't *appear* just, it must be because I am failing to grasp some underlying unity.
All this isn't much in the way of answers, but it's how I try to think about such things.

2024-09-13 21:17:15

- reply

Fair point. The Old Testament has some difficult passages, and I don't claim to know completely how to think about them.
"The Lord giveth, and the Lord taketh away." The utter sovereignty of God is a theme of the Old Testament, to be sure. If God commands the destruction of a people, it must be just, because God is just.
Abortion is different because God is not commanding it.

2024-09-13 15:59:15

- reply

Thanks for the patch! I'll download and try it out next time I'm working on this project.
I didn't know the large patches would cause issues, but it's good we've identified that.
I still need to prep for that discussion and read up based on the other thread. FWIW, when I've tried to puzzle out git over Nostr, I've concluded that full blobs can't/shouldn't live in Nostr events. The events, rather, should point to where the client can download the blob it needs. Blossom might be a good solution for that (though I don't understand Blossom very well yet).

2024-09-13 14:39:34

- reply

I figure explaining the spec in terms of JSON is fine, since JSON is the structural framework of the protocol messages. But yeah mixing implementation details leads to confusion.
Less code examples, more Gherkin acceptance criteria.

2024-09-13 14:33:14

- reply

Thanks for looking into it!

2024-09-13 14:32:54

- reply

Not sure. I'll have to go back and check later.

2024-09-13 13:58:24

@npub15qy…yejr on ngit 1.4.5, when I try to run `ngit push` or `ngit pull`, I get the following message:
> Error: cannot find proposal that matches the current branch name
The branch name on my local computer is `article-editor`, and I'm trying to push updates to the below proposal on GitWorkshop:
#nevent1q…txfp

2024-09-13 13:18:54

- reply

I'm thinking through d tag conventions more, and we may have to revise our pattern somewhat.
The pattern `<title>-<author>-<version>` only really works for the root index of a whole book. Chapters/sections within that book won't have author and version attached to them by default. I see at least two options:
1. Carry author and version information down into the book's hierarchy, and attach it to every chapter and section index. This makes the ids of _everything_ longer (which increases URI length within our app), but it increases the likelihood of name uniqueness even of sections within a book.
2. Don't include author and version information in the d tag identifier of every chapter and section, but include that information in the tags. If we know the author and edition of the book within a chapter resides, for instance, we'll include it in the index event generated for that chapter.
2.5. If we take this latter approach, I'm interested in exploring adding additional fields to the d tag array. The question is whether the first identifier in that array is _always_ used to generate note identifiers for 30000-series events, or whether the whole d tag array is used. Perhaps we can include full author and version information in the d tag array, but not have it be mandatory for looking up an event. The details probably depend on relay indexing and search implementations, there.
Let me know which option you prefer, or if you have other alternatives.

2024-09-13 12:50:59

Tried using Nostter, but all I got was this loading screen.
https://image.nostr.build/be05c21b34a8149c8edaed3301fe4c33b2b3cabcf57bbffda698a7e245730a4a.png

2024-09-13 01:15:53

https://image.nostr.build/dfa301f94f353673578a585026e080e38a019d8b34078cf31f6799fe8eb9216b.jpg
@nprofile…c878

2024-09-12 14:59:02

- reply

The understanding of those passages that I've heard runs along a few parallel tracks.
The first is that God commands this to protect the Israelites. As it turns out later, the Israelites don't completely uproot the inhabitants of the land, and they fall into the pagan practices of the Canaanites. If they had obeyed God's commands, they would not have been as tempted towards idolatry.
A second reading is more metaphorical. We can see in the Canaanites an image of sin and temptations. If we are to be holy as God wishes for us, we must completely uproot sin and all of its occasions from our lives. In this reading, God's command is directed at us today: we must purge all that separates us from him.
All of this is not necessarily incompatible with God's mercy. The Canaanites were utterly lost in multifarious sins and idolatries. Even the children would just grow up to heap condemnation upon themselves. If they die at the hands of the Israelites that spares them from the future sins they would otherwise commit.

2024-09-12 13:23:18

- reply

8-9am CDT usually works for me. I could probably pull 7am CDT as well.

2024-09-12 13:12:44

- reply

👀 I'll read it when I get a chance.

2024-09-12 13:11:22

- reply

So is appeal to Wikipedia 🤣

2024-09-12 13:11:04

- reply

The moral quality of the popes does not change my view about whether they are of the line that Christ established.

2024-09-12 13:10:08

- reply

Talk to Descartes and tell me how far you get with pure reason.

2024-09-12 13:09:25

- reply

That's past my bedtime 😅

2024-09-12 13:08:47

- reply

Just turned it on. It was off before.

2024-09-12 13:07:12

- reply

I'll check my settings!

2024-09-12 05:15:02

- reply

A totally empty document should throw an error. But I think if the user tries to publish a document, as long as we can pull the required fields for the index event tags from the document, we should go ahead and publish it. Trust that our users know what they're doing, or are at least smart enough to figure out out sooner or later.

2024-09-12 05:11:46

- reply

That seems to me to be a somewhat incoherent position. If someone holds a legitimate position, it is natural in our use of language to use the term of address that goes with that position. It is clear that Jesus is saying that we should not pridefully seek station for ourselves, nor should we be sycophants and give others accolades they do not deserve. However, I fail to see the substantial distinction between acknowledging a spiritual station and according an honorific proper to that station.
If Paul is a spiritual father to the church in Corinth, it would be strange to say that he ought never address the Corinthians as "my children in Christ," or some such title accordant to their relative stations. Likewise, if the Corinthians can call Paul a spiritual father, it would be counterintuitive to say that they can never address him directly as such. The honorific in such a case is given out of love and respect rooted in Christ; it is not insisted upon out of pride, nor is it bestowed out of a fawning servility.

2024-09-12 05:00:28

- reply

I can do most days 11pm-12am CDT (6am-7am CEST).
In the meantime, I'll make a note to myself to read up on git diffs to be sure I understand the proposed solutions.

2024-09-12 04:53:02

- reply

I'm having a hard time figuring out by the question.
Are you asking what happens if the first index event doesn't have any child events?
In general, each paragraph will become its own kind 30041 zettel, so if there are no subsections, the document will be turned into a single index with a bunch of one-paragraph zettels.
Does that answer your question, or did I just misunderstand it?

2024-09-12 04:41:59

- reply

One tradition is founded by Christ, and all others are made up.
Does yours have an unbroken lineage of succession tracing itself back to Peter, on whom Christ said he would build his church?

2024-09-12 04:40:29

- reply

It would seem that Jesus is speaking somewhat hyperbolically in his denunciation of the hypocrisy of the Pharisees, who take on such titles in order to exalt themselves. This is clear because he concludes by saying "whoever exalts himself will be humbled, and whoever humbles himself will be exalted" (Matthew 23:12).
Likewise, it would seem that we are not to take it completely literally when Jesus says that we must hate our father and mother, for he also says that those who voice literal hatred in terms such as "raca" or "you fool" are liable to judgement and hell. Thus it cannot be that Jesus is prescribing hatred.
Rather, our love for God should be such that, relative to it, our affection for parents is as hatred. Likewise we should not seek or insist upon honorifics for ourselves, but it is not wrong for someone to use a title of respect when addressing another.

2024-09-12 04:26:53

- reply

Then why does he, from the cross, entrust Mary to John's care saying to him "behold your mother," and to her "behold your son?" Was he telling John he ought to hate Mary?

2024-09-12 04:19:44

- reply

By that standard, then, should we not call our own parents Father and Mother?

2024-09-12 04:18:39

- reply

Throwing out the majority of the New Testament that the entirety of Christianity has held as canon is a bold move, brother.

2024-09-12 04:07:55

- reply

From that point of view, what do you make of Paul calling himself a father to the Corinthians in 1 Corinthians 4:15?
"For though you might have ten thousand guardians in Christ, you do not have many fathers. Indeed, in Christ Jesus I became your father through the gospel." (RSVCE)

2024-09-12 03:59:24

- reply

That's kinda exactly my point. Just standardize around AsciiDoc everywhere.

2024-09-12 03:41:29

- reply

@nprofile…j8qs and @nprofile…lvcy y'all about to break zapvertising wide open.

2024-09-12 03:38:11

- reply

ReplyGuy is the leader 🤣

2024-09-12 03:33:43

- reply

This is one of my favorite tracks off of that album.

2024-09-12 03:31:51

- reply

What about AsciiDoc?
@nprofile…xuyp has converted me on that point.

2024-09-12 03:27:42

- reply

We're watching monetary deflation in real time.

2024-09-12 03:27:07

Zapvertising zaps never seem to make it into my Minibits wallet. Where do the sats go? 🤔

2024-09-11 20:11:10

- reply

Is that...is that Shaggy? https://image.nostr.build/4852e75c7eaecdb63573bdb68eff5dd1a794fba4c3309146901109b9e1e5ecc9.jpg

2024-09-11 04:23:40

I want to give a shout-out and say thank you to @npub1qdj…fqm7. While I've been working on event editing for Alexandria, he has been carrying the torch for Aedile.
The #noscrypt Nostr cryptography library is now fully integrated into Aedile, which uses it for key generation and encryption operations related to remote signing actions.
Everyone go check out noscrypt, it is the C reference implementation of NIP-44, and some high-quality code.
https://www.vaughnnugent.com/Resources/Software/Modules/noscrypt
You can also check the `note-signing` branch on Aedile to follow progress on our work to add remote signer support.
https://github.com/buttercat1791/aedile-ndk/tree/note-signing

2024-09-11 04:09:44

- reply

Recording here what we discussed in Slack:
- 'Zettel' is the term we're using specifically for kind 30041 events. They are intended to be bite-sized notes.
- 'Index' is the term we're using for kind 30040 events.
- 'Event' is the generic term. Wiki entries, long-form articles, indices, and zettels are all 'events.' If we don't have a specific term for an event kind in a given instance, we'll call it an 'event.'
Terms like 'node,' 'block,' and 'section' are specific to Asciidoctor. I can add details in the code comments explaining how we are using different terms throughout the parser logic.