The following feed can be quite slow, since it doesn’t just fetch from your own relay settings — it also pulls from the relays used by all the people you follow. I saw you’re following over 400 users, which could mean fetching from more than a hundred relays. I wouldn’t really recommend browsing the following feed with Jumble for now. Hopefully, in the future, there’ll be relays dedicated to serving following feeds.
Discussion
Can you implement something like the proxy relay setting in Amy? aggr.nostr.land works quite well, and I believe nostr.wine has a similar feed relay too.
As far as I know, aggr.nostr.land does plan to implement the outbox model, but it doesn’t seem to be finished yet. Once it is, I’d be happy to support it — that would significantly reduce performance overhead.
I suppose YMMV but it works well as a proxy in my personal testing so far. nostr:nprofile1qqs99d9qw67th0wr5xh05de4s9k0wjvnkxudkgptq8yg83vtulad30gpz9mhxue69uhkummnw3ezumrpdejz7qgkwaehxw309askwemj9ehx7um5wghxcctwvshsz9thwden5te0wfjkccte9ejxzmt4wvhxjme0e68ksk what is the status?
The goal is that for broadcasts it will use outbox. For receiving, it scrapes all relays so that should be a solved problem.
But I am intending to add a proxy mode where it can AUTH proxy as well
I don't fully understand what you mean. Jumble allows users to choose feeds from individual relays. It's been doing fine with following feeds. Are you sayikg some posts from my follows won't show up in my chosen feeds?
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.
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.
nostr:npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl nostr:npub1qdjn8j4gwgmkj3k5un775nq6q3q7mguv5tvajstmkdsqdja2havq03fqm7 nostr:npub1m3xdppkd0njmrqe2ma8a6ys39zvgp5k8u22mev8xsnqp4nh80srqhqa5sf nostr:npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku any input on this?
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