.jpg){kind=avatar}
why does nostr need this feature?
Mr nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s , I have a question.
In the future, will you add the ability to show which client a post is from? (For example, like Tweet source labels)
Elon said "〜no one even knows why we did that …" In fact, it may not have been necessary for Twitter. But, I think Nostr needs this feature. Sorry if you already mentioned this. Please let me know the remark link or any other information.
Discussion
Japanese people communicate frequently. Some messages do not work unless you know the other party's client.
As long as the clients implement the NIPs properly you shouldn’t need to know the client, unless you mean for debugging purposes 🤔
There is a “client” field in tags that some client add, but I wouldn’t want to re-create the UserAgent hacks that the web had, which is why damus does not add or read these.
I use amethyst. There is a meme that enjoys partial Japanese conversion to Chinese.
I just thought it wouldn't work for people using Damus or Iris.
There was no particular Important meaning.
I'm so sorry and thank you.🤙💜
If you post “verified images” they will be seen in only very few clients, as far as I know that’s the only major incompatibility if you can call it that.
🤔
It's useful to know what features the other client has... no point sending dm-s to someone whose client doesn't implement dm-s at all..
Coracle already adds a 'client' field somewhere by default I think. Gossip has an option for it too...
Then again, 1 post coming for a cetrain client doesn't (and shouldn't) imply that the other user is using that client consistenly. Still, it's a simple enough feature..
We should not be using a client field for this. We should have features fields NIP if anything. But like you said the problem is when users login to multiple clients with different feature sets.
So we can more easily stigmatize Amethyst users.