<unnamed>

Public Key

npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl

Profile Code

nprofile1qqsgzfdez8ksa9xmuvqg5zly3nl9e5xqkpvj8nllj9aw06ra4pqq3qcpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsq4camnwvaz7tmswfhhs7fwdehhxarj94ex2mrp0yhxzurs9ask2vesvfsnyvehxf3k2epkvvcnjd3svs6rjcesxgmrvenyvsek2vphvdjkzdfjvgckye3nxuuxverzxcurgct9v5mrxd3nv3jkxdpkqyvhwumn8ghj7urewfsk66ty9enxjct5dfskvtnrdaks47evv0

Publishing to

relay.damus.io

nos.lol

proxy.nostr-relay.app/ae30ba2372ced6c1960d49c0266fdd3e07cea52b1bf378fdb684aee6363dec46

pyramid.fiatjaf.com

Last Notes

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-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-01-31 11:33:14 CET

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

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-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-08 17:28:16 CET

- reply

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

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:00:00 CET

- reply

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

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

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-11 02:06:59 CET

- reply

Long-press actions on buttons generally aren’t very intuitive. If mis-taps are common, we should probably switch to an interaction like the one in Fevela, or add a confirmation step.
I just tested it on my side though, and touching that button while scrolling doesn’t trigger it. Does it get triggered accidentally when you scroll in your browser?

2025-09-11 16:11:53 CEST

Any recommendations for reliable blossom servers? #asknostr

2025-06-02 17:56:37 CEST

🐋
https://image.nostr.build/3bb97fa62502f172a967af5a8d51d2a46371629243b4d14c036c8fa4118339c8.jpg