Nostr Web Client

For a long time I didn’t realize Nostr wasn’t useful just for “social networking” things. I wonder what else could have been better designed in the relay-client interface if the needs of non-social-networking apps were kept in mind.

PABLOF7z 2y ago

nostr:note1d8hgcwt0gj38tfgmxuqy2av9rwesk2c08j46d5pte69406ts8ezqxx5z8a

Talking about social-media vs non-social-media use cases for me sometimes feels weird.

Most of the stuff that nostr improves *is* social media, understanding that term as "things that benefit from a social graph". In that sense, i.e. nostr:npub1zapstrdhq7rxrw224apgvs5ajlh9y473f2rdd0a9fjcys2u8d7cqzxqhp9 is a social media client, it's just not focused on short-text as the main driver but rather songs and podcasts.

With that caveat out of the way:

yes, as a developer mostly focused on non-twitter-like interactions, often I find myself having to think around the design constraint of kind:1s being, well, #1. -- I don't think is a big deal, but would be nice if all use cases had mostly equal footing in the protocol.

Reply to this note

Please Login to reply.

Discussion

Ben Eng 2y ago

Would use cases beyond social media add message types to the protocol rather than be built on top, so that weird encoded text show up everyone's social media feed? I'm going to guess that's the case, otherwise other use cases could never be on equal footing.

PABLOF7z 2y ago

Read https://dev.highlighter.com/a/naddr1qqgrxwrfw5m8garwdvm85aenwajxgq3ql2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqxpqqqp65wxtanuc

it discusses exactly what you are thinking

Ben Eng 2y ago

That web site does not render properly in Chrome and Brave browsers, as the page doesn't scroll or respond to inputs. Only in Firefox can I highlight the text to scroll by highlighting, then copy to a text editor to read. There is a WebSocket connection error and uncaught exceptions in the debug console.

Ben Eng 2y ago

Ok, was able to read. Thank you. Event kind identifies a type of data for a use case. NIP-31 gives an alt tag so apps seeing an unrecognized kind can still display a text description for context. NIP-89 lets users discover microapps from other Nostr users for handling a kind, so that we can have a free market for microapps instead of being vulnerable to centralized control by an app store. This also decentralizes control by verticalized silos that tie data to apps. Brilliant.

Chiefmonkey 2y ago

I think I get what you’re saying and agree that kind 1 viewable text should be equal to hidden data

I’d argue privacy (hidden data of any kind) is more important than free speech… because without privacy there is no free Speech

Perhaps it’s simply because the first interaction between humans is open communication … and so kind 1 takes prevalence

You openly agree To communicate with another human before you choose if you want to speak in private

Kind 1 is a priority for community

For self sovereignty it’s privacy

So from a Self Sovereign perspective, privacy is equal to or more important than Kind 1

Should we look at nostr, community first or self sovereign first ?

Are you thinking community first?

That’s my 2 sats

(I don’t have an answer)