buttercat1791
Michael J

Nostr Stability Advocate

Public Key

npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsyn

NIP-57 Address

[email protected]

Profile Code

nprofile1qqs8qy3p9qnnhhq847d7wujl5hztcr7pg6rxhmpc63pkphztcmxp3wgpr4mhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet5e399et

Publishing to

nostr-pub.wellorder.net

Author Public Key

npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsyn

Show more details

Last Notes

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 16:38:21

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

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-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:32:54

- reply

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

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 05:38:11

- reply

ReplyGuy is the leader 🤣

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 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: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 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-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.

2024-09-03 19:26:25

- reply

The German philosophy Josef Pieper argued that true culture depends on—or is at least seeded by—religion.
He says that culture is an affirmation of the goodness of the world and of life, and such an affirmation naturally expressed itself in thanksgiving. The act of giving thanks, of course, implies an object, namely, God.
That said, while this religious connection is implicit, it is not always the focal point of each and every element of a culture. What is always necessary, however, is an attitude of wonder and receptivity to the gift that is our existence. That is why we typically associate culture with music, food, and poetry; they are all things we receive that cause us to stop and ponder the world as it is.

2024-09-03 15:29:55

- reply

Having a means of specifying the git connection protocol looks good to me. Two things:
1. I personally prefer using a query string for relay hints and server protocol. It keeps the repo address itself concise and a little more human-friendly, while extra detail can be added as needed in the query.
2. In addition to npubs, will we be able to use NIP-05 addresses? Npubs are rather cumbersome. Ideally, I'd want to be able to type out a repo address into my command line, rather than always having to copy-paste it.

2024-09-03 14:51:25

- reply

The young adult community at my church started what they call "Wojtyla nights," named after Karol Wojtyla (Pope John Paul II), and they consist of sharing of food and presentation of performance of various kinds of art by members of the community.
Last year, just before Christmas, my wife and I hosted a party with a formal toast, cocktail menu, and poetry readings.
It's possible to create spaces for culture to develop, but it requires active and persistent effort, and buy-in from others.

2024-09-03 14: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 04:28:24

- reply

Whole articles and videos with narration, all AI generated.

2024-09-03 04: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-03 03:09:39

- reply

Great, so go to the GitHub page, go to Releases, and look at the latest release. From there, find the file that ends with .dmg. If your Mac has an Intel chip, get the one with x86 in the name, otherwise get the file with arm64 in the name.
When you've download the dmg file, double click it, and it should install.
https://github.com/mikedilger/gossip/releases/tag/v0.11.3

2024-09-03 02:37:46

- reply

Are you on Windows, Mac, or Linux?

2024-09-02 17:38:30

- reply

Zapping posts regularly through Amethyst works just fine, though.

2024-09-02 17:34:31

- reply

I managed to zap back @nprofile…6zvh and @nprofile…7rsf, but I had to initiate it from the Minibits wallet.
When I tried to send zaps to their profiles via Amethyst, Amethyst appended 3 zeroes to the end of the amount. So 33 sats became 33,000! 🤣
#minibits #amethyst #nostrdev

2024-09-02 17:13:47

Testing out Minibits, can someone send me a small zap, and I'll send it back?

2024-09-02 15:47:36

- reply

I'll give it a look!

2024-09-02 15:34:42

noStrudel is getting stuck whenever it tries to publish an event, and Coracle isn't finding my relay list, so I guess I'm just noting from my phone today 🙃

2024-09-01 19:33:10

- reply

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

2024-09-01 15: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-09-01 00:46:02

- reply

I like the border better.

2024-08-31 00:24:55

- reply

But like. Why is he pulling on its udder.

2024-08-31 00:23:03

- reply

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

2024-08-31 00:18:13

- reply

That's a fun one!

2024-08-30 22: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 22:21:45

- reply

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

2024-08-30 22:11:51

- reply

That sounds really good!

2024-08-30 14:36:02

- reply

Yeah something like that. Amber will give you the URL to copy-paste.

2024-08-30 14:10:07

- reply

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

2024-08-29 22:31:19

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

2024-08-29 21:39:58

- reply

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

2024-08-29 21: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 21: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 21:26:05

- reply

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

2024-08-29 17: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 15:46:13

- reply

That's the thing, Nostr only needs to be as big as each app's use case.
If a team wants to go global in reach, they can run all the relays necessary to do that.
Smaller-scale, more dedicated applications will be more cottage-sized.

2024-08-29 15: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 15:41:36

- reply

Platinum-tier, white glove Nostr developer support.

2024-08-29 02:16:41

- reply

Say more about pluggable events 👀

2024-08-28 23:02:41

- reply

That would be a real value-added.

2024-08-28 22: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 22:29:06

- reply

Possibly, especially if indices reference external URLs.

2024-08-27 23:40:54

- reply

2024-08-27 22: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 21:49:36

- reply

Tell me more?

2024-08-27 19: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 19:09:35

- reply

We love that too! 🚀

2024-08-27 18: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 17: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 16: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 16:40:42

- reply

What is Gemini?

2024-08-27 16: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 16: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 15: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 15: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 15:11:05

- reply

I am! 🫂

2024-08-26 23: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 20: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 20: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.

2024-08-26 20:26:37

- reply

That's a perspective I have not heard before.
Of course, it must be mentioned here that the Founders did not exactly intend a standing army, either. Instead of a professional army, a militia would be responsible for defense.
We've obviously departed a long way from that, and this departure certainly colors more recent discussions on the Second Amendment.

2024-08-26 19:05:56

- reply

Glad to see you back on Nostr!

2024-08-26 15:53:26

- reply

Same with Marvel. Having multiple new shows per year is obviously too much.
It seems the pace that prevents fatigue is to have only one big event going on at a time. One big movie every year or two, an ongoing show to keep people interested and keep discussions going.
And they'd better be at least halfway good.

2024-08-26 14:17:52

- reply

This would suggest that we should pay close attention to the companies that are seeking income sources. Alby is an example. If they can make money from their service, they're likely to succeed.

2024-08-26 06:22:55

- reply

Much of it dates back to the era of Jim Crow laws, by my understanding.
A friend told me that some old Houston HOAs still have regulations on the books forbidding black people from living in the neighborhood (though they're not enforced).
Most new developments, especially since the early 2000s, are instituted with an HOA when the homes are first built. The theory is that they'll help preserve home value in those developments. Anyone who buys into such a neighborhood is forced to abide by HOA rules.
Most of the more affordable homes in growing cities, then, are in HOA neighborhoods, since established neighborhoods that predate the rise of HOAs tend to be closer to city centers and thus more expensive just by virtue of location.

2024-08-26 06:07:04

- reply

HOAs have a reputation for being full of petty tyrants. They often have very specific lists of what kinds of plants and animals you can and cannot have, they insist your house must be painted one of a few approved colors, they extract often absurdly high fees with little to show for them, and when you violate one of their dictats they send passive-aggressive letters and slap you with a fine.
Allegedly it is to keep property value higher, but that is dubious.
When we bought our house one of our priorities was to avoid HOAs. My wife wants to grow an extensive garden, replant the yard with native grasses and shrubs, and raise backyard chickens or quail. Many of those things are not allowed by most HOAs.

2024-08-26 02:52:47

- reply

But see, we're pitting the bureaucrats against the bureaucrats 😆