THE SHORT ANSWER

Treat the quote as belonging to a version, not to the post in general. Record what the screenshot showed and when it was taken, note what the live post now says, and check any edit history you can legitimately access. If the two disagree and the history is unavailable or unclear, quote each version with its own label and stop there rather than assuming the current text is what was originally shared.

Have a username or photo?

Find public social profile clues with our TraceSeek app.

Start by dating each observation, not by picking a winner

A screenshot is a record of what one person saw at one moment. A live post is a record of what it says now. Neither automatically corrects the other, and neither proves what a reader saw earlier. Open a small note beside the quotation and write two dated lines: when the screenshot was captured (if that time is visible or was recorded) and when you viewed the live post. Then write the wording from each, exactly, in separate lines. The useful artifact is a versioned quotation with timestamps, not a single settled sentence chosen by preference. [Mastodon: edit history and shared-post notifications]

  • Label each quotation with the time you observed it and the medium (screenshot or live page).
  • Keep the exact wording of each version in your notes before summarising anything.

What an edit history can and cannot settle

Mastodon's editing feature was introduced with original and previous versions kept in a history view, and people who had shared a post were notified of edits. That means an accessible history view is the closest thing to a timeline of the post's wording. It can show that a wording changed and roughly what changed. It does not tell you what any particular reader saw, why the edit happened, or what the author intended. It also does not prove that a screenshot was taken before or after a specific revision unless the dates line up. [Mastodon: edit history and shared-post notifications]

  • If a history view is open to you, quote the specific version you are using and say where it sits in the list.
observationlimitnext step
An accessible history lists an earlier version with different wordingIt shows the post's own recorded history, not what any reader encounteredQuote the earlier wording as 'an earlier version in the history, viewed on [date]'
People who shared the post were notified of an editNotification does not mean every share or screenshot reflects either versionDo not infer what a particular sharer saw; date your own observation instead
The current live post matches your screenshotIt may simply mean no later edit is visible, or that controls differ by server or clientNote it as a match at the time of checking, not as proof of an unchanged history

Why availability varies and what to do about it

Current Mastodon documentation covers editing statuses and viewing a status edit history, but availability and access depend on the status and the server. Which controls appear can differ between interfaces and versions. Do not treat a missing history button as evidence that no edit occurred, and do not treat a visible one as proof that every earlier version is listed for you. If the history is not reachable in your app, quote only what you directly observed and record the gap as a limitation. [Mastodon: current status history documentation]

  • Check the options shown in your own app version rather than assuming a standard layout.
  • If history is not accessible, write 'edit history not accessible to me on [date]' in your notes.

Separate observation, limit and decision

Keep three things apart in the final write-up. The observation is the wording you saw and when. The limit is what the observation cannot establish, such as the original text, the author's intent, or what other readers saw. The decision is what you will quote and how you will label it. For example: 'This quote matches a version visible to me on 3 May; I could not access a history view, so I cannot say whether the wording changed before or after.' That sentence is honest and still usable. What it avoids is the quiet move of presenting the current text as if it were the text someone shared earlier.

observationlimitnext step
Screenshot wording differs from current live wordingThe screenshot may precede or follow an edit; capture time may be uncertainPresent both quotations with their dates and sources, and quote neither as the sole version
Live wording differs from a quotation in an older articleThe older article may have quoted a version now supersededAttribute the older quotation to its own date rather than correcting it silently
Wording is identical in bothNo visible change at the time you checkedStill date the quotation, because the post could be edited later

When the source is absent, private or ambiguous

If the post is gone, restricted, or you cannot confirm that the screenshot and the live page refer to the same post, stop. Record the precise limit: 'live post not accessible on [date]', or 'cannot confirm the screenshot depicts this post'. Do not try to reconstruct a private post from replies, quotes, caches or other people's descriptions, and do not try to identify an account from a similar image or username. A matching avatar or handle is not proof of identity, and a privacy setting is not evidence of intent. The safe outcome is a labelled uncertainty, not a confident quote built on inference.

  • If the post is unavailable, quote only the screenshot and say it could not be verified against a live post.
  • If you cannot confirm the two items are the same post, do not merge them into one quotation.

A hypothetical example of versioned quoting

Hypothetical: a screenshot saved on 12 April shows a public post reading 'the proposal will be reviewed next month'. On 20 April the live post reads 'the proposal was reviewed last month'. An accessible history shows one earlier version. The write-up does not say 'the author said the proposal would be reviewed', because that treats one version as the standing text. It says: an earlier version visible in the history, quoted as captured on 12 April, said one thing; the version visible on 20 April said another. Any argument built on the first wording is then clearly tied to that date. This example is illustrative only. [Mastodon: edit history and shared-post notifications]

A couple more questions

The live Mastodon post says something different from my screenshot. Which one should I quote?

Quote both, each with the date you observed it, and say whether an accessible edit history explains the difference. If history is unavailable, describe the disagreement as a limit rather than choosing one version as the post's true text.

Does an edit notification or history view prove what the original post said?

Mastodon's editing feature retains original and previous versions in a history view and notifies people who shared a post. That supports a versioned quotation, but it does not prove what any particular reader saw or why the edit was made. Quote the specific version you can see, with its date.

What if I cannot see an edit history at all?

Record it as a limit: 'edit history not accessible to me on [date]'. Availability depends on the status and server, so a missing control is not evidence that no edit occurred. Quote only what you directly observed and keep the uncertainty explicit.

Can I check the same post on another app to see the history?

You may view the post through another interface you legitimately use, but interfaces differ and you should not assume another app exposes the same controls. Whether it helps depends on what that interface offers. In any case, keep each observation dated and attributed to where you saw 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.