damus

damus copied to clipboard

Add method to discuss with purple subscribers direction and feedback on Damus.

Could telegram, or a private, or invite-only write relay.

cc @jb55

This would be an useful method for product, design, business team to gather direct feedback from the Damus supporters @danieldaquino

How might we achieve this?

Private relay + auth

Private relay + auth

I wonder if there are any out of the box solutions out there for this? I would advise against a custom solution/setup at this point, to avoid spreading ourselves too thin 😅

Private relay + auth

I wonder if there are any out of the box solutions out there for this? I would advise against a custom solution/setup at this point, to avoid spreading ourselves too thin 😅

I would advise against a custom solution/setup at this point, to avoid spreading ourselves too thin 😅

:100:

I wonder if there are any out of the box solutions out there for this? I

How about a invite only write permission relay (i.e. like nostr.wine, except gate opens with proof of purple purchase)? Read side can be either public, or private. I like public as it keeps development discussion open, and it helps market purple subscription as a perk in having say where Damus goes next.

How about a invite only write permission relay (i.e. like nostr.wine, except gate opens with proof of purple purchase)? Read side can be either public, or private. I like public as it keeps development discussion open, and it helps market purple subscription as a perk in having say where Damus goes next.

Maybe! I wonder what kind of software/product makes this easy. https://github.com/fiatjaf/khatru comes to mind, but I haven't tried it yet to be sure it fits our needs.

@MSauce what do yall use for nostr.wine paid relay?

from what I understand they have a business-logic proxy in front of a strfry backend

to dogfood our own stuff it might be cool to do a rust relay with a nostrdb backend

although khatru is definitely an attractive option. from reading the code awhile back it seems to have an LMDB backend as well.

Which one of these is the least amount of development effort? The least amount of maintenance effort?

khatru probably

from what I understand they have a business-logic proxy in front of a strfry backend

Yes, that's correct though it's primarily for other features like restricting DM metadata, AUTH, NIP-50, etc.

If all you want to do initially is a pay-to-write relay, you could just use strfry + a simple write plugin (https://github.com/hoytech/strfry/blob/master/docs/plugins.md) that checks if the pubkey is a purple subscriber before accepting/rejecting an event.

You only need something more involved if you want to do read access control/AUTH.

Goal:

From mutiny blog: guaranteed support for purple subacribers

With something like a blinded support system, we could restrict it to paying users only without knowing which user it is and without associating multiple support requests to the same user. All we care about is whether or not the user paid for support tickets at some point and the one-off pubkey they have so we can communicate securely with them. We could allow two monthly support tickets for any subscribed Mutiny+ user, possibly doing one-off paid support tickets for non-subscribers.

https://blog.mutinywallet.com/blinded-authentication/

On Thu, May 16, 2024 at 10:23:27AM GMT, alltheseas wrote:

From mutiny blog: guaranteed support for purple subacribers

With something like a blinded support system, we could restrict it to paying users only without knowing which user it is and without associating multiple support requests to the same user. All we care about is whether or not the user paid for support tickets at some point and the one-off pubkey they have so we can communicate securely with them. We could allow two monthly support tickets for any subscribed Mutiny+ user, possibly doing one-off paid support tickets for non-subscribers.

https://blog.mutinywallet.com/blinded-authentication/

this is really cool