I still think we need a new kind number for "very important note" that will go on a prominent location on people's inboxes -- a place like an email inbox where those important messages won't get lost in a feed of neverending garbage -- and then somehow clients and relays must enforce that users can only send these "very important notes" at most once per week or something like that.

Reply to this note

Please Login to reply.

Discussion

Maybe this could be just a "very important" class of relays that enforce this stuff and people subscribe to only a few accounts on these relays specifically, like subscribing to an email newsletter.

Would be useful for notifications.

‘discoverability & dependability’ of this very important class of relays should probably be the priority.

what does very important note mean? who decides why it is important? why do we need to rely on relays to enforce this thing?

The sender decides what is important and you trust the sender to be mindful of these important notes by following them. It doesn't have to be anything important, it's just that it's content expected to be come at more reasonable schedules than microblogging, like when you subscribe to an email newsletter.

I don't know if we need relays, but as long as decentralization isn't compromised I'm all for delegating more tasks to relays.

What do you think?

This sounds like boosts

All VINs cost sats equal to $1 in bitcoin?

I'm very important and would love my important messages to be boosted.

Priority notes.

Yes. And no additional priority notes irrespective of how much you want to pay

could be a user option in client to set a time frame for accepting those notes. at x time request that kind from relay. could also use filters client side to allow users to filter requests from people who may attempt to abuse the system. like "request all important notes at 1800 utc except from this npub or list of npubs"

I could also see this as being useful for "important zaps" 🤷‍♂️.

perhaps a broader "important event"?

So many RSS readers are either limited or expensive. It’s probably just a fix for that using something they’re using anyway.

Cool type. Enforcement would be best client side. Relays can just relay these. Clients can let users de-escalate abusers, clients can even de-escalate the abusers if enough followers de-escalate or other similar rules. Let clients make all UX decisions.

Boosts or value-for-VIP sats fees are handled on the client side too. Relays stay out of that and just relay. Let the users decide what they like based on a simple rule set client-side. The clients will figure out the formula that people will like.

...using a CNN, customised for the user based on their revealed preferences.

I do agree we need a "priority" category of notes, but hard-coding it and limiting to once a week will be notably inflexible.