Skip to content

Editorial Policy

Nothing on this site is published from memory of an app. A guide gets written after the steps have been walked, either in the app or through the maker’s published documentation, and the page records which of the two it was.

The two fields at the top of every guide

verified_against names what the steps were checked against, and it takes one of exactly four values rather than free text, so it cannot be softened into a vague freshness badge:

  • device: <app and version> means that build was open in front of me. Naming a version I did not use would be fabrication, so the field stays empty of one unless it was.
  • vendor-docs means the company’s own help pages, newsroom or developer documentation, and nothing else.
  • vendor-docs+community means the documentation did not cover part of it and a community answer filled the gap. The body marks which claim came from there.
  • vendor-docs+thirdparty means the maker documents no route for this at all. The body marks the step where you leave supported ground.

verified_on gives the date of that check, and it is a separate field from the date the text last changed.

The last two values look like admissions and are meant to. Spotify documents no playlist copy function, so a guide about copying one cannot claim vendor documentation behind every step and stay truthful.

What counts as a source

Company documentation, help centres, and official developer references count. A vendor’s own community forum counts as weaker evidence and is labelled as such where a page leans on it.

A blog post reciting another blog post does not count. Neither does a screenshot of unknown age. Every guide carries a Sources block naming publisher and document, so the chain is visible instead of implied.

Where a number exists but nobody has published it, the page says the number is unconfirmed and moves on. The old version of this site printed hourly and daily following limits for Instagram as plain fact, and Instagram does not publish those figures. That is the pattern this rule exists to stop.

When the date is allowed to move

Only with the text. An app renames a menu item, the steps get rewritten, and the date follows the rewrite.

The reverse, bumping the date and leaving the words, is the most common way a tutorial site rots while looking maintained. It will not happen here, and the verified_on field exists partly so you can catch me if it does.

What happens when a step breaks

A guide whose steps no longer work gets rewritten or removed, not patched with a warning note. Where the underlying feature is gone rather than moved, the page goes and the URL is retired rather than redirected to something loosely related, because landing on an unrelated page is a worse outcome than landing on nothing.

Eight pages were removed on this basis in September 2026: dead devices, features that no longer exist, and instructions that asked readers to hand their login to a third-party app.

Corrections

Write to [email protected]. Corrections get made on the page itself, with a note of what changed, and the date moves because the text moved. I do not edit silently, because a silent fix leaves you unsure whether you misread the earlier version.

Sources

Last reviewed .