1. "Which bunker signer are you using? Did you approve the connection request?"

I'm using nsec.app signer. I was using nsec.app on my mobile browser and it wasn't showing any pop-up or anything. After seeing your message, I tried nsec.app from desktop browser and then it showed the prompt and I could sign into Jumble without issue. So the issue was not Jumble's fault. It was at my end.

2. "The like/comment counts only load when clicked. This is because loading likes and comments is heavy, each like/comment is a separate event. If we were to load all likes and comments for every note right from the start, it would be a disaster for the computer's performance."

Every app/site should have a design choice. Likewise, this is Jumble's design philosophy and I respect that. But I asked as other clients have it implemented. If it goes against Jumble's goal, then that's okay, too.

3. "As for the message/DM feature, I don’t plan to add it for now. You may need to use another client for that. Jumble doesn’t aim to be an all-in-one client; it will focus on relay browsing. In the next phase, I’ll focus on enhancing the relay discovery feature."

It's also a design goal of Jumble and I can't say anything about that.

4. "If you want to mention someone, you need to type nostr:npubxxxxx as specified by the protocol. I know it’s not very convenient, and it will be improved in the future! Also, if you want to reference a specific note, you can type nostr:neventxxxxxx"

Yeah, not that convenient and hoping it would get more convenient in the future.

So, thank you nostr:npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl for your detailed repsonse.

Reply to this note

Please Login to reply.

Discussion

Thank you too