Skip to content

Conversation

@CodyTseng
Copy link
Contributor

No description provided.

@vitorpamplona
Copy link
Collaborator

Isn't it nicer to have an older version in the .content so that something can be displayed while the app figures out the updated version via the a-tag?

@vitorpamplona
Copy link
Collaborator

Also, if the inner event is replaceable, it's super easy to reassemble the a-tag and look for updates in the same relay hint of the e-tag. That can be a fallback for when the event is malformed.

@CodyTseng
Copy link
Contributor Author

You're right 👍

@Aspie96
Copy link
Contributor

Aspie96 commented Nov 21, 2025

My take is that the content should actually not be included. Yes, it gives something to display, but since the actual new content has to be fetched anyways, it's also a bit of a waste of bandwidth.

It still appears that the "e" tag is required even when the "a" tag is present. Is this intended?

The new suggestion doesn't even allow quoting a specific version of a replaceable event (through an "e" tag and excluding the "a" tag). Is this intended? Note that if one could do this, in that case the "content" surely would have to be provided (that version might otherwise become unavailable.

@CodyTseng
Copy link
Contributor Author

My take is that the content should actually not be included. Yes, it gives something to display, but since the actual new content has to be fetched anyways, it's also a bit of a waste of bandwidth.

Indeed it does waste some bandwidth, but as @vitorpamplona mentioned, it lets the client show something before it finishes fetching the latest version.

It still appears that the "e" tag is required even when the "a" tag is present. Is this intended?

I don’t think it’s necessary, but I’m not sure whether it might have other uses, so I didn’t change that part.

The new suggestion doesn't even allow quoting a specific version of a replaceable event (through an "e" tag and excluding the "a" tag). Is this intended? Note that if one could do this, in that case the "content" surely would have to be provided (that version might otherwise become unavailable.

That’s something I hadn’t considered at all. You’re right, if someone intends to quote a specific version of a replaceable event, they should use only the "e" tag and include that version directly in the content.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants