nostr is just keys, clients, and relays, that allow you to access clients, not all social clients will be compatible and share all the data with each other.

We’re clearly moving away from 4 Twitter clones, to something more unique for the each platform.

I’ll use my keys to view all these clients, but not all clients will see what I post.

Reply to this note

Please Login to reply.

Discussion

I agree. Nostr right now is largely a twitter use case, but that isnt to say that it cant be some other thing partitioned into another use case with relays purpose-built for it. The powerful thing there is that onboarding effort is nothing and your social graph will be available when you arrive.

Yea - maybe there are many devs building crazy tools and ecosystem#[7] ,#[8] ,#[9] and more ! It’s super exciting seeing their build and growth

I disagree, I think that defeats the purpose of nostr and what it originally stands for.

If there is a major news highlighting content from amethyst, users all have to login to view via amethyst aka centralisation.

I don’t care who is fighting with who but as a user, I should not be forced to used a client to engage with other users. On Nostr

If a user decides to remain private then it’s the users choice

If a client prohibits users from Nostr from viewing their users, then it should be relabelled as some thing else - private client etc.

We want to move away from centralisation. This impact is way worse

At the same, client competition is key to nostr and standardizing clients would make having different clients pointless. Some features should definitely be everywhere, but clients shouldn’t be forced into making changes just because another client did it and vice versa

You are not standardising clients at all. In fact we want to celebration innovation. But you want to make Nostr Protocol doesn’t break.

Yeah that’s why i said some features need to be adopted by all clients. But if you force all clients to adopt all features then you’re standardizing it and clients won’t be unique. There’s a balance.

Agreed - it should be flexible. I am certain this is just a small problem in the large ecosystem of things - with more devs and more innovations it’s gonna be a wild wild ride here 😅 but so as long as all devs remember the risk involved and that users are what matters

And hey welcome back!

Thank you! 🫂

🫂