Another thing you could do is pay-to-play.

Our https://theforest.nostr1.com relay accepts all zap events, as those can be spammy, but so what. We can just let anyone zap and limit display of the zaps to a minimum sat amount _or_ write-access to the relay. You have to be whitelisted or pay at least 100 sats, for instance.

But, we can then allow them to include a message in the zap event (like Nostrudel does), and display that message in the feed, as a reply with a ⚡ icon or something (nostr:npub1636uujeewag8zv8593lcvdrwlymgqre6uax4anuq3y5qehqey05sl8qpl4 ?)

So, you can pay 100 sats to the pubkey, to have your comments show up, in our app.

And you can use anon zaps instead of private ones. Get away from encryption.

Reply to this note

Please Login to reply.

Discussion

If you don't pay at least 100 sats, then just the money amount gets listed, not the comment.

This solves for advertising, as well. To advertise on Alexandria, you have to pay n amount to the npub who owns the thread.

Each npub could also set a minimum amount, all the way down to 0 sats, or a maximum amount, all the way up to 100k sats.

That's the cost of having your ⚡messages show up in their thread, for the general public. Anyone who is not logged in, can only send zap messages. Anyone who is logged in, can do either, anon or not anon.

Those are like sponsored messages, but for any npub, and the money goes straight to the author of the event being zapped.

What do you think nostr:npub149p5act9a5qm9p47elp8w8h3wpwn2d7s2xecw2ygnrxqp4wgsklq9g722q ?

Communikeys (and the apps built on them) have the advantage that:

1) they have a global state (and don't need to know who you are for reading + conditional display of replies, etc...). Spam is defined by the Community.

2) they can define their publishing conditions (price list) for each content type. So if the price for publishing an Article is ⚡ 100, they don't need to know anything about you to accept that publication.

That said, there are huge benefits to signing publications with your nsec.

To me, a good daily driver = your signer

Zapchat is (becoming) such a daily driver. (although you can browse in it without adding any profile)

Zapstore, on the other hand, is an app where "adding a profile" or "spinning up an nsec in the app" probably makes less sense. It can just display the app releases of some default communities, lets you select other ones. By adding profiles (i.e. getting npub info via Android Signer, like Zapchat or Amber) the UX will still be better though. And I don't see anything wrong with that. For publishing app releases, zaps, etc... you need a signer connected. And on Android and Desktop (not web), there is very little issues with that.

Yeah, it's highly use-case dependent. Is it my daily-driver or favorite community app, setup with my favorite relays? Sign away.

Am I just exploring it, is the repo owner bit dodgy/unknown or is it closed-source? No sign.

Do I only use it, occasionally? Read-only login and I interact over my daily driver's generic event search (find an event and hit *reply*, *zap* or *react*).

And so on. But the levels only work if the app takes the different states into consideration in the design, and tries to stick to the lowest state that is practical, with an offer to "upgrade" to a higher state, during a specific action.

They should always be upgrading _for some specific reason_.

Exactly

I can't wait to show you what I did with the wiki disambiguation page. 😁

You've created a feature monster. All your fault. I was old and needed the zaps.

I don’t know if it’s possible to thread comments that are all zaps and wallets have their own rules about content length and such.

But design wise, it’s possible to go multiple ways with this. Even so far as to allow a publisher to include a min amount in the index tags and have it honored by the client.

Ooooh, yeah. Custom zap-message amounts, by client, npub, or event. Damn.

And the client can have an option, for you to share your zaps with the devs.

Well, zaps have an e tag, so they can be replies, otherwise, they default to the kind 0 replies.