Repository navigation
Conversation
gynsus
force-pushed
the
pr/promotion-fields
branch
2 times, most recently
from
September 22, 2026 08:24
9997ccf to
212dd06
Compare
A per-channel meta.first_comment (≤2200, Instagram's comment limit) is
posted by FirstCommentPoster right after a successful publish — YouTube
via commentThreads.insert, Instagram via /{media}/comments. Failures
are logged and never fail the live post; Stories and in-review posts
get no comment. Connect flows request the comment scopes.
Reworked for the post_platforms-into-posts merge: the poster takes the
post itself and the rules use the prefix-parameterized meta keys.
…, video alt text
- Instagram/Facebook location_id (Facebook place ID, entered by hand
since Meta closed place search) + location_name display label; tags
feed/reel/carousel containers and page posts, never stories
- YouTube Shorts SEO: tags (≤30 of ≤100 chars), default_language
(BCP-47) and recording_location {lat, lng, description}, sent through
snippet and recordingDetails
- video alt text on the networks that support it (Bluesky, Mastodon),
gated by the supports_video_alt_text media rule so the editor only
offers the alt tab there
Reworked for the post_platforms-into-posts merge: publishers read the
post's own meta, rules use the prefix-parameterized keys and the panels
read errors through useMetaErrors.
gynsus
force-pushed
the
pr/promotion-fields
branch
from
October 11, 2026 08:24
34f8778 to
d9c6c9d
Compare
gynsus
changed the title
This branch has not been deployed
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.
One post per network — but the fields that make a post promote well differ per network. This adds three per-platform capabilities, all stored in the post's
meta, all validated centrally inPostPlatformMetaRulesso the web editor, REST API, and MCP accept them equally.Location tagging (Instagram + Facebook)
meta.location_id/meta.location_nametag IG feed/reel/carousel containers and FB feed/photo posts with a Facebook place. Meta closed place search to third-party apps, so the ID is entered by hand — the name field is just a human label. Stories and carousel children don't acceptlocation_id(API limitation), and the publisher respects that.YouTube SEO metadata
tags→snippet.tags,default_language, andrecording_location{lat, lng, description}→recordingDetails— the upload request asks forsnippet,status,recordingDetailsparts accordingly (meta.title,category_idand the description are upstream's own fields now).Video alt text (Mastodon + Bluesky)
Both accept media descriptions on video, but the alt editor only opened for images. It now opens for video items on the networks that support it, gated by a new
supports_video_alt_textmedia rule; Mastodon sends it as the mediadescription, Bluesky asembed.alt.Testing
Meta persistence covered in
PostApiPlatformMetaTest/PostPlatformMetaToolTest; publisher behavior in the Instagram (location on container), Mastodon (video alt), Facebook, Bluesky, and YouTube suites. All running in production on a self-hosted instance.