buttercat1791
Michael J

Building the library of Alexandria

Public Key

npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsyn

NIP-57 Address

gitcitadel@geyser.fund

Profile Code

nprofile1qqs8qy3p9qnnhhq847d7wujl5hztcr7pg6rxhmpc63pkphztcmxp3wgppamhxue69uhkummnw3ezumt0d5q3gamnwvaz7tmwdaehgu3wdau8gu3wv3jhvwl6hge

Publishing to

nostr.mom

nostr.oxtr.dev

nostr.thesamecat.io

Author Public Key

npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsyn

Show more details

Last Notes

2024-09-20 19:10:50

- reply

Hey I think I saw that place in the Dune movie.

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 14:52:11

- reply

Maybe revealing the capability is intended to deter Iran. If Iran can't develop a countermeasure quickly, then Israel could use the same tactic against Iran in coordination with a strike against their nuclear facilities.

2024-09-19 01:48:24

- reply

Still, this seems to be a foolish time to unveil such an attack.
That's the kind of tactic you save for a first strike on Iran, for instance.

2024-09-19 01:47:19

- reply

Maybe his literal grave as well.

2024-09-19 01:47:00

- reply

🤔 https://image.nostr.build/1528e309c585a29af496adc813d539eb5c23ecdde20c41229216316c14db4b61.jpg

2024-09-19 00:40:36

Israel blowing up Hezbollah's pagers is a first-day-of-the-war type of exploit. Once you've revealed that capability, your enemies will start developing defenses and mitigations.
So the question is, why did Israel choose to reveal that capability now?

2024-09-18 20:29:45

- reply

And here I was wondering if the second attempt against Trump by a loony lefty was evidence for it being an organic happening rather than a conspiracy.
If they're not hiding anything, moves like this sure make it harder to believe them.

2024-09-16 18:06:30

- reply

TBH I'd much rather the US military be patrolling our southern border than gearing up to play capture-the-flag over Taiwan. Maybe that's what it would take.

2024-09-16 17:55:31

- reply

That's why you close the border. Send everyone home, then no one new comes in.

2024-09-16 13:14:53

- reply

I think the caching DB could be part of our premium offering.
The client is open-source, so anyone can run an instance. The data? Not everybody will have that.
We can attach a caching service to TheCitadel relay and introduce a paid tier for those who want that additional performance.

2024-09-16 12:29:02

- reply

A friend of mine says that we should give all the illegal immigrants in the US a million dollars each, send them home, then close the border, and it would still be less costly than our current policy.

2024-09-14 20:05:30

So...wen notes over carrier pigeon?

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 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 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: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 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-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:10:08

- reply

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

2024-09-12 13:07:12

- reply

I'll check my settings!

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: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: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:05:29

- reply

It will parse the document down to 5 levels of nested sections (`===== Section`). Currently, any sections deeper than that will be lumped into the content of the kind 30041 events generated from fifth-level blocks.
In theory, we can go arbitrarily deep, but at a certain point, we don't need that much depth in an editor workflow that is driven by direct user input (versus a programmatic upload of something large and complex, like the Bible). Setting a cutoff makes things a bit easier for both us and, IMO, for the end user.

2024-09-11 04:02:13

- reply

I don't do anything to pull author from the document yet, though I will add that soon. Asciidoctor has some nice convenience methods that automatically parse fields like author out of the document.
Thank you for reminding me to include author and version information in the d tag, I hadn't thought about that detail yet.

2024-09-10 23:30:06

This funding problem is exactly why the @nprofile…vd7t team is pursuing alternative funding sources beyond grants.
#nevent1q…pysh

2024-09-09 19:04:01

- reply

Output should involve detailed work tickets with acceptance criteria so the devs can just knock out the work to remediate.
Like you've done with the Issues board for Alexandria.

2024-09-09 15:22:22

GM Nostr! I've been working on a custom extension to Asciidoctor to help #Alexandria turn AsciiDoc documents into Nostr Knowledge Base event collections. Would others be interested in using this AsciiDoc utility in isolation?
If there's interest, I can make it available separately from the rest of the Alexandria code base so that other devs can use it to build their own apps.
#NostrDev #GitCitadel

2024-09-09 03:32:45

- reply

I'm a fan of low childhood morbidity and a steady diet, to be sure.
This is why BMI is a bad index, I've heard. It was made when everyone was skinner due to poorer diets.

2024-09-08 18:42:53

- reply

I've heard the exact opposite take (well, minus the fat part, everyone knows that), so this is interesting to me.

2024-09-07 21:52:13

- reply

Maybe it's true under ideal circumstances.

2024-09-07 20:44:09

@nprofile…anjs do you have prototypes of your social onboarding we can play with? I've got a couple of friends who might be interested if I gave them an easy on ramp.

2024-09-06 17:40:49

- reply

I should be able to see it on read mode next time I test, then!
Looking forward to turning you loose on the editor and getting your feedback.

2024-09-06 17:30:51

- reply

What if Bryan is behind the Reply Guy bot? 🤣

2024-09-06 17:27:57

- reply

Why do you think that?

2024-09-06 17:27:45

- reply

What debugger are you using?

2024-09-05 14:01:05

- reply

Pulling author from the AsciiDoc would be good. We could even have a prompt before sending to ask if the user wants to use whatever author name we found in the content.

2024-09-05 12:40:08

- reply

I would think that creating an index of things that already exist would be a separate workflow. It might start while browsing in reading view. The user clicks a button next to a note that says "remix" or "add to index," and they are taken to an editor/search view where they can find other notes to add to the index and/or write their own content. I still need to think that through, since it's different from purely writing new content.
Kind selection also impacts how we might parse the AsciiDoc content. If a user wants to publisj a wiki article, we probably wouldn't break down the content into smaller events. Rather, it would be one large wiki event kind. I'll have to think through how to represent that in the UI. Changing kinds may cause sections to merge together and such.

2024-09-05 12:33:50

- reply

Yeah it's more tedious for power users, but less error-prone for newbies.
We can always add a power user mode later.

2024-09-05 12:29:17

- reply

The UX rule of thumb I've heard is "Don't punish the user before they've performed an action."
So best practice is to make optional fields optionally visible, and not to show the red stars and such oj mandatory fields unless the user tries to submit the form without filling out all the necessary fields.

2024-09-05 04:32:27

I'd like some design feedback on Alexandria.
I'm working on an article editor feature. A screenshot of an early draft is below. The overall goal is to be able to type AsciiDoc-formatted text, preview it in rich text form as it would appear in the Alexandria reader view, then publish it as a cluster of kind 30040 and 30041 events.
My thinking is to break the content down into sections. The content of each section will be published as a kind 30041 note. Each section will be indexed by a kind 30040 note, which will reference the content of the section as a kind 30041 and any subsections as 30040 notes.
Question: How would you like to preview your published events?
I see two options:
1. There are two preview steps: one is a "quick preview" you can see with a click while editing. It doesn't break the content down into 30040 and 30041 events, but it shows you what the nicely-formatted AsciiDoc content would look like. The second preview steps shows the content as it would appear in reader view, after it's been broken down into its constituent 30040 and 30041 events. This preview would have a confirmation dialogue that lets you approve or cancel publishing the events.
2. There's just one preview, and clicking the preview button while editing shows you the content as it would appear in reader view, broken down into 30040 and 30041 events. There would be no separate screen with a confirmation dialogue, and a publish button on the editor page would publish the events.
I'd love to hear people's thoughts!
#asknostr #alexandria #gitcitadel #nostrdev #nostrdesign
https://image.nostr.build/2328fa70d7207dfbfa0196a869dadae7cb03925005786456a00e6107b905438e.png

2024-09-03 17:49:20

- reply

Everyone wants to start a commune with their friends 🤣

2024-09-03 12:48:06

- reply

I've observed the same thing in the US—most of us don't have any cultural traditions, even family traditions.
The unfortunate thing, as I see it, is we can't just create culture, nor can we merely return to traditional practices. Tradition that was not handed down can be artificially reinstated, but it loses something in the process. New traditions can be created but often they don't stick.
I think we have to create occasions in which culture can arise, then hope it comes about naturally.

2024-09-03 02:28:24

- reply

Whole articles and videos with narration, all AI generated.

2024-09-03 02:06:29

Want to see something wild?
Go online and search for "2025 Chevrolet Bel Air."
Then come back and tell me what's wrong with all the articles and videos.

2024-09-01 17:33:10

- reply

https://image.nostr.build/186bfb91d98be7cf525d81d72b97275a046f898ec9a3bb74d4dfb52201aa5367.jpg

2024-09-01 15:00:48

"Marijuana has surpassed alcohol as America's favorite addiction. In 1992, fewer than one million Americans were daily smokers of pot. In 2022, the number had soared to 17.7 million. In the same year, 14.7 million Americans reported drinking alcohol daily. Writing for UnHerd, Mary Harrington speculates that the ascendancy of marijuana bespeaks a cultural change. In Anglo-American culture, coffee, cigarettes, and afterwork booze were part of a culture of work. Factory workers chugged Budweiser at the corner bar when their shifts ended. Corporate managers poured martinis at home after a long commute. By contrast, here in New York, I often smell pot as I walk to work in the morning. It's not the aroma of productivity."
— R. R. Reno writing in First Things

2024-09-01 13:40:56

The Windows installation on my laptop totally broke, so I'm installing Linux Mint in its place.
Gotta say, I love how small the install files are. 5MB on a thumb drive and it's a whole operating system.
Now to start setting Mint up for my Nostr projects.

2024-08-30 22:24:55

- reply

But like. Why is he pulling on its udder.

2024-08-30 22:23:03

- reply

Wait but how does it guess whether someone has facial hair???
Incredible

2024-08-30 22:18:13

- reply

That's a fun one!

2024-08-30 20:49:37

- reply

We gotta get you some backing tracks!
It sounds like you're hitting all the right notes, but my brain is looking for the rest of the mix to fill in the chords and the rests. 😁
This is fun! Love the Nostr karaoke.

2024-08-30 20:21:45

- reply

Everyone is weirded out hearing their own recorded voice. Doesn't mean it's bad!

2024-08-30 20:11:51

- reply

That sounds really good!

2024-08-30 12:10:07

- reply

Yep! I've been doing it for a few weeks now!

2024-08-29 20:31:19

When you walk into the bathroom stall right after someone came out, but the seat is cold 😱

2024-08-29 19:39:58

- reply

I try to keep a good mix of all three on my feed 😆

2024-08-29 19:35:32

- reply

I'm waiting for the day when the user experience seamlessly and automatically transfers you between phone or desktops apps to give you the best tools for each activity.

2024-08-29 19:32:56

- reply

Also give @nprofile…l937 a follow, he has had some significant activity lately in the low-level cryptography space.

2024-08-29 19:31:52

Some notable points of collaboration have been with @nprofile…crvd on Git over Nostr, and @nprofile…8qkt on wikis and event design for Alexandria.
There are plenty of other devs building parts of the Nostr ecosystem. We work with them to give feedback and boost their apps' capabilities while we carve out our own nice.
It's cooperative competition.
#value4value
#nevent1q…7yrr

2024-08-29 19:28:34

- reply

This is what a good analyst does! You analyze the environment we're working in and give us actionable conclusions.
"Analyst" feels like a fake role when the analyst is bad. But when she's good, it's invaluable.

2024-08-29 19:26:05

- reply

Who are the cool people?
I think libraries are cool.

2024-08-29 15:59:53

- reply

Making this measure of interaction work would require clients to automatically rebroadcast notes on view. Not just scrolling by in a feed, but if I click on a post, my client should rebroadcast it to my relays, even if I don't like or comment or zap. Then other clients can measure the "viralness" of a post by counting how many relays have that post.

2024-08-29 13:42:54

- reply

Do you think we could rig up some way to use NIP-05 addresses to sign up for centralized services?

2024-08-29 13:41:36

- reply

Platinum-tier, white glove Nostr developer support.

2024-08-29 00:16:41

- reply

Say more about pluggable events 👀

2024-08-28 22:19:18

- reply

Those days are always rough.

2024-08-28 21:02:41

- reply

That would be a real value-added.

2024-08-28 20:37:37

- reply

Maybe we can run external URLs (as opposed to event IDs) through a content scanner that automatically blocks suspect images or sites.

2024-08-28 20:29:06

- reply

Possibly, especially if indices reference external URLs.

2024-08-28 20:25:55

- reply

We could probably pass everything through a filter layer client-side before downloading.

2024-08-27 21:40:54

- reply

2024-08-27 20:12:49

- reply

The amount of data and computation needed to watch it real-time would be huge. But it would be super cool.
Maybe we could bake graph traversal algorithms into Aedile and make it a data science tool. 🤔

2024-08-27 19:49:36

- reply

Tell me more?

2024-08-27 17:10:57

- reply

I've been working with Flowbite Svelte components for Alexandria and learning good patterns for web component design.
All the work I've been doing with C and C++ for Aedile helps me think better about what's going on under the hood of our C# projects.
Just as two examples.

2024-08-27 17:09:35

- reply

We love that too! 🚀

2024-08-27 16:02:10

You know it's getting real when the stuff you learn on your Nostr side project cross-applies to your day job. 💪

2024-08-27 15:38:31

- reply

Will nostrmeet.me be able to integrate with OtherStuff clients?
Suppose I'm working on a code project, and we're collaborating via GitWorkshop. Can I send an invite to friends that directs them to GitWorkshop so they can set up their code workspace?
Likewise, what if I want to invite writers to apps like Habla or Yakihonne. Can I give them a customized invite that points them to long-form writing clients?
I think OtherStuff will become bigger than social media for Nostr, in the long run. We need smooth onboarding for those use cases just as much as we need good notification managers.

2024-08-27 14:49:05

- reply

Just the ngit commands. I'm not sure yet what the remote helper is, and I didn't take time to look into it last night.

2024-08-27 14:40:42

- reply

What is Gemini?

2024-08-27 14:30:47

- reply

Maybe different kinds coming with different thread rules, then? It might make more sense if we move away from kind-1-for-everything, anyway.

2024-08-27 14:02:02

Yesterday, I used ngit and GitWorkshop to propose new changes to @npub1s3h…75wz's Alexandria app. Alexandria collaboration is fully managed over ngit and GitWorkshop, which is amazing to see. The future of code collaboration is already here!
Big props to @npub15qy…yejr's tireless work on ngit. It gets better every time I use it!
I went from v1.2.1 to v1.4.2, and in the new version I was able to use Amber to sign most events, interaction prompts were easier to understand, and the app seamlessly worked with multiple repo events from different maintainers. Looking forward to seeing where ngit goes in the future!

2024-08-27 13:45:54

- reply

Maybe what will be needed ultimately will be thread viewer hints to suggest to clients how to display messages in a thread.

2024-08-27 13:16:22

- reply

Allowing deeply-nested threads opens up a whole can of worms, as I've learned from playing with different Nostr clients. Amethyst and noStrudel have the best viewing experience for large and complex threads.
There's something to be said, I think, for Facebook- or Slack-style threads that only go one layer deep. Deep enough to keep side conversations out of the main replies, but much more manageable, visually.

2024-08-27 13:11:05

- reply

I am! 🫂

2024-08-26 21:00:49

- reply

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.

2024-08-26 18:59:44

- reply

Just a thought: maybe you could separate the metadata event from the human-readable descriptions and conversation.
The issue/cover letter event could reference other events needed to reconstruct an issue thread, including a PR description, references to code or commits, comments, etc.
This could use a model similar to the index events in @nprofile…xcg6's Nostr Knowledge Base spec.

2024-08-26 18:39:01

- reply

Of course, without constitutional protection for the citizens to arm themselves, there are fewer guarantees such locally-organized militias would be possible at all.