Cody

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

Public Key

npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl

NIP-05 Address

Profile Code

nprofile1qqsgzfdez8ksa9xmuvqg5zly3nl9e5xqkpvj8nllj9aw06ra4pqq3qcpp4mhxue69uhkummn9ekx7mqpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq4camnwvaz7tmswfhhs7fwdehhxarj94ex2mrp0yhxzurs9ask2vesvfsnyvehxf3k2epkvvcnjd3svs6rjcesxgmrvenyvsek2vphvdjkzdfjvgckye3nxuuxverzxcurgct9v5mrxd3nv3jkxdpkqyvhwumn8ghj7urewfsk66ty9enxjct5dfskvtnrdaksk3fqgy

Publishing to

nos.lol

relay.damus.io

proxy.nostr-relay.app/ae30ba2372ced6c1960d49c0266fdd3e07cea52b1bf378fdb684aee6363dec46

pyramid.fiatjaf.com

Author Public Key

npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl

Show more details

Last Notes

2026-03-06 17:23:47 CET

- reply

No worries at all, feel free to submit a PR anytime. 😊

2026-03-06 17:22:51 CET

- reply

Currently the shortcut is Ctrl + Enter (or Cmd + Enter on Mac), the same as when creating a post. This is just temporary though, I’ll listen to feedback and see which shortcut works best for everyone.

2026-03-03 14:53:12 CET

- reply

What I meant by building it on top of DMs mainly refers to the encryption/decryption protocol, not the DM feature itself.
Any encrypted content requires both the sender and the receiver to use the same protocol. Jumble plans to use NIP-4e to encrypt gift wrap events. At the moment, other clients don’t support this protocol, so even if I implement this feature, it may only allow private replies between a small group of users.
These replies would still appear in the comment section like normal comments, but they would only be visible to the intended participants.

2026-03-03 08:01:04 CET

- reply

This feature would need to be built on top of DMs, so I’ll only be able to consider it after Jumble supports DMs.
Also, since I’m planning to use a DM protocol that isn’t compatible with most existing clients, this feature might ultimately only be available to a small group of users.
That said, it’s definitely an interesting idea, and I do think I’ll end up implementing it.

2026-03-03 02:28:54 CET

- reply

Sure, feel free to submit a PR 🫡
https://github.com/CodyTseng/awesome-nostr-relays

2026-03-03 02:26:31 CET

- reply

This is actually a kind of DM as well, I find it pretty interesting too.

2026-02-28 08:12:17 CET

- reply

https://nostr.media/791857b50fadb704a2c5af91b78785de346a5d0e9275a85dee802e74623c4437.png
I agree, it's confusing.

2026-02-26 17:27:52 CET

- reply

I completely understand your concerns.
You’re absolutely right, and I’ve already made optimizations as you described. Logged-in users can continue using Jumble as themselves regardless of whether bunker is connected properly. However, there might still be issues when it comes to signing events. That said, the experience is much improved compared to before

2026-02-26 16:43:10 CET

- reply

Thanks for the feedback! I’ve made some optimizations, though I’m not entirely sure if they’ll resolve your issue.
Bunker remote signing isn’t very stable in browsers, especially when there are many relay connections. The browser may block new connections, which can cause the login state to appear inconsistent or get stuck spinning.
If you’re using Jumble on a desktop browser, using a browser extension signer may provide a more stable experience.

2026-02-24 03:51:50 CET

Every coffee shop should run a nostr relay instead of a message board :MEOWDY:
#nevent1q…9a64

2026-02-23 13:16:27 CET

- reply

First, just to clear up a misunderstanding: almost all of Jumble runs locally on your device. So there’s no real difference between using jumble.social and running it locally.
And actually, this happens because Jumble uses the outbox model. It fetches data from the outbox relays of the people you follow, which means it has to connect to a lot of relays. The more people you follow, the more relays it needs. I only follow a bit over 200 people, but Jumble still connects to dozens of relays just to load my following feed.
At that point, the browser starts blocking new connections. For example, if I try to like a note, it may need to connect to a few additional relays, but those connections just sit in pending, and the like can fail.

2026-02-23 10:22:44 CET

- reply

If you follow too many users and browse the following feed in Jumble, the experience can indeed be pretty bad.
Fetching content from the people you follow requires connecting to a large number of relays, and the browser will block some new connections, which can prevent certain operations from working properly.
Unfortunately, I don’t have a good solution for this at the moment haha. My recommendation is to fetch content directly from relays and only follow a small number of users. As nostr becomes more decentralized and everyone uses different relays, following feeds will become increasingly difficult to retrieve.

2026-02-19 08:02:39 CET

- reply

Jumble has used the outbox model from day one.

2026-02-16 06:50:53 CET

- reply

Jumble uses nostr.build as the default media uploader. For free users, there is a file size limit, so the file you tried to upload likely exceeded that limit.
You can try switching to a different media uploader in the settings, or upgrade to a paid plan on nostr.build to increase the file size limit.

2026-02-02 16:34:18 CET

- reply

I think there may be a bit of a misunderstanding about my concern. What I want is to be able to see and approve every single decryption request a client makes. With DM-capable clients today, that’s basically impossible in practice.
That’s why I think NIP-4e is necessary: it separates the keys used for DMs from the user’s main key. My main key may be used to encrypt other data, and I don’t want to grant a client the ability to decrypt everything just so I can use DMs, even if most clients are well-intentioned and won’t do anything malicious.

2026-02-02 16:15:35 CET

- reply

A big part of why I’ve always been resistant to NIP-17 is the UX: unless the user fully agrees to all decryption requests, the app basically becomes unusable. You just keep getting spammed with decryption permission pop-ups over and over again.

2026-02-02 15:09:19 CET

- reply

That branch is entirely AI-generated code. It implements the basic functionality, but it has a lot of issues. I found it pretty painful to work on, so I’ve been focusing on other things lately, DM will need to be delayed for a while. :doge:

2026-01-31 11:33:14 CET

Vibe coded a Nostr comment component :FLASHBANG:
https://nostr-comments.pages.dev/

2026-01-30 04:17:29 CET

- reply

This is key info.

2026-01-29 02:47:20 CET

- reply

Sure 👍

2026-01-26 08:39:46 CET

- reply

Jumble’s relay info is rendered just like a regular post, it supports images, embedded posts, and so on.

2026-01-26 04:55:24 CET

- reply

It’s mainly just my personal feeling that it’s not really necessary.

2026-01-26 04:35:19 CET

- reply

That’s still content they chose to publish, so of course it won’t be hidden from the timeline. What it does is prevent your notifications tab from being polluted, so you don’t miss important notifications because of all the noise.

2026-01-26 04:33:27 CET

- reply

I get what you’re asking for, and I understand the desire for that level of control. That said, the benefit of this feature doesn’t really feel worth the cost to me.
If it’s just a single note, it won’t stay in your timeline for long anyway—it’ll quickly get pushed out by newer content. But once you add a “hide this specific note” feature, every note would need to be checked against a list of notes you’ve chosen to hide before being shown. Sure, there are ways to optimize this, but the question is: is it really worth it?
That hidden-notes list would also keep growing over time. You might be disciplined and keep it small, but other users probably won’t, and that complexity adds up fast.

2026-01-26 04:23:09 CET

- reply

The purpose of “hide indirect” is to deal with hell threads, that is, to hide replies from other users to the note shown in your screenshot.
As for the case you mentioned:
* If the account is just spam, you can easily filter it out using the trust filter.
* If it’s a normal account but you personally find them annoying and don’t want to see their content, you can simply mute them.

2026-01-26 02:37:01 CET

- reply

The reason you’ve only run into it twice so far is simply because bad actors haven’t shown up yet. Once they do, blocking won’t really help.
Blocking the original user doesn’t solve the hell thread problem, because the issue isn’t the original note itself, it’s the flood of replies from many other people.
I think hiding indirect notifications is sufficient here

2026-01-25 17:35:31 CET

- reply

Honestly, manual blocking isn’t a real solution, this spam is super easy to mass-produce, so users can’t block every single one. Their blocklists will just keep growing unwieldy and ruin the client experience.

2026-01-25 15:36:42 CET

- reply

Click ‘hide indirect’ in the top-right corner.
https://nostr.media/f8b1b20740a8a10be80c5a61017347754388bd4110eda73ca66b8338c059a97b.jpg

2026-01-23 15:02:09 CET

- reply

Got it 🫡

2026-01-23 15:01:34 CET

- reply

Thanks for the feedback! It’s been a while since anyone last mentioned this, so I thought I’d already fixed it 🤣
Looks like I need to carve out some time to take a closer look again.

2026-01-23 04:48:41 CET

- reply

This isn’t your issue. If search.nos.today doesn’t accept report events, the error makes sense.

2026-01-23 04:45:21 CET

- reply

Reports are sent to the relay where the event was seen on. If that relay doesn’t support report events, getting an error is expected and normal behavior.

2026-01-23 04:05:15 CET

- reply

When Jumble receives an error that starts with `auth-required`, it will automatically trigger authentication. From your screenshot, though, search.nos.today is returning an error that starts with `block:`, so the auto-auth flow never gets triggered, haha

2026-01-23 02:37:58 CET

- reply

Jumble is fully client-side (no SSR), so it can’t provide link previews for shared posts. If njump’s reliability doesn’t improve, I may consider building a similar service.

2026-01-22 11:21:01 CET

- reply

That’s definitely an issue.

2026-01-22 02:16:52 CET

- reply

My guess is they were probably setting up a rizful wallet.

2026-01-22 02:14:07 CET

- reply

If we can identify exactly which post isn’t showing up, that would help a lot with troubleshooting 🫡

2026-01-21 14:47:48 CET

- reply

> Então, para eu ler todas as bobagens do nostr, coloco 100%, ou deixo em 0%, como está?
0%

2026-01-21 14:47:17 CET

- reply

It can be slower when you first use it, as many things need to load. After some time, once the necessary cache is built up, it should feel faster. Of course, it also depends on the device's performance and network speed.

2026-01-16 03:07:22 CET

- reply

If nostr keeps getting more decentralized, with everyone on different relays, pulling the following feed will get heavier for clients. Using relay feeds and following just a few people seems like a good way to handle it.

2026-01-16 02:43:15 CET

- reply

Absolutely, I get that. But the cost of showing them is pretty high right now, so I need to find a balance.

2026-01-16 02:40:32 CET

- reply

I don’t think that’s really doable, haha

2026-01-16 02:29:45 CET

- reply

This's an njump share link
https://nostr.media/42baccf49a026b8570e21799c8c3321e541d1adb4151480b0f9705538a7c6c58.png

2026-01-16 02:27:04 CET

- reply

Right now it uses a greedy algorithm to minimize the number of relays while still ensuring that each user is covered by at least two relays when fetching the following feed. That said, once you follow more than a couple hundred people, there’s really no way around connecting to a large number of relays no matter how you optimize it.
Also, read relays are mainly used to fetch events that mention you, essentially your notifications feed.

2026-01-16 02:22:37 CET

- reply

I’m not sure this approach fits a web client very well. My guess is that Notedeck works more or less like this.
The "background process" you’re describing might make more sense as a separate application, essentially a personal local relay that quietly collects your following feed in the background. Any client that supports browsing relays could then benefit from it.

2026-01-16 02:17:05 CET

- reply

Yes, that’s expected. Browsing the following feed can indeed be very slow, especially on first use and if you follow a lot of people.
Jumble first needs to fetch your follow list, then query each followed user’s relay list, and based on that connect to potentially hundreds of relays to retrieve their events...

2026-01-15 02:31:05 CET

- reply

Thanks ☺

2026-01-14 05:36:05 CET

- reply

That’s good news, I can handle it manually for now, and of course it would be nicer if the process could be automated. But it’s not a big deal, no rush.
By the way, I noticed that users added via the NIP-86 allowpubkey method don’t seem to get updated in the 13534 membership list event.

2026-01-12 16:05:43 CET

- reply

Most clients support this now, so even if you only have a couple of read relays configured, you should still see replies from most people in your notifications.

2026-01-12 16:01:43 CET

- reply

Because @npub1hqa…t56s's client didn’t send the event to your read relays :)

2026-01-12 15:41:49 CET

- reply

Could you share an example? I can look into it and add support when I get the time.

2026-01-12 15:40:02 CET

- reply

You mean expanding a discussion/thread directly in the feed? If so, I think nosotro works like that, if I remember correctly.

2026-01-12 15:37:43 CET

- reply

Because of how the Nostr protocol works, preloading that kind of data isn’t trivial and would significantly increase bandwidth usage and computation. That’s why I chose to load likes, replies, and similar data only when a note is opened.
I also personally prefer that users open a note because of its content, rather than being influenced by how many likes or reposts it already has :)

2026-01-12 11:46:15 CET

- reply

An ambitious goal! 🫡

2026-01-12 11:35:22 CET

If you want a more organized way to browse threads, give https://jumble.social/ a try!
https://nostr.media/579223580fa776f78630fa6001d30612b880022ec91cddd7856cf1f91075f322.png
https://nostr.media/c0215826be9d89983668f0495964d765eb56fa1ebf39a6d8bd0f5a6e647413cc.png

2026-01-12 10:30:43 CET

欢迎所有华人加入 nostrzh 中文社区 relay 🎉
https://nostrzh.org/#relay

2026-01-12 02:24:13 CET

- reply

Yes, it’s been on the roadmap for a long time, but I’ve kept procrastinating on it

2026-01-12 02:15:43 CET

- reply

If the “http auth” shown in the screenshot refers to NIP-98, then it’s very unlikely those requests happened with no user action at all. In Jumble, HTTP auth is only required when uploading images or requesting translation services. Also, the screenshot shows that a reaction was made.
As for NIP-42 auth: Jumble only requests signing when it cannot fetch events without authentication. When you’re browsing the following feed, it is possible to see multiple auth signing requests. If other clients don’t trigger the same behavior, it’s reasonable to suspect that they either don’t support the outbox model or are not fetching a complete dataset.
Some people argue that clients should always prompt the user before performing NIP-42 auth, and allow users to block auth to specific relays to avoid potential privacy leaks. Personally, I think this logic belongs in the signer, not the client. Otherwise users end up having to approve things twice, and approve things for every client.
Based on my own experience using many different clients, I can say confidently that Jumble is actually quite conservative when it comes to signing requests. In my signer setup, only get public key and NIP-42 auth are allowed without prompting, and with that configuration, most other clients are almost unusable.

2026-01-09 02:11:28 CET

- reply

Got it 🫡

2026-01-09 02:10:49 CET

- reply

You still haven’t really answered my question.
If a mute-word list ends up being widely adopted, does that mean we’ll all have to constantly check our posts to make sure they don’t contain any of those words? Is that really a future you want to see? I don’t, and I definitely don’t want to be someone helping push things in that direction.
Let’s look at it from another angle. If you were a spammer, wouldn’t you just collect the most commonly used mute lists and then deliberately work around them? Once those lists are public, they basically lose their effectiveness. For example, if you mute "jumble," the poster only needs to write “j u m b l e” and the filter is useless.

2026-01-08 17:28:16 CET

- reply

Most people are foolish, thinking they are free while blindly following influencer

2026-01-08 17:17:41 CET

- reply

What if the muted word list were made public by Jack? If the list were extensive, many people might adopt it without scrutiny.
I personally don’t like this feature, as China made this mistake centuries ago.

2026-01-08 17:04:24 CET

- reply

I don't think that's a good idea. If a list of muted words is widely adopted, it could make people afraid to post anything containing those words on the Nostr network. If the list keeps growing... Wait, isn’t free speech what you’re all about?

2026-01-08 16:13:02 CET

- reply

Not at the moment, doesn’t really feel intuitive, and there are some tricky issues with implementing it.

2026-01-08 16:00:00 CET

- reply

https://nostr.media/0a46e8ab435327e83b78d4686b3043b70b60fbd41992b6cdda45429a4c963aaa.png
Settings -> General

2026-01-08 15:58:40 CET

- reply

supported, but it won’t sync across devices. didn’t feel super necessary, so I kinda just lazy-ed out

2026-01-08 15:25:46 CET

- reply

Wow, a fat zap! Thanks a ton 💜

2026-01-08 15:21:32 CET

- reply

already removed :padme:

2026-01-08 14:53:59 CET

- reply

So many people have asked for this that it looks like I’ll have to implement it

2026-01-08 14:52:58 CET

- reply

Yeah, I think that makes sense 👍

2026-01-08 14:51:41 CET

- reply

Make sure WoT is disabled and PoW is set to 0
https://nostr.media/e0c03fcc4001c9086df892c86d1c550ffaf3c742d41cb7a7bdf79aca910df8a3.png

2026-01-08 09:50:04 CET

- reply

It does support that already!
https://nostr.media/864c0d4152927d4a9a3d881c7923e89aaff4b97990f3112a0e0921fd1d06be81.png

2026-01-07 02:26:48 CET

- reply

Totally doable, it’s just not very high priority at the moment. Let me procrastinate on it a bit longer :)

2026-01-07 02:23:19 CET

- reply

Fixed 🫡
https://nostr.media/16b3dbd530d155e110d20657eabddcb245d72e90e686e860bae225a8240daf15.png

2026-01-07 02:02:22 CET

- reply

URL regex matching is always a headache 🤕

2026-01-06 15:17:52 CET

- reply

Seems like you haven’t discovered this yet.
https://nostr.media/64e68b77d40db6c20a1476495379ad80c4059a47c7ceef4190b7eeac13d83bd6.png
https://nostr.media/39fa7cd2d2a23652fad19a64ad1d15a6f0695e74c7e8598acebdfb064a44b504.png

2026-01-05 04:07:56 CET

- reply

Users without configured relays will use the default relays to fetch their events. These bots’ posts might not be sent to Jumble’s preset default relays. You can adjust the default relays under Settings → System, but it’s best not to make major changes.

2026-01-05 03:32:13 CET

- reply

Yes, exactly like this
https://nostr.media/51f00b2a3e6c47d385b776065ff8fee275cbc46ffda9568de67457b553b77706.png

2026-01-05 03:28:33 CET

- reply

I agree. I plan to let users set a default in the settings, and if they adjust it for a specific feed, their setting will be remembered and applied just for that feed.

2026-01-05 02:24:30 CET

- reply

I agree. Enable the "live feed" only when the user is at the top. Otherwise, use a "new notes" button instead of inserting notes directly into the feed and disrupting the current cursor position.
What do you think about this? @npub1a3p…sgh3

2026-01-05 02:17:42 CET

- reply

The mute list supports encrypted storage. If you have privately muted users, Jumble may trigger a decryption request on startup.

2026-01-05 02:07:08 CET

- reply

#nevent1q…a0mf

2026-01-05 02:06:42 CET

- reply

Maybe it’d be better to automatically disable the "live feed" while browsing 🤔
Only keep it active when the user is at the top of the feed.

2026-01-04 15:23:03 CET

- reply

"Live feed" means that new events are inserted directly into the feed in real time, instead of being held back behind a "new notes" button.
From my observation of how Japanese users use Nostr, many of their notes are very short and posted quite frequently. In that case, it works really well to stay at the top of the feed and just wait for new notes to appear automatically—almost like watching a live news ticker.

2026-01-04 15:08:37 CET

- reply

Really glad to hear that Jumble has become your daily driver ☺
I’m developing Jumble in my spare time as a personal project, so unfortunately I’m not able to offer any paid dev positions at the moment.

2026-01-04 11:15:04 CET

- reply

Sorry about that, you can click "Don’t remind me again," and it won’t show those annoying warnings anymore.

2026-01-04 11:13:28 CET

- reply

It seems like Japanese users really need this feature. I’ll add support for it tonight.

2026-01-04 02:23:19 CET

- reply

I tried it out, but doing it this way might cause Alby to sign an incorrect event 😂
Given how many users it has, the impact could be pretty big.

2026-01-01 07:31:34 CET

- reply

You don’t really need to understand the details, just know that it helps filter out spam. If you’re still seeing spam, you can raise the threshold a bit.

2026-01-01 07:30:09 CET

- reply

Good suggestion 👍

2026-01-01 07:28:36 CET

- reply

Yeah, I’ve been debating whether it makes sense to split it into multiple, separate filters.

2025-12-31 16:13:36 CET

- reply

Exactly. If a newcomer starts completely disconnected from everyone in the network, it’s indeed hard to enter the trust graph. But if they come to Nostr through someone they know, they can gain some initial reputation from that recommender, enough to help them stand out from the spam accounts.

2025-12-31 14:50:09 CET

- reply

I’m not really into meetings, mostly because my English isn’t great haha. But if your protocol is out on GitHub or somewhere, I’d be happy to check it out and throw in a few suggestions.

2025-12-31 11:43:32 CET

The last feature of https://jumble.social/ in 2025:
A reputation filter that hides notes from the bottom X% of users by reputation.
It works across feeds, notifications, and replies, and is especially effective at reducing spam when browsing large public relays. #devstr
https://blossom.primal.net/df3db41079a69958bb56ee92718fa0682f4b74b6605597f8ae797b4be197f802.png

2025-12-20 06:36:27 CET

- reply

You can give it a try. I’m detecting touch support by checking whether `window.ontouchstart` exists, so I’m not sure if that property will still be present after you disable touch.
Also, on touch devices you can refresh by pulling down.

2025-12-20 06:04:29 CET

- reply

On touch-enabled devices, I hide the refresh button and emoji picker. The emoji picker is hidden due to some unresolved bugs.
If your device doesn’t support touch, then my detection logic is probably wrong.

2025-12-20 06:00:23 CET

- reply

Why would it request this URL? That seems a bit odd, I’ll keep an eye on it.

2025-12-19 02:45:35 CET

https://libroot.org/posts/going-through-snowden-documents-part-1/

2025-12-19 02:18:02 CET

- reply

With the current protocol, this may not be possible, and I’m worried it could cause compatibility issues with other clients. It’s also quite hard to design a good interaction for it.

2025-12-19 02:13:21 CET

- reply

Thanks 💜