Jumble is mainly designed for browsing content directly from a specific relay. Nowadays, there are special types of relays like community relays, curated relays, or language-based relays. When you browse these, it’s independent of who you follow — the data only comes from that single relay, which makes it much faster.

The following feed, on the other hand, fetches notes from the write relays set by all the users you follow. That means it needs to pull data from dozens or even hundreds of relays and then aggregate them, so it’s naturally much slower.

Reply to this note

Please Login to reply.

Discussion

Thank you for clearing that up. So we need to do a better job at designating the different types of relays. Do community, curated, and language-based relays have a secure method of distinguishing read and write relays?

Honestly, there isn’t a reliable way to distinguish them right now, since the boundaries are quite blurry. Users still need to understand what each relay they use is for, which isn’t very user-friendly. The good news is that most relays today are unrestricted public ones.

What do you think of adding local storage of notes specifically for the following feed + building the feed directly from the local storage + background syncing of new notes from follows from relays? Would you accept a patch for that?

This would be amazing.

Id really like that, one of the remaining features that keeps me on nostrudel is that with slow relay loading I don't have to sit and wait for my notes to load every time I refresh the page (which is often enough to be annoying). I didn't realize that jumble lacked this feature until I started trying to use it more regularly.

Could just be me, with privacy browsers, dns, being blocked by cloudflare, and privacy blocking extensions apps get buggy for me really fast so I often have to reload the page just to make sure im seeing things,

That would definitely make the experience better, but I’m not sure if it’s the right approach for a web client. Still, it’s worth trying