buttercat1791
Michael J

https://geyser.fund/project/gitcitadel

Building the library of Alexandria

Public Key

npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsyn

NIP-57 Address

[email protected]

Profile Code

nprofile1qqs8qy3p9qnnhhq847d7wujl5hztcr7pg6rxhmpc63pkphztcmxp3wgpz3mhxue69uhkummnw3ezummcw3ezuer9wc5nhrdw

Publishing to

nostr.oxtr.dev

Author Public Key

npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsyn

Show more details

Last Notes

2024-09-20 16: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-20 16:12:10

"It's like a startup within a large company."
--Heard in a virtual work meeting with 700+ people on the Teams call. 🤡

2024-09-20 15:16:24

- reply

It's cause Gemini was programmed by a bunch of white Silicon Valley tech bros.

2024-09-19 22:16:39

- reply

It's like when I stop seeing homeless people. Like, I know they didn't all get homes. Where did they go? 🤔

2024-09-19 21:37:21

- reply

Where did they go?

2024-09-19 03:47:00

- reply

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

2024-09-19 02: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 22: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-18 14:17:35

- reply

I think the language is that way because you can't technically reject all cookies and still have a functioning website.
Some are used for basic functionality, such as to track whether you're logged in. So "reject" does seem like a misnomer.
How would you suggest handling that?

2024-09-18 03:59:02

- reply

It's here!

2024-09-17 16: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 16: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 19:55:31

- reply

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

2024-09-16 16:21:47

@npub15qy…yejr ngit v1.4.6 seems to be broken with my repo setup. When I try to run it from the root directory of the repo, it gives me this error:
```
Error: git should set GIT_DIR when remote helper is called
Caused by:
environment variable not found
```
If I manually set GIT_DIR to point to the repo's `.git` file, then run `ngit push`, I get the following:
```
Error: invalid nostr url
Caused by:
relative URL without a base
```
Has my configuration gotten messed up somehow?

2024-09-16 03:52:37

- reply

How do you handle window organization?

2024-09-14 22:29:32

- reply

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

2024-09-14 22:05:30

So...wen notes over carrier pigeon?

2024-09-14 21: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 18: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 18: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 18: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 17: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 16: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 16:38:21

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

2024-09-14 16:37:37

- reply

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

2024-09-14 16: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 16: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 15:45:28

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

2024-09-14 15: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 14: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 14:37:03

- reply

CLI dev is still dev

2024-09-14 14: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 05:54:28

- reply

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

2024-09-14 05: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 04: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 04: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-14 00: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 17: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 16:33:14

- reply

Thanks for looking into it!

2024-09-13 16:32:54

- reply

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

2024-09-13 15: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 15: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 03:15:53

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

2024-09-12 16: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 15:23:18

- reply

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

2024-09-12 15:12:44

- reply

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

2024-09-12 15:11:22

- reply

So is appeal to Wikipedia 🤣

2024-09-12 15: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 15:10:08

- reply

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

2024-09-12 15:09:25

- reply

That's past my bedtime 😅

2024-09-12 15:07:12

- reply

I'll check my settings!

2024-09-12 07: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 06: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 06: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 06: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 06: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 06:19:44

- reply

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

2024-09-12 06: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 06: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 05:59:24

- reply

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

2024-09-12 05:41:29

- reply

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

2024-09-12 05:38:11

- reply

ReplyGuy is the leader 🤣

2024-09-12 05:31:51

- reply

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

2024-09-12 05:27:42

- reply

We're watching monetary deflation in real time.

2024-09-12 05:27:07

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

2024-09-11 22:11:10

- reply

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

2024-09-11 06: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 06: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.

2024-09-11 06: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 06: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-11 05:59:36

- reply

Asciidoctor parses a document into blocks. A block can be a paragraph, an image, a chart, a code block, a mathematical formula, a section, or even a whole document.
For sections, the ID consists of the underscore-separated section title. So if you had a section header `== Part 3: The Reckoning` in your document, then Asciidoctor's ID for that section would be something like `part_3_the_reckoning`.
It does something similar to generate IDs for paragraph blocks that don't have an explicit title, but I'm not sure yet exactly what the results come out to be.
If two IDs clash, Asciidoctor appends numbers them to guarantee uniqueness.

2024-09-11 01:30:06

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

2024-09-11 00:34:44

- reply

Dude sign me up!

2024-09-11 00:14:21

- reply

I'd ride in a zepplin. Slower but more stylish than a jetliner.

2024-09-11 00:00:35

- reply

The biggest obstacle I can see to the baggage part is making baggage handling fast and efficient enough to make the slight inconvenience bearable.
In general, I would much prefer to walk into an airport with just my phone, wallet, and a book than a whole backpack or carry-on bag.

2024-09-10 17:34:04

- reply

It could be I'm seeing less of both real people and bots because of my relay setup.

2024-09-09 21:33:41

- reply

Exactly. Very loose.

2024-09-09 21:09:31

- reply

You could also scale your service offerings and rates to the size of current Nostr projects and build up a clientele in the early days.
A service like this is actually a boon that would enable more lone wolf Nostr devs to bootstrap innovative projects more effectively.

2024-09-09 21: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 20:05:03

@ReplyGuy you a hoe

2024-09-09 17: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 05: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 20: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 23:52:13

- reply

Maybe it's true under ideal circumstances.

2024-09-07 22: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-07 22:42:02

I was just explaining Nostr to some friends.
They were captured by the idea of Nostr as digital identity.
We also agreed framing it as digital subsidiarity works well.

2024-09-06 19: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 19:30:51

- reply

What if Bryan is behind the Reply Guy bot? 🤣

2024-09-06 19:27:57

- reply

Why do you think that?

2024-09-06 19:27:45

- reply

What debugger are you using?

2024-09-06 00:34:19

- reply

Wait how does that volumetric display work?

2024-09-05 20:00:35

- reply

Bold maneuver.
Like re-chaptering the Bible.

2024-09-05 16: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 14:40:47

- reply

We could have a little confirmation pop-up as one final exit hatch in case the user changes their mind.

2024-09-05 14: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 06: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-05 04:09:58

- reply

Yeah, if you connect Minibits to your Nostr apps with NWC, you can do one-tap zaps.
I like how Alby Hub allows for self-custody, but currently it's not the best option for people to use as a daily driver unless they have home server setups or feel like paying for hosting.

2024-09-03 21:54:41

- reply

I have them on!

2024-09-03 19:49:20

- reply

Everyone wants to start a commune with their friends 🤣

2024-09-03 19:33:01

- reply

In my experience, people often end up with responsibility when everyone else takes a step back.