uses multiple nostr events + publishes to relays = nostr client
Discussion
Is nostr.band a nostr client?
it’s more of a collection of services client
but we could ask them man himself what he thinks of his own project nostr:npub1xdtducdnjerex88gkg2qk2atsdlqsyxqaag4h05jmcpyspqt30wscmntxy
yes, you can follow, unfollow, add to lists, etc. it's more than just search.
this is what i'd say
Its word for word what you said 💀 it’s a good definition
I wonder how nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 would define it.. would prob be the same
See! I knew I liked it!
Probably. I just found out recently that an upcoming major client may not fit my definition of a client... It uses login, but doesn't publish anything, and it's more of a content scrapper. I did not know this. It's also early in development so they still have time to become more of a client and publish data.
What upcoming thing is that?
I would only give that title to something that is interoperable or potentially interoperable with other apps. Some random spammer abusing relays as free storage isn't a real client, for example.
An app can also use Nostr identities and consume Nostr data but not want to be interoperable, and I think that makes it not a client, or a partial client, but that isn't a bad thing either. We don't have to use Nostr events for things not suited for Nostr events.
Absolutely. I'm building a non-client app with nostr login only, because I love what nostr stands for in comparison with X etc. The app follows in the same spirit as nostr: education, fun, generosity etc. But that doesn't mean I'm making all data in the app event-based. There is no need to do this in my case, it would just fill up relays and degrade the UX needlessly.