Replies (7)

The issue is not the usage from a user perspective; the issue is that it creates a fork, between clients that support this and clients that don’t. A client that shows edits will show an entirely different thing than a client that doesn’t. Keeping kind 1 simple is crucial which is also why we don’t support markdown, html, and all kinds of bells and whistles. If you increase the cost of running a node few people will. If you increase the cost of creating a client few people will.
You can’t depend on SDKs to abstract complexity; that’s the death of protocols because then the SDK becomes a choke point and developers using the SDK become captive, downstream, to the SDK.