Corrections
Event data arrives from agency feeds and camera coordinates are compiled by hand, so mistakes are possible in both. If you spot one, telling us is the fastest way to get it fixed — every report is read.
What to report
- A camera that does not belong to an event. The most common case: a camera is technically nearby but points somewhere irrelevant, or is on the wrong side of a mountain range.
- A wrong location. A camera pinned in the wrong city, or an event whose location label does not match its coordinates.
- A stale event. Something shown as active that ended days ago.
- A duplicate. The same earthquake or storm appearing as two separate pages.
- A figure that does not match the source. If our page and the agency’s own page disagree, ours is wrong.
- Wording that overstates what a camera shows. We treat this as seriously as a factual error.
- A stream that should not be listed. Broadcasters can ask us to remove their stream at any time, for any reason, and we do not ask why.
What to include
A useful report has:
- the URL of the page (event or camera);
- what is wrong, in a sentence;
- what it should say, if you know;
- a link to the official source, if your correction is about a figure or a location.
Send it to ai0lus@proton.me, or use the contact page. There is also a report control on individual camera pages for streams that are broken or geoblocked.
How we handle reports
- Removals come first. A request to unlist a stream, or a report that a page carries material we should not be showing, is acted on before anything else — usually the same day we see it.
- Wrong camera matches are fixed by unlinking the camera from that event. The unlink is permanent for that event: our automated matcher is explicitly prevented from re-attaching a camera an editor has removed.
- Wrong coordinates are corrected on the camera record itself, which fixes every event, city and map page that uses it at once.
- Figures that came from an agency feed are checked against that agency’s current record. If they have revised it, our next scheduled read picks the revision up automatically; if our copy is wrong for another reason, we correct it by hand.
- Duplicate events are merged, so the surviving page keeps every source link and the duplicate URL stops being served.
Where a correction materially changes what a page said — not a typo, but a figure or a claim — we note it on the page. Event pages already carry the timestamp of their last update, so you can always see how current the information is.
What we cannot do
We cannot verify what is happening at a location, confirm whether anyone is safe, or tell you whether an official order is in force. TubeTraveler is a live-camera discovery service, not an emergency service or a news organisation. For anything urgent, contact your local authorities and follow official emergency agencies directly.
We also cannot control the streams themselves. Cameras are operated by their own broadcasters on YouTube and can go offline, change their view, or be geoblocked without notice.
Related
Methodology · Data sources · Editorial policy · Reading live cameras during a major event