Cody

Building 👨‍💻
https://jumble.social/
& nostr-relay-tray

Public Key

npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl

NIP-05 Address

Profile Code

nprofile1qqsgzfdez8ksa9xmuvqg5zly3nl9e5xqkpvj8nllj9aw06ra4pqq3qcpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsc8ekkl

Publishing to

relay.damus.io

nos.lol

Author Public Key

npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl

Show more details

Last Notes

2026-07-07 13:58:56 UTC

- reply

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

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 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 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: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-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: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: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-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-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 01:10:09 UTC

- reply

What error are you seeing?

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-02 16:14:57 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-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 02:34:11 UTC

- reply

Please check your DMs on Jumble or Coop, sir.

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-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-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 💜

2026-05-26 14:07:55 UTC

- reply

Cats Saving the World :RAGEY:

2026-05-26 03:05:10 UTC

https://blossom.primal.net/ca8b69f1e8b50c845ff2b0c08e86586cb368b3f8b8d78e77e4aafedda225c686.mp4

2026-05-24 15:04:34 UTC

- reply

The reset key feature currently has some issues. It should already be fixed on the web version a few days ago, but I haven’t had a chance to update the desktop client yet.
For now, you can reset the key in the browser version first. I’ll try to release a new desktop version as soon as possible.
If you run into any other issues, feel free to mention me anytime.

2026-05-24 02:56:43 UTC

- reply

While waiting for it to sync, did you click "Send Key" in Safari?

2026-05-21 03:30:18 UTC

- reply

If you copied it from nostrord, then it looks like there’s an issue with how it generates the id.

2026-05-21 03:04:04 UTC

- reply

For reposts, any zap goes to the original author, because Jumble actually doesn’t allow zapping a repost. Zapping a quote post won’t forward it to the original author.

2026-05-21 01:31:27 UTC

- reply

The `naddr1...` you copied can’t be decoded.
https://blossom.primal.net/85e6216e73b423018f75392c2dcd236b3537d76ff05c4c30332120634e909cd5.png

2026-05-18 09:12:13 UTC

- reply

Just a thought. Nostr feels like a natural complement to Silent Payments. The sender can wrap the txid in a NIP-17 encrypted event to notify the recipient, so they know exactly which transaction to verify locally with their scan key. Payments sent without a notification still need to be discovered through scanning, of course.

2026-05-14 15:11:31 UTC

- reply

The first launch can be a bit slow since it needs to load a lot of data. Is it still slow after you’ve used it for a while?

2026-05-13 14:47:16 UTC

- reply

Looks like I probably shouldn’t rely on syncing only through DM relays. Or maybe adding a manual import option would be a better fallback.
Thanks for the feedback!

2026-05-13 10:40:32 UTC

- reply

It’s possible that relay doesn’t support syncing the encryption key event? I’m not sure, I’ll take a closer look later. I’m still on my way home.
In the meantime, you could also try resetting the encryption key on desktop and then attempting to sync again.

2026-05-13 10:31:37 UTC

- reply

Are you able to send messages on desktop now? You could also try changing your DM relays and test again.

2026-05-13 10:21:22 UTC

- reply

When you open Jumble on the device that already has the encryption key (your desktop), do you not see the popup to sync the encryption key?
https://blossom.primal.net/2a800aeb7dd5b2fc7d98f0f547391e796b5c4da7d20fa868a82e8fa4a804eea0.png

2026-05-12 04:03:24 UTC

- reply

I love that old hag too fr =ω=
https://blossom.primal.net/467833117cc45b3cf7661d9be6c57563c6d7d66854e75f9031cd370215f33dd3.jpg

2026-05-09 13:51:09 UTC

- reply

Thanks for the report. Don’t worry, your content wasn’t modified, it’s just rendering incorrectly in Jumble. I’ll get it fixed shortly.

2026-05-08 15:33:51 UTC

- reply

Looks like Alby was having some issues earlier.
https://alby.instatus.com/

2026-05-08 08:03:08 UTC

- reply

Noted, thanks!

2026-05-08 01:23:45 UTC

- reply

Personally, I don’t think the EU would block every suspicious IP. Even China hasn’t gone that far.
And if they ever do, the bigger issue would be how to connect to relays in the first place. At that point, maybe using Nostr wouldn’t even be the main concern anymore. There’d probably be more important things to worry about.

2026-05-07 12:14:33 UTC

- reply

A thin native shell wraps the web app to bypass browser restrictions.

2026-05-07 10:26:25 UTC

- reply

I’ll try my best, hopefully Apple goes easy on me.

2026-05-07 10:23:43 UTC

- reply

I’m not sure if it’ll make it onto the App Store though haha.

2026-05-07 10:20:03 UTC

Okay, I’m going to make a wrapped native mobile app for Jumble. 😌

2026-05-03 11:14:56 UTC

- reply

Looks great!

2026-05-02 15:58:53 UTC

- reply

This will be supported in the next version.

2026-04-30 15:24:18 UTC

- reply

Sorry about that, I’ll look into improving it.

2026-04-30 04:20:31 UTC

- reply

Yeah, that’s a fair point, but the underlying issue is a bit deeper.
Media upload services require ongoing funding to operate, and unlike traditional internet companies, we don’t really have a strong revenue model backing this. So it’s not hard to imagine a future where free media upload services become very limited or even disappear entirely. In that context, automatically retrying different servers doesn’t really solve the root problem.
A more sustainable approach might be to provide clearer error messages and guide users toward paying for reliable upload services. That way, the ecosystem can actually sustain itself instead of relying on a shrinking pool of free options.

2026-04-30 01:51:39 UTC

- reply

You can try switching the media upload service in Settings → Post settings. Jumble doesn’t provide its own upload service, it uses nostr.build by default, and you may have hit its free upload limit.

2026-04-28 02:14:28 UTC

- reply

I can’t guarantee that haha, but supporting direct URL input for avatars and banners is definitely necessary.

2026-04-28 02:13:09 UTC

- reply

I really couldn’t fetch metadata for those users. @npub1gcx…nj5z, how did you manage to get them?

2026-04-22 15:12:07 UTC

- reply

you’ll like it :doge:

2026-04-22 15:07:31 UTC

- reply

As long as you keep using it, you’ll come across small updates and little surprises from time to time. Isn’t that more fun than having an update banner?

2026-04-21 16:38:03 UTC

- reply

Coop https://github.com/lumehq/coop

2026-04-21 15:25:26 UTC

- reply

Glad to hear that :MEOWDY:

2026-04-21 01:42:23 UTC

- reply

These relays aren’t just for your own use. Other people need to query your write relays to fetch the events you publish, and your read relays to find events that mention you.
Clients usually need to fetch data for many different users, so it’s not realistic for them to connect to every relay each user has configured. In practice, most clients will only use the first 2 to 4 relays.

2026-04-16 15:09:00 UTC

Not enough voters yet so nothing hit the threshold lol. Added a self-evolution mode where the agent thinks for itself about what to improve and ships it when no community request qualifies.
#nevent1q…urwy

2026-04-15 13:59:19 UTC

- reply

I like this approach.

2026-04-15 13:57:27 UTC

- reply

https://ouro.jumble.social/

2026-04-15 10:17:06 UTC

- reply

I think it’s a really interesting idea, but the cold start might be tough. Creators would be paying for exposure, which usually means they’re not already influential, and that only works if the relay already has a large, active audience.

2026-04-14 15:55:15 UTC

- reply

You could try that, but I’d recommend just giving it the relevant documents and letting it figure things out on its own.

2026-04-14 15:24:52 UTC

- reply

Please don’t submit PRs, I’d like this project to iterate on itself via AI, so just describing the requirements clearly is enough.

2026-04-14 14:34:40 UTC

- reply

Just open an issue and get support from others.

2026-04-14 10:18:59 UTC

An experiment: Jumble Ouro, a fork of Jumble where what gets built is decided entirely by community votes.
Open an issue, people 👍 / 👎 it, and every day at 20:00 UTC the top-voted one gets picked up, implemented, and merged by an AI agent. No humans in the loop. Needs net score ≥ 5 for now; the threshold may change later.
Come propose, come vote. Let's see where it grows.
Try it: https://ouro.jumble.social/
Repo: https://github.com/CodyTseng/jumble-ouro

2026-04-04 06:13:27 UTC

- reply

I think the features are already pretty complete. From here on, most of the work is about improving the experience and fixing bugs. So a lot of updates might not be very noticeable from the user side, it’s not that development has stopped 😂

2026-04-02 10:28:17 UTC

- reply

Yeah, just putting your Signal/Whisper/TG/... in your bio is probably better lol

2026-04-02 01:28:36 UTC

- reply

Chat is currently being tested on https://beta.jumble.social . It uses NIP-4e (https://github.com/nostr-protocol/nips/pull/1647), where the encryption key is separated from the user key, which works better for users with a bunker remote signer. However, it’s only compatible with Coop for now.