How these guides are made.

Who writes it

The guides are written by the person who builds RepurposeThis. That has one advantage and one obvious conflict. The advantage is direct access to the pipeline: the effect ranges, the filter order and the encoder behaviour described on this site are read from the code that ships, not from a press release. The conflict is that the product is ours, so product claims are separated from general explanation wherever possible.

There is no anonymous “team of experts” claim here. If a page says something was measured, it was measured on a real file with the tools described below.

What gets tested, and how

• Effect ranges. Read from lib/effects.js and the image pipeline, then cross-checked against the interface. If a slider says 4–12, the table says 4–12.
• Uniqueness claims. Measured with dHash distance on output files, not asserted. Where a page gives a tendency (“geometry moves the hash more than colour”), it reflects measurements on the sample footage we had, and is labelled as a tendency.
• Platform behaviour. Based on published policy, public statements and observed behaviour. Platforms do not publish their detection pipelines, so these sections describe the class of technique and say so.
• Rights and licensing. Based on licence text and general copyright principles, not legal advice. Pages that touch rights say so in the byline.

What we will not claim

We do not claim that any file will be “undetectable”, that an account will not be actioned, or that a video will reach an audience. Those outcomes depend on systems and decisions outside the software. Where a competitor promises certainty, that is a reason to be sceptical, not a feature to copy.

Sources and links

Where a claim depends on a platform policy, the guide links to the policy or to the platform's own help page rather than to another blog. Where a term is technical, the glossary gives the definition and the guide gives the context.

We do not cite numbers we cannot reproduce. If a statistic appears — say, a copy limit or a range — it comes from the product or from a named public source.

Dates and corrections

Every guide carries a published date and a last-updated date. When a platform changes a policy or a claim turns out to be wrong, the page is updated and the date changes. Corrections are not quietly deleted; the current text is simply what stands.

If you find an error, send it to Telegram with the page and the sentence. Corrections that hold up are published with the next update.

Independence and compensation

There are no sponsored posts, affiliate links or paid placements on this site. The only commercial relationship is the one you can see: the app is sold here, and the guides exist because people searching for this topic may need it.

Competitor pages name products we have not purchased or tested in every configuration. Where that is the case, the comparison sticks to architecture and published terms, and says “check with the vendor” instead of inventing a price.

Use of automation

Drafting and editing use software, including language models, in the same way an editor uses spellcheck and a style guide. Measurements, code references and product claims are verified against the build. No page is published from a prompt without review.

Contact

Editorial questions, corrections and evidence requests: t.me/Sssaaalah2. The same channel handles support, so expect a human reply rather than a ticket number.