Replies: 3 comments
-
i agree. good point. |
Beta Was this translation helpful? Give feedback.
0 replies
-
This has been fixed by #1679 by @pablof7z, as updated by @staab. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
According to NIP-18, the
content
of a repost should be the stringified original event, although it may also be an empty string.NIP-70 defines protected events, which shouldn't be hosted on relays which otherwise fetch events from other relays.
I'd argue that, while normally the
content
of a repost should be the stringified original event and an empty string is not recommended, it actually should be an empty string when the original event is protected.Of course, it's not guaranteed that an event will not be hosted by other parties anyways, but we do have NIP-70 and if the author of the original event doesn't want it to be posted elsewhere, I think it's reasonable that reposts should merely reference it, not contain a copy of it.
I think either NIP-18, NIP-70 or both should be amanded to state this.
Implementing this change on clients in the reposting operation is absolutely trivial and implies no change in parsing reposts (since clients should already be able to handle empty strings). It would also require no change whatsoever on the relay side.
Beta Was this translation helpful? Give feedback.
All reactions