Maybe it’s just that the users mentioning in the past couple of days didn’t have write access to nostr.land.

- It might be that nostr.land recently changed its restriction policy. - Coracle might not only query your read relays but also check some larger public relays for notifications. That helps avoid missing them, since some clients don’t fully follow the outbox model. Jumble, on the other hand, only queries from your read relays, because some users rely on their own WoT relay as a read relay to filter out notifications they don’t want to see. If Jumble were to query from other relays on its own, it would defeat that purpose.

Jumble only looks for notifications from your read relays. That means if someone mentions you, their client needs to publish that event to your read relays. If your notifications look incomplete, there are usually two possibilities: * The other client doesn’t follow the outbox model and didn’t send the event to your read relays. * Your read relays rejected the event. I just tried replying to you and saw that nostr.land rejected my event with: `restricted: Pay on https://nostr.land for access.` So it might not be ideal to rely only on a single paid relay as your read relay.

test

Not at the moment

There’s still plenty to improve. 🫡

To avoid accidental taps, it now requires a long press.

If you want to save data, you can go to Settings → General → Auto-load media and set it to `Never` or `Wi-Fi only` (supported by some browsers) #Jumble

Using an LLM to filter content and create topic-focused relays is a great idea. I’ve thought about having admins review posts before, but that’s obviously far too inefficient.

你用的是什么浏览器？

好的👌

加载不到画面的话就会退回音频模式，可能是网不太好？我可以正常显示

哦哦，看错了，以为是上传慢哈哈。加载的话我得研究研究了，可能是因为会先查询一下是视频还是音频导致的

Which client did you use to post it? You might need to update. Earlier this year, kind 34235 was changed to kind 21/22. https://github.com/nostr-protocol/nips/pull/1704

换个服务试试？

When you request jumble.social, it only serves JavaScript, HTML, and CSS files. The data comes from relays around the world, and all that fetching happens on the user’s device. I’d say it’s reasonable to call it a static site. Even if you don’t fully agree with that definition, the fact that it’s easy to deploy is undeniable.