The core of Jumble is pretty messy, it just happens to work :FLASHBANG:

If every client were the same as Jumble, nostr would be way too boring. Please don’t discourage developers from building around their own vision.

There are too many possible points of failure. All I can do is try to make sure any mentions of you from your read relays show up, and do my best to pick suitable relays when publishing events — but I can’t guarantee delivery success.

It might be because the note didn’t reach your read relays due to a network issue. In Jumble’s logic, this note is supposed to be sent to 10 relays, but maybe Jumble was closed before it finished sending to all of them. I rebroadcast it just now, so you should be able to see it.

Good idea!

Yes, but the catch is the price can’t be too high—otherwise, why not just use a VPN haha.

In simple terms, the outbox model works by posting your own events to your outbox relays and events that mention others to their inbox relays. So when you want to fetch a user’s events, you have to go to their outbox relays.

Now, imagine I follow a European user whose outbox/inbox relays I can’t connect to—how would I find their events or mention them? This is exactly the issue the outbox model faces under China’s network environment.

Tor barely works in China.

Thanks so much for your feedback!

Yes, Chinese users rely on bostr2 for now. But it won’t really work in the outbox model era.

Looking forward to it!

Sounds good. Is the proxy relay already running? What’s the address?

Many relays can’t be directly accessed from China. Once the outbox model becomes more common, Chinese users will have a hard time fetching the events they want. I think a proxy relay can help to some extent, but if too many people use it, it might get blocked too haha.

With a proxy relay, how would I send events to a specific set of relays?

Great approach

Any more technical details on this? It sounds like it could help solve connectivity issues for users in China.

Jumble fully supports the outbox model as well — that’s exactly why the performance is so bad when browsing the following feed.

nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 also reported an undefined error, but in his case it happened when reporting a post. Looks like it might be the same root cause—under certain conditions Jumble hits an undefined error when publishing an event.

What exactly happened? I haven’t made any recent changes to the mute-related code.

There‘s a cross-origin issue.

Thanks a lot for your understanding!

Thanks

If you’re running — or know of — any community relays, topic-focused relays, relays with special algorithms, or any other interesting relays, please submit them to jumble.social ! 🚀

#nostr #asknostr #grownostr #relay #devstr

https://github.com/CodyTseng/awesome-nostr-relays/issues/new?template=add-relay.md

Cool! Jumble already supports LibreTranslate. nostr:npub17nd4yu9anyd3004pumgrtazaacujjxwzj36thtqsxskjy0r5urgqf6950x , you can give it a try

service address: https://translate.nostr.wine

Thanks a lot

Do you see any error messages in the console?

Currently kind 24 isn’t supported, so there won’t be related notifications.

I’ve thought about packaging it with Tauri / Electron, but then I can’t resist bundling a local relay inside, haha. And that’s when I start procrastinating.

That’s a good idea.

The real security is in keeping your keys safe and not signing events blindly, haha. When I use Jumble, every event (except AUTH) asks for my consent before it’s signed. I know that with this configuration, many apps become almost unusable.

You're right

Kind 1 posts can also contain photos and voice, so I’m worried users might get confused if they deselect photo/voice posts but still see photos or audio. To avoid that misunderstanding, it’s probably better for now to make it clear that the filtering is based on kind.

Since the filter currently only supports kind, I don’t think it needs to be that complex for now.

Yeah, that is a bit odd, maybe it failed to fetch the video metadata and mistakenly treated it as audio.

Thanks so much for the kind words and feedback! Glad you like it 😊

The relay discovery is definitely something I plan to improve next. It shouldn’t just dump all relays in the list, most relays aren’t actually suitable for casual browsing

Yes. The preview feature will also be removed in the future, and the editor is intended to be fully WYSIWYG. It will also need to support custom emojis… implementing all that on a plain HTML textarea would be quite difficult for me, so the rich text editor is a must.

As I understand it, line breaks when copying shouldn’t be an issue anymore. If they still are, then my understanding is wrong — which could mean there are many other potential bugs. So this bug might actually be important.

There are quite a few features that rely on the rich text editor, so switching back to a plain HTML textarea isn’t really an option. Could you describe the issue you’re experiencing in more detail? I’ll work on fixing it as soon as possible.

No need to clear the cache, just try refreshing a few times.