Repository navigation
Lexicon proposal: presentation hint on app.bsky.embed.record for "From @handle" media shares #5820
petermazzocco
started this conversation in
Bluesky Lexicons
Replies: 1 comment
|
Updated to add example images of a branch I am actively working on that allows me to work within the limits of the protocol for proper credit and sharing. I'll commit and add the branch on the issue soon! |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Quick Summary
Add an optional
presentationfield toapp.bsky.embed.record(and pass it through on#view), mirroring the existingpresentationfield onapp.bsky.embed.video. A value of"media"tells clients the author is sharing the quoted post's media, so clients can render the quoted video or images at full size with a compact "From @handle" attribution instead of a nested quote card.Motivation
This was one of my favorite features on Twitter. On Twitter, people can copy a video's address and paste it into a new post. The new post plays the video full size with a "From @originalauthor" badge linking to the original. It's widely used for reaction videos, meme replies, and "saving this for later" posts, and the creator keeps credit. It's led to an increase in people using the bookmark feature as well.
On Bluesky the closest action is a quote post, which renders the video small and nested inside a quote card. However, a client can't simply render every quote of a video post media-first, because that would also change commentary quotes ("look at this"), where the quoted post's text and context matter. The author's intent needs to be recorded in the post.
Why not just re-upload the video?
I prototyped that in social-app first: download the original blob, upload it to the poster's repo, and quote the original via
recordWithMedia, rendering a badge when the two blob CIDs match. It did not work for me, and has real downsides:Proposed change
lexicons/app/bsky/embed/record.json:The AppView copies
presentationfrom the record into the view, the same wayapp.bsky.embed.video#viewcarriespresentationtoday.Semantics
"media"is only meaningful when the embedded record is a post with media (video, and optionally images or galleries). For anything else, clients treat it as"default".app.bsky.embed.recordonly, notrecordWithMedia.Why this shape
detachedEmbeddingUris), disabling quotes (postgatedisableRule), and blocks.app.bsky.embed.video#presentation.Alternatives I considered
viastrongRef onapp.bsky.embed.videoused with a re-uploaded copy. This records intent explicitly but keeps all the copy downsides above.app.bsky.embed.mediaShare). Clearer naming, but older clients would render nothing instead of a quote, and it duplicates most ofapp.bsky.embed.record.Open questions I would like discussion on
"media"also cover images and galleries, or start with video only like Twitter? I could see benefit in doing images as well with alt text.Examples
Click the ellipsis and choose

Share video in a postComposer dialog with

From @handlebadgeAll reactions