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_.
Thread collapsed
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.
Thread collapsed