A sharing button changes the trust boundary of a transcription app. The editor belongs to one person; anyone holding a public link can read the published text. Those are separate responsibilities.
I am Julian Tao, the maker of ShortTranscript. This note describes the sharing behavior we implemented, rather than a claim that transcripts are automatically accurate.
Separate the private draft from the public snapshot
Publishing an editable result directly would make every later correction public. Instead, the owner reviews the draft, chooses a public title, confirms permission, and creates a snapshot. Private edits do not silently change it. An explicit update refreshes the snapshot at the same link.
The public representation only needs the chosen title, a platform label, reviewed text and timestamps. It does not need the account email, private job identifier, uploaded filename or original video address. Use a separate random public identifier rather than exposing the private job route.
Revocation is a lifecycle operation
Turning sharing off invalidates the link. Recreating it produces a different identifier. Deleting the original result also removes its snapshot. For expiring guest results, access must stop at expiry even before a scheduled cleanup runs. None of these operations can recall copies another person already saved.
Unlisted is still public
A noindex directive asks search engines not to index a page; it is not access control. The UI should say that anyone with the link can read it. Do not create links by default, and do not place them in a sitemap.
A useful acceptance sequence is: create, open without a login, edit privately, check that the snapshot is unchanged, update deliberately, revoke, recreate, and delete the original. Check the exported public fields at each step.
The Instagram transcription tool I maintain produces drafts that should be checked against the source audio before sharing. This is a maker-authored implementation note, not an independent review.
Disclosure: AI assisted the drafting of this note. Its product claims were checked against the implemented behavior and acceptance evidence.
Top comments (0)