that makes sense for sure but couldnt you just allow for longform kind 30023 just for folks who want to make use of it?
or is that problematic in some way I dont see?
Discussion
yes but its more complicated than just write a new kind. longform supports editing via replaceable events, etc. would be a lot of ux work.
i see now on the git:
""Social" clients that deal primarily with kind:1 notes should not be expected to implement this NIP."
i am supposing what you wrote above is why they stated that...