A Mastodon boost places someone else's post on the boosting profile, so treat the displayed text as the author's words and the profile as a redistribution point. Check the two separately: read the post to find its original author, read the profile to understand who shared it, and record both without assuming the booster endorses every sentence or has any personal tie to the author.
Find public social profile clues with our TraceSeek app.
Why a boosted post looks authored by the profile
A boost moves an existing post onto a profile's timeline, where a screenshot or OCR pass may flatten the two into a single line of text attached to the profile name. The platform documents boost as a distinct reshaping action, separate from a favourite, which only adds the post to a list and notifies its author. That distinction matters editorially: the words belong to whoever wrote the post, while the boosting profile is a redistribution point. When a capture merges them, the first move is to split the record back into author, content and booster before drawing any conclusion. [Mastodon: federated timelines and post interactions]
- Label every quote with the account that wrote it, not the account that shared it.
- Keep the boosting profile name in a separate field from the author name in your notes.
Checking the original author from the public post
Open the post itself and read the attributed account, timestamp and any visible context rather than the profile that surfaced it. Because a server may only hold some public posts and may exclude replies by visibility or authorization, a single view can be incomplete; searching a known remote public URL can fetch that object to the local server, but this does not guarantee a complete thread or an authoring view. Use whichever public view you can reach and state which one you used. If the original post cannot be opened or its author is ambiguous, record that specific limit and stop there rather than guessing an author from layout or avatar style. [Mastodon: federated timelines and post interactions]
Checking the boosting account as a separate object
The boosting profile deserves its own pass: what it publicly shares and how it describes itself. A profile description is self-entered, so record it as an unverified claim. A profile name, avatar or similar look is not identity, ownership or proof of intent, and a resemblance or a search result is not confirmation. Keep the profile's description and its boosts in separate evidence rows, each with its own confidence note.
- Record the profile's self-description as an unverified claim, not a fact about the person.
- Note when a search returns only partial or no public coverage for the account.
Recording redistribution without implying endorsement
A boost is a sharing action; it does not document agreement or a personal relationship. Write the observation in neutral terms: this account reshaped this post onto its profile at this point in the public record. Do not extend a boost to approval of the post's claims, shared membership in a group, or a personal connection to the author. Where an AI tool summarises the profile and the post together, mark each merged statement as a guess unless a public source states it explicitly.
| observation | limit | next step |
|---|---|---|
| The post appears on a profile timeline | The display may be a boost, not authorship | Open the post to read its attributed author |
| OCR output joins a name to quoted text | OCR can merge author and booster lines | Split names and quotes into separate fields |
| Another profile looks similar | Similarity is not identity or intent | Treat as an unresolved lead, not proof |
| A favourite is noted on the post | A favourite is not a boost or an endorsement | Keep the two actions in separate rows |
When to stop rather than infer
Stop when the original post cannot be retrieved, when only a screenshot is available and it crops the attribution, when an AI summary blends author and booster without a citable public line, or when a search result is a lookalike account. In each case record the missing piece and the date. Do not seek private records, do not attempt to identify the person behind an account, and do not treat a profile photo, badge or privacy setting as proof of identity or safety. The record is finished when the limits are written down, not when a guess fills the gap. [Mastodon: federated timelines and post interactions]
- Close the note with the missing artifact and what public evidence would resolve it.
A couple more questions
Does a boost mean the profile agrees with the post?
No. A boost is a sharing action documented as reshaping a post onto a profile; it says nothing about agreement, and it should not be read as endorsement of the post's sentences.
How should OCR output be handled when it joins a profile name to another account's text?
Treat the joined line as an extraction error until you can open the post and read its attributed author. Split the author, the text and the boosting account into separate records.
What if the original post is unavailable or only a screenshot exists?
Record that the original source is absent or cropped and stop the authorship inference. Note the date and what public evidence would be needed to resolve it.
Sources & editorial notes
Official references checked on October 24, 2026. Checklists, comparison tables and example wording are DateClues editorial tools, not official tests or validated risk scores.
General information. No guide or tool can certify a person’s identity, intentions or safety. Read our editorial standards.