alltheseas

Great suggestion @Sjors I added this as a suggested best practice on nostrability repo https://github.com/nostrability/nostrability/issues/96

> But the UI should make it clear that the author won't see it. Agree it's a design problem. Unsure of the best solution. @robagreda @karnagebitcoin

@asoltys do you have plans for NWC?

NWC reported trouble coinOS -> Damus https://damus.io/nevent1qqstf89qghlekk22xc3wzsy69nqnm4vydxqmvpketvex3jxt9g0qfmqpp4mhxue69uhkummn9ekx7mqppamhxue69uhkummnw3ezumt0d5q3qamnwvaz7tmwdaehgu3wwa5kuegprfmhxue69uhhyetvv9ujumn0wd68yurvv438xtnrdakskv863q

Nostur nwc behavior might help troubleshooting Https://njump.me/note1z6u7gnq0h4qhhtmrukq0jfh2qyzlp3vx08u0s5zesymmlvy7emlst2cz9k

If I remember @merryoscar and @hzrd149 @danconwaydev @tyiu dustin d and others were discussing at one of the Riga workshops

https://satcom.app/ by @jinglescode attempts this for websites. i think with kind1s

nip-22 long form article reply support added to nostrudel by @hzrd149

> We should maybe deprecate it "It" is not clear to me. What are you suggesting to deprecate? Kind 1 replies?

Here is a nostrability/schemata nip-22 JSON validation [schema](https://github.com/nostrability/schemata) - https://github.com/nostrability/schemata/tree/master/nips/nip-22. cc @hzrd149