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

nprofile1qqsph70j88w2zcmpfx7z707rxsrh462ea2tq0jk0j300379myf7utcgpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq37amnwvaz7tmpw3kxzuewdehhxarj9ekxzmny9a5kuan0d93k2ucexuufk

Publishing to

relay.damus.io

atlas.nostr.land/invoices

nos.lol

Author Public Key

npub1r0ulywwu593kzjdu9uluxdq80t54n65kql9vl9z7lrutkgnachssk7zzyc

Show more details

Last Notes

2024-09-17 22:25:14

- reply

Was looking for this the other day but couldn't find it via search, strange. 🤷‍♂️

2024-09-17 17:35:50

Also just noticed zap reciepts/notifications are having intermittent issues. They are usually from "unknown" pubkeys, they don't have follows or followers and are without a subscription to paid relays. 🤷‍♂️

2024-09-17 16:53:19

I've realized in Amethyst, in the general relays settings, you don't need to completely remove a relay from the list to stop incoming spam from it, you can just turn off all of the Home, DM, Global and Search icons.

2024-09-17 16:40:42

Something that could be useful for paid relays to provide is negentropy syncing between relays for the follow list of subscribers, with configurable depths. Also, calculating how much storage space and bandwidth are being used on behalf of a subscriber and having having rates per GB or similar (the could also extend into media storage, images, video and audio).

2024-09-16 19:56:34

- reply

You can open in Inkscape and then export/save it as an EPS or PDF, and adjust the Document Properties (in the File Menu) to be the size that you want.

2024-09-16 19:04:42

- reply

Removed all client side filters as well, still doing well. The solution to spam is simple.

2024-09-16 17:49:05

- reply

It's a vector, download the svg file.

2024-09-11 21:00:58

FULL SEND 🤘
https://image.nostr.build/f287ec88cc36d1c8c500ce6c5b23ffb8264bad628cc54b6ab966594a6cd7a280.jpg

2024-09-07 15:49:04

I've moved almost all applications to be installed via Obtainium instead of Aurora Store (Google Play) and have removed F-Driod (although many Obtainium apps pull from the repository still). Down from five installer apps to four, it's not much, but it's a step.

2024-09-07 00:49:21

- reply

Didn't know there was this feature.

2024-09-07 00:47:08

- reply

Sounds like it's from Anatomy of the State.

2024-09-06 22:02:39

- reply

Invites, paid, to relays and suggested follow lists? This is more on the client though.

2024-09-06 21:04:01

- reply

Amethyst will still show the count and they could be filtered from reports from those you follow.

2024-09-06 20:45:05

- reply

A cool feature of using `git` for dependencies is that you can verify signatures of the commits when pulling them into a project.

2024-09-06 17:38:51

- reply

Was just looking at using NIP44 for private data in events, as this NIP describes. Could be a good option.

2024-09-06 17:15:10

- reply

This could be an interesting feature for a local relay like Citrine @nprofile…fpck for caching purposes — notes would load very quick and would save bandwidth too.

2024-09-06 16:01:22

If you're setting up a private Nostr relay with strfry, you can use this small plugin to only provide write capabilities for your own pubkeys.
https://github.com/braydonf/strfry-writepolicy
It uses the strfrui library that can do a lot more if that is needed.
https://github.com/jiftechnify/strfrui

2024-09-06 14:54:01

Good morning, from wss://relay.braydon.com 👋☀️

2024-09-06 07:17:18

GN, from wss://relay.braydon.com

2024-09-06 00:49:26

Could be a good option to support .onion addresses by default.
#nevent1q…qegt

2024-09-05 15:00:19

@nprofile…k0h3 and @nprofile…pyug is there any documentation or how private zaps are implemented in Damus and Amethyst?

2024-09-05 14:58:12

GM ☀️. Working more on a key migration and revocation implementatiom today.

2024-09-04 18:35:36

- reply

Hmmm... yeah, it's not displayed on the website 🤔, it is on the podcast feed though.
On Podcast Index:
https://podcastindex.org/podcast/531078
Direct RSS:
https://parallelsociety.libsyn.com/rss

2024-09-04 15:11:24

Just finished reading "A Lodging of Wayfaring Men" by Paul Rosenberg and highly recommend it!
https://freemansperspective.com/wp-content/uploads/2020/12/ALOWM_cover_image.png
You can purchase the book at:
https://freemansperspective.com/product/a-lodging-of-wayfaring-men/
And, yup, bitcoin lightning payments are supported!
There is also an audiobook by @nprofile…y22c available on this podcast:
https://freemansperspective.com/podcast/

2024-09-04 05:21:36

https://www.rfc-editor.org/rfc/rfc2119

2024-09-04 04:38:33

Just set this up with Citrine.
#nevent1q…vtrx

2024-09-04 01:33:13

Finished the first round of the Recover Key Setup event test vectors.
https://github.com/braydonf/go-nostr/tree/4cdba67d768bc7d7ce9449258da10cad8d5f025a/nipxx
I will update the NIP to reflect any changes when there are more test vectors.
#nevent1q…u7wv

2024-09-03 16:40:28

Working today on implementing and defining the specifics for Nostr events in go-nostr for NIP Key Migration and Revocation.
https://github.com/braydonf/go-nostr/tree/key-migration-and-revocation
My goal is to have a set of test vectors available for implementations.

2024-09-03 14:12:53

- reply

Working on it! Draft is up:
https://github.com/braydonf/nips/blob/key-migration-and-revocation/xx.md
https://github.com/nostr-protocol/nips/pull/1452

2024-09-02 22:40:38

- reply

Closest that I know:
https://tropicsquare.com/product

2024-09-02 21:24:28

- reply

The ping is similar with VPNs and a SSH reverse tunnel, the bandwidth might be better though.

2024-09-02 21:13:46

- reply

It'll probably be most apparent with streaming video, loading images and etc. Otherwise delays wouldn't be that perceived, as there wouldn't usually be a comparison.

2024-09-02 19:48:53

- reply

Perhaps https://gitworkshop.dev and NIP-34?

2024-09-02 19:20:30

- reply

I've been thinking about this and have been sketching UX ideas on how this could be done on nostr. Will post more when I have something ready. Moving towards git repos on nostr, with issues, I think is a part of it.

2024-09-02 19:11:28

I think this type of thing is very important!
A software economy is a different than an economy of products manufactured, distributed and purchased at a store.
Software is mostly zero cost to replicate and not scarce, time for development on the otherhand is scarce and benefits from being able to determine where time is valued the most.
Software development is a service, buying software is about the next marginal unit that doesn't yet exist. People will value it very differently.
#nevent1q…mt48

2024-08-30 21:40:07

Favorite quote of the day:
"Not your relay, not your data."
— @nprofile…pyug

2024-08-30 21:34:33

It's wild to see folks on GH claiming Nostr isn't a censorship resistant protocol!
If it's not, what is the point of any of this!? 🤦‍♂️
I think we need a GH replacement sooner rather than later.

2024-08-30 21:16:52

Looking forward to testing out a @nprofile…ntld device! ☀️

2024-08-30 19:03:17

Starting to implement Nostr Key Migration and Revocation! Feels good to be back at coding.

2024-08-29 17:10:58

If anyone is interested in helping to implement this in several clients and relays to flush out the details of the specification, please reach out to me! Thanks!
#nevent1q…7z7c

2024-08-29 16:48:42

GM. The pull request for Key Migration and Revocation is ready for review:
https://github.com/nostr-protocol/nips/pull/1452
Next step, I think is to look at implementing in several clients and relays and tuning the specification.

2024-08-29 15:13:52

- reply

Also wondering if Podcasting 2.0 w/ lightning can be compatible (sans RSS?). Perhaps something @nprofile…3623 and team are more familiar?

2024-08-29 15:09:46

- reply

Not sure either, perhaps there is a library for their use that could be reused.

2024-08-29 01:53:29

- reply

I wondered the same a bit ago and turned it off after learning of Nostr.

2024-08-29 01:48:52

- reply

Is there a specification for private follow lists, or another solution towards the same goal?

2024-08-28 23:11:02

- reply

Signals inteface for emojis and reactions I think is one of the better ones.

2024-08-28 23:01:59

- reply

More human art. Would not think glass would behave that way.

2024-08-28 22:58:20

- reply

In-app marketplace for media bloom servers, relays, shop profiles and etc I think would also help a lot for determining what services are desired, where and how.

2024-08-28 22:20:20

- reply

I don't know of one, strfry was the most simple, I found. I also needed to a write filter for it though.
I wrote a small one in Go based on a library for the purpose:
https://github.com/braydonf/strfry-writepolicy
I believe @nprofile…9929 has also written one, however can't find it now :(

2024-08-28 22:10:20

Yes, agreed.
#nevent1q…305j

2024-08-28 20:50:04

- reply

Just got Dichronauts by Greg Egan, looking forward to reading it.

2024-08-28 19:09:01

"Key Migration and Revocation" pull request is up!
https://github.com/nostr-protocol/nips/pull/1452
"This NIP defines the protocol that SHOULD be implemented by clients and relays to handle a key migration and revocation of a key. At a minimum this specification defines a protocol for a compromised private key to be revoked. Clients give warning that the key is compromised. Relays and clients delete events and reject future events from a revoked key. Also defined is a protocol to migrate to a new successor key with multiple optional methods for users of clients to verify and accept or reject the change. This includes methods such as: a social graph with attestations, recovery keys and side-channel identity anchors."
Read in full:
https://github.com/braydonf/nips/blob/3fffa43f0cc33421c76605bfe8beb406f567d3eb/xx.md
UX storyboards (PDF):
https://github.com/braydonf/nostr-key-migration-and-revocation/blob/7b542a07a4ab01f0784b6d58350b8bd4cc0a54ad/graphics/ux-storyboard.pdf?raw=true

2024-08-28 18:47:35

Finally at zero notifications on GH again.

2024-08-27 23:53:01

- reply

Okay cool.

2024-08-27 23:50:01

- reply

Wait... maybe they are.

2024-08-27 23:48:27

- reply

Still not working w/ ntfy.

2024-08-27 21:49:47

- reply

The attestations are similar to the Key Migration proposal by @nprofile…pyug

2024-08-27 21:44:20

- reply

Yup! It has many of the same elements. It has "whitelisting of a pubkey", however this is the " recovery key setup" and includes ability to use multiple keys (for `m` of `n` signatures) and does not need to be opentimestamped (though it is still an option). Instead social attestations are made.

2024-08-27 21:19:36

UX storyboards are now in sync with the specification for Nostr key migration and revocation.
NIP specification at:
https://github.com/braydonf/nostr-key-migration-and-revocation/tree/86f5b44145ad47d11e8777a28ccb35177b5a5a57
UX storyboards at (PDF):
https://github.com/braydonf/nostr-key-migration-and-revocation/raw/fe86c23e01c50aa80539d4f5f1e5d868fdb1e2ba/ux-storyboard.pdf

2024-08-27 00:07:55

Completed more of a NIP specification for key migration and revocation:
https://github.com/braydonf/nostr-key-change/blob/master/specification.md

2024-08-26 18:46:04

- reply

A relay could send it on request ONLY to the IP that created it, no?

2024-08-25 20:58:52

Started to draft a Nostr protocol specification for key changes and revocation.
https://github.com/braydonf/nostr-key-change/blob/master/specification.md

2024-08-25 17:12:11

- reply

Mayo is like this too, just because it says it made with olive oil doesn't mean it isn't ALSO made with canola or soybean oil. It's quite deceptive. Making it homemade with animal fats is surprisingly easy.

2024-08-25 15:33:40

- reply

A big issue with Nostr is that you can't, yet, switch keys. While preferrable for it to be a key, it's similar.

2024-08-25 04:19:35

When is the last time Telegram client code has had a security audit?
https://github.com/DrKLO/Telegram
Taking a quick look and two things stand out; committed binary library files and huge commits very much lacking commit notes and details, just version bumps.
Binary files could be deterministically built and compared to known hashes. Commits could include notes about the changes in smaller increments. It appears that many changes are made in private and then only pushed live at each release, lots of opportunity for underhanded coding.

2024-08-24 19:46:05

- reply

Why require a login and a wallet connection (currently only alby) to the Fanfares web app? It could be much more simple; send 2100 sats from any wallet and view/listen.

2024-08-24 17:28:13

If anyone else has or knows of a proposal for key migration, revocation and deletion please post a link! Thanks!
#nevent1q…qs6u

2024-08-24 16:35:02

@nprofile…8qkt @nprofile…pyug @nprofile…cy6q
I am taking a look at designing the UX for how clients can handle a compromised key gracefully; this includes key revocation, migration and deletion.
These are the proposals that I found that are related, are there any others that I should know?
https://github.com/nostr-protocol/nips/pull/829
https://github.com/nostr-protocol/nips/pull/637
https://github.com/nostr-protocol/nips/pull/1056
https://github.com/nostr-protocol/nips/pull/1256
https://github.com/nostr-protocol/nips/pull/377
https://github.com/nostr-protocol/nips/pull/1032
https://github.com/nostr-protocol/nips/pull/1335

2024-08-24 00:11:21

Finally switched to use Obtainium to install Amethyst. 💪

2024-08-23 22:05:49

- reply

Somewhat unfortunate... perhaps it will improve! More desktop options for Andriod apps would be great. Waydriod could be a good option until then!?

2024-08-23 21:31:43

- reply

I don't know if it because Kotlin Multiplatform is still somewhat new or something else, however building phoenixd (Kotlin Multiplatform) on Debian required some very specific versions of dependencies, so very few OS distributions will work.

2024-08-23 20:39:35

Starting to design a UX for a key recovery/change process for Nostr clients:
https://github.com/braydonf/nostr-key-change

2024-08-23 18:51:12

Happy Friday!

2024-08-23 18:51:02

Any engineers familiar with Kotlin able to give guidance or help with these changes to phoenixd?
https://github.com/ACINQ/phoenixd/discussions/55

2024-08-22 18:15:17

- reply

Zap for a magnet link!?

2024-08-22 17:54:37

- reply

Reading this book now :)

2024-08-22 15:05:08

- reply

If it happens again, I will check.

2024-08-22 02:33:27

Just watched this film!
#nevent1q…mjy2

2024-08-21 22:45:49

- reply

Nevermind! I built it again and now it is working!!! 🤷‍♂️

2024-08-21 18:28:34

@nprofile…9929 I am taking a look at Notedeck, I have the dev environment setup, compiled and when I run ./target/release/notedeck (with or without queries) nothing launches and the process exits with status 0.
This is on Debian 12 with Gnome 43, Wayland and virtualized with QEMU/KVM. Any ideas?

2024-08-20 18:16:07

With better HID devices and displays, gestures I think can more expressive and rich. Similar to keyboard-only text editing but for graphics, drafting, engineering and etc.
#nevent1q…k5hm

2024-08-20 18:12:15

What about Huion pen tablets?
#nevent1q…rlcn

2024-08-20 18:10:21

- reply

WiFi + Bluetooth + LoRa phone next?

2024-08-20 18:09:17

https://youtu.be/9M6zT0mRvW0

2024-08-20 14:57:57

- reply

*used

2024-08-20 14:54:17

- reply

Cool, so geohashes are uses so less precise location can be defined. A "place" could then be associated with a business profile?

2024-08-19 21:49:36

Anyone have much experience with Wacom Tablets (or similar stylus tablet) with Debian / Gnome or a similar distro? Any recommendations?

2024-08-19 18:21:22

- reply

Not sure how well gzip will compress filters, most cryptographic bytes do not compress well as they are usually high entropy.

2024-08-19 17:36:11

- reply

So, business profiles would include a location (and/or approx. location)? How would it work?

2024-08-19 17:31:10

- reply

Any other alternatives, golomb-coded sets (GCS)?

2024-08-19 17:17:53

- reply

Great, thanks!

2024-08-16 23:11:44

- reply

In no particular order, a few:
- Key setup more like a bitcoin wallet with a mnemonic phrase and a backup step, and a recovery process if that key were lost.
- Non-complicated and simple relay configuration, paired with an in-app marketplace for relays and other services that add clear value: long-term storage of notes, lightning/ecash wallet services, media and etc.
- Invitation system to bootstrap various suggested WoT for suggesting notes and profiles to follow. This could be topical relays!?
- An illustrated in-app explanation of why Nostr is awesome.

2024-08-16 22:58:52

- reply

The new nostrich experience I think could improve, a lot.

2024-08-16 22:52:23

- reply

*approximate location

2024-08-16 22:50:00

- reply

Yeah, a Nostr profile with an approximate tag of some sort could likely be enough with client support (perhaps in OPA) to use it for searching, businesses or otherwise.

2024-08-16 22:38:44

So apparently @nprofile…mwfv doesn't work with GrapheneOS w/o Google Play Services? The approximate location doesn't work, can it work without?

2024-08-16 21:23:26

I've cleared out all custom purpose relays in #Amethyst relay settings and just have a general relays now.
I run my own relay, I understand each section and the purpose, however it seems far too complicated and repetitive.
What's the goal and how can the UX be improved?

2024-08-16 21:09:12

Make Nostr Simple Again

2024-08-16 20:59:51

- reply

IDK, I think it has become far too complicated... 😐

2024-08-16 19:42:36

Looking forward to webapps being less common and Nostr based desktop and mobile applications being more common.