Docs · Get started
Can we confirm your post is live? Test results by platform
Short answer
We publish real posts through each platform's official API, then ask the platform for the post again and record what it says. The results show which platforms let a third-party tool confirm a post is live and visible, and which only confirm that a request was accepted. This page lists each experiment's method and result, with the date it was run. A result appears only when a record of the run exists; everything else says “not yet run”.
- Verified live
- Found on the platform with the visibility shown; not necessarily Public.
- Not yet tested
- No completed test is recorded; it is not a publishing failure.
Results
| Platform | Result | Test date | Visibility requested | What the platform confirmed | Evidence |
|---|---|---|---|---|---|
| YouTube | Verified live | 10 Nov 2026 | Public | Public — confirmed by YouTube. | View YouTube evidence — 10 Nov 2026 |
| YouTube | Verified live | 12 Nov 2026 | Public | Public — confirmed by YouTube. | View YouTube evidence — 12 Nov 2026 |
| YouTube | Verified live | 12 Nov 2026 | Public | Public — confirmed by YouTube. | View YouTube evidence — 12 Nov 2026 |
| Verified live | 13 Nov 2026 | Public | Public — confirmed by Instagram. | View Instagram evidence — 13 Nov 2026 |
What we learned
- Asking is not the same as getting. A platform can accept a post and apply a different visibility. Reading it back is the only way to see which one it applied.
- Some platforms can't be checked at all. Telegram is the clear case: A1 Lane keeps Telegram's own send response and labels the receipt Delivered (limited) rather than claiming more.
- A lost response is not a failure. If the publish answer never arrives, the post may exist. We look for it instead of retrying.
How we test
The same method for every platform:
- Publish one post through A1 Lane to an account we control, with a stated visibility.
- Record the platform's response to the publish call.
- Read the post back through the platform's API, by its ID, and record what the platform reports: existence, visibility, media.
- Compare the visibility we asked for with the visibility the platform reports.
- Where possible, also check the post from a signed-out browser (the human check).
LinkedIn: LinkedIn confirms sending, but A1 Lane cannot check the post afterward. No dated experiment is recorded in this table.
Telegram: Telegram confirms sending, but A1 Lane cannot check the post afterward. No dated experiment is recorded in this table.
Technical references — the read call behind each result: YouTube: videos.list (privacyStatus).
Tests still to run
These are questions, not results. A result is added only when its run is recorded and its evidence is public.
- Can we find a post on X after sending it? Not yet tested.
- Can we find a post on Bluesky after sending it? Not yet tested.
- Can we find a post on Mastodon after sending it? Not yet tested.
- Can we find a post on Discord after sending it? Not yet tested.
What each planned test checks
| # | Platform | Question | Pass looks like |
|---|---|---|---|
| E1 | X | Does the post we read back from X match the text and media we sent? | Text equal; media count equal |
| E2 | Bluesky | Does Bluesky show the post as soon as it is created, when we ask the account's own server? | Post found on the first check |
| E3 | Discord | Does Discord return the message we sent when we read it back? | Same content and attachment |
| E4 | Mastodon | When we ask for Public, does the server ever lower the visibility? | Visibility confirmed = visibility requested |
| E5 | YouTube | When we ask for Unlisted, does YouTube confirm Unlisted? | Visibility confirmed = visibility requested |
How each platform confirms a post: How each platform confirms a post. Why checking matters: How to prove a post actually published.
Written against A1 Lane on 2026-11-11; each result carries its own test date.