Best user experience, video and chat wise, is watching on zapstream or noStrudel. Both embed all sorts of nostr events and noStrudel also embeds images and gifs. Most clients talk about how cool interoperable apps are but they only interoperate if your APP actually lives up to the nip and kind standards.
nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub16c0nh3dnadzqpm76uctf5hqhe2lny344zsmpm6feee9p5rdxaa9q586nvr nostr:npub1n0sturny6w9zn2wwexju3m6asu7zh7jnv2jt2kx6tlmfhs7thq0qnflahe nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z
Here’s a comparison of how zap.stream links display on the three clients I regularly use.
Out of all of these, Amethyst is the clear winner, with Nostur in second place. Damus and Primal for Android are tied for a distant third and Primal on iOS doesn’t even finish the race. (Damus and Primal display an ugly hyperlink. The link on Primal for iOS is actually broken. Nostur doesn’t display the thumbnail image.)
People are pushing for us to do more zap.stream content at nostr:npub1key55ax33gkl50uqemvl4khrtqrhzm7wzpc7fhseutt5ddkcwcrqgxlt3h but the user experience on the most popular clients is wildly inconsistent and in some cases completely broken.
What can we do about this?
Discussion
nostr:npub1ejd9gpnqtzx9q6hhv6jt4xf9lgmn9x744rd5ep663p3h78lps3yqm9mf0l I actually just suggested to Kieran to change the "share on nostr" to share the nostr:ID event rather than http. It makes no sense and at least the stream will embed correctly in any client supporting the event. Meant to suggest the change for a while but kept forgetting and your screenshots just showed me how important it is.