Nostr notes by rafftyl

I have some gold for you today. .clipping is one of the most ...

2026-10-18T13:10:29Z

I have some gold for you today. .clipping is one of the most interesting rap projects that I know of. The interplay between "rhyme-rhythm", "accent-rhytm", "musical-note-rhythm" is simply impeccable. The timbres used in their beats are unorthodox in the best way possible.
The drum machine built from garbage is just a bonus.
#musicstr #music #tunestr #rap #hiphop
https://www.youtube.com/watch?v=h0-k7vW9Xek

I went to hell and back after one particularly humongous dose. ...

2026-10-15T17:30:55Z

In reply to nevent1q…7qhy
_________________________

I went to hell and back after one particularly humongous dose. Never doing this again. Still worth it.

You should have a look at @npub17fe…nzuc

2026-10-11T07:33:48Z

In reply to nevent1q…4jvn
_________________________

You should have a look at nostrich (npub17fe…nzuc)

Armada for communities, @npub1980…hr0x for highlights and ...

2026-10-10T20:22:05Z

In reply to nevent1q…yv7p
_________________________

Armada for communities, Boris (npub1980…hr0x) for highlights and highlight feeds. ConduitMarket (npub1nkf…2svu) also shows a lot of promise, though Nostr marketplaces are still on a very early stage. If you're into short-form brain rot, you can have a look at c4a39f1291291d452405cd8ddd798c4a29a3858c52cd0d843f1f6852cf17682e (npub1cj3…klr7), but it's definitely not for me.

If you're using mainly kind 1 clients, I think you migh be ...

2026-10-10T18:39:22Z

In reply to nevent1q…hkr4
_________________________

If you're using mainly kind 1 clients, I think you migh be missing a lot of "other stuff" traffic happening: highlights, Concord comms, marketplace stuff, Divine videos, and probably all sorts of other arcane arts that I'm not even aware of.

@npub1der…xzpc are you aware of any tools for kind 1111 ...

2026-10-09T12:57:18Z

Gigi (npub1der…xzpc) are you aware of any tools for kind 1111 discussions tied to highlights (or better: tied to any kind)? Highlight feeds in Boris are quickly becoming more interesting than my kind 1 feed and it would be great to be able to get some conversations going.

Now that I think of it, daily might not be healthy, but nostr ...

2026-10-08T17:10:25Z

In reply to nevent1q…zytj
_________________________

Now that I think of it, daily might not be healthy, but nostr would greatly benefit from more art being posted regularly.

Please do. Social media is not that bad without the ragebait ...

2026-10-08T17:09:26Z

In reply to nevent1q…30q7
_________________________

Please do. Social media is not that bad without the ragebait algo.

Unless a social media break is a kind of break when you engage in ...

2026-10-07T14:14:34Z

In reply to nevent1q…uj7c
_________________________

Unless a social media break is a kind of break when you engage in social media. English confuses me.

Anyone seeing this note is most definitely not on a social media ...

2026-10-07T14:13:34Z

In reply to nevent1q…4fwp
_________________________

Anyone seeing this note is most definitely not on a social media break.

:red: :green: :cyan: :grey: :blue: :orange: :purple: :white:

2026-10-07T14:10:36Z

In reply to nevent1q…t9gs
_________________________

:red: :green: :cyan: :grey: :blue: :orange: :purple: :white:

I clanked it: ...

2026-10-06T19:52:16Z

In reply to nevent1q…lggr
_________________________

I clanked it: https://github.com/rafftyl/custom-umbrel-app-store/tree/master/rafftyl-custom-store-rustress

Still requires the user to generate a signing private key manually for NIP-57 to work, but it's good enough for me.

Have you talked to @npub1nkf…2svu people about interop? ...

2026-10-04T19:53:28Z

In reply to nevent1q…jx3r
_________________________

Have you talked to ConduitMarket (npub1nkf…2svu) people about interop?

STACI (npub1tan…hjmr) EricFJ (npub10xv…g437)

Testing custom emojis on @npub17fe…nzuc :Kneading: ...

2026-10-04T07:19:35Z

Testing custom emojis on nostrich (npub17fe…nzuc) :Kneading: :Pawraisewhilesitting: :Pawraised: :Kneading: :Tailaroundlegs: :Tailquiver:

Reading Pillars of Propagation again. This will become a classic. ...

2026-10-03T06:36:47Z

Reading Pillars of Propagation again. This will become a classic.

quoting
naddr1qq…zc7r

When the internet goes down, a lot goes down with it. All communication grinds to a halt. And communication entails more than WhatsApp, TikTok and other brainrot-catalyst apps. It is about getting in the new order for tomorrow's groceries that will await you fresh 'n green. It's about getting the truck-driver at the right loading-dock to pick up that load, and give him the right delivery address. It's his navigation to even get there. It's the Fuel-pump payment terminal to get him the gas to do it. And (nowadays), it's your good night's sleep.

F*cked would be an understatement to say the least. Now imagine that when the internet goes down, we simply...

...wouldn't care?

What if we can live in a way where we wouldn't even notice that the internet is down. That's what I want to talk about with you today.

The first two pillars

I want you to think about the physical location of data. Now what does that mean? I mean the physical location where a copy of data exists.

On the normal internet, this data is in a central data centre somewhere far away. When you visit a site, you pick up that data, it gets displayed on your browser, and discarded when you close the page.

This is a very wasteful and fragile model. If you visit the same page, and try to find the same information again, the whole circus starts all over, to once again throw away the data at the end. This means that you're incredibly dependent on all parts remaining accessible. Which we know isn't always the case.

Compare this to processes in nature, like a tree that gathers nutrients. A tree doesn't send out something to go to the roots and pick up a nutrient, go back, and deliver the nutrient. Go out and fetch, go out and fetch, and so on... Instead, a tree has liquids that flow up and bring along nutrients as they are needed, after which it travels down with products like sugars that go back into the soil. It's a continuous flow, with no start and no end.

This is exactly the model that's possible with Nostr and Blossom. Because the data integrity can be validated from the data itself, the data can flow freely. And since it's data, these flows can be filtered and duplicated at any point.

If that sounds a bit woowoo, let me give you an example: I go to a friend's profile on a Nostr social app and I load their posts, including the images, which are Blossom files. At that very moment I tap into an existing flow of data somewhere on a far-away relay & blossom server and filter it to my liking. But unlike the go-and-fetch model, the data is now physically replicated on my device. This means that the connection to that far-away relay is never again needed for this same information to propagate.

Let me repeat that: After receiving data from a far-away relay, that same connection is NEVER AGAIN needed for the same information to propagate.

Now that this data exists in my local community, ANYONE in need of this information can retrieve it from me rather than the far-away place.

THIS is what makes Nostr + Blossom so incredibly potent. Though few seem to realize it.

The monetary pillars

Because Nostr/Blossom are free of any interpretation of the data, we can transport anything with the model described above. AKA: relays don't care if it's a social media post or some event that makes a doorbell ring.

So, for example, this model can be used for propagating websites with nsite as well. Now anyone in my community can view a website that I've already collected from the other side of the world once.

I want to sketch a scenario here:

Let's say the internet is down and this (nsite) website happens to be a webshop for a local bakery. I've visited the webshop before, and just by doing that this data has already been propagated to my devices.

This means that anyone in my community can get this data from me, rather than from that connection to far away that's now unavailable. My neighbour who's a carpenter now loads the site and products by getting it from me, selects what he needs and goes to check-out.

Now we're stuck with a problem, because we can't pay without an internet connection. Except... we actually can. With Bitcoin Cashu mints. And not with fancy token-locking, but because our community has its own Cashu mint that continues to be accessible within the bounds of our local network.

Yes, we can't make bitcoin payments OUTSIDE our community as the internet went down, but we can definitely keep circulating the value that is already present within the community. Which accounts for MOST economic activity that we need to survive.

My neighbour can order his bread for later pick-up. I can pay him for that job he did for me the other day from the sats I have of this local mint.

Then, whenever the wider internet returns, we all pay in/out of the mint as we desire. I might top-up because I net spent and the bakery might cash out over lightning to pay their supplier for next week's flour.

Foundation for propagation

But, one huge problem remains... The internet's architecture doesn't support this organic flow of information. It is structured in a way that is too rigid to support a flow so organic, between parts that move around in physical space. The foundations are rattling and about to crumble...

It's not strange that it evolved this way, the great minds behind TCP/IP and adjacent protocols couldn't have designed for this world of flowing, self-validating data, as the tools we have at our disposal now simply didn't exist yet.

But we can't keep using a hammer now that we have screws. The tools may look similar and have similar goals. Yet, they're fundamentally different.

Many projects have come and gone that tried to create this new foundation, but never seemed to put all the parts in at once. Focussing on the reinforced concrete, but built on unstable ground. Or put in the pile foundation, but neglect the reinforced concrete. All these genuinely want to build a beautiful structure, but you need to get the touch-points between earth, foundation and structure exactly right.

In internet-land that means that we can't throw away 4+ decades of TCP/IP libraries for a new protocol. We have to be 100% compatible with the existing IP stack. You can't build a protocol and rebuild everything from the ping application up to Minecraft.

At the same time, we can't build on top of IP itself either, inheriting all its limitations. But, we won't get anywhere without fully supporting it either. It's a fine line and hard to get right, but I think FIPS has a good shot at making it work.

The harmonious hand-off

The key is in the touch points on top, where applications interface with the networking stack. And the earth, where the networking stack interfaces with the physical world.

Structure & foundation

This is the intersection where the pillars rest on their foundation. We can't require the whole structure to be designed around the foundation, it should just expect a sturdy footing.

Cashu mints, Nostr relays and Blossom servers currently rely on DNS as their de-facto identity, it's not truly theirs. An npub is. However, the system already exists, current tools expect a domain name. FIPS won't fight this fact, but interoperates with it. Npubs as domain names cover this gap, owning their identity, zero code changes.

Not forever, but as an in-road, possibly for decades, but it must be in place to invite the transition to Free Internetworking.

Foundation & Earth

The foundation & earth connection is the interface between FIPS and physical transport, which can be any medium and should be many of them at once. A good spider-web is attached at many places, a leaf, a piece of bark and a branch. Any of which can fail for its own reasons, amounting to a mere nuisance when it happens. No catastrophic failures like an interrupted network today.

In practical terms this means a network where fiber, Bluetooth and Serial all become your carriers, regardless of the application, or type of data. No application should be bothered with how Bluetooth transport works. And no Bluetooth transport implementation should care what application is using its link.

In closing

We're in a huge paradigm shift of data propagation, in a way we've never done, on a scale we've never seen. And with that scale I mean a scale so small that we tend to overlook it. A resilient internet is not one with huge backbone gateways, hyperscale compute clusters and fiber lines. It's a messy interplay of small relays, mints and Blossom blobs hopping over crappy links in all directions, right to where it needs to be. It is a network that persists through power-cuts, human error and shutdowns. It's a network where Bluetooth, USB cables and MicroSD cards become your carriers. Data will flow no matter the circumstances, or the scale. You can dam a river, but not the rain.

-Arjen

The meshed internet:

My @nprofile…7etp over @nprofile…nsnk has been running for a ...

2026-10-02T16:28:48Z

My BitBlik (nprofile…7etp) over fips (nprofile…nsnk) has been running for a couple of days (now at https://npub1ekuzl82ewlx7s9xdz9uq6lmadt9slv8n9m47z5fxkp7k57vpfvysuhxzvu.fips:8080/) and it seems like it's working really well. The speed is not exactly what I would call blazingly fast, but it's still magical that you can run a web service with no permission from a domain registrar or a hosting provider. Well, you still need an ISP, but a) it's only a matter of time, as FIPS is transport agnostic (imagine TollGate (nprofile…8mrq) + FIPS) b) the ISP does not even know what's up, because EVERYTHING IS ENCRYPTED.

This tech is beautiful.

quoting
nevent1q…4ups
Decentralized commerce needs decentralized infrastructure. A time will come when Bitcoiners will be forced to build in places that are harder to reach for the state apparatus, away from censorship, ID checks and takedown notices.

A central piece in all of that transitioning away from traditional internet domains that can be shut down easily. Luckily, achieving this has never been easier and it will take years before the machine catches up with us.

As a little demo, you can check out a BitBlik (nprofile…c3df) instance served over fips (nprofile…nsnk) from my personal PC: https://npub1d97zuys7eg0ehdsnrf8t3cs2xy0xfvrj4ukrx64hdrrda6r76nfsc0n7qr.fips:8080/

No domains, no static ip, no rented hosting, just a goddamn computer standing under my desk. To reach it, ask your clanker how to set up FIPS (from this repo: https://github.com/jmcorgan/fips) service and .fips name resolution on your machine. After it is done, you can just use your standard internet browser. And if you wanna reach it from an Android phone, just grab fips2go (https://zapstore.dev/apps/org.fips.android) from Zapstore, add your internet browser to the list of FIPS-enabled apps and voila!

Expect intermittent availability, from time to time I step away from the computer and shut it down :)

LLMs are intelligence amplifiers, you're gonna go places. ...

2026-10-02T08:38:19Z

In reply to nevent1q…02ex
_________________________

LLMs are intelligence amplifiers, you're gonna go places. Your co-workers won't like you :D

@nprofile…ma5h Some feedback on fips2go: when bootstrapping on ...

2026-09-23T14:37:07Z

fr34aky (nprofile…ma5h) Some feedback on fips2go: when bootstrapping on a cellular network, I'm getting errors like '2026-09-23T13:41:28.632354Z WARN fips::node::lifecycle: Failed to send handshake message link_id=link:2 error=send failed: Address family not supported by protocol (os error 97)'.

My clanker says this:
"On a DNS64/NAT64 mobile network (IPv6-only carrier), every handshake send fails
with `os error 97` (EAFNOSUPPORT) and the node ends up with 0 links. On any
normal IPv4/DNS network the same config links fine.

Root cause looks like an address-family mismatch: the UDP transport is bound to
`0.0.0.0:37259` (AF_INET) but the peer endpoint is a hostname
(`$name.fips.network:2121`), which DNS64 resolves to a synthesized AAAA. The
resulting `SocketAddr` is AF_INET6 and `sendto()` on the AF_INET socket fails.
`udp_bind` is in `ConfigStore.RETIRED_KEYS`, so the bind family can't be
changed from the UI."

A more permanent instance of Bitblik over FIPS is up. It's on ...

2026-09-23T14:17:02Z

A more permanent instance of Bitblik over FIPS is up. It's on a fucking Raspberry, so I cannot vouch for its stability. Let me know if it's reachable!

quoting
nevent1q…qsew
Very cool.
Do let us know when running 24/7
nevent1q…e9d4

Decentralized commerce needs decentralized infrastructure. A time ...

2026-09-20T11:38:08Z

Decentralized commerce needs decentralized infrastructure. A time will come when Bitcoiners will be forced to build in places that are harder to reach for the state apparatus, away from censorship, ID checks and takedown notices.

A central piece in all of that transitioning away from traditional internet domains that can be shut down easily. Luckily, achieving this has never been easier and it will take years before the machine catches up with us.

As a little demo, you can check out a BitBlik (nprofile…c3df) instance served over fips (nprofile…nsnk) from my personal PC: https://npub1d97zuys7eg0ehdsnrf8t3cs2xy0xfvrj4ukrx64hdrrda6r76nfsc0n7qr.fips:8080/

No domains, no static ip, no rented hosting, just a goddamn computer standing under my desk. To reach it, ask your clanker how to set up FIPS (from this repo: https://github.com/jmcorgan/fips) service and .fips name resolution on your machine. After it is done, you can just use your standard internet browser. And if you wanna reach it from an Android phone, just grab fips2go (https://zapstore.dev/apps/org.fips.android) from Zapstore, add your internet browser to the list of FIPS-enabled apps and voila!

Expect intermittent availability, from time to time I step away from the computer and shut it down :)

Are there any high-quality curated lists of nostr clients grouped ...

2026-09-20T06:21:16Z

Are there any high-quality curated lists of nostr clients grouped by NIPs they implement?

I figured out that it's a bug in lnSwitchboard, gotta wait ...

2026-09-19T14:08:09Z

In reply to nevent1q…m6t9
_________________________

I figured out that it's a bug in lnSwitchboard, gotta wait for a fix.

Holy fuck, I sometimes forget how deranged people can be. ...

2026-09-18T18:01:51Z

In reply to nevent1q…j8hg
_________________________

Holy fuck, I sometimes forget how deranged people can be. Luckily, I have my neighbor next door who keeps my memory fresh. And now this subreddit.

To jest skomplikowana sprawa, bo bawię się w self hosting, co ...

2026-09-18T16:47:49Z

In reply to nevent1q…x0j0
_________________________

To jest skomplikowana sprawa, bo bawię się w self hosting, co nie jest najlepszym pomysłem, jeśli chcesz, żeby coś działało. Ale za to jestem kurwa suwerennym indywiduum, heh.

Dobra, zdaje się że jeszcze Amethystowi coś nie pasuje. Z ...

2026-09-18T15:51:07Z

In reply to nevent1q…57kg
_________________________

Dobra, zdaje się że jeszcze Amethystowi coś nie pasuje. Z innych klientów już działa. Debuguję dalej. Ależ to jest gówno.

Shit, już byłem pewien że to naprawiłem. Amethyst?

2026-09-18T15:41:41Z

In reply to nevent1q…lqsm
_________________________

Shit, już byłem pewien że to naprawiłem. Amethyst?

The future is meshed. #naddr1qq…zc7r

2026-09-18T14:10:30Z

The future is meshed.

quoting
naddr1qq…zc7r

When the internet goes down, a lot goes down with it. All communication grinds to a halt. And communication entails more than WhatsApp, TikTok and other brainrot-catalyst apps. It is about getting in the new order for tomorrow's groceries that will await you fresh 'n green. It's about getting the truck-driver at the right loading-dock to pick up that load, and give him the right delivery address. It's his navigation to even get there. It's the Fuel-pump payment terminal to get him the gas to do it. And (nowadays), it's your good night's sleep.

F*cked would be an understatement to say the least. Now imagine that when the internet goes down, we simply...

...wouldn't care?

What if we can live in a way where we wouldn't even notice that the internet is down. That's what I want to talk about with you today.

The first two pillars

I want you to think about the physical location of data. Now what does that mean? I mean the physical location where a copy of data exists.

On the normal internet, this data is in a central data centre somewhere far away. When you visit a site, you pick up that data, it gets displayed on your browser, and discarded when you close the page.

This is a very wasteful and fragile model. If you visit the same page, and try to find the same information again, the whole circus starts all over, to once again throw away the data at the end. This means that you're incredibly dependent on all parts remaining accessible. Which we know isn't always the case.

Compare this to processes in nature, like a tree that gathers nutrients. A tree doesn't send out something to go to the roots and pick up a nutrient, go back, and deliver the nutrient. Go out and fetch, go out and fetch, and so on... Instead, a tree has liquids that flow up and bring along nutrients as they are needed, after which it travels down with products like sugars that go back into the soil. It's a continuous flow, with no start and no end.

This is exactly the model that's possible with Nostr and Blossom. Because the data integrity can be validated from the data itself, the data can flow freely. And since it's data, these flows can be filtered and duplicated at any point.

If that sounds a bit woowoo, let me give you an example: I go to a friend's profile on a Nostr social app and I load their posts, including the images, which are Blossom files. At that very moment I tap into an existing flow of data somewhere on a far-away relay & blossom server and filter it to my liking. But unlike the go-and-fetch model, the data is now physically replicated on my device. This means that the connection to that far-away relay is never again needed for this same information to propagate.

Let me repeat that: After receiving data from a far-away relay, that same connection is NEVER AGAIN needed for the same information to propagate.

Now that this data exists in my local community, ANYONE in need of this information can retrieve it from me rather than the far-away place.

THIS is what makes Nostr + Blossom so incredibly potent. Though few seem to realize it.

The monetary pillars

Because Nostr/Blossom are free of any interpretation of the data, we can transport anything with the model described above. AKA: relays don't care if it's a social media post or some event that makes a doorbell ring.

So, for example, this model can be used for propagating websites with nsite as well. Now anyone in my community can view a website that I've already collected from the other side of the world once.

I want to sketch a scenario here:

Let's say the internet is down and this (nsite) website happens to be a webshop for a local bakery. I've visited the webshop before, and just by doing that this data has already been propagated to my devices.

This means that anyone in my community can get this data from me, rather than from that connection to far away that's now unavailable. My neighbour who's a carpenter now loads the site and products by getting it from me, selects what he needs and goes to check-out.

Now we're stuck with a problem, because we can't pay without an internet connection. Except... we actually can. With Bitcoin Cashu mints. And not with fancy token-locking, but because our community has its own Cashu mint that continues to be accessible within the bounds of our local network.

Yes, we can't make bitcoin payments OUTSIDE our community as the internet went down, but we can definitely keep circulating the value that is already present within the community. Which accounts for MOST economic activity that we need to survive.

My neighbour can order his bread for later pick-up. I can pay him for that job he did for me the other day from the sats I have of this local mint.

Then, whenever the wider internet returns, we all pay in/out of the mint as we desire. I might top-up because I net spent and the bakery might cash out over lightning to pay their supplier for next week's flour.

Foundation for propagation

But, one huge problem remains... The internet's architecture doesn't support this organic flow of information. It is structured in a way that is too rigid to support a flow so organic, between parts that move around in physical space. The foundations are rattling and about to crumble...

It's not strange that it evolved this way, the great minds behind TCP/IP and adjacent protocols couldn't have designed for this world of flowing, self-validating data, as the tools we have at our disposal now simply didn't exist yet.

But we can't keep using a hammer now that we have screws. The tools may look similar and have similar goals. Yet, they're fundamentally different.

Many projects have come and gone that tried to create this new foundation, but never seemed to put all the parts in at once. Focussing on the reinforced concrete, but built on unstable ground. Or put in the pile foundation, but neglect the reinforced concrete. All these genuinely want to build a beautiful structure, but you need to get the touch-points between earth, foundation and structure exactly right.

In internet-land that means that we can't throw away 4+ decades of TCP/IP libraries for a new protocol. We have to be 100% compatible with the existing IP stack. You can't build a protocol and rebuild everything from the ping application up to Minecraft.

At the same time, we can't build on top of IP itself either, inheriting all its limitations. But, we won't get anywhere without fully supporting it either. It's a fine line and hard to get right, but I think FIPS has a good shot at making it work.

The harmonious hand-off

The key is in the touch points on top, where applications interface with the networking stack. And the earth, where the networking stack interfaces with the physical world.

Structure & foundation

This is the intersection where the pillars rest on their foundation. We can't require the whole structure to be designed around the foundation, it should just expect a sturdy footing.

Cashu mints, Nostr relays and Blossom servers currently rely on DNS as their de-facto identity, it's not truly theirs. An npub is. However, the system already exists, current tools expect a domain name. FIPS won't fight this fact, but interoperates with it. Npubs as domain names cover this gap, owning their identity, zero code changes.

Not forever, but as an in-road, possibly for decades, but it must be in place to invite the transition to Free Internetworking.

Foundation & Earth

The foundation & earth connection is the interface between FIPS and physical transport, which can be any medium and should be many of them at once. A good spider-web is attached at many places, a leaf, a piece of bark and a branch. Any of which can fail for its own reasons, amounting to a mere nuisance when it happens. No catastrophic failures like an interrupted network today.

In practical terms this means a network where fiber, Bluetooth and Serial all become your carriers, regardless of the application, or type of data. No application should be bothered with how Bluetooth transport works. And no Bluetooth transport implementation should care what application is using its link.

In closing

We're in a huge paradigm shift of data propagation, in a way we've never done, on a scale we've never seen. And with that scale I mean a scale so small that we tend to overlook it. A resilient internet is not one with huge backbone gateways, hyperscale compute clusters and fiber lines. It's a messy interplay of small relays, mints and Blossom blobs hopping over crappy links in all directions, right to where it needs to be. It is a network that persists through power-cuts, human error and shutdowns. It's a network where Bluetooth, USB cables and MicroSD cards become your carriers. Data will flow no matter the circumstances, or the scale. You can dam a river, but not the rain.

-Arjen

The meshed internet:

https://i.nostr.build/piKlq2vF2eo2Z5M8X0An75.jpg Browsing FIPS ...

2026-09-16T22:56:41Z

In reply to nevent1q…8nav
_________________________

Browsing FIPS sites from a fucking Chrome. This is magic.

Much too soft for me, but holy fuck guys, you are pros!

2026-09-16T16:08:46Z

In reply to nevent1q…rh9u
_________________________

Much too soft for me, but holy fuck guys, you are pros!

Subtle and elegant.

2026-09-16T16:03:08Z

In reply to nevent1q…yj28
_________________________

Subtle and elegant.

Sound intriguing, but I'm afraid to touch this shit 🙃

2026-09-16T05:08:55Z

In reply to nevent1q…4g52
_________________________

Sound intriguing, but I'm afraid to touch this shit 🙃

Currently using https://github.com/RyleaStark/lnSwitchboard on an ...

2026-09-16T05:06:26Z

In reply to nevent1q…tsfh
_________________________

Currently using https://github.com/RyleaStark/lnSwitchboard on an Umbrel. Most of my problems were caused by reverse proxy setup and not lnurl itself.

Trying out fips2go by @npub1ypt…a52w. Is there any public index ...

2026-09-15T19:52:36Z

Trying out fips2go by fr34aky (npub1ypt…a52w). Is there any public index of fips (npub1y0g…00ly) sites that I could visit?

Bierzcie i czytajcie. #naddr1qq…r7kg

2026-09-15T19:44:41Z

Bierzcie i czytajcie.
nostr:naddr1qq2kshm429rz6d6gvcmkyaphtuuxk3zywd5kzq3qk3g092rlzvn7nftz3jte9pkx63zp705nh78r6hjpjm55fjg7r2cqxpqqqp65wqzr7kg

Today I learned that self-hosting a lightning address is a bitch. ...

2026-09-15T19:41:40Z

Today I learned that self-hosting a lightning address is a bitch. Should be working now, but boy why am I doing this to myself?

I should be, just verified it. Maybe you have stale lightning ...

2026-09-13T12:33:22Z

In reply to nevent1q…3m68
_________________________

I should be, just verified it. Maybe you have stale lightning address data? The current one is rafftyl@sats.rafaltyl.com

Listening to Breedlove talking about harmony in music, I felt the ...

2026-09-13T10:10:41Z

Listening to Breedlove talking about harmony in music, I felt the need to set something straight. On X, unfortunately. I thought I should also post it here.

A steak of course. 1. Grab fatty ribeye 2. Put it on a fucking ...

2026-09-12T19:39:56Z

In reply to nevent1q…ee6q
_________________________

A steak of course.

1. Grab fatty ribeye
2. Put it on a fucking hot frying pan
3. Fry medium rare
4. Salt to taste
5. Add a fuckton of butter

10 minutes, best meal ever. I pity all those wretches who have to spend hours to make their food edible.

Please teach me how to highlight YT vids.

2026-09-11T17:52:35Z

In reply to nevent1q…75vx
_________________________

Please teach me how to highlight YT vids.

Cool idea! Do you have any info on cost-effectiveness (savings vs ...

2026-09-11T13:14:41Z

In reply to nevent1q…n259
_________________________

Cool idea! Do you have any info on cost-effectiveness (savings vs investment made)?

So called "white voice" is a type of folk singing common ...

2026-08-30T15:31:25Z

So called "white voice" is a type of folk singing common to all Slavic cultures (although it can be found all across the globe) and is characterized by a very strong, forward-placed resonance, producing a distinct "buzz". The buzz is the raw sound of fully connected vocal folds, not attenuated by any unnecessary tension in the vocal tract.

Anglophone sources speak of this type of singing as a "controlled shout", but this is a huge misconception, in my opinion. I would call it more of a call than a shout. You can hear it in our example below - even quiet, delicate sounds possess the same consistent quality. Too me, it's the most pure type of singing - no mannerisms, no hiding your shame behind various stylizations, no trying to sound impressive.

From my experience, people are either mesmerised by this song or (rarely) find the voice too harsh, too piercing. I wonder how you guys will react.

https://tidal.com/track/240158095/u

#music #musicstr #tunestr

Today is the right time for some gay metal! I present to you one ...

2026-06-20T17:33:25Z

Today is the right time for some gay metal! I present to you one of the grooviest tracks by Monuments. Great riffs, tasteful rhythm section, amazing vocals. A little bit poppy (adjective) but still metal enough to be cool.

https://tidal.com/track/212427069/u

#music #musicstr #tunestr

Working fine, thank you!

2026-06-17T14:59:44Z

In reply to nevent1q…mrys
_________________________

Working fine, thank you!

@nprofile…z866 was great and all, but the coolest thing that ...

2026-06-07T20:24:50Z

BitcoinFilmFest (nprofile…z866) was great and all, but the coolest thing that happened is that I realized the word "popcorn" sounds like "cock porn". Feel free to make use of this amazing fact whenever someone says "popcorn" in your presence. Highly recommend shouting "COCK PORN" to their face. Tried this on my wife (multiple times) and it was the funniest shit ever.

I guess I stopped maturing after the age of 12 and have been only growing since then.

Guess who's running a local @nprofile…c3df instance in the ...

2026-06-06T11:05:21Z

Guess who's running a local BitBlik (nprofile…c3df) instance in the browser, open at all times on his work computer.

Haha, I'm only 11 years in and already thinking about ...

2026-03-11T06:54:14Z

In reply to nevent1q…nsq8
_________________________

Haha, I'm only 11 years in and already thinking about becoming a cattle farmer. Nevertheless, I still think there's a huge difference between 30 years of dev and 30 years of construction work.

A great explanation of Keychat protocol. #naddr1qv…cza7

2026-03-09T10:27:55Z

A great explanation of Keychat protocol.

quoting naddr1qv…cza7

Imagine sending a letter. You write your message on a sheet of paper, put it in an envelope, write the recipient's name and address, your own name and return address, stick on a stamp, and drop it in the mailbox. The post office reads the envelope and delivers it.

This process has worked for centuries. Keychat does fundamentally the same thing — delivering a message from one person to another — but it redesigns every element of the process. This article uses the mail analogy to explain how the Keychat protocol works, across five layers.

I. Identity: Self-Generated, Self-Owned

In traditional mail, your name and address are bound together, written on the envelope, visible to both the post office and the recipient.

In Keychat, your identity is a Nostr keypair — think of it as a name you give yourself. You generate it on your own, no registration with any authority required. No service provider can revoke it, and no one can impersonate it (because only you hold the private key).

Unlike traditional mail, your name doesn't need to appear on the envelope. Neither the sender's name nor the recipient's name is written there. Your identity exists only inside the sealed letter — only the recipient learns who sent it after opening.

II. Encryption: Every Letter Gets a Different Lock

A traditional envelope is made of paper — the postal worker shouldn't open it, but technically could.

Every Keychat message is encrypted with Signal Protocol. Think of each letter being placed in a combination lockbox that only the recipient can open. But Keychat goes further: every letter uses a different lock and key.

This is thanks to the Double Ratchet algorithm. After each communication, the ratchet advances one step, deriving entirely new encryption keys. Old keys are immediately destroyed. This produces two important properties:

Forward secrecy: Even if someone steals your current key, they cannot open previous letters — each letter used a different lock, and the old keys no longer exist

Backward secrecy (post-compromise recovery): Even if a key is stolen, the next communication will derive new keys, locking the attacker out again

For users, all of this happens automatically in the background — you just write and read messages.

III. Addressing: The Envelope Is Nearly Blank

This is where Keychat diverges most from traditional mail.

A traditional envelope carries two sets of information: the recipient's name and address, and the sender's name and address. A Keychat envelope needs only one thing: the recipient's current receiving address. The sender's address is randomly generated each time — random means effectively none. The relay cannot determine who sent it.

And the receiving address itself keeps changing. Keychat repurposes the Double Ratchet algorithm — originally designed only to derive encryption keys — to also derive receiving addresses. Each time the DH ratchet advances, it updates both the encryption keys and the receiving addresses. After one round-trip of communication, both parties' receiving addresses are updated and old addresses become invalid. It's like moving to a new house after every letter exchange, with only the other party knowing your new address.

Random sender addresses, rotating receiver addresses — every letter looks to the relay like one stranger writing to another, completely unlinkable. No one can collect your mail by watching a single address, and even the relay cannot construct a social graph of who communicates with whom.

Adding a friend: the one exception. You know someone's identity (Nostr public key), but there are no rotating addresses between you yet. You prepare a special introduction letter (Hello) containing your identity, encryption keys, and a temporary receiving address, wrap it in a sealed package (NIP-17 Gift Wrap), and send it directly to the other party's identity — this is the only time identity serves as a receiving address. The recipient opens the package, establishes an encrypted channel (Signal session), and sends their first reply to your temporary address. From the moment you reply to their first letter, ratchet-derived receiving addresses take over and both parties enter the continuously rotating address flow.

IV. Transport: An Open Relay Network

Traditional mail depends on a national postal system. Keychat's relays (Nostr relays) form an open network — anyone can run their own relay.

Each letter can be posted to multiple relays simultaneously, and the recipient collects from multiple relays simultaneously. It's like dropping the same letter into mailboxes at several different post offices while the recipient checks their box at each one. As long as any single post office delivers successfully, the letter arrives. No single point of failure, no censorship bottleneck, no monopoly.

V. Stamps: Turning Relays into Post Offices

Some relays charge postage. Keychat handles this with ecash stamps — anonymous micropayments using Cashu tokens.

The analogy is literal: you buy a stamp (a small ecash token, typically a few satoshis) and attach it to the envelope. The relay validates the stamp before delivering the letter. Stamps are bearer instruments — the relay knows the stamp is valid, but not who bought it. The stamp is attached outside the Event as a transport-layer credential, not part of the letter content, and is not forwarded to the recipient.
Free relay:   ["EVENT"]
Paid relay:   ["EVENT", "<stamp>"]
Relays get paid for delivery, users get spam filtering, and neither party sacrifices privacy. With stamps, relays truly become post offices — not just passive message pipes, but operators providing paid delivery services. When every relay can set its own pricing, an open postal market naturally emerges.

Through the mail analogy, you should now find it easier to understand what the Keychat protocol actually delivers: self-sovereign identity, end-to-end encryption with forward and backward secrecy, metadata-resistant addressing, decentralized transport, and a free market for message delivery where ecash stamps turn relays into competing post offices — sovereign communication.

This is exactly how it is.

2026-02-20T20:09:31Z

In reply to nevent1q…kpfx
_________________________

This is exactly how it is.