What??!!!! Lol - this is one of the most important thing

1. You are not limited by client’s decisions and choices - you carry your profile anywhere you go.

2. There can be many types of social media - you can have your Twitter, tik tok client here, your FB, your snap chat - or come up with something new - it’s all going to be Innovation’s built upon this

3. And of course, irrelevant here but you should have anything related to digital and finance tech built on Nostr - it’s a huge ecosystem.

Not being able to see from one client to another is an annoying and ridiculous problem as a user

Reply to this note

Please Login to reply.

Discussion

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.

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! 🫂

🫂

I understand your perspective, but I think this is probably not possible. It isn’t the case now and will become even less so as more features emerge. It will be impossible for every client to offer all of the content types available on every other client. There will be a core set of content that social clients are expected to support, but there will be many clients that take a specific approach to features and content.

Nobody would be able to manage their product roadmap by playing whack-a-mole with other developers and their priorities. Even more so if some developers are not interested in signaling their roadmap or coordinating new features or changes.

What is crucial is that core features that have been rolled out across clients continue to work and that developers don’t unilaterally break things that have worked in a specific way.

Nah. That what NIP is for. If there are innovations out of the NIP, that impacts viewers of other social clients for whatever reason, then there must be a ground rule that all devs agree on this

I don’t think we are talking about the same thing. My comment was about expecting that every client is going to support every type of content. Maybe that wasn’t your point.

It is also the case that clients already implement things differently and have used NIPs in ways that break existing content implementations in other clients.

Some developers are going to be more interested in collaboration and ensuring the ecosystem is healthy than others.

Nobody is asking every client to be identical to each other - nobody wants Twitter 1,2 and 3 lol, and clients can pick any feature NIP. Be different and celebration innovation.

But if there is a functional interoperability issue between clients that prevents users from interacting with other users on Nostr then it’s a problem.

We agree.

is text and zaps the minimum functional interoperability now?

But if one wants to utilize/participate in polls, they would access nostr through a client that supports them..that is the whole idea, no?

The only issue I see, specifically with Polls, is selection bias.

But you are right.

Which isn't necessarily always bad. You ask mostly client & device specific questions, so its very appropriate in those cases.

There is a long way to go before nostr polls could be sited as accurate unbiased research data and these gaps will be filled by then.

> You are not limited by client’s decisions and choices - you carry your profile anywhere you go.

You are right that you can carry your profile anywhere.

BUT

Your client choice definitely affects the way you see Nostr. It will always affect you. There is no guarantees that all clients will display things correctly.

In other words: you are ALWAYS trusting your Client app.

and relays

For deletions, yes. They cant do anything else.

Clients can change content before displaying and pretend this were verified.

Clients can change user’s content on notes ?

Yes up to client to build however they want. But as a user i should be able to interact with other Nostr users.

Relays are diff context - users can have private relays by choice. Paid relays you can still view, find common relays and engage. So using relay as analogy is not the same here.

The problem here is that core functional issue that’s preventing interoperability between clients - and it impacts users. I should not be forced to use amethyst to engage amethyst users - this is wrong.

In the long run, when another dev say Lex Luther shows up with bad intentions and implement stuff that other Nostr clients can’t interoperate - and other users can’t view, has enough money to promote globally and increase user base, pushes algo - it defeats the purpose of Nostr.

The actions here of not being interoperable and closed up client will have detrimental impact on Nostr in the long run.