docs(linkedin-reshare): warn that activity id and share id can differ - #27
Open
sergebulaev wants to merge 1 commit into
Open
docs(linkedin-reshare): warn that activity id and share id can differ#27sergebulaev wants to merge 1 commit into
sergebulaev wants to merge 1 commit into
Conversation
The parent-URN guidance said the activity id and share id are 'typically the same' and to swap the prefix. In practice they are not guaranteed to match: real posts exist where urn:li:activity:<a> and the share/ugcPost id differ, so a blind prefix swap silently reshares the wrong post or 400s. Clarify to prefer the post's real shareUrn/ugcPost URN and treat the activity->share swap as a best-effort fallback only.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The
parentformat guidance says the activity id and share id are "typically the same number" and suggests swappingurn:li:activity:→urn:li:share:.In practice they are not guaranteed to match. On real posts the activity URN and the share/ugcPost URN can be different numbers (e.g. a post whose activity id ends
...641024but whose ugcPost id ends...488704). A blind prefix swap then reshares the wrong post or is rejected with theparent must be a valid LinkedIn post URN400.Clarifies: prefer the post's actual
shareUrn/ugcPostURN (most scrapers return it), and treat the activity→share swap as a best-effort fallback only. Docs-only, one section.