Cross-platform publishing
One idea, one edit, and a version per platform that respects what that platform actually accepts.
This describes a design, not a running service
The problem
Posting the same text everywhere produces a version that is truncated on one platform, missing a required title on another, and carrying a link that a third one silently strips. The alternative, rewriting by hand five times, is where the work actually goes.
How the product is designed
- A master draft holds the idea. Each selected account gets its own version, and an edit to the master applies only where it fits, saying plainly which targets could not take it and why.
- Validation runs against the recorded limits for each platform, counted the way that platform counts, so a character ceiling is checked in graphemes where the platform uses graphemes and in weighted units where it uses those.
- Every platform limit shown anywhere on this site is generated from the connector registry and carries the document it came from and the date a person read it.
What is actually built
The composer, the per target versions, the validation rules and the generated limits dataset are built. The publishing step is not: no connector is verified in production, so a validated draft can be scheduled internally and cannot reach a platform.
Found something wrong on this page
Contact channels will be published here before general availability. No legal or support inbox is operating during this preview.