Nostr notes by Stuart Bowman

Yes

2026-02-19T02:37:25Z

In reply to nevent1q…7ea7
_________________________

Yes

https://findaspring.org/map

2025-12-30T22:06:24Z

I deployed an update to the cdn backend recently but it should ...

2025-12-26T13:37:52Z

In reply to nevent1q…7azs
_________________________

I deployed an update to the cdn backend recently but it should work the same. What do you mean "the hashing thing" is not working?

That's slick!

2025-12-23T19:45:23Z

In reply to nevent1q…mhuw
_________________________

That's slick!

Check out https://satellite.earth

2025-12-23T18:35:42Z

In reply to nevent1q…3jyj
_________________________

Check out https://satellite.earth

Nostr event nevent1qqs2gm0tvsu85qdpdkh7g86flg566h9vx26qqvp0vl094nkhy6exwxszyrlj05quk8jkldv9sqcxc7a8dwcr00epr3d4w0zkunnse2zcw4d0qav4sf4

2025-12-23T02:41:57Z

日本のnostrユーザーの皆さん、こんにちは！

https://satellite.earth を日本語にローカライズしました。おそらく間違いがあると思いますので、もし見つけたらお知らせください、修正します。ありがとう 🙏

That he had to plead guilty because he knew that the law as ...

2025-12-20T18:13:18Z

In reply to nevent1q…mz7r
_________________________

That he had to plead guilty because he knew that the law as written would not be respected is perhaps the darkest aspect

Is @npub1lt6…p8hj still a thing?

2025-12-12T18:31:09Z

Is nostroots (npub1lt6…p8hj) still a thing?

I have a theory that nothing actually ever gets fixed. Things ...

2025-12-11T15:47:09Z

I have a theory that nothing actually ever gets fixed. Things just die, and then, ex nilhio, new things come into being, and it's all good.

That's surprising

2025-12-11T15:28:38Z

In reply to nevent1q…3xfh
_________________________

That's surprising

Man I miss the old Australia, like crocodile hunter stuff

2025-12-10T17:42:21Z

In reply to nevent1q…9vk8
_________________________

Man I miss the old Australia, like crocodile hunter stuff

I doubt that the average person who lived 100 years ago had more ...

2025-12-10T17:09:25Z

I doubt that the average person who lived 100 years ago had more freedom than we do today

Re-education

2025-12-06T17:10:08Z

In reply to nevent1q…ja97
_________________________

Re-education

not for long

2025-12-03T18:55:33Z

In reply to nevent1q…7pkh
_________________________

not for long

None currently, but I'm almost ready to ship the update that ...

2025-12-03T17:00:22Z

In reply to nevent1q…tt7p
_________________________

None currently, but I'm almost ready to ship the update that adds relay-based communities. It's not going to follow any NIP, it will a Satellite specific thing. Although, as I've said before, I think what hodlbod (npub1jlr…ynqn) is doing with Flotilla is directionally the right approach, and I'm trying to make it as interoperable as possible.

Actually basic relay feeds are actually working already (though it's sort of a hidden easter egg right now since I haven't wired up the UI) e.g. https://satellite.earth/relay/pyramid.fiatjaf.com

Regressive Web App (RWA)

2025-12-01T22:38:48Z

In reply to nevent1q…vvn2
_________________________

Regressive Web App (RWA)

real

2025-11-30T14:16:16Z

In reply to nevent1q…vhjk
_________________________

real

I see. Thank you

2025-11-27T14:56:51Z

In reply to nevent1q…rxt0
_________________________

I see. Thank you

It occurred to me that the new key rotation thing makes it ...

2025-11-27T01:38:48Z

It occurred to me that the new key rotation thing makes it possible to implement a credible low friction "Sign up with email, then migrate a self custody nostr id later" sort of flow.

So basically the way it would work is that the client allows the person to sign up with email, and you have a backend service that generates an nsec for them, and the backend signs stuff for them.

Then if the user wants to move to self custody at any point, they go in their account settings and click like "Enable self custody" or something.

This causes the client to generate a local nsec in the usual way, and the backend creates a key rotation event pointing at the self custodied nsec, and as soon as it's timestamped, immediately rotates to that new nsec.

So far so good.

However, there is still a problem -- there's no way for the backend to prove that it did not also publish an earlier timestamped rotation event with the new pubkey (which would allow the backend to rug the user in the future)

But we can solve this by having the user rotate *again* (using their new nsec) to a second locally generated nsec. (which the backend service could not have known, and thus could not have created any prior key rotation events for)

So bottom line is, yeah it involves two rotations (ie a 20 minute process on average given block time) but it massively reduces sign up friction while providing a way to migrate to self custody while keeping the social graph you may have accumulated prior to rotating into self custody.

hodlbod (npub1jlr…ynqn) Max (npub1klk…x3vt)

Got it, I'll add a button to mark all as read like the DMs

2025-11-21T01:55:14Z

In reply to nevent1q…hmeu
_________________________

Got it, I'll add a button to mark all as read like the DMs

What's up guys After my year break from social media I ...

2025-11-20T21:29:13Z

What's up guys
After my year break from social media I deployed the total rebuild of https://satellite.earth I created over course of these past 12 months.
It's a major upgrade.
The old Satellite was cool aesthetically but was not functional enough to be a daily driver. I had to fix this, to make the nostr client that I've always wanted.
Something beautiful that gets the basics right.
I changed the front page and the profile pages to focus on *just* what you're looking for, but I kept reddit-style threads because they are amazing for reading long conversations, e.g
https://satellite.earth/thread/note15yhl85e6jnayprt3ufp4ucuzwqry0uxd8sxqn4twctxxf4gkfdpsfyea0e
I got rid of NIP-172 communities. They were just too messy. I'm working on replacing them with relay-based communities instead (something like what hodlbod (npub1jlr…ynqn) has been cooking). This will be ready and deployed in the near term.
In the meantime, straight up relay feeds are already functional. You just have to type the url in yourself, e.g.
https://satellite.earth/relay/pyramid.fiatjaf.com
You can create aggregate relay feeds too by just including multiple comma separated relays in the url, e.g.
https://satellite.earth/relay/pyramid.fiatjaf.com,relays.land/spatianostra
Satellite CDN got reworked and refreshed as well. You can now see all your transactions, your current balance, and your burn rate. It's way more clear now what's going on.

I added client side search, based on your social graph (or *my* social graph if you're not signed in). It pulls all your contacts, your contacts' contacts, and indexes your web of trust locally. Believe it or not this is actually quite performant (especially if you are on a multicore machine).
To be clear, this is not really *search*. Something like what pip (npub176p…vgup) is building that is not strictly local will be necessary for finding obscure people.
This is essentially navigation UX, and it works great for jumping to someone's profile when you know where you want to go.

Notifications are super reliable now.
Aside the feed working well (which is the #1 live or die UX that absolutely must work) having notifications that are useful and where you can reply immediately from the interface without hunting down the post context is pretty important.

Added NIP17 support.
Maintained legacy NIP04 support for existing chats only.
The future is White Noise (npub1wht…r3ec) style Marmot Protocol (pending)

One of things that always annoyed me about legacy social media is that they spend all their screen real estate trying to get you to go somewhere *else* (???)
I mainly designed this profile page to be the client that I want to use.
I want to link to my page and not have the sidebars to like a billboard or something.
In the new Satellite the profile page looks pretty and only shows your stuff (and nothing else)

Added full featured rich text editor. This was one of the main things the old Satellite was lacking.
In the new Satellite you can upload media inline, directly to Satellite CDN or whichever is your preferred blossom server.
Mentions, emojis, embedding nostr notes inline are supported as well.

The Satellite CDN UI is much improved as well, especially if you have lots of files.
The terms and cost are the same as old Satellite.
You can upload big files (like > 5GB).
Bandwidth is free. $0.05/GB/mo.
Prepaid. Lightning only.
If you want a nice blossom-compatible gallery UX to be a home for all your media on nostr, I would encourage you to check it out.

I added some other thread improvements too. One feature I'm really happy about in the new Satellite is that you can link directly to deeply nested reply, e.g.
https://satellite.earth/thread/note1lqgmper99zj566xlc0gha4fmx4929njdckcq2w80yej0vrkcsyqqkqqh4s#note1zukmyf2nxrn5xamzawdez6f9egzaexjlhtjsza07rd7df9fn89esd40url
The ability to link to replies while seeing the whole context of the conversation I feel like really increases the "surface area" of the thread.
* * *
There are some more cool things in the pipeline.
Relay communities are the priority right now.
After that I will show you guys the new relay that I also built during this 12 month interlude.
Finally, if you still want to use the old satellite, you may at https://v1.satellite.earth

quoting
nevent1q…3pts
Satellite v2 check it out
https://satellite.earth
I'll do a write up tomorrow

Satellite v2 check it out https://satellite.earth I'll do a ...

2025-11-20T03:02:10Z

Satellite v2 check it out
https://satellite.earth
I'll do a write up tomorrow

Yeah, the update is a complete rebuild with all the old stuff and ...

2025-06-04T02:30:16Z

In reply to nevent1q…wehj
_________________________

Yeah, the update is a complete rebuild with all the old stuff and a bunch of new stuff

Ive just been working on a big new release of Satellite. Still ...

2025-06-04T02:27:40Z

In reply to nevent1q…wyya
_________________________

Ive just been working on a big new release of Satellite. Still here!

Relays but for media #note10uf…5slg

2024-03-19T23:31:00Z

Relays but for media

quoting note10uf…5slg
I'm really excited about this. Blossom is deceivingly simple, which is why it is powerful and why it has a chance of working.

What #nostr got right (and Bitcoin, for that matter) is that duplication is a feature, not a bug. "It takes advantage of the nature of information being easy to spread but hard to stifle," to quote Satoshi. De-duplication is a fools' errand, as it assumes a God's-eye-view. A global state is required to properly understand what to delete and what to keep. The second problem is of course indexing and discovery, which is indeed a hard problem if a global state is to be avoided. It's hard, but solvable. Especially if you already know what you're looking for, and especially especially if you have a common and purple-coloured discoverability layer.

Blossom is basically copying what nostr did for notes and applies it to arbitrary files. Instead of relays handling events, there's simple HTTP servers handling files. Like relays, servers are interchangeable as they share the same interface, encouraging duplication and redundancy. Instead of uploading something to a single server, you might upload it to five different servers. Popular and/or important files will be on many servers, which is how the online world works today already. Files that you need often might even be served by a #blossom server that is geographically close to you, just like we now have local cache relays packaged with some clients (or that you can self-host on your home server).

In the best case, Blossom will organically mirror what YouTube et al's content delivery networks already do well today, which is to provide file hosting that is high in availability and proximity. The neat thing about it all is that you can provide monetary incentives as it is nostr-native, and you get web-of-trust characteristics for free, as you can use only your servers, or those who are trusted by your friends, etc. And in the future, we'll probably have paid servers that whitelist npubs, just like we have paid relays now.

So why is all of that awesome? Well, here's the thing: as the user, you actually don't care where a file is hosted; you just care about the file itself. The current iteration of image (and other) hosts is incredibly stupid. Images are uploaded, downloaded, and re-uploaded without end, often with massive loss-of-quality as the same image is compressed and re-compressed a hundred times. It's always the same image, or at least it *should* be. With Blossom, it actually is.

Gone are the days of finding a thing and uploading again. You just need the hash, and the thing will appear. You could even insert images directly in notes with something like a blossom:ef1c26172f55017c9d9d6afa7cf22605b237b0fe92425e81e3b5e24d46c95448 and each client can choose how (HTTP, torrent, I2P, etc.) and where (public servers, private servers, etc.) to retrieve it from.

But wait, there's more. Remember the monetary incentives we talked about? It is what allows for the emergence of a proverbial "assassination market" for files: you provide the hash, along with a bounty of 21k sats to anyone who can provide the file most readily. Servers could provide cryptographic proof that they have the file, and you could escrow the money until delivery is done and you verify the file on your side. The building blocks are already there, we just need to put them together in the right way.

Blossom is one of the most exciting projects that came out of the first Sovereign Engineering (npub1s0v…rmq5) cohort, aka #SEC-01. I'll have more to say about all the other amazing #SovEng projects that came out of the discussions and collaborations we had, but now I'll have to go and upload some files.

nevent1q…390z

If you read one thing today, read this! #note1l2h…jaqs

2024-03-19T20:16:10Z

If you read one thing today, read this!

quoting note1l2h…jaqs

While I was in Mediera with all the other awesome people at the first SEC cohort there where a lot of discussions around data storage on nostr and if it could be made censorship-resistent

I remember lots of discussions about torrents, hypercore, nostr relays, and of course IPFS

There were a few things I learned from all these conversations:

All the existing solutions have one thing in common. A universal ID of some kind for files

HTTP is still good. we don't have to throw the baby out with the bath water

nostr could fix this... somehow

Some of the existing solutions work well for large files, and all of them are decentralization in some way. However none of them seem capable of serving up cat pictures for social media clients. they all have something missing...

An Identity system

An identity system would allow files to be "owned" by users. and once files have owners servers could start grouping files into a single thing instead of a 1000+ loose files

This can also greatly simplify the question of "what is spam" for a server hosting (or seeding) these files. since it could simply have a whitelist of owners (and maybe their friends)

What is blossom?

Blossom is a set of HTTP endpoints that allow nostr users to store and retrieve binary data on public servers using the sha256 hash as a universal id

What are Blobs?

blobs are chunks of binary data. they are similar to files but with one key difference, they don't have names

Instead blobs have a sha256 hash (like b1674191a88ec5cdd733e4240a81803105dc412d6c6708d53ab94fc248f4f553) as an ID

These IDs are universal since they can be computed from the file itself using the sha256 hashing algorithm ( you can a files hashing on linux using: sha256sum bitcoin.pdf )

How do the servers work?

Blossom servers expose four endpoints to let clients and users upload and manage blobs

GET /<sha256> (optional file .ext)

PUT /upload

Authentication: Signed nostr event

Returns a blob descriptor

GET /list/<pubkey>

Returns an array of blob descriptors

Authentication (optional): Signed nostr event

DELETE /<sha256>

Authentication: Signed nostr event

What is Blossom Drive?

Blossom Drive is a nostr app built on top of blossom servers and allows users to create and manage folders of blobs

What are Drives

Drives are just nostr events (kind 30563) that store a map of blobs and what filename they should have along with some extra metadata

An example drive event would be
{
  "pubkey": "266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5",
  "created_at": 1710773987,
  "content": "",
  "kind": 30563,
  "tags": [
    [ "name", "Emojis" ],
    [ "description", "nostr emojis" ],
    [ "d", "emojis" ],
    [ "r", "https://cdn.hzrd149.com/" ],
    [ "x", "303f018e613f29e3e43264529903b7c8c84debbd475f89368cb293ec23938981", "/noStrudel.png", "15161", "image/png" ],
    [ "x", "a0e2b39975c8da1702374b3eed6f4c6c7333e6ae0008dadafe93bd34bfb2ca78", "/satellite.png", "6853", "image/png" ],
    [ "x", "e8f3fae0f4a43a88eae235a8b79794d72e8f14b0e103a0fed1e073d8fb53d51f", "/amethyst.png", "20487", "image/png" ],
    [ "x", "70bd5836807b916d79e9c4e67e8b07e3e3b53f4acbb95c7521b11039a3c975c6", "/nos.png", "36521", "image/png" ],
    [ "x", "0fc304630279e0c5ab2da9c2769e3a3178c47b8609b447a30916244e89abbc52", "/primal.png", "29343", "image/png" ],
    [ "x", "9a03824a73d4af192d893329bbc04cd3798542ee87af15051aaf9376b74b25d4", "/coracle.png", "18300", "image/png" ],
    [ "x", "accdc0cdc048f4719bb5e1da4ff4c6ffc1a4dbb7cf3afbd19b86940c01111568", "/iris.png", "24070", "image/png" ],
    [ "x", "2e740f2514d6188e350d95cf4756bbf455d2f95e6a09bc64e94f5031bc4bba8f", "/damus.png", "32758", "image/png" ],
    [ "x", "2e019f08da0c75fb9c40d81947e511c8f0554763bffb6d23a7b9b8c9e8c84abb", "/old emojis/astral.png", "29365", "image/png" ],
    [ "x", "d97f842f2511ce0491fe0de208c6135b762f494a48da59926ce15acfdb6ac17e", "/other/rabbit.png", "19803", "image/png" ],
    [ "x", "72cb99b689b4cfe1a9fb6937f779f3f9c65094bf0e6ac72a8f8261efa96653f5", "/blossom.png", "4393", "image/png" ]
  ]
}
There is a lot going on but the main thing is the list of "x" tags and the path that describes the folder and filename the blob should live at

If your interested, the full event definition is at github.com/hzrd149/blossom-drive

Getting started

Like every good nostr client it takes a small instruction manual in order to use it properly. so here are the steps for getting started

1. Open the app

Open https://blossom.hzrd149.com

2. Login using extension

You can also login using any of the following methods using the input - NIP-46 with your https://nsec.app or https://flare.pub account - a NIP-46 connection string - an ncryptsec password protected private key - a nsec unprotected private key (please don't) - bunker:// URI from nsecbunker

3. Add a blossom server

Right now https://cdn.satellite.earth is the only public server that is compatible with blossom drive. If you want to host your own I've written a basic implementation in TypeScript github.com/hzrd149/blossom-server

4. Start uploading your files

NOTE: All files upload to blossom drive are public by default. DO NOT upload private files

5. Manage files

Encrypted drives

There is also the option to encrypt drives using NIP-49 password encryption. although its not tested at all so don't trust it, verify

Whats next?

I don't know, but Im excited to see what everyone else on nostr builds with this. I'm only one developer at the end of the day and I can't think of everything

also all the images in this article are stored in one of my blossom drives here

naddr1qv…6jka

I've been quiet lately, working on something. Looking forward ...

2023-12-15T06:46:10Z

I've been quiet lately, working on something. Looking forward to showing you all very soon

Hahaha

2023-11-03T06:45:08Z

In reply to nevent1q…swrw
_________________________

Hahaha

@npub1ltx…z40t So I’ve been thinking about this. To keep ...

2023-07-21T03:11:03Z

In reply to nevent1q…efh9
_________________________

Vivek (npub1ltx…z40t) So I’ve been thinking about this.

To keep things simple, for Satellite, I’m going to go ahead and use kind 4549 as a direct clone of kind 1 as VitorPamplona (npub1gcx…nj5z) suggested. So the content string of 4549 will be text just like kind 1.

My initial concern was that having a single kind defined as a “community post” would preclude the reuse of other event kinds, which is why I suggested “wrapping” the events.

I still intend to use kind 4549 as a wrapper to post non-kind-1 events into communities. When a non-kind-1 event is posted, the 4549 event will include a “k” tag indicating the kind of event that was wrapped.

But for 4549 events that do not have a “k” tag (or a “k” tag equal to 1), Satellite will assume that they should be treated like kind 1 and render the content directly.

I like this cause it’s just doing the simple “clone kind 1 thing” but adding the “k” tag allows me to do also do the wrapping thing so I can support other event types on Satellite. If other apps only care about kind 1 that’s fine.

I’m also implementing this weekend and writing up some documentation. Lmk if you wanna collab 🤙

Satellite update: deployed "conversations" tab Now you ...

2023-07-16T19:09:01Z

In reply to naddr1qq…g2v0
_________________________

Satellite update: deployed "conversations" tab

Now you easily can keep track of (and get notifications for) all the threads you've recently been involved with. You can even reply directly in from the notifications UI without having to navigate to the thread.

Check it out.

Just what I was looking for, thank you!

2023-05-22T03:25:49Z

In reply to nevent1q…a502
_________________________

Just what I was looking for, thank you!

Is there a comprehensive list somewhere of all the lightning ...

2023-05-22T02:58:51Z

Is there a comprehensive list somewhere of all the lightning wallets that have implemented NIP-57?