I would say it needs to exist outside Nostr in addition to inside Nostr. The main purpose of nostr report starting was to gather and summarize notable posts and happenings for people using Nostr because once you miss something it can be hard to find it, or you may never even know it happened. But it also needs to be accessible for those not on Nostr yet. Agree 100%

For the critics complaining about notifications and scrolling too much, this is a client issue. Clients need to get better at handling long form notification management. This is not something unique to what NostReport is doing.

Reply to this note

Please Login to reply.

Discussion

I completely agree. #[18] is just the first mover in a nascent space to bring up this issue. Asking users to voluntarily push all long form content outside of Nostr won’t fix the problem as it doesn’t prevent someone else from doing it (eg,#[21] ). There needs to be a client focused solution, or if Nostr is truly for short form content then a character limit in the protocol itself.

Cc #[21]

How about a simple truncated, read more?

I’m not a developer but that seems a simple enough solution, at least from a user standpoint.

all I know is all this talk about nostr report ruining our notifications is additionally ruining my notifications..!

we need a mute optionality for posts at some point

Just wait til you get in a #plebchain thread 🤣

🥲

I think that helps fix the long form issue. But not the other issue of notifications that #[2] brings up. For this I think clients need to enable users to mute or snooze/turn off notifications similar to how telegram or signal do it. Maybe even for certain threads that get out of control (eg, anytime someone envokes the “he who shall not be named” bot)

Voldermort

Worse, much worse

cc #[13]