cody on Nostr: I’m really sorry about this! The following feed is fetched based on the read relays ...
I’m really sorry about this! The following feed is fetched based on the read relays you’ve set, and I just noticed that your read relays are empty, which is why it couldn’t load. I’ve already fixed this issue in the latest version—if no read relays are set, it will now default to using a few larger relays to load the feed. The latest version is v0.1.0 (d1b8b98). You can check it in the settings.
In a few days, Jumble will add a feature for setting your read/write relays, so you can configure your preferred relays then. Alternatively, you can set them now using another client, like noStrudel.
As for the algo relay, I’m not the operator. It’s still an experimental relay for now, so it’s not very stable. I just tried it myself, and the response time for the algo relay is currently as long as a minute, which might be why Jumble is unable to process it properly.
In a few days, Jumble will add a feature for setting your read/write relays, so you can configure your preferred relays then. Alternatively, you can set them now using another client, like noStrudel.
As for the algo relay, I’m not the operator. It’s still an experimental relay for now, so it’s not very stable. I just tried it myself, and the response time for the algo relay is currently as long as a minute, which might be why Jumble is unable to process it properly.