yonson
Nick

https://blog.yonson.dev

Public Key

npub1jy2pa43vcr3jkwny2f9edsx0cdavzkcwqcla4qqyf03y66nxlgrq3m9p6d

Profile Code

nprofile1qqsfz9q76ckvpcet8fj9yjukcr8ux7kptv8qv076sqzyhcjddfn05pspz4mhxue69uhk2er9dchxummnw3ezumrpdejqzrthwden5te0dehhxtnvdakqzyrhwden5te0dehhxarj9ekxzmnyqyg8wumn8ghj7mn0wd68ytnhd9hx2qg5waehxw309aex2mrp0yhxgctdw4eju6t0qyv8wumn8ghj7un9d3shjtnndehhyapwwdhkx6tpdsn58udr

Publishing to

Author Public Key

npub1jy2pa43vcr3jkwny2f9edsx0cdavzkcwqcla4qqyf03y66nxlgrq3m9p6d

Show more details

Last Notes

2026-07-30 22:52:04 UTC

Heads up mk3 owners: https://blog.coinkite.com/coldcard-mk3-seed-generation-warning/

2026-03-18 15:39:00 UTC

- reply

What almost destroyed it for me was the original author passed away before he finished the series (while I was on like book 7). But then the author of mistborn stepped in and actually stuck the landing pretty well all things considered.

2026-03-18 15:18:37 UTC

- reply

It ain’t perfect, but The Wheel of Time is still the GOAT for me.

2025-11-19 22:33:04 UTC

- reply

I added a self-signed, self-hosted url, hopefully works better for tor/vpn access: https://census.labs.yonson.dev

2025-11-18 15:35:09 UTC

- reply

Oh dang, that’s unfortunate. Thanks for the heads up. I’ll see if it’s a setting on the bucket and re-host if necessary.

2025-11-18 15:04:05 UTC

- reply

It’s just hosted on a GCP bucket so I assume so? I’ll try to kick it a bit later today to make sure not an issue on my end though. Let me know if you want me to add anything to it in the future though!

2025-11-12 15:12:52 UTC

- reply

Hmm, I’m not seeing the “spend bitcoin”. Maybe state dependent?

2025-11-04 14:55:11 UTC

@npub1art…m0w5 impressed by your patience

2025-10-23 19:47:45 UTC

- reply

https://github.com/TheCharlatan/kernel-node

2025-10-05 03:16:09 UTC

- reply

This flow works for the Q or mk4

2025-07-11 21:49:16 UTC

open water bitcoin

2025-07-07 23:15:21 UTC

- reply

Is this cause the socks connections don’t have to be encrypted or something?

2025-06-20 16:33:30 UTC

- reply

Ah ok, more to learn. I wasn’t aware v2 required new firmware.

2025-06-20 15:27:37 UTC

- reply

Why v1? Does it not make sense to use v2 if even just for the encryption?

2025-06-03 19:33:21 UTC

- reply

First time watching bluey with my kids now and wow the feels

2025-05-28 19:13:50 UTC

- reply

There are other impls, but the rust bitcoin guys generally want very few external dependencies. Plus this impls interface is kept small, just what the bitcoin use case requires.

2025-03-09 00:03:53 UTC

- reply

I gotta frame this

2025-02-27 18:22:23 UTC

- reply

Next up notedeck package 👀?

2025-02-12 17:32:00 UTC

- reply

Always panic a little when I see the block height represented as 3 bytes. What will we do in 300 years when I am long gone??

2025-02-01 21:12:06 UTC

- reply

Yea, just making sure I understand the problem. I agree in general that pow appears to still be lookin for a second use case.
I was thinking a user id (if one exists) would make a pow at least only useable for one user.

2025-02-01 18:09:10 UTC

- reply

If the PoW scheme requires the user to commit to some user id in the hash, would that satisfy specialization?

2025-02-01 17:47:32 UTC

- reply

What’s wrong with PoW?

2025-01-26 21:27:01 UTC

- reply

Been a bit since I looked into it, but I was thinking of these expansion ports which all go to usbc instead of being like, directly connected to a motherboard (I assume, not actually sure if that’s right): https://frame.work/marketplace/expansion-cards

2025-01-26 19:57:46 UTC

- reply

What’s it like having all the peripheral dongle things going over usb 3? Seemed like a headache for some things I take for granted to just work these days

2025-01-24 20:21:48 UTC

- reply

I am getting the “does not exist” error as well, I am nyonson:matrix.org if I can be added

2025-01-18 15:29:04 UTC

- reply

I avoided hm for as long as I could too. It still feels very heavy, but has iron’d out a few quirks like this.

2025-01-18 15:10:07 UTC

- reply

Yea, I am running Wayland too and had to add some settings in home manager for my cursor. Only issue I still have with gossip is the scrolling feels very different than my other apps. But hard to track down why.

2025-01-18 05:58:36 UTC

- reply

Tried to capture a history of the proposals for it cause curious why it seems to have stalled: https://blog.yonson.dev/log/2025-01-vol1/
Could see it having some tricky UI issues though for something like chat use cases.

2025-01-18 05:41:43 UTC

- reply

Are you using the unstable channel? SDL2 stuff was cleared up for me with this tweak to the package: https://github.com/NixOS/nixpkgs/commit/db6be866d53a65f0081792b05cb37c2a21e5ef89

2025-01-15 19:48:22 UTC

Trying to recap the history of nostr proposals for onion routing to preserve network metadata privacy: https://blog.yonson.dev/log/2025-01-vol1/
Are there any current onion routing proposals using NIP-17? CC @npub1l2v…ajft and @npub1gcx…nj5z I believe I saw some rumbling from you guys in some deep comment threads.

2024-12-29 02:32:56 UTC

- reply

“OH…I can feel it.”

2024-12-16 03:57:42 UTC

- reply

Not sure I follow on the two receiving addresses. Wouldn’t we want two envelopes so it’s hard for outsiders to trace the path of the message?

2024-12-16 03:48:55 UTC

- reply

A built in nostr solution (ie a bunch of republishers) may lower the bar for more user usage. Also maybe better privacy if a republisher is popular? Versus just offloading trust to a proxy.

2024-12-15 21:42:21 UTC

@npub1h0u…rwx8 any thoughts on this simple onion routing proposal for nostr as an extra privacy layer? Feel like it could be useful for low bandwidth, but extra sensitive messages. Or is something like this already baked in? https://github.com/nostr-protocol/nips/issues/411

2024-12-05 16:29:20 UTC

- reply

Like an easier dbus?

2024-11-21 23:59:47 UTC

- reply

Maybe @npub1xts…kk5s knows? Any chance you think this would have a good enough value/cost for nostr?

2024-11-21 19:42:38 UTC

Has there been any consideration for #nostr relays to support some sort of compact filters like BIP157/158 style in order to preserve user privacy? Allow reading from a relay without disclosing exactly which events they are interested in.

2024-10-22 20:41:49 UTC

- reply

Epic.

2024-10-19 22:05:59 UTC

- reply

Very cool. Curious if this could be used as a payjoin v2 async communication channel, but would need to be able to have the read side too

2024-10-19 20:50:20 UTC

- reply

Do you think this could also support onion routed event reads?

2024-09-19 01:11:22 UTC

- reply

https://image.nostr.build/d98aeecff6b3fc0245ff462e59d42b5c42c378ac1fad688e8c403c5330aacdd6.jpg

2024-09-18 04:13:38 UTC

- reply

Nice, good enough for me!

2024-09-18 01:27:05 UTC

- reply

Seeing someone else wonder about this is pushing me to give up on the capitalized version

2024-08-21 04:46:42 UTC

Added a flake to my little liquidity management app if you are into that: https://github.com/nyonson/raiju

2024-07-04 18:07:35 UTC

- reply

Ah, totally missed the different requirements. Gotta dig into it more, thanks!

2024-07-04 17:47:19 UTC

- reply

Any thoughts on OHTTP vs. MASQUE? A quick reading of that paper and it kinda sounds like OHTTP is better in the NOSTR use case?

2024-04-09 17:33:05 UTC

- reply

Ah, the bip mentions Noise in its motivation: https://github.com/bitcoin/bips/blob/master/bip-0324.mediawiki#user-content-Rationale_and_References
I didn’t see authentication in Noise, but sounds like that’s a big part of it.

2024-04-09 15:01:46 UTC

- reply

Sounds a lot like BIP324. Is there a reason the bip didn’t just use this?

2024-01-02 21:28:22 UTC

Did a little deep dive on OP_RETURN, ordinals, and STAMPS: https://blog.yonson.dev/log/2024-01-vol1/

2023-12-04 00:40:38 UTC

Why do a lot of nostr web clients in the wild register to the “web+nostr:” scheme instead of the nip-21 “nostr:”?

2023-04-09 00:04:57 UTC

- reply

Hackers 5 times