Nostr Web Client

I don’t think it’s an over optimization. You would need to make N relay subscriptions sequentially (N being the number of events in the thread) instead of one relay subscription in the worst case to even be able to populate your event graph in the first place. It’s highly inefficient, but also as you described it, probably necessary because it’s easy to not conform to NIP-10 properly.

greenart7c3 9mo ago 💬 2

Maybe it's the same problem nostr:npub1yaul8k059377u9lsu67de7y637w4jtgeuwcmh5n7788l6xnlnrgs3tvjmf was having

nostr:nevent1qqszqzmnegqs0je7gqd4u2q360z730grq78a69q6mzqw0qm4n20g3pcpzemhxue69uhhyetvv9ujumt0wd68ytnsw43z7q3qyaul8k059377u9lsu67de7y637w4jtgeuwcmh5n7788l6xnlnrgsxpqqqqqqz760h2m

Reply to this note

Please Login to reply.

Discussion

Terry Yiu 9mo ago 💬 2

I have a fix incoming for Damus today. It will give you the option to mute notifications for notes with more than 10 mentioned profiles, with it enabled by default.

KoalaSat 9mo ago 💬 1

That's a cool approach, thanks for the idea

Ryan 9mo ago 💬 1

At a certain number it doesn't even make sense, and should be blocked proactively. What's that number though? Would someone ever need to tag 50,100,500 other npubs?

KoalaSat 9mo ago

I think I'll make it active to 10 by defaultanf allow users to change the number or disable it

Ryan 9mo ago

👍

Madrugada 9mo ago

Please make one with more than ten hashtags, please!