Very inspiring. Lots of great ideas.

There’s a website that lets you restore various lists, but I can’t remember which one it was.

It looks like fevela already has that.

Yeah, I agree. Even if a client fully fetches and displays notes from nearly a thousand people, I don’t think anyone can realistically read all of that. Once the number of followings passes a certain point, "following" kind of loses its meaning. (And since most people don’t stay on a page for very long, I’m not sure a slow, patient syncing process would really work in practice either.)

You can see other people’s comments and reactions to this link or anything else.

Nostr is just a communication protocol. The reason it isn’t generating revenue right now, in my opinion, isn’t because of the protocol itself. It’s simply that the people using it haven’t found the right ideas yet, or many are comfortable with the status quo. Nobody thinks today’s internet industry is profitable because of how the HTTP protocol was designed. But if by nostr you mean the Twitter-like kind 1 clients, then I have a genuine question: what is the actual goal of a nostr kind 1 client? A. Become the next Twitter. In that case, we’d need to spend money bringing in influencers and give them ways to monetize on nostr, stronger ads, storefronts, creator tools, etc. B. Become a place where ordinary people can speak freely and post their everyday, boring, normal lives. A platform where the main characters are regular users, not influencers. If that’s the goal, then we’ve already achieved it. On Japanese and Chinese relays, most of the content is exactly that, simple, mundane posts from normal people.

This is just a solution specifically for users who follow too many people.

Something new is on the way #jumble

Maybe you’re right, I can’t argue with that.

No plans for that at the moment. There are several incompatible DM protocols in Nostr right now, so users can never be sure whether the other party actually received their message. And once an app integrates DMs, users basically have to grant the client blanket decryption access for all messages at once — otherwise, they’d have to approve each decryption request individually. I don't like that approach

What if this special relay is run locally by the user? Or what if the relay is actually a client itself? Would that change the outbox model? Why would a client need to support two models? At least Jumble doesn’t need to make any changes. If such a special relay emerges, the user simply needs to bookmark the relay and browse it. They can still click on the following feed and connect to dozens or even hundreds of relays as before.

Are there any error messages?

I’m only talking about the following feed here. Posting, replying, reacting, getting notifications… all of that would still follow the outbox model as usual.

As far as I know, I haven’t made any related changes recently. I’ll test it tomorrow.

This approach doesn’t change the current model at all, it only moves part of the client’s workload onto a specialized relay. For example, if someone follows too many users and the outbox model becomes painful for them, they can run a local relay that automatically pulls events from their followings’ write relays. Then they just browse that relay with Jumble. This is actually a feature I’ve wanted to add to nostr-relay-tray for a long time, but have kept putting off. And of course, if they don’t want to run a local relay themselves, they can wait for a paid service to offer it. If someone doesn’t follow many users, or mostly browses relays directly, then they don’t need to do anything, they’re already perfectly happy with the outbox model.

You don’t need to add it as your read/write relay. Simply set it as a favorite relay and access it directly from the homepage.

Could you share your relays configuration? Or you could try accessing this URL to check if it works. https://jumble.social/?r=ws://127.0.0.1:4869

The experience with nsec.app on mobile doesn’t seem to be very good, since it needs to stay in the foreground to work properly. If you’re on Android, you could try 's Amber instead.