How we research
The short version: primary sources first, dates on anything that changes, and no invented numbers.
Where do the facts come from?
From primary sources wherever possible: X's Help Center and developer documentation, X's open-source code, standards bodies and government agencies.
Examples of what we rely on:
- X's own pages for features, menus and limits, such as the Help Center and the developer docs on counting characters.
- X's open-source twitter-text configuration for the exact counting rules the tools use.
- Standards such as RFC 4180 (CSV) and RFC 5545 (iCalendar) for the export formats.
- Government and regulator guidance such as the FTC's charity and endorsement pages and the IRS charity search, for campaign ethics.
When X's own pages are unavailable or contradict each other, we use reputable independent coverage, say so on the page, and word the claim carefully.
How do we handle facts that change?
We date them. X changes limits and features often. Statements like posting caps or scheduling options are written "as of November 2026" and rechecked when we update a guide. The "Updated" date on each guide changes only when the content changes.
What do we never do?
We do not invent statistics, testimonials, user counts, case studies or experts, and we do not claim to have tested things we have not.
Example posts in guides are clearly examples. Where a guide shows numbers in an example campaign, they illustrate a format, not a real result.
How do the tools get checked?
Each tool's logic is covered by automated tests run before every release, including the character counting rules and the CSV and ICS output.
How do I report an error?
Email contact@tweetdrive.org with the page and the source. We correct mistakes quickly.