ignore unknown tag type in incoming post, rather than raise exception #639
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Various ActivityPub implementations and proposals introduced tag types, e.g.
Edition
from Bookwyrm andLink
in fep-e232 Object Links, and assume this list will continue to grow.Given most folks behind these changes will consider backward compatibility and making things pain-less for other implementations, it should be generally safe for us to just ignore the tag type and treat the post as is, rather than to raise exception and discard the whole post.
Personally, I think fep-e232 inline quote is really interesting, and backed by most implementations like Pleroma/Misskey/Firefish except Mastodon, but that can be its own pr in the future.