Cody

fiatjaf has been building a lot of napps lately. I just tried Napp Maker, and it feels full of possibilities! I can’t wait to release the next version of PsstPsst, with support for napps, napplets, and nsites!
https://blossom.jumble.social/6fe305327f69f1b72e07334db6970dcdb7eedb9bad5ef0bf4f6ac28d49fa3d77.png
https://blossom.jumble.social/c9a5380ca8194298e832d8c224ae7c6a437ee9ec52f5376ac0bd244b2531a3d1.png
https://blossom.jumble.social/371cea3207bfc1a3399532643857488ffa77da710a4ea73dbf3b77e2d65b1773.png
#nevent1q…fz3r

2026-10-25 16:04:59 UTC

- reply

Great news!

2026-10-25 15:47:04 UTC

- reply

You can record your screen on iOS using the built-in Screen Recording feature. Open Control Center, tap the Screen Recording button (the circle icon)
If you don’t see the button, go to Settings → Control Center and add Screen Recording first. 😊

2026-10-25 02:59:26 UTC

- reply

Could you record your screen? It might help me pinpoint the bug.

2026-10-24 10:03:24 UTC

- reply

I suspect it’s an issue with the emoji picker’s positioning. Someone reported it before, but I haven’t been able to fix it haha. The emoji component might be the problem, so I’m thinking of having AI build one from scratch.

2026-10-22 14:26:28 UTC

- reply

Fixed! Thanks for the report.

2026-10-22 01:45:25 UTC

- reply

Thanks for the report!

2026-10-22 01:38:54 UTC

- reply

It looks like it was incorrectly detected as a mobile device because the window height was too small. I’ve made some adjustments, so when you have time, try refreshing the page to see if it’s fixed. You may need to refresh a few times, waiting a bit between each refresh. The latest version is v26.9.2 (3bc0427).

2026-10-22 01:08:16 UTC

- reply

Could you share a screenshot?

2026-10-21 01:05:27 UTC

- reply

This is related to a change I made yesterday. I’ll fix it asap. Thanks for the report!

2026-10-20 15:17:39 UTC

- reply

The client checks that the seal event’s author matches the author claimed in the rumor it wraps, so the attack you describe wouldn’t work. Anyone who knows your pubkey can fabricate a rumor event claiming to be from you, with any content they like. But they can’t produce a valid seal for it that other clients would accept.

2026-10-20 13:48:46 UTC

- reply

It exports rumor events, which are unsigned. You could certainly tamper with the contents of your exported events, but I don’t see what purpose that would serve.

2026-10-20 01:27:27 UTC

https://psstpsst.chat is now available on all platforms! I’m planning to eventually remove DM features from Jumble to avoid maintaining two similar implementations, but it won’t happen anytime soon.
If you still use Jumble DMs (probably not many), you can export your message history and import it into PsstPsst.
You can already disable DMs under Settings → General in Jumble.

2026-10-20 01:10:43 UTC

- reply

Both are possible. It depends on how you build it.

2026-10-19 15:27:05 UTC

napps / nsites / napplets / websites
https://blossom.jumble.social/d0c33a46abfa4d5ca6755c9eaa668d1f31af64712b2009f6aff9bcd34bcbd12d.png

2026-10-19 09:23:28 UTC

- reply

我也不知道哈哈哈，一年前 gpt 生成的题目。我还是直接邀请你吧

2026-10-19 09:03:31 UTC

- reply

题目是随机的:bili_doge:

2026-10-19 08:49:46 UTC

- reply

我也很高兴认识你:bili_doge:中文不错呢，relay.nostrzh.org 加入需要做几道简单的测试题，希望你能通过

2026-10-19 08:23:55 UTC

- reply

Thanks for the kind words ☺

2026-10-19 07:54:00 UTC

- reply

来 wss://relay.nostrzh.org

2026-10-19 02:13:43 UTC

- reply

There’s no single right answer, but adding multiple servers is generally better. That way, your uploads can be stored on more than one blossom server, so even if I delete your files in the future, people can still access copies on the others.

2026-10-19 01:33:59 UTC

- reply

You could try https://blossom.jumble.social
It’s free, so there’s a file size limit, and I can’t guarantee files will be kept forever. If running costs get too high, I may periodically delete some older files. I haven’t deleted anything so far, though.

2026-10-18 14:15:59 UTC

Psst... something new is brewing 👀
https://blossom.jumble.social/1014b6a6718869c21d20f37170adca580755e9b9603093dece2b4ae7d0fc2ee5.png
https://blossom.jumble.social/392b3b0000e37fcd2933daf480b3f3c90faefce4c782d5b875e524184a6c6330.png

2026-10-17 02:05:01 UTC

- reply

那是用户名首字母分组你这个应该是没设置名称吧所以放到 ? 分组了哈哈确实有些迷惑

2026-10-16 13:39:37 UTC

- reply

I’d definitely recommend creating a new account to try it out. It’s not compatible with the other clients anyway

2026-10-16 12:27:41 UTC

PsstPsst is now open for public testing on TestFlight! 🎉
https://testflight.apple.com/join/5J4qhthx
If you’re on iOS, give it a try and let me know what you think!
https://psstpsst.chat
https://blossom.jumble.social/3526e1e7ff49132877a230378af3ecd4665e70bfe593c029c9e65246a298f88b.png

2026-10-16 09:20:51 UTC

- reply

It's time for clients to let relays handle building the following feed.

2026-10-16 07:08:25 UTC

- reply

Looking forward to having you back! 😊

2026-10-15 14:00:01 UTC

- reply

I still need some time to explore and understand it better, but I genuinely believe in the model, that’s why I added pomegranate support to jumble.
For psstpsst, though, I’m hoping to introduce it to more of my non-technical friends. Given the reliability concern I mentioned above, I’ve held off on adding it for now.

2026-10-15 04:26:47 UTC

- reply

My main concern is Pomegranate’s reliability. Non-technical users who sign in with Google may never bother to back up their nsec. If the Pomegranate service goes down, they could be left with no way to access their account.

2026-10-15 01:17:06 UTC

- reply

I’ve been exploring napps lately too, and I’m planning to add a napp runner to PsstPsst

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.

2026-09-16 08:42:30 UTC

- reply

You’re right, this is indeed a problem. My current solution is relatively simple: when a user rotates their encryption key, they don’t immediately discard the old key. They keep it around for a period of time so they can still decrypt messages that were encrypted with the old key by senders who haven’t received the latest key announcement yet and are still encrypting messages with the old key.

2026-09-16 01:24:35 UTC

- reply

Yes, it’s on the roadmap. :)

2026-09-15 09:13:05 UTC

- reply

Thanks! Just a small note though: this is a NIP-17 implementation built on top of NIP-4e, so it won’t be compatible with NIP-17 in most other Nostr clients.

2026-09-14 15:51:38 UTC

- reply

The issue may be fixed now. If you still run into it, feel free to let me know anytime.

2026-09-14 15:51:19 UTC

- reply

The issue may be fixed now. If you still run into it, feel free to let me know anytime.

2026-09-14 15:51:05 UTC

- reply

The issue may be fixed now. If you still run into it, feel free to let me know anytime.

2026-09-14 06:08:03 UTC

- reply

#nevent1q…55ft

2026-09-14 02:39:05 UTC

- reply

Got it 🫡

2026-09-14 02:38:27 UTC

- reply

Thanks!

2026-09-13 15:28:22 UTC

- reply

Thanks so much for the feedback, it sounds like I still have more testing to do. I haven't run into any crashes on my Android device, but someone else just reported the same issue to me as well, so it's definitely something I need to look into.

2026-09-13 14:45:17 UTC

- reply

You can just choose not to use it 😂

2026-09-13 14:44:36 UTC

- reply

Got it

2026-09-13 14:17:42 UTC

- reply

Very hard, especially for a DM app

2026-09-13 13:56:43 UTC

Hi everyone! I’d like to share PsstPsst, a messaging app I’ve been working on over the past three months through vibe coding.
https://psstpsst.chat
It’s intended for staying in touch with friends and family, and supports iOS, Android, macOS, Linux, and Windows. Releases are currently available for all platforms except iOS.
I haven’t had a chance to test the Linux and Windows builds myself yet. If you try either and run into any problems, I’d really appreciate hearing about them.
PsstPsst is built on NIP-17 with NIP-4e, which separates encryption keys from identity keys. This means it isn’t compatible with most existing Nostr clients.
You don’t need to think of it as a Nostr DM app, though. I’ve tried to keep Nostr terminology out of the app and make it approachable on its own. My hope is that people can generate a fresh key and use it with their friends and family.
Why NIP-4e?
With a separate encryption key, the app doesn’t need to repeatedly request encryption and decryption operations from your identity key. This makes it possible to use the app with a bunker remote signer.
Encryption keys can be rotated periodically, so a leaked key won’t expose your entire message history.
A few things I’d like to add over time:
- Small group chats, likely limited to 10 people or fewer. NIP-17 isn’t well suited to large groups, and small circles feel like a good fit for the app’s focus.
- Voice and video calls.
- A built-in browser for napps.
- Communication without an internet connection, using FIPS.
There’s still plenty to improve, but I hope some of you might find it useful. If you feel like giving it a try, I’d be grateful for any feedback or bug reports. Thanks for taking a look!
https://blossom.jumble.social/b5761bc7a6986333d27efc67dd9fec204e08b6b0828dd8d36a1abb64a0bc6f15.png
https://blossom.jumble.social/3526e1e7ff49132877a230378af3ecd4665e70bfe593c029c9e65246a298f88b.png

2026-09-09 02:05:59 UTC

- reply

Cool, I'll add po.oslim.dev to Jumble's default operators.

2026-09-08 04:17:24 UTC

- reply

Got it 🫡

2026-09-06 15:47:58 UTC

- reply

The key never exists on any server. The client splits it into shares and stores them across multiple operators. Google is only used for authentication, to prove to the operators that those shares belong to you.
So the Google identity and the key are separate, you can bind any key to your Google account.

2026-09-04 14:39:37 UTC

- reply

I think Pomegranate's approach is better. https://viewsource.win/fiatjaf.com/pomegranate/_/master

2026-09-03 04:13:29 UTC

- reply

Sounds good to me. I’ll add support for it later today.

2026-09-01 09:12:38 UTC

- reply

But that would leave a lot of empty space unused. I’m actually considering changing it to a horizontally scrolling layout like X’s image gallery instead.
https://blossom.jumble.social/ccc206a470446e4fc62fab3451f55f69afc8eda0bb61b4c5a805275946624b72.png

2026-08-25 14:11:43 UTC

- reply

For now, the code is only hosted on GitHub because I still rely on GitHub Actions. Do you not have a GitHub account, or are you unable to submit a PR? If it’s the latter, please try again. I just realized I’d blocked PRs from first-time contributors because I was getting so many spam PRs from bots.

2026-08-24 14:35:36 UTC

- reply

You can make integrating the WebTorrent player a second PR. Maybe I was overestimating the complexity of it.
I can't guarantee that I'll merge it yet though, I need to understand the impact better before making a decision. If it's lightweight and doesn't affect relay connections, I think it could be acceptable.
Currently, relay connections are already frequently blocked by browsers, so I'm not sure whether adding a WebTorrent player would make this issue worse.

2026-08-24 14:32:11 UTC

- reply

Sure, feel free to submit a PR. Thanks!

2026-08-24 02:15:09 UTC

- reply

I still don't think it makes sense to bake it into the client. I'm fine with just clicking through to an external app or site to watch.

2026-08-23 03:55:26 UTC

- reply

I think it’s a bit too heavy for Jumble. :catLurk:

2026-08-22 16:08:13 UTC

- reply

If it only means supporting kind 2003 events for display, and clicking them simply opens the local torrent client for downloading, I would be okay with that.
However, I don't want to add support for creating kind 2003 events in the post editor.
Also, I don't quite understand why comments on these events use kind 2004 instead of using kind 1111 events. Is there a specific reason behind this design choice?

2026-08-19 10:20:46 UTC

- reply

Got it 🫡

2026-08-19 03:18:41 UTC

- reply

That said, cached avatars are a pain to keep in sync across devices and clients, it doesn't really address the root problem. If someone wants to be recognized, they won't be constantly swapping out completely different avatars and display names. And if they'd rather not be recognized, that's their prerogative. Let them change it.

2026-08-19 02:57:30 UTC

- reply

I understand what you mean. The problem is I couldn't find a better way to indicate that the user themselves reacted. Using the specific emoji makes it clearer that you used that reaction, but I agree it can also be interpreted as the total count for that specific emoji.

2026-08-18 15:40:27 UTC

- reply

Ah, I think I see what's confusing you. That emoji is the one from your last reaction, the number next to it is the total reaction count on that note. If you hadn't reacted to it, it would look like what I see instead.
https://blossom.jumble.social/31e202f63a2f0305310c2e6dde2f81f16bb7f89b50d14c745569f835cfd1958b.png

2026-08-18 14:04:11 UTC

- reply

Grouping them would definitely be a better experience. Most clients haven't done it because relay event queries are pretty limited, and matching centralized platforms is tricky. But I'll try to optimize toward that.

2026-08-18 13:59:23 UTC

- reply

If you run into this again, could you paste the note here? That way I can dig into what's causing it. Thanks!

2026-08-18 01:49:58 UTC

- reply

A kind 10044 event with empty tags has a specific meaning, it can be used to announce that you're no longer using NIP-4e. So it shouldn't be treated as an anomaly and auto-updated.

2026-08-18 01:45:06 UTC

- reply

you can find the download link in the settings