Cody

Building 👨‍💻
https://jumble.social/ & https://psstpsst.chat/

Public Key

npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl

NIP-05 Address

Profile Code

nprofile1qqsgzfdez8ksa9xmuvqg5zly3nl9e5xqkpvj8nllj9aw06ra4pqq3qcpr9mhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5q3wamnwvaz7tmjv4kxz7fwdehhxarj0f5zummjvuagv6en

Publishing to

Author Public Key

npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl

Show more details

Last Notes

2026-10-13 15:02:00 UTC

- reply

Nice! Great work! 👍

2026-10-13 14:42:52 UTC

- reply

I’m not sure if this also covers the case where users add a `,` right after a URL. I’ll test it when I get a chance. Thanks for the report!

2026-10-12 01:30:21 UTC

- reply

I wouldn't call myself a libertarian. I just like ideas around privacy, decentralization, and giving users more control over their own data.
Also, I don't think the small number of Chinese users on Nostr is because of restrictions. Most people just don't find it interesting enough. There were more Chinese users a few years ago, but many gradually left. There are actually quite a lot of Chinese users on X 😌

2026-10-12 01:25:54 UTC

- reply

I think it makes more sense as a standalone tool. Jumble relies entirely on relay data, so it’s not really able to provide SEO. A separate tool could focus on custom njump pages and help drive discoverability.

2026-10-10 14:03:55 UTC

- reply

I mean the DMs are not interoperable with other Nostr clients. PsstPsst is still a Nostr client, but it only focuses on private messaging. It doesn't have a social feed like other clients that are more like X.

2026-10-10 01:59:35 UTC

Added a simple relay monitoring table to Jumble
https://blossom.jumble.social/1c369eda516138c910548b0420deb2744d12e1b10ee3ef5cf2b5d79fcacf03eb.png
https://blossom.jumble.social/423e264ae607ef55ef6cc90412f12394f679d75c28a4e9718ae63de2a1781d4a.png

2026-10-10 01:23:06 UTC

- reply

Haha, not a genius mastermind 😄 Thanks for your great contributions!

2026-10-10 01:17:26 UTC

- reply

The main reason is to avoid breaking the original layout of the note. Links are not always standalone, they can be placed in the middle of the text, and showing a preview for every link could make the content look messy.
But yeah, I agree that standalone links should show a preview. I’ll improve this in a future update.

2026-10-08 15:31:08 UTC

- reply

It's pretty difficult to implement this on Nostr. That's also why Jumble doesn't show your follower count. To get that number, we'd need to search across relays for everyone's follow lists that include you, which is extremely difficult and usually inaccurate. After all, nobody even knows how many relays exist on the Nostr network anymore.

2026-10-08 01:46:51 UTC

- reply

Most Chinese people use crypto either for speculation or for moving money overseas. For cross-border transfers, people usually stick with things that are widely accepted, like USD stablecoins, Bitcoin, or Ethereum. I honestly rarely hear anyone in China using Monero.
The digital yuan is basically just RMB in another form. Ordinary people don’t really care about it. The only time many people use it is when there are government promotions or digital coupons distributed through it.

2026-10-08 01:33:00 UTC

- reply

But that only solves half of the problem. People in China still can't access your write relays to fetch the content you publish, and they can't send replies to your read relays either.

2026-10-07 14:41:11 UTC

- reply

China's firewall is basically blacklist-based. If a service isn't on the blacklist, it usually still works. Jumble is still a pretty small project, so it's not on the list.
Also, Nostr content lives on relays, not on the client itself. Being able to access a Nostr client doesn't really prove much. In fact, some of the bigger relays are already blocked by the firewall.

2026-10-04 06:35:28 UTC

- reply

Not removed, just lowered its priority

2026-10-03 05:50:00 UTC

- reply

Worried about disturbing the people nearby

2026-10-02 16:11:21 UTC

- reply

Yes, that's likely the reason. But it's not a bad thing, it actually makes your setup more decentralized. If the first Blossom server removes your file, the client can still fetch it from your other configured Blossom servers.

2026-10-02 15:26:58 UTC

- reply

If you have configured more than one Blossom server, Jumble will first upload the file to the first Blossom server, then mirror it to the other configured Blossom servers.
The mirroring process does not upload the file again, but it may still take some time to complete.

2026-10-02 14:59:17 UTC

- reply

Jumble doesn't compress images or files right now

2026-10-02 14:17:02 UTC

- reply

Nobody has told me this change was causing problems, so it’s not that I don’t care about users. I can only make decisions based on the feedback I receive.
But since you mentioned it, I think you have a point. I’ll make the long-form article entry less prominent in the UI.
Please keep the feedback coming, but there’s no need to be so aggressive. The extra insults don’t really help the discussion.

2026-10-02 11:38:56 UTC

- reply

That’s a fair point. But improving an existing app is often harder because of all the historical baggage and the original author’s own ideas.
PsstPsst is trying to feel like a normal messenger app, so people don’t need to know anything about Nostr. It’s more for your non-technical friends and family. Don’t think of it as just another Nostr DM app, it’s not compatible with most of them anyway haha.

2026-10-02 11:34:04 UTC

- reply

Very soon!

2026-10-02 11:31:55 UTC

- reply

Nope, I’m Chinese haha. My girlfriend is learning Spanish recently, so she changed the system language to Spanish

2026-10-01 13:19:58 UTC

- reply

Yeah, if the process isn’t too complicated haha.

2026-10-01 13:18:29 UTC

- reply

Thank you! It’s designed to be friendly and easy to use for non-technical users, especially for chatting with family and friends.

2026-10-01 13:14:10 UTC

- reply

No. PsstPsst uses NIP-17 DMs built on NIP-4e, which separates the encryption key from the identity key, so it’s not compatible with most Nostr clients.
The Bluetooth protocol is custom for now, but I plan to support it via FIPS in the future.

2026-10-01 08:02:37 UTC

Chat even when you’re offline.
https://psstpsst.chat
https://blossom.jumble.social/f3d35e2bfe75771a40f0aaca27238b6e0b44725d3d06b4fd0e9c58cb0f47df6c.jpg

2026-09-25 03:45:03 UTC

- reply

Where does the data come from? If it’s just scanning multiple relays, it might be difficult to recover historical events, since relays usually don’t store or return old replaceable events by default.

2026-09-24 07:31:06 UTC

- reply

Glad to hear that 🫡

2026-09-23 13:55:19 UTC

- reply

Got it. Clients should definitely provide some indicators to help users quickly understand whether a relay is working properly or not.

2026-09-23 13:52:42 UTC

- reply

I agree, this definitely needs some improvement.

2026-09-23 09:41:24 UTC

- reply

Removing relays that you can’t connect to or that reject your events is more effective than simply adding more relays.

2026-09-23 08:30:07 UTC

- reply

Most clients don't only send replies to the relays you configured. They also try to send them to the read relays used by the people you mention, so you usually don't need to add a huge number of relays for your replies to be seen.
In fact, adding too many relays can make things worse. When someone replies to you, they may need to publish to all of your relays, and some clients (including Jumble) may ignore users with an excessive number of relays to avoid this problem.
Adding too many relays can also hurt your own experience, because it increases the workload for your client. More relays mean more connections to maintain, more events to process, and more complexity overall.
Relay management is definitely still a complicated part of Nostr, but having more relays isn't always better. The goal is to find a balance between decentralization and usability.

2026-09-21 11:39:33 UTC

- reply

Has the move to kind 1111 become the consensus yet? Jumble is still using kind 1 replies for kind 1 notes. If the community has settled on switching to kind 1111, I’ll update it as soon as I can.

2026-09-21 11:37:15 UTC

- reply

Jumble supports displaying both kind 1 replies and kind 1111 replies at the same time.

2026-09-16 10:11:59 UTC

- reply

I’m not sure what an attacker gains by spreading an old 10044 event elsewhere. Clients should be fetching 10044 events from the user’s write relays / DM relays anyway.
I don’t think putting it on-chain fundamentally solves the issue of senders not getting the latest update in time. It feels more like a different source of truth, querying relays versus querying the chain.