Different social clients show content very differently and while it's often by preference of the respective developers and not just a missing feature, it results in a mismatch between authors' intended impact and readers' actual impact.
For example:
- You use markdown to have a pretty link but most clients do not render markdown links, resulting in rather ugly "gibberish"
- You react with ๐ and the recipient sees only a โค๏ธ counter go up - or no reaction at all because the client dev wants to push towards zaps
- You zap an event but the recipient only supports ln tips, not zaps, so while the recipient gets money, others don't see that you liked this content.
- You embed some events in your post and most clients only add a links to those events without rendering them inline
- You mention somebody and clients go all over the place on how that looks. Some render the nip-5, some render the username with the nip-5 domain if present, some show avatars inline and some only show plain npubs.
I think, we need to communicate that these differences exist and we need words to describe them as a first step to help consolidate ways of doing things where desired.
Currently nips describe mostly the network layer - how events should look like in their JSON form but we don't standardize how things should look for the user. At least not to great detail. And while , others would argue that we need more - but not in Fiatjaf's GitHub repository. And for that, we need a way to collaborate and . We will get there ...