0 sats \ 0 replies \ @BlueSlime 5 Feb 2023 \ on: Nostr sucks: A contrarian viewpoint nostr
-
Pay for relaying traffic. This is an obvious use-case. Having a dumb relay for hole-punching between NATs is very useful. There is already a market developing for this.
-
Pay for storing data. This is another obvious use-case. Relays provide access to websocket native data storage with non-custodial identity. That is actually quite incredible.
-
Pay for pubkey -> name resolution services. This is already quickly becoming a thing. It's very useful for verification and routing.
-
Subscription to a curated platform. A combination of the above, where you are provided a social media experience as a service. Essentially Twitter / Mastadon / etc with a subscription.
-
Pay for API / Integrations. Also quickly becoming a thing. It's simple to setup a chatgpt bot on nostr and charge money.
-
Mining / selling data. We are all aware of this revenue model. The interoperability between clients-relays will make aggregation much simpler.
You don't have to use lightning.
Nostr uses schnorr keys for identity, meaning that they also support lightning directly (with taproot channels) i.e your nostr private key can also sign lightning invoices.
Lightning invoices already have a slick integration into nostr (see zaps) and nostr profiles include lud16 payment addresses.
This is a common red-herring that you can bring up for any platform. Relays need better moderation tools but they are actively being developed.
Same as any other key custody solution: hardware and software signing devices. See nos2x.
This is another common red-herring framed as a nostr-centric problem. Write good code and sanitize your inputs.
Most likely.
With decentralized identity and client-native data replication, yes.