hzrd149

> first app installed wins
Didn't know that, and that kind of sucks. it means I would have to specifically add support for each signer, and use a hard-coded URL that will go offline in the future...
I'm glad your building this and not me, I don't think I could put of with apples innovations

2026-05-06 20:49:54 CEST

- reply

I saw this and it took me a few minutes to figure out why my wallet was trying to send 149 sats on-chain.

2026-05-06 06:22:44 CEST

- reply

I like the idea. And I did build full support for remote signers into applesauce, so maybe that would make it easier?
https://applesauce.build/creating/signers/nostr-connect.html
https://applesauce.build/examples/#/example/signers/bunker

2026-05-06 06:15:36 CEST

Great listen, I recomend it if you still haven't heard about FIPS
#nevent1q…4p7n

2026-05-05 20:38:38 CEST

- reply

I need to look into that. apparently the small AI model its using can be run in the browser

2026-05-05 19:10:16 CEST

- reply

I'm not even sure how to type an emdash, my keyboard does not have a key for them.

2026-05-05 18:57:33 CEST

Mute the emdash "—" character and never see bots again, your welcome :)

2026-05-01 22:41:06 CEST

- reply

What is this a map of?

2026-05-01 21:27:11 CEST

- reply

"Press up on your remote to shop"??? Can you buy stuff from your TV now? That's seems almost more ridiculous

2026-05-01 19:45:07 CEST

Its possible to add a search input to your notifications / mentions if your inbox relays support NIP-50. very useful when trying to find that one thing someone talked about and tagged you on
https://cdn.hzrd149.com/fb700c934fbd69ea50455b0f9970e374f408aa6a3f4b589a2c6804c82b3f8230.webp

2026-05-01 19:22:44 CEST

- reply

awesome :)

2026-05-01 19:22:19 CEST

- reply

On and off. I'm mostly trying to keep it maintained and updated but not really adding new features
https://github.com/hzrd149/nostrudel/pull/351

2026-05-01 19:20:07 CEST

- reply

noStrudel also cant display it, but it does support linking to another app that does 😁
https://cdn.hzrd149.com/66c15934666e85eefd76aa0adb7c90ecee49fb7ee8629999193772fa55b6d1c0.webp

2026-05-01 19:18:57 CEST

- reply

Does it offer any options to open it in other apps? It should show a link to gitworkshop.dev that knows how to handle these events
@npub1utx…50e8 NIP-89 support when?

2026-05-01 19:12:55 CEST

Testing linking to a git repo
#naddr1qv…xyl8

2026-05-01 15:42:57 CEST

- reply

I hope we can avoid making the same mistakes that protocols before had

2026-05-01 01:46:35 CEST

- reply

This makes me sad I didn't go, would have loved to meet you guys in person. Also @npub16dh…0nkq nice shirt 😉

2026-04-30 23:15:51 CEST

my gitworkshop.dev page is looking more complete :)
https://cdn.hzrd149.com/57bd0f23edfb613c28e29f275f24f3398bd0a3ffcae6d3bcde8e051d176194b2.webp

2026-04-30 22:59:38 CEST

- reply

This is what blossom has been needing for a long time. a way to test all the implementations and a report that can easily be copied into an agent to start fixing

2026-04-30 21:03:15 CEST

Built three more examples in #applesauce to test out the NIP-34 support 😀
I'm probably wasting time but its been fun to go down the list of NIPs and add support for them into applesauce. It also allows me to find edge cases can things the library cant handle well
https://cdn.hzrd149.com/2a7f295c3e85f99b6f63baae579c73825c50742428411676e0efe7ba32073599.webp https://cdn.hzrd149.com/21f723ce6c017e0b3bf03ef330a4c3486828676fbc57bee54b94710c65934a02.webp https://cdn.hzrd149.com/a4a92bb37e91854edd41682f892879491217d9e6135ccead38f879c99cf1ed3d.webp

2026-04-30 19:34:34 CEST

- reply

All nsites should be hosted at the root path ( unlike github pages ) so you wont need to update the base path for vite. and if you want to change the nsite from a root site to a named site you only have to clone the event, change the kind and add a "d" tag

2026-04-30 19:18:37 CEST

Really great NIP-29 client. and the best part is it does not spam me with signing requests 😀
#nevent1q…ee0g

2026-04-30 19:11:37 CEST

NIP-05 identifiers in NIP-34 nostr git URLs was a bad idea. how am I supposed to parse the URL when it requires me to make a network request. that or I now have to make my whole app consider arbitrary NIP-05 ids as valid user identifiers

2026-04-29 23:37:03 CEST

- reply

Happy to make a PR for this if you can point me to the source code :)

2026-04-29 23:36:24 CEST

- reply

One small issue... This is what my computer looks like after I login, I know nostr login might not be the primary focus. but please tell someone to turn down the DM decryption. or at least wait till I click on the DM tab to start decrypting
https://cdn.hzrd149.com/38f108587c4960a8229ee2b344adaa9cfafaa02a4b0894baa67cff009b991603.webp

2026-04-28 20:46:24 CEST

- reply

Both are the same, basically just nsite: + <nsite address> + URL path
I guess it would basically just be like an nsite gateway URL but replace the https:// with nsite: and drop drop domain name of the gateway

2026-04-28 20:36:45 CEST

- reply

hmm, so something like
nsite:2zrgjemvgxppn2jwgm61w6yrqqlcmm8njvhby68a9cj7ooo5phditto/index.html
or
nsite:npub1c2dqhzgsxhnsvtyj3qcvc4nzfxjafksn48q3hul9gl8fskr44kksksdm94.nsite.lol/
Could be useful. 🤔

2026-04-28 20:00:29 CEST

Decent talks so far
#naddr1qv…79da

2026-04-27 19:54:52 CEST

- reply

Ho9w does this handle needing to remap the base URL to /<repo name>?
Thats always be the issue for me, when building apps I have to have two build, one for nsite ( root path ) and another for GH pages ( base path )

2026-04-27 18:08:54 CEST

Fancy zap modal using applesauce, It supports connecting a NWC wallet on the LN payment page
https://applesauce.build/examples/#/example/zap/zap-modal
If your using applesauce in your app it should be enough to copy the code and tell your agent to update or add the zap modal into your app :)

2026-04-26 14:11:50 CEST

- reply

Please keep us posted what you work on. Even if your not working on Nostr stuff I still want to read about it.

2026-04-26 14:09:01 CEST

- reply

nsite are pretty decentralized. The sites metadata (file map) is stored on Nostr relays and the files are stored on the users blossom servers. So in theory this nsite is stored in 2-5 places.
Using curl -> Firefox on noStrudel or any other website / app won't work because your only downloading the html page, it's missing all the other JavaScript and CSS files

2026-04-25 22:08:48 CEST

Opened by first PR to a project using ngit ( git nostr )
https://gitworkshop.dev/npub15qydau2hjma6ngxkl2cyar74wzyjshvl65za5k5rl69264ar2exs5cyejr/gitnostr.com/gitworkshop/prs/nevent1qyf8wumn8ghj7emfw3hx7um5wghxxmmdqqsrhmlhhl6x346vutt8953dd64e4xfpct948sdhja4ee0xqvsrqr8gt9jd0k
I'm not really sure what I did but it was pretty easy using the ngit cli

2026-04-25 19:09:25 CEST

- reply

One small complaint. the text in the UI tends to get really small and seems to be all different sizes.
I'm guessing this is from claude bad habit of always setting text-xs classes on everything

2026-04-25 19:03:39 CEST

Finally a good homepage i can bookmark and use to watch for new issues and PRs
https://cdn.hzrd149.com/df98d1c9d1801cefd25d2f593dc9c07dad81693f352d879a9aa0273a576fb254.webp
#nevent1q…gs5y

2026-04-25 00:15:57 CEST

Why don't we have a bitcoin price NIP for nostr yet? wouldn't be too difficult to setup, you would just need a live replaceable even for current data and then delta events for historical. similar to what NIp-66 does but instead of tracking relays you track prices of asset A -> asset B

2026-04-25 00:09:17 CEST

- reply

Any idea how we could actually support native ETH zaps?... asking for a friend

2026-04-24 21:30:49 CEST

Already liking it in noStrudel, I also like how it shows what the 1 sat zaps are worth ( $0.00 ) 😁
https://cdn.hzrd149.com/ef84319b00a4c560502f936f41782e6b19524df2194e8fbd709f16d179c4230c.webp
#nevent1q…l5k7

2026-04-24 21:28:43 CEST

- reply

Might also make sense to add support for other crypto currencies...

2026-04-24 21:28:02 CEST

- reply

You don't, but I think this helps the existing users a little. at least it shows the 1 sat zaps as $0.00

2026-04-24 21:10:54 CEST

Every Nostr client should support showing zaps in USD or any other currency. It's hard to describe but this feels good.
https://cdn.nostrcheck.me/50cbfcc88e4ea2e1b4cb73a0ae4f76ec43fe79bf5731057db8d25a2e5c897b39.webp

2026-04-24 20:59:57 CEST

- reply

I liked this feature, it was the simplest way to make an original feed. But I never figured out how to show it to the user or how to prompt them to pick another user who might have different interests

2026-04-24 02:30:31 CEST

- reply

Awesome. For a second I was worried you would be using the outdated spec.
I'm super excited about it now, is this written up anywhere or are you waiting to release it in vagas?

2026-04-23 19:17:03 CEST

Updating the nostr-social-graph example in #applesauce to support saving and loading the graph from storage. I also took the opportunity to add a "since" filter when syncing so that apps can only look for updated contact lists.
https://cdn.hzrd149.com/b66effe0b71038026a047daa67bada52e8443a3d6f5d63ec7f680982b08b8837.webm
All these examples are available in the MCP server or soon in an llms.txt on https://applesauce.build
My goal is to build lots of solid examples of common things nostr apps will need to implement, then when your vibe coding with applesauce your agent can go read working examples instead guessing how to implement something.
Thanks to @npub1g53…drvk for building the social graph library

2026-04-23 18:28:01 CEST

Today is one of those days I get distracted by optimizing something in applesauce and don't get anything else done... :(

2026-04-23 16:36:17 CEST

- reply

ah, so its talking to the device and app over serial. In that case what needed to be changed from the original Nostr Signing Device extension / protocol to get this to work?
Also if your intending this to be a first class feature of the passport prime then I would suggest we come up with a new signing protocol that isn't tied to an old ESP32 device.
I would love to have something that could work over bluetooth or USB so that (some) mobile web apps could talk to it.

2026-04-23 16:00:57 CEST

- reply

It should try the server hints in the URI first, should be a little faster and save a step

2026-04-23 00:48:12 CEST

- reply

took me a minute to realize that rake didn't have a pressure washer handle...

2026-04-23 00:13:26 CEST

- reply

Cant wait to see it. always makes me happy to see other devs use my libraries because it means Ill get bug reports :)

2026-04-23 00:11:38 CEST

- reply

Pushed a fix in v6.1.4
I'm guessing the server was not honoring the X-Forwarded-Proto headers from reverse proxies like nginx or caddy

2026-04-22 19:06:33 CEST

- reply

I demand to see the source code for that extension... So I can add official support for it in the app 😁
Also a little embarrassing that noStrudel doesn't have a loading state for when its waiting for a signature

2026-04-22 01:22:49 CEST

- reply

The URL is missing the file extension. It's not required for the blossom server to support it but it does make that URLs compatible with all Nostr clients :)
Also that's a cool logo

2026-04-21 23:04:16 CEST

- reply

This is probably the most difficult link for a nostr client to handle. A link to a video stream from multiple fallback servers 😁

2026-04-21 16:48:15 CEST

Testing HLS video inside a BUD-10 blossom URI
blossom:ce7cad1ad75f26b5ebbd72d1048cb627a1d34529a0eeea087454c96aad8fc3f4.m3u8?xs=cdn.hzrd149.com&as=266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5

2026-04-18 14:28:30 CEST

- reply

I copied nostr-tools and used a REQ with an impossible author's pubkey.
https://github.com/hzrd149/applesauce/blob/master/packages%2Frelay%2Fsrc%2Frelay.ts#L134-L137

2026-04-18 01:34:14 CEST

Running @npub1y0g…00ly http://fips.hzrd149.com/
No clue what I'm doing but I'll learn

2026-04-16 19:35:22 CEST

- reply

Do you have the source for this? and is it compatible with https://github.com/hzrd149/blossom/blob/master/implementations/hls-video-formatting.md

2026-04-16 19:06:14 CEST

Testing, please ignore. and yes I'm sharing a localhost URL, your client should know how to deal with it
http://localhost:3000/8e6fa6cfdf5cc1c265b74e03eb96737adf80b4e53e85ab486cdad6b5c9502503.jpg
blossom:a94b7005b2f6256e0335b0de05dd6a9ce771c1ac27018a9de2d169538710962d.jpg?xs=blossom.nogood.studio&as=55f04590674f3648f4cdc9dc8ce32da2a282074cd0b020596ee033d12d385185

2026-04-15 18:21:13 CEST

- reply

Its not connected to my local network, so its talking to my PC over Bluetooth

2026-04-15 17:34:30 CEST

And now I managed to make an HTTP request that goes from: my laptop -> LAN -> my PC -> UDP -> FIPS test gateway -> other nostrich's server.
Its not a direct connection, the HTTP request is getting routed through two other computers. This is crazy... 🤯
Unfortunately the BLE was too slow to support more than pings so
#nevent1q…9huc

2026-04-15 17:23:19 CEST

@npub1y0g…00ly blowing my mind right now. I'm pinging my offline laptop over BLE
https://cdn.hzrd149.com/9f4ddf98651dbec0feeaed88dfd2c5aece2d9100a424d6143b42a697a2205891.webp

2026-04-13 20:58:26 CEST

- reply

Not much. the ngit cli seems to work well enough for pushing and pulling code.
The main reason I don't use it is I cant use github as the "main" remote repo and then mirror it to the grasp servers. I run into issues with branches getting out of sync and there is no easy way to force push to the grasp servers in order to reset them

2026-04-13 20:14:04 CEST

- reply

I doubt it, maybe if they had a CLI it could figure it out but there is no way its going to figure this UI out

2026-04-13 17:01:05 CEST

ffs where is the merge request button on gitlab... I cant make a contribution to ditto because gitlabs UI has more drop down menus than excel

2026-04-12 19:39:39 CEST

Cleaning out my web bookmarks and I had so many old links to linux articles to remember how to set stuff up on a server... never going to need that again with AI, even local models can answer those questions now

2026-04-12 19:07:17 CEST

- reply

Love to see it

2026-04-12 00:50:07 CEST

Shilling my own PRs but I want some feedback https://cdn.hzrd149.com/6fbe563c634f7487ba30fd37544482bd8c5a6bf9aafde09f7384ba96067ef88d.webp
I've got five new PRs that cleanup some stuff and introduce some new things in blossom. no breaking changes but maybe some more complexity for clients.
Either way if you have ideas head over to https://github.com/hzrd149/blossom/pulls and add them or open a PR

2026-04-11 18:35:06 CEST

Also the /upload endpoint should really be a POST and not a PUT... I should have read the HTTP spec first I guess
#nevent1q…pytq

2026-04-11 18:30:04 CEST

Reading over section 9.6 of RFC 2616 I'm not sure why I didn't make the upload endpoint on blossom servers a `PUT /<sha256>` instead of a `PUT /upload`. it would make a lot more sense... 🤔
https://www.rfc-editor.org/rfc/rfc2616#section-9.6

2026-04-11 18:12:37 CEST

- reply

Its there but I'm unsure about merging it or making it part of the blossom spec. chunked files is something blossom needs but that PR still isn't as clear or simple as id like.
Its simple enough to have a list of chunks and concat them, but the tricky part is where to store them ( relays or not ) and whether blossom servers should resolve the chunked files or if the client should resolve them.

2026-04-11 18:07:36 CEST

- reply

For these gateways we need some kind of fun way to visualize the sites, or some way for users to explore a little. when you open then its kind of a dead end and you leave

2026-04-10 20:59:50 CEST

v6.1.0 of https://jsr.io/@hzrd149/blossom-server is published. No breaking changes but it has a lot more specific HTTP status codes based on https://github.com/hzrd149/blossom/pull/98
Appreciate feedback if anyone is running it, and feedback on the PR. Id like to get stricter HTTP status codes added to the Blossom spec so we can have better interoperability between servers.

2026-04-10 01:09:18 CEST

Great episode, and I love to hear what @npub1g53…drvk is working on. the hashtree stuff sounds like the second phase of blossom I've been waiting for, real chunked files and folders on blossom...
Although now I have a lot of homework to do before I can be sure.
#nevent1q…ez5y

2026-04-09 20:40:22 CEST

- reply

The root site ( kind 15128 ) is the site that gets updated whenever there is a new release. the historical versions are snapshots ( kind 5128 ) of the replaceable event.
All based on this PR so far https://github.com/nostr-protocol/nips/pull/2287

2026-04-09 16:11:26 CEST

Getting nostalgic while playing with older versions of #noStrudel
https://cdn.hzrd149.com/387876bd69121e397f7d079b895cc9149186bf0616ae50a23dc2a097c2027779.png
2 years of noStrudel versions are runnable as nsites
https://2tlb607yn9ai420jf20b3ge69so4zeoi0bmj6iri8u8n067hmgsites.nsite.lol/

2026-04-09 14:06:30 CEST

- reply

Now that it only takes a single event to publish a new static site. I think we are going to see a lot less monolithic Nostr apps :)

2026-04-08 19:35:50 CEST

- reply

What makes it functionally different than btc.us and ENS? From what I read it looks like its just names on a blockchain

2026-04-08 19:19:46 CEST

Went back and compiled a bunch of the old #noStrudel versions and published them as nsite snapshots to test out my ideas in https://github.com/nostr-protocol/nips/pull/2287
So if you enjoyed old versions of noStrudel you can find them here for now. although be warned, most of them default to loading global which has a lot of spam...
https://nsite.lol/status/npub1wyuh3scfgzqmxn709a2fzuemps389rxnk7nfgege6s847zze3tuqfl87ez

2026-04-06 19:47:23 CEST

Still love the mini nsite list app that @npub1uac…99rx created that I stole. super easy to find all my nsites I've deployed
https://0ygl461f4ecz5thkn8eksa36nepjpij86s83ti8yzokopd3ag5nsites.nsite.lol/

2026-04-06 19:10:54 CEST

Very happy with https://sw.kovidgoyal.net/kitty/
Tab and windowing shortcuts are easy to learn and it lets me resize the panels using the mouse 😁
https://cdn.hzrd149.com/6ba9922a9b468faa9abcc54912f882c459657226855b92af33c68facc6b56d39.webp

2026-04-06 18:48:10 CEST

- reply

thanks for the links. and I was actually listing to that podcast now :)

2026-04-06 18:27:54 CEST

This will also help agents write clients and servers for blossom. The more I've been working with agents the more I'm realizing that trying to publish libraries and package to help them work with a spec or protocol is the wrong way.
Its better to make the protocol very explicit and detailed so they can just implement the part they need. hopefully with less code then pulling in a full library.
#nevent1q…wlt2

2026-04-06 18:25:52 CEST

Taking full advantage of HTTP status codes https://github.com/hzrd149/blossom/pull/98
The idea is to define all the common HTTP status codes and how they relate to blossom endpoints. This has kind of been an unspoken rule for too long that clients and servers should follow HTTP but its much better to actually define it in the blossom spec.
#asknostr I would appropriate lots of feedback on this since its a big change. although its not a breaking change

2026-04-06 17:11:47 CEST

@npub1equ…hkj6 you need to include some kind of git link or something is your profile. I cant find your source code anywhere....

2026-04-06 01:39:39 CEST

The password is "syncing". Enjoy
#nevent1q…knm7

2026-04-05 21:16:00 CEST

- reply

lol, its all black and white so its probably super easy to compress 😅

2026-04-05 20:54:03 CEST

- reply

yeah, the site itself is an encrypted site.7z file. the wrapper site just serves as a way to decrypt the file and then put it in local storage so it can be served

2026-04-05 20:35:13 CEST

A locked nsite... whatever could it be? 👀
https://0ygl461f4ecz5thkn8eksa36nepjpij86s83ti8yzokopd3ag5test.nsite.lol/

2026-04-05 20:02:39 CEST

- reply

what does this do?

2026-04-05 19:51:54 CEST

- reply

This is probably a better idea, having ctrl+c close the app isn't great for the world of TUI's

2026-04-05 19:50:50 CEST

- reply

They are saved, but its really annoying to start opencode again and try to remember what sessions where in the middle of work. then I have to tell the agent to "continue work"

2026-04-05 19:35:12 CEST

#asknostr how can I prevent ctrl+c closing my opencode editor? I've lost too many coding sessions by accidentally pressing it

2026-04-03 18:44:01 CEST

Shakespeare as an nsite? which you can use to vibe code more nsites??? 👀
https://2zrgjemvgxppn2jwgm61w6yrqqlcmm8njvhby68a9cj7ooo5phshakespeare.nsite.lol/

2026-04-03 18:21:24 CEST

@npub168h…9rgg archive https://npub168hzlrhxpeajf9shd937nacsefrkc3t0t7d79wlrknc7d33q2tls5u9rgg.nsite.lol/

2026-04-03 14:38:50 CEST

- reply

2026-04-03 14:30:12 CEST

- reply

I remember watching all that dramma unfold. It was a single Dev with admin access to some important repos.
I remember thinking at the time how many years of bugs it was going to cause

2026-04-02 19:27:16 CEST

For those who are using the applesauce packages and want to see them be more useful for agents I need some help.
I want to build a large catalog of mini example apps that agents can read and understand how to implement certain nostr features. I've already built a decent amount of them in the repo but for this to really be useful I need more, and more crazy ideas.
I'm looking for PRs that add a single focused example for a specific other-stuff thing on nostr or example that show how to implement common nostr things like zap modals, login dialogs, feeds, etc
The example MUST be less than 500 lines and should use the event casting system to keep the code clean. its also best to tell the agent to avoid using too many tailwind classes to avoid bloating the example.
Ill probably have to do some cleanup work on all PRs since agents generally don't know now to write less code or write rxjs observables well, but that's fine.
Steps:
- git clone https://github.com/hzrd149/applesauce
- Open editor `claude`, `opencode`, `codex` etc
- Tell agent to build a new example demonstrating a simple nostr feature
- Open PR
Existing examples: https://github.com/hzrd149/applesauce/tree/next/apps/examples/src/examples

2026-04-02 17:10:27 CEST

Forgot to mention yesterday but next release of #applesauce will have support for NIP-58 badges and some examples for AI agents to look at to understand how to implement them
https://cdn.hzrd149.com/d3d89772df46cde246db7f12f16aa54ddb062b733c87bb23962c18d78204a3bf.webp
https://cdn.hzrd149.com/b70fb6f365ec8ab43c414ffea6aa32eb5713ebfe9e00e8c4a9134af5334b244c.webp
https://cdn.hzrd149.com/faf62ff83ba1dba65692047a7056a89b855884522f627cf5805d65711da0652d.webp