Braydon Fuller

Software Engineer • Bitcoin & Nostr • Economics • Security

"Do not give in to evil, but proceed ever more boldly against it." —Motto of Ludwig von Mises

Lightning self-custody with https://github.com/braydonf/satdress

Public Key

npub1r0ulywwu593kzjdu9uluxdq80t54n65kql9vl9z7lrutkgnachssk7zzyc

NIP-05 Address

_@braydon.com

NIP-57 Address

zap@lightning.braydon.com

Profile Code

nprofile1qqsph70j88w2zcmpfx7z707rxsrh462ea2tq0jk0j300379myf7utcgpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcpz9mhxue69uhkummnw3ezuamfdejj74668yf

Publishing to

relay.primal.net

nostr.wine

eden.nostr.land

Author Public Key

npub1r0ulywwu593kzjdu9uluxdq80t54n65kql9vl9z7lrutkgnachssk7zzyc

Show more details

Last Notes

2024-11-09 16:38:20

- reply

I think there may be a typo, *now available. Anyways, congrats!

2024-11-01 00:40:22

- reply

I think in a similar book Against Intellectual Monopoly (2008) they present the case that it's a customer <-> business dispute rather than a business <-> business dispute. So rather than a business suing for trademark violation, the customer would open a dispute with the business for deception, for making them think they were buying a different product.

2024-10-31 23:57:02

Happy Halloween! 👻

2024-10-31 23:17:56

- reply

Done this with microservices before, it can get so unnecessarily complicated and impossible. The phrase, "make it work, make it right, make it efficient" still holds IMO.

2024-10-31 21:16:48

- reply

Yeah, I think topic based relays, perhaps using an LLM to filter by relevant-ness through 3+ degrees into a social graph, will help with this. LLMs look to be fairly good at this from simple testing.
Topics like outdoors, food, sports, travel, economics and etc could be navigated pretty easily in an app. In-app configurability here I think will be interesting.
If someone is watching a sports game, they may want to have a feed that is filtered specifically for it being related to that game for example. The next day that feed won't be as relevant.

2024-10-31 13:03:14

- reply

Happy bitcoin whitepaper day!

2024-10-31 12:39:37

- reply

Follow up video:
https://youtube.com/watch?v=v7D_t3RW3M4

2024-10-31 12:31:35

This is 🔥
https://video.nostr.build/27566699bd639bde8876a720472e03d02548d3d3b13cea49fe68a0c97511530d.mp4
Video:
https://youtube.com/watch?v=Om4pEWnOTL8
#liondiet #carnivore

2024-10-30 23:31:35

- reply

Yup, I agree! The existing software is effectively a non-economic good and non-scarce, support on the other hand is still scarce.

2024-10-30 22:49:34

- reply

TBH, surprised it's lifetime, not membership by month or year.

2024-10-30 22:15:09

- reply

This seems more towards the fundraiser approach, similar to geyser.

2024-10-30 20:08:32

- reply

BTW, you're NIP-05 for some reason isn't validating in Amethyst. Maybe because of the redirect?

2024-10-30 19:38:01

- reply

Understandable. If I was implementing a Nostr app at this stage, I would probably include a signer app built-in for a mobile and desktop app (not for a web app) as the default. If there is an Andriod distro with Nostr support to replace Google Play Services, then it could be assumed available and no longer needed, but we're not there. A Nostr "web browser" could also be something that could have built-in Nostr support (no need for additional extensions) that could include a signer and other base features for Nostr apps.

2024-10-30 19:10:03

- reply

A few thoughts here:
While having more options is good, it can also increase the amount of time it will take to onboard. Take Hick's law: "...the time it takes for a person to make a decision as a result of the possible choices: increasing the number of choices will increase the decision time logarithmically. "
Furthermore, similar to microservice vs monolithic server architectures, debugging can become quite complex as the number of interconnected services increases. There can be a gain in modularity, however there is a tradeoff. Take the Linux kernel compared to something like GNU Hurd.
https://en.m.wikipedia.org/wiki/Hick's_law

2024-10-28 23:25:39

- reply

It's possible to add more pubkeys to a filter by breaking it up into seperate connections. I ran into a similar issue when trying to filter 2 degree follows (follows plus their follows) and would create a new stream when it reached the max. However, I'm not sure what clients are doing around this case.

2024-10-28 20:20:47

Recently released by the Mises Institute, "Playing with Fire: Money, Banking, and the Federal Reserve":
https://video.nostr.build/6ebd6a776a62117b8c61b6dbfe51e9900c7e5bc38ca90578a902de189eee792b.mp4
Full Video:
https://youtube.com/watch?v=qeXxU8SDyAo

2024-10-25 21:11:18

- reply

The use case for it I think is limited to cases in which delegation is a need, for example for an organization with employees.
It being any kind of added safety or security, I think is a far stretch and confusing use of naming.
It's often custodial and by that nature already leaked; not your keys, not your profile. As for it being self-hosted, a simple signer app that isn't remotely accessible or managed has much less risk.

2024-10-25 20:54:37

- reply

Indeed, I've been thinking about how to achieve that. It should be fairly simple.
I see it in two parallel goals:
1. Ability to revoke a key. This will inform followers that a key can not be trusted anymore. This will not include any suggestion of the next key. As it has been compromised it would be useless anways.
2. Ability to confirm an identity through a social graph (e.g. people you know can help to verify that a profile is the authentic one). This will be useful for completely new users, as well as a user that has had a compromised key.

2024-10-25 17:26:40

- reply

Entering a private key into a web app is much less secure than a signer app or extension. However, a signer app still can have its issues, just less.
A few of the issues:
- Phishing attempts from similar looking domains.
- Hot loading code from a remote server, not signed releases from the maintainer.
- Encourages entering nsec somewhat carelessly into more than one web app. It could be entered into a clipboard, which as been another vector of attack.
- Users habits of this type of behavior from passwords on every other web app. Passwords can be reset via email resets, a private key can not be reset. It can thus not communicate the importance of it not leaking, and thus careless backups and storage.
None of that is good for non-technical users.

2024-10-25 17:06:32

- reply

Good move on the disclosure, difficult but necessary thing to do.

2024-10-25 17:03:11

- reply

Why have it even as an option?

2024-10-25 16:54:22

Do not enter your private key into a web app! Why are there Nostr apps that are doing this?
Second, a dependency supply chain attack could make even signer apps leak passwords.
#nevent1q…p2yu

2024-10-24 18:20:12

- reply

Possible it's closer than that.
Combination of GrapheneOS App Store + Zap Store, Amber, Pokey and perhaps some others and Google Play isn't needed at all and the whole sandbox system for Google Play Services can be deprecated. It's headache anyways.
With a hardware partner (perhaps a company like @nprofile…ntld) phones could be distributed with it.

2024-10-24 15:44:52

- reply

I think all this is headed into the direction of a Nostr Android distribution or even a GNU/Linux distro. 🤘

2024-10-24 15:38:44

- reply

Granted, I haven't done this in awhile so there may be better models available now.

2024-10-24 01:55:09

A fun thing to do is benchmark user interface efficiency for tasks (similar to code benchmarks). It can be useful for comparing the time between different tasks and adjusting the user interface based on user's priorities as well as for optimizing the time for frequent tasks.
Some of this is intuitive, however there are some useful models to calculate and compare times:
Hick's Law - The time a person takes to make a decision from multiple choices.
Fitts Law - The time to move (mouse or finger) to a target is expressed as a ratio between the distance to, and width of, the target.
GOMS - A method to compare efficiency of different interfaces using a standard set if times for each action.

2024-10-23 18:26:08

- reply

More precisely, access to a file. A file can be both a non-economic good, of which the quantity of it far exceeds any need for it, and an economic good through limited access.
Using non-free software to accomplish that I think is very deceptive and is another topic.

2024-10-23 17:11:56

If you haven't read Mikhaila's story on her health journey and the healing power of food, you probably should as similar issues can effect around 24% of the population.
https://liondiet.com/my-story/

2024-10-23 14:28:13

- reply

Yeah, what up with that?

2024-10-22 21:05:17

- reply

Most of these resturants or fast food places will give you a deal if you only order the patties.

2024-10-22 01:20:02

- reply

Fun idea.

2024-10-22 00:54:59

- reply

This is what Angel Studios has done. Much of the Tuttle Twins episodes have been "payed forward" and are now available to everyone on their website, however new episodes are for members only and people can voluntarily "pay it forward". This isn't with bitcoin payments yet, as that audience grows that will likely change.

2024-10-22 00:43:35

- reply

That seems incorrect. There are reasons someone may not want to share. It may provide a competitive advantage, even temporary. Value is entirely subjective.

2024-10-21 22:07:47

The first step I think towards solving the "key rotation" problem will be simply key revocation. No suggested next key to follow, no rotation, no migration. Just a simple event that says, this key is burned and can not be trusted.
The next step, or simultaneous step rather, I think will be a way to help authenticate identities starting from zero; no domains, DNS, other socials and etc. I think this can be done through a web-of-trust and through a new attestation event that duplicates the kind 0 meta data. Many people who initially joined Nostr came from Twitter and were able to verify who was who by posting their npubs there. I think the need for this will grow as more people join that were never on Twitter or some other social platform.

2024-10-21 19:11:37

- reply

Sounds good, I'm not sure what else.
@nprofile…deau this could be how to add additional relay based lists to Amethyst for the drop down on the Home feed view. This could also be in Gossip.

2024-10-21 15:56:33

- reply

Validation of a kind, based in the spec, by a relay makes sense in the same way that signatures are verified. The flexibility of what isn't verified can be something in the design of the spec.

2024-10-21 15:47:32

- reply

Kind 30002 could potentially work.
1. How to specify that these are relay view lists (for example that could be displayed with other lists like those of kind 30000) and not some other type of arbitrary relay list (not sure what else is using or will use this kind).
2. How to include params? In the relay URL, as another tag, encrypted with a shared key with the relay (for privacy)?
Perhaps @nprofile…nq40 may have some ideas.

2024-10-20 06:59:20

Perhaps this could be a new list type that defines a relay (or more) plus additional params?
A private list could just be a private relay that's configured with a set of pubkeys and pulls just those notes.
#nevent1q…u8m8

2024-10-20 06:31:38

- reply

Done.

2024-10-20 06:13:30

strfry 1.0.2 is released with new config options:
https://github.com/hoytech/strfry/releases/tag/1.0.2
I'll update https://github.com/braydonf/strfry-tools to use the new connectionTimeout option for the router soon here.

2024-10-20 00:20:31

- reply

Pretty good episode. Glad you found relief!

2024-10-18 22:38:36

- reply

Cool. I'm looking forward to clients supporting custom "lists" which each is just a relay. I'd like to do a topic based one that uses a relevancy metric using an LLM and pulls from thousands to hundreds of thousands of other relays via a 3+ deep social graph.

2024-10-17 16:41:44

- reply

Haha... interesting find. Probably a small bug with some code that will omit empty lists and the encrypted list "appears" empty.

2024-10-17 03:55:32

- reply

Perhaps with "transfer keys" that could be associated with a profile (and attested to by peers) and later used to send a multisig transfer event should that pubkey become revoked.

2024-10-15 22:43:45

- reply

Thanks for organizing it!

2024-10-15 22:42:53

- reply

This is awesome.

2024-10-15 22:25:15

Okay, Organic Maps is pretty good. Used it for navigating (even without cell service). No need for Google Play services (or compatible layer, or sandboxed). I think this is a win!
Now I want to add more layers and customizations. This will do for now though.

2024-10-15 01:09:56

- reply

Negentropy (drafted as NIP-77) a way for relays to more efficiently sync notes between each other by determining what each relay has prior, and then only sending this missing notes.
So if you move relays from A to B, all your notes will follow that change. For example, if you decide a year from now you want to run your own relay, you can use it to sync all your notes from other relays to it.
It could also be useful to create topic based relays that sync with thousands, hundreds of thousands to millions of relays. It could then use an LLM to filter notes based on a topic.
It's robustness and efficiency.

2024-10-14 23:32:10

- reply

Yeah, 69% are not very much to none at all.

2024-10-14 23:19:32

- reply

Yup, I think this would be useful for organizations and businesses. There could be a queue of pending notes and etc.

2024-10-14 23:09:58

- reply

At some point I want to experiment with a Nostr relay that pulls in events from contacts 3+ degrees deep into a social graph of a set of pubkeys in a topic area. Then use an LLM (or other type model) to filter based on relevancy of a topic, it could potentially also be useful for search. One step at a time. 😅

2024-10-14 21:10:14

- reply

I've found that relay.westernbtc.com is one that supports negentropy syncing that is good to add. Several people use nostr.wine however they don't yet support negentropy syncing; looking forward to more options. Running one on your own hardware is also another good option, Start9 and Umbrel may have some options for running a strfry relay via it, however I am less familiar with this area. I think relays will be developed a lot in the next year, along with simple hosting options for media and video streaming and etc.

2024-10-14 17:22:12

- reply

With multiple clients for different use cases (notes, git collaboration, video channels and podcasts), I do think it is more efficient for relays to do more of the work that a client might do, such as streaming and syncing all the events that one will need. A global view wouldn't be so much global as it is relative to a relay's configuration, perhaps another term could be used. Each client need not implement the full complexity of coordinating with thousands of different relays, when that can be done once with a private relay and many clients can benefit.

2024-10-13 19:12:12

- reply

Cool. I also added that regexp to Version String Extraction and $2 as the match group. Gives a version number instead of the hash.

2024-10-13 18:33:36

- reply

Yeah

2024-10-13 17:53:34

- reply

Yup.

2024-10-13 17:53:03

- reply

Ah. Okay cool. Finally got this working.
Using the source url:
https://www.torproject.org/download
And adding a custom APK Link Filter with a regexp:
(.*)\-arch\-(.*).apk$
Replacing arch with the available options: aarch64, arm, x86_64 or x86.

2024-10-13 17:25:13

- reply

What App Source URL do you use?

2024-10-11 23:43:36

- reply

Truth can be destablizing to a house build on a foundation of lies and deception

2024-10-11 22:06:01

- reply

Okay thanks. I haven't seen that many relays listed in kind 3 and haven't looked yet at nip-5 entries, but it could be worth it to at a minimum look and also search across other known relays as discovered. Simple awareness of missing NIP-65 relay meta may also help. Will dig more into this later.

2024-10-11 20:53:43

- reply

That's an issue regardless and is a censorship resistance problem. If time can delete, assuming you don't want it to, so can another way. Owning a relay, renting a relay or trusting someone else fixes it. Negentropy syncing also greatly helps. I don't see that being a fundamental issue.

2024-10-11 18:45:19

@nprofile…nq40 What's been your strategy for getting events for contacts that don't have NIP-65 listed relays?

2024-10-11 17:03:23

- reply

Been running this for more than 12 hours now. There is still a fair amount of work to be done.
Some contacts don't have a NIP-65 relay list defined, so notes are not pulled down for those yet. I'm not sure which specifically, but it could be useful to know what clients don't support listing them (at a minimum).
How many discovery relays are too many and which have the most current info? Should such a relay as this attempt to pull in as many NIP-65 and follow lists for 2+ degrees of follows?
Negentropy is useful to sync past events or what may have been missed while offline. There is support, however some contacts don't benefit from it yet as a relay that supports negentropy isn't listed yet.

2024-10-11 16:39:12

- reply

I've noticed that Gossip has made it an option the merge, pull down or push up the local version. None of that would be needed if each was its own event because it would continuously be merged without a conflict.

2024-10-11 16:31:16

When using multiple Nostr clients, wouldn't it make more sense for a "follow" to be its own event rather than editing one event with all follows listed. Multiple clients wouldn't conflict with each other and clobber the other because of stale information.

2024-10-11 01:01:44

- reply

I need to run strfry with a config option to increase the timeout for the router. This should be in the next release; however, I have code for it now here:
https://github.com/braydonf/strfry/tree/router-timeout
Some related issues:
https://github.com/hoytech/strfry/issues/45
https://github.com/hoytech/strfry/issues/127

2024-10-11 00:39:02

Okay, this is awesome. I have the "outbox model" working in #amethyst today.
It's using a topic relay that pulls down events for everyone that I follow.
It's using `strfry relay`, `strfry router` and `strfry sync` with negentropy. I have a set of tools to create the necessary config files.
It's very much a work-in-progress; however, I'm currently using it now for my relay and already I see notes coming in via it, so great to see.
The early code is here:
https://github.com/braydonf/strfry-tools
cc: @nprofile…vzaw

2024-10-10 21:24:52

- reply

I concur. I also accept sats instead of time.

2024-10-10 17:44:28

- reply

NaN?

2024-10-10 17:06:01

- reply

AOSP software distribution did many things well, dev signing APKs was a good move. Having an app with a dependency of another on the other hand, is something every GNU/Linux distro has done so much better. In my opinion, some of the Nostr functionality should be much closer to the OS, and a Nostr distribution of AOSP (like a fork of GrapheneOS) will be an inevitable solution.

2024-10-10 16:31:01

- reply

Indeed, just finished reading it, and recommend it. Will have to listen too sometime.

2024-10-08 20:36:23

- reply

The hamburger patty "hack" is funny, but works.

2024-10-08 18:37:08

- reply

Could be, could not be. Reminds me of monolithic vs microkernel architecture arguments of kernels. Today both are used as well as hybrids. The monolithic Linux kernel has its advantages. Space for all approaches.

2024-10-08 17:42:25

- reply

By the way, I'm planning to work on implementing these ideas soon after I finish some work on strfry tooling. However, I wanted to get them documented early (for discussion, improvements and etc.)

2024-10-08 17:17:30

From "The Allegory of the Swamp" Appendix A of "A Lodging of Wayfaring Men":
"No, to get out of this, we will have to fly in defiance of our feelings, and think. The truth is that most people will do almost anything rather than this."

2024-10-08 16:49:15

Engineers working on what they think, or their customers think, is important while others disagree with them, who are not their customers or manager, is what makes Nostr great. Value is ordinal and not cardinal and determined at the margin. Carry on!

2024-10-08 03:50:04

From "The Allegory of the Swap" Appendix A of "A Lodging of Wayfaring Men":
"No, to get out of this, we will have to fly in defiance of our feelings, and think. The truth is that most people will do almost anything rather than this."

2024-10-07 23:59:26

I want to briefly go over some great UI features of a few clients that help confirm identities and how I think it can improve.
1. Amethyst and Gossip both include an icon on the top right of the pfp to show that you follow that profile. With some exceptions, this helps identify profiles and which ones are honest and which are impostors.
2. Gossip also includes a number on the bottom right of the pfp to show how "connected" you are to the profile. This represents how many of your follows also follow the profile.
So in what scenarios do these features not provide help?
A. If the profile (maliciously or otherwise) changes their name, pfp, bio and etc (kind 0), it'll be difficult to know which one of your follows/contacts it was when you initially followed them. This could be used to impostor someone that could look "verified". A compromised private key is not a part of this attack and hardware signing or multi-sig will not help. Note also that Gossip does have a feature to enter a "pet-name" (I'm assuming this goes into the `kind 3` NIP-02 follow list) and this could be useful to help mitigate.
B. If the private key of a profile is compromised (similar to A) all metadata can change. If notes (`kind 1`) start to appear from this profile that the private key has has been leaked; it will be difficult to recover and determine honesty and the original profile. For example, the Nostr Address (NIP-05) could have changed to the attacker's instead.
C. If you're not following someone yet still want to be able to verify them, the followed mark will not help. However in the case of Gossip, displaying the "connected-ness" could help in this scenario.
How can all these scenarios be mitigated?
By having different levels of profile confirmation, starting with the least to the most:
Level 1. Display "verified-ness" (or "connected-ness" as is current in Gossip) of the profile, this could be an icon on the pfp, however the exact number isn't as important as the names of the people that follow. For example displaying "Murray N. Rothbard" verified "Ludwig von Mises" has different value than "John Maynard Keynes" verified "Ludwig von Mises". This information could be displayed on the profile view. Level 1 will help scenario C.
Level 2. Display if you follow the profile, at this point displaying Level 1 is less relevant now. This could also be an icon on the pfp and could replace Level 1. Note that having an option to jump all the way to Level 3 could be a UX efficiency improvement when a profile is followed.
Level 3. Display if you have verified the profile. This will help scenarios A, B and C. The verified profile metadata will be duplicated and self-signed (either private or public). This could also be an icon on the pfp and could replace Level 2 and 1. Displaying that you've verified this profile on the profile view will also be helpful to provide clarity (including the specifics).
Here is a possible UX implementation for profile verification (wire-frame animation):
https://raw.githubusercontent.com/braydonf/nostr-key-migration-and-revocation/89a9437e958f44bf748f145b85e603d83cf7ef2f/graphics/ux-storyboard-animation.webp
Here is the NIP proposal:
https://github.com/nostr-protocol/nips/pull/1499

2024-10-07 21:31:58

The strfry websocket library is using an event loop with libuv, I'm a fan, good stuff!
https://github.com/hoytech/uWebSockets/blob/master/src/Libuv.h

2024-10-07 16:50:49

This is great info! The fat:protein ratio especially as well as including bone broth and etc.
#nevent1q…c89t

2024-10-07 15:39:28

- reply

Cool, are you using negentropy at all yet? Code for this available any place?

2024-10-07 14:34:30

Key revocation and rotation is a solvable problem and is ultimately about authentication, regardless if a key is ever compromised!
How do you know who is who? Do you remember their npub? Where do you save the name you have for their npub? Right now it is all just a list of pubkeys in a follow list (mostly).
#nevent1q…xsmw

2024-10-07 14:21:12

- reply

I disagree! Key revocation and migration is a solvable problem!
https://github.com/nostr-protocol/nips/pull/1452
https://github.com/nostr-protocol/nips/pull/1499

2024-10-07 13:53:48

- reply

Awesome! What type of course work, books and study guides are you using? The Mi Primer Bitcoin workbooks?

2024-10-06 16:33:06

- reply

I've been thinking about integrating with my homepage with a profile view similar to njump.me and npub.pro for this purpose (among others).

2024-10-05 19:07:24

- reply

Yeah, weight fluctuates, a huge percentage of body mass is water. When I first started carnivore +/-, I didn't weigh myself for the first 90 days or think about portion control, just ate until I was full, and stuck with it for that commited time period. About a month or two in there were some days I hardly felt hungry and ate about once a day, not trying for fasting or anything. First thing I noticed was my pants not fitting that well and older shirts fitting again. I found it felt freeing to not think about it.

2024-10-05 17:30:15

- reply

Yeah, not much more than could be found via `kind 3` (follow list) and `kind 10002` (relay meta), that are known anyways.
Private lists may help also in that regard.
And yup, VPN, Tor, reverse proxies can all help with IP address tracking for the private relay and clients.

2024-10-05 16:00:46

- reply

Not really, that relay could be yours and could take care of that censorship resistance for you by connecting to other relays owned by your contacts (two way syncing and streaming). Ultimately, you only need to connect to it (redundancy would also help still though).

2024-10-05 15:00:14

- reply

Already planning to do this once I have my strfry relay syncing (down, up or both) and streaming (down, up or both) for all my contacts (NIP-02 `kind 2` and eventually other lists) from their NIP-65 listed relays.

2024-10-05 12:04:18

- reply

Yeah I agree, too early. Also, there's negentropy syncing and other optimizations / simplifications that can be done with relays.

2024-10-05 11:28:45

- reply

Right, however in my case, I noticed the relay was either a paid relay that we happen to share (single point of failure) or a wot relay that uses someone elses pubkey (not including my contacts, even if I'm in theirs) and will probably only store notes temporarily.
Yes that is part of it. With many different clients; short notes, git collaboration, long notes, video, audio, markets (desktop or mobile) and etc. (desktop or mobile), it could get quite complex for each separately to do all the heavy lifting of communicating with thousands of relays, etc. etc.

2024-10-04 23:49:44

- reply

A few things, however, it solves a problem I have now in Amethyst, which is that many notes are only "seen" by one or two relays (and without connecting to many more relays listed via NIP-65 for contacts).
Once complete, Amethyst connects to that private relay (and a few others) and it will stream and sync from many hundreds to thousands of relays. Much more than just a few as it is currently.

2024-10-04 15:41:29

- reply

For a relay that has your and your networks events with relay-to-relay network topology. I'm working on a tool for strfry that will use a configured pubkey to grab the `kind 3` (NIP-02) contact/follow list and then sync (with negentropy) and stream events for those contacts from their relays defined in `kind 10002` (NIP-65). I haven't added support for other lists other than `kind 3` yet, however it could easily. However, if the list is encrypted, then it wouldn't be able to do that.

2024-10-03 22:59:10

- reply

Another benefit of an "outbox model" is that it's asking only their relays about their notes (without auth) so still somewhat private.
Not entirely sure yet how to have a private relay fetch these without access to decrypt the list. Will have to think about this one, perhaps lists could be shared with other pubkeys.

2024-10-03 22:01:52

TIL that Gossip supports private lists and Amethyst supports viewing public lists (not private nor their creation).

2024-10-03 19:29:13

- reply

Yeah or send to a Nostr npub via DM (not NIP-04), email or PDF receipt to save (or similar).
Something that I've noticed some folks ( e.g. @nprofile…yfa4 ) will do for films purchased with sats, is to use a URL (Vimeo) and a password. So perhaps the encrypted URL can also include some additional meta data? And perhaps a clickable link and/or redirect!?
More integration with Nostr could also be interesting, a sort of receipts or paid stuff catalog kind. Could eventually integrate with Kodi, NewPipe, @nprofile…ntld devices for books and etc. And could also work with subscription services for relays, vpns and such.

2024-10-03 10:11:21

- reply

Worked w/ open wallet, cool.
One thing I'd suggest is that the URL that is unlocked could be more above "the fold" on mobile, as it's just on the edge and could be easy to not see it change after payment.

2024-10-03 03:55:08

- reply

That's awesome.

2024-10-03 03:54:50

- reply

Great to see :)

2024-10-03 03:39:09

- reply

What about kind 3 (follow/contact list), kind 10002 (relay list meta) and kind 0 (profile meta) or is that assumed?