Cody

I understand what you mean, and I agree with your point.
What I was trying to emphasize earlier, though, is that many clients make signing and encryption/decryption requests far too frequently, which creates a very poor experience for users relying on bunkers or browser extensions.
For example, the first time you use a client with NIP-17 DMs, your signer may receive hundreds or even thousands of decryption requests. If you are using a bunker, many of those requests may not even reach it because relay rate limits block them first. With a browser extension, meanwhile, the only practical option is often to trust the client and approve all decryption requests at once.

2026-07-17 09:30:37 UTC

Since several major Blossom servers currently do not support uploading encrypted files, Jumble cannot send files in DMs.
So I’m running a simple Blossom server at https://blossom.jumble.social . Feel free to use and test it.
The current file size limit is 20 MB. I may periodically clean up files in the future depending on operating costs, so it’s better to use it together with other Blossom servers.

2026-07-17 01:14:38 UTC

- reply

I assume you gave Amethyst full permissions through the bunker and didn’t review each request individually. That’s not fundamentally very different from giving the app your keys directly, the main difference is that you can revoke the access and walk away at any time.

2026-07-16 15:23:10 UTC

- reply

I’d rather not have Jumble make frequent decryption requests during normal use, so I’m not planning to implement this feature there. Wisp and Amethyst are different, they hold the user’s keys, so they don’t have to worry about this issue. They can use the keys however they want.

2026-07-12 12:19:52 UTC

- reply

是的，上传的是加密后的文件

2026-07-12 09:28:33 UTC

- reply

Any progress on this? Currently, several major blossom services no longer accept `application/octet-stream` files and return a `415 Unsupported Media Type` error. This prevents NIP-17 DM clients from sending encrypted images/files.

2026-07-07 13:58:56 UTC

- reply

I never said that. In fact, without OpenSats, Jumble might not even exist today.

2026-07-06 04:01:36 UTC

A better way to browse your following feed
#nevent1q…tree

2026-07-04 13:42:33 UTC

- reply

When WoT mode is enabled, it only accepts events that come from the WoT. It doesn’t actively fetch or pull any events on its own. Tray is just a normal relay.

2026-07-04 09:28:12 UTC

- reply

Tray doesn’t support this feature yet, I’ve been procrastinating on it, haha.

2026-07-03 03:58:59 UTC

- reply

Because the URL doesn’t include a file extension, Jumble can’t quickly infer that it’s an image. In theory, you could solve this by sending a `HEAD` request for every URL to check the `Content-Type`, but that runs into a practical issue: a lot of these URLs are blocked by cross-origin restrictions.
Browsers simply don’t allow a webpage to fetch or inspect headers from cross-domain URLs unless the server explicitly enables CORS. I just checked `pbs.twimg.com` as well, and it has those cross-origin limitations too, so the client wouldn’t be able to reliably probe it anyway.

2026-07-03 01:16:38 UTC

- reply

Jumble only removes image metadata (like location data) and does not compress the image. The softness is likely caused by the media upload service you’re using.

2026-07-01 01:21:50 UTC

- reply

I’m just using it for coding. Even in a 5-hour window I usually only use about 30% of the usage limit. Might just be something like nationality/region-based restrictions lol.

2026-06-30 15:26:28 UTC

- reply

Jumble’s DM protocol isn’t compatible with most other apps. The keys used for encrypting DMs are separate from the user identity keys, which makes it more friendly for users with remote signers. On top of that, rotating the encryption keys periodically provides a small degree of forward secrecy.

2026-06-30 03:30:40 UTC

- reply

Yes, but my American colleague’s account was also banned.

2026-06-30 03:28:37 UTC

- reply

Because I’m Chinese, but even my American colleague’s account got banned too.

2026-06-30 03:10:22 UTC

- reply

I think a new account probably wouldn’t last very long either, haha.

2026-06-30 03:01:46 UTC

- reply

Using the API is too expensive. 🫠

2026-06-30 02:41:05 UTC

:sadCat:
https://npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl.blossom.band/0cf542e4290ca1e30551546da942416b1d357f90c7a73fd37d0c11dd0361517b.png

2026-06-27 04:56:51 UTC

- reply

Yep, I applied the same fix to the other NIP-51 lists too. If I missed any, feel free to let me know.

2026-06-26 15:11:32 UTC

- reply

Not sure, but I don't think mutelists have that issue. :TheVoices:

2026-06-26 14:35:42 UTC

- reply

Fixed, thanks for the report!

2026-06-26 01:19:20 UTC

- reply

I understand. It definitely makes the user experience worse when people have to understand which third-party services they're using and pay for each of them separately.
That said, if clients decide which relays and media upload services to pay for on behalf of users, the Nostr network will eventually become more centralized. I think it's better for users to make that choice themselves.
Also, you don't need to pay for 20 relays. With the outbox model, most people only need around 3–4 relays.

2026-06-21 09:39:52 UTC

- reply

Got it 🫡

2026-06-21 09:39:24 UTC

- reply

I think the problem is that fiatjaf replied with kind 1111. After that, everyone replying to that comment also ended up posting kind 1111 events, so clients that don’t support kind 1111 can’t display those replies properly.
#nevent1q…yhtq

2026-06-21 09:34:23 UTC

- reply

Using blossom.band returns a 415 unsupported media type error.
What kind of identifier are you looking for? I’d be happy to add support for it in Jumble.

2026-06-20 06:57:43 UTC

- reply

Sorry about that. I'll investigate what caused it. Thanks for the report!

2026-06-19 16:56:12 UTC

- reply

Google login also uses NIP-46 remote signing, so it has the same issue.
There doesn't seem to be much progress on https://github.com/nostr-protocol/nips/issues/1712 yet.

2026-06-19 12:28:24 UTC

Finally, clear skies after a week of rain.
https://blossom.primal.net/871c3ea9260b55da60fa87bd1f9ff2ff10b0340b5f0411be09d22309139410ba.jpg

2026-06-18 01:50:10 UTC

A friend of mine made a Chrome extension called Better GitHub.
One feature I really like is the enhanced user hover card. It shows more useful account info, making it much easier to spot spam accounts.
If you're also dealing with lots of spam PRs, give it a try.
https://github.com/rrbe/better-github
https://blossom.primal.net/dd43bc8b1fc9314ca13957fe4896fb2c09fb8344ca8e80e63218355a96c3c5f8.png

2026-06-15 13:54:07 UTC

- reply

People have to make it into your playground first. Then they can leave Google behind.

2026-06-15 13:48:10 UTC

- reply

I couldn't think of a good reason to say no. The only thing I'm not entirely happy with is that the central server still isn't mature enough. Users can't manage permissions very granularly yet. But I'm confident fiatjaf will keep improving it.

2026-06-15 01:26:22 UTC

- reply

By default, it's https://auth.njump.me/

2026-06-15 01:25:25 UTC

- reply

That message appears whenever the signer doesn't respond within one second. It's the same issue you see when using Amber.

2026-06-14 15:24:40 UTC

- reply

Just disconnect your account and connect it again haha.

2026-06-14 10:26:21 UTC

- reply

Good call, noted!

2026-06-14 10:25:18 UTC

- reply

To split your key into shares and distribute them across operators, Jumble needs the key itself, so linking Google is only available for nsec users. With Amber, your key stays external and Jumble never sees it.

2026-06-14 05:59:28 UTC

- reply

Gives new users a simple way to get onboarded.

2026-06-14 05:32:15 UTC

Jumble now lets you sign up or log in with Google. It is not custodial, no server ever holds your key.
Your private key is split into shards and signing uses FROST threshold signatures. Two roles cooperate:
- Central server: the coordinator that verifies your Google sign-in and relays NIP-46 signing requests to the operators. It never holds a shard or your key.
- Operators: independent servers that each hold one shard of your key. No single operator can sign on its own, signing needs a threshold of them.
Google is only used to prove it is you, it never touches your key.
If you already log in with an nsec, you can link a Google account under Settings → Account.
Powered by Pomegranate: https://viewsource.win/fiatjaf.com/pomegranate/_/master

2026-06-12 08:34:22 UTC

- reply

I took a quick look at the Chinese translation, and it looks pretty good overall.

2026-06-11 14:00:10 UTC

- reply

:confusedCat:

2026-06-11 13:59:22 UTC

If you see a custom emoji on Jumble that you find interesting, try clicking it.

2026-06-11 01:11:24 UTC

- reply

I think it's fine. People can already repost and reply to their own posts, so reacting to your own note doesn't seem too strange to me.

2026-06-10 15:17:35 UTC

- reply

I think it should be solved by having more blossom cache servers over time, acting like CDN edge nodes.

2026-06-10 14:37:29 UTC

- reply

I don’t think this should be handled by the client. Otherwise, while loading the resource, the client would also have to keep signing the auth tokens needed for mirroring the blob.

2026-06-10 14:18:32 UTC

- reply

Any blob you upload will be mirrored to all servers in the blossom server list. If you've configured a cache server, Jumble will try to load blobs from the cache server first.

2026-06-10 14:09:19 UTC

- reply

You just need to add that server to the Blossom server list as well.

2026-06-10 09:21:30 UTC

- reply

会发送至提及人自己设置的 read relays

2026-06-10 01:39:29 UTC

- reply

What's this?

2026-06-09 13:51:14 UTC

Hi @npub180c…h6w6! It looks like pomegranate can't sign events with timestamps in the past. This prevents building NIP-59 seal events.
Error: `can't sign event in the past`

2026-06-09 02:25:21 UTC

- reply

I agree 👍

2026-06-07 02:41:11 UTC

- reply

Sorry about that. He doesn’t work for me and we have no business ties, so it’s not really my place to control what he says. I’ve told him before it’s not a good look though, Nostr needs different clients, and users should use whatever they like.

2026-06-06 17:10:33 UTC

- reply

Some users consider it private, so Jumble doesn't add the client tag by default.

2026-06-06 16:58:37 UTC

- reply

That's because you, as the CMO, forgot to enable the client tag on your posts 🤣

2026-06-05 16:20:25 UTC

- reply

That’s not supported yet. I’m planning to add it this weekend

2026-06-05 15:23:24 UTC

- reply

You're right. The bunker login should have a timeout, and if it times out, the user should be able to retry or cancel.

2026-06-05 15:12:08 UTC

- reply

I tried it on Firefox and it works fine on my side. From your screenshot, it looks like it's stuck at the bunker login stage, the registration already went through, so it might be an issue with relay connections.

2026-06-05 01:29:04 UTC

- reply

Looks like I'll need to test that on the desktop app as well.

2026-06-05 01:10:09 UTC

- reply

What error are you seeing?

2026-06-04 10:54:33 UTC

- reply

Yeah, I was thinking the same thing. You can now set a custom blossom cache server URL.

2026-06-04 10:19:11 UTC

Hi @npub13sy…gns9, the Blossom cache server is now disabled by default. Enable it in Settings → System to use it.

2026-06-03 14:52:15 UTC

- reply

Yes, it’s in the plans.

2026-06-03 01:56:15 UTC

- reply

Cool!

2026-06-02 16:20:15 UTC

- reply

Cool! If you use AI, you can let it periodically sync upstream bug fixes and any features you want.

2026-06-02 16:14:57 UTC

- reply

Thanks 💜

2026-06-02 16:14:34 UTC

- reply

Thanks 💜

2026-06-02 15:49:59 UTC

Grateful to OpenSats for the support. First interview and a really fun, unique experience.
#nevent1q…jpsk

2026-06-02 14:01:15 UTC

- reply

Which relays are anonymous notes published to?

2026-06-02 13:58:03 UTC

- reply

I don't think there's much point in doing that, since Jumble will show your own posts in the following feed whether you follow yourself or not.
If you really want to edit it, you could try using https://listr.lol and see if it lets you remove yourself from your contacts.

2026-06-02 06:48:47 UTC

Ran the wrong command just now, and my first instinct was esc, not ctrl+c 😂

2026-06-01 14:05:41 UTC

- reply

I think @npub1vxd…rs50, @npub1a4w…cxw0, and @npub13sy…gns9, among others, are always willing to test things and report bugs. A big part of Jumble's stability comes from their feedback and bug reports.

2026-06-01 13:57:37 UTC

- reply

I DM'd you because I can't retrieve the key shards from po.f7z.io and po.nostrver.se. When I try to authorize with Google OAuth, I get this error:
"Access blocked: This app's request is invalid."
I also run an operator at https://po.jumble.social

2026-06-01 13:54:36 UTC

- reply

Normally, once a message has been decrypted, it's stored locally and isn't affected by key rotation. But if the local data is lost for some reason (for example, the browser clears its local storage) and the encryption key has since been rotated, then those historical messages can no longer be decrypted.

2026-06-01 02:34:11 UTC

- reply

Please check your DMs on Jumble or Coop, sir.

2026-06-01 02:17:43 UTC

- reply

Sure. What exactly would you like me to add? Do you mean logging the events sent to and received from the remote signer?

2026-05-31 02:35:10 UTC

- reply

It looks like your network might be having trouble reaching Primal Blossom. I'm able to load the image on my end.
https://blossom.primal.net/3d1ce7d19ba322177715860598a8121555cf08156aecc2951f1b396f95e70f51.png

2026-05-31 02:32:41 UTC

- reply

I tried reproducing it, and it doesn't seem to be related to notifications. It looks like something else caused the editor to close unexpectedly.

2026-05-30 05:13:41 UTC

- reply

The desktop app isn't limited by the browser's relay connection limits. If you often see relay connection errors or have trouble sending notes, it's worth giving it a try.

2026-05-29 15:33:45 UTC

- reply

The draft box already kind of handles that.

2026-05-29 15:22:56 UTC

- reply

You can try again in a bit and see if you’re able to tap send directly now. Hopefully this fixes the issue for you. Latest commit hash is `98f07ca`.

2026-05-29 15:14:15 UTC

- reply

There are still a few issues to figure out first. But honestly I don’t think performance will change much. I mostly want it to help with network related issues.

2026-05-29 15:09:31 UTC

- reply

I’ll take a look. This seems to depend on the OS and browser behavior, on my side I don’t need to close the keyboard first.
Also, Jumble really doesn’t seem very smooth on your phone :TheVoices:

2026-05-29 02:16:28 UTC

- reply

Yeah, which makes it really hard to troubleshoot.

2026-05-29 01:51:44 UTC

> The main problem of course is that it costs the slopmaker perhaps a minute to generate their submission. But it costs us hours to read, understand, and engage with them. And they can be generated at a semi-infinite pace.
https://turso.tech/blog/the-wonders-of-ai

2026-05-29 01:10:30 UTC

- reply

I don’t really have a good solution for this either, which is why I’ve never implemented it. And over time I’ve started to feel that petnames might not be that necessary for Twitter-like social clients. If you want to build influence, you usually won’t change your username or avatar randomly anyway.
Petnames probably make more sense in clients centered around people you actually know, like DM-focused social clients.

2026-05-29 01:04:54 UTC

- reply

Did you mute them? 🤔 Or maybe try lowering the trust score?

2026-05-28 13:49:22 UTC

- reply

Thanks for sharing the extra details. If you have the time and feel like helping me investigate it further, I’d definitely appreciate any feedback or screen recordings.
But if you don’t have the time, that’s totally fine too, this isn’t your responsibility, so don’t feel any pressure about it.
Hope you have a great day 🫶

2026-05-28 13:43:25 UTC

- reply

Got it 👍

2026-05-28 13:42:54 UTC

- reply

I’m a bit concerned that petnames could leak privacy, since as far as I know they’re public (though I’m not sure if that has changed now).
That said, I do admit they’re pretty useful. Some users change their avatar and username so often that it becomes hard to keep track of who’s who.

2026-05-28 07:06:32 UTC

- reply

I’ll keep an eye on it. The emoji picker can be a bit laggy right now, I haven’t optimized it yet.

2026-05-28 04:32:54 UTC

- reply

I checked the DM relays you configured and only found `wss://spatia-arcana.com/inbox`. My guess is that the issue happens because this relay does not accept the events used for encrypted key synchronization.
It looks like relying solely on user-configured DM relays for synchronization is not sufficient. I’ll add some public relays as fallbacks to avoid this issue in the future.

2026-05-28 03:37:41 UTC

- reply

@npub1gm7…8rf6 fixed this a while ago.

2026-05-28 01:18:32 UTC

- reply

Some emojis failed to load and fell back to displaying their short codes instead. I’ll find some time to fix it today.

2026-05-28 01:14:02 UTC

- reply

No worries, just use the client that works best for you. I’ll take a closer look into what’s causing this issue and see whether the UI/UX can be improved.
Ideally, when device B doesn’t have the encryption key, it sends a key sync request. Then, when you open the app on device A (the one that already has the key), you should see a popup asking whether to sync the key. Pressing the "Send Key" button should then send the key to device B.
If it’s convenient, could you tell me whether:
1. You never saw the sync request popup on device A, or
2. You pressed "Send Key" but nothing happened afterwards?

2026-05-26 14:49:36 UTC

- reply

Thanks 💜

2026-05-26 14:47:38 UTC

- reply

Thanks 💜
You finally gave your avatar a white background 😇

2026-05-26 14:46:38 UTC

- reply

Thanks 💜

2026-05-26 14:46:20 UTC

- reply

Wisp is already a new legend 🔥

2026-05-26 14:10:36 UTC

- reply

That happens when the browser loads HTTP resources (like images or videos) posted by other people, or when it connects to ws:// relays. In those cases, the browser marks the page as not secure.

2026-05-26 14:08:54 UTC

- reply

Thanks for the kind words 💜