SIGHT-E

What this is

SIGHT-E is a live UAP sighting tracker built for E Meta (e-meta.co, @emeta777). It keeps a running log and history, plots what can be mapped, flags viral social posts, and attaches a “likely explanation” tag — official when AARO has published a resolution, otherwise a clearly labeled heuristic.

Public satellite imagery cannot reliably catch a brief, car-sized hovering object. Free Landsat and Sentinel revisits are days apart at 10–30 meter pixels, and sharp commercial tasking is neither live nor free. This site tracks reports and official case files, then cross-checks them against public launch schedules and simple pattern cues. It is not a live infrared satellite feed, and it is not a government product.

Domain

The site is branded SIGHT-E · e-uap.com. As of the 15 November 2026 check, e-uap.com was still unregistered (Verisign RDAP 404 “not found,” and public DNS NXDOMAIN). It has not been purchased or pointed at this project yet. A .com registration and renewal were about $11.17 at Cloudflare Registrar (at-cost) and $11.81 at Porkbun (optional $1 off first year with code AWESOMENESS). See DEPLOY.md for DNS and hosting steps. This project is not affiliated with the existing sight-E energy company at sight-e.app / sight-e.com.

Sources

• AARO — official case resolutions and official UAP imagery from aaro.mil. The box’s datacenter IP is blocked by AARO’s Akamai edge, so v1 uses a dated public-page snapshot with links back to the official pages. Nothing is invented.
• X — public posts supplied through a seed file and a drop-in inbox (data/inbox/x_posts.json). The paid X API is not used. The Afghanistan “jellyfish” posts in this build were read with built-in public X tools on 15 Nov 2026 (CT).
• NUFORC — not mirrored. Their robots.txt allows public-page crawling, but their Terms of Service (updated 19 August 2026) forbid scraping and also forbid republishing or hosting a collection or substantial portion of the databank, including JSON. The AI/search-crawler permission explicitly says “No redistribution.” SIGHT-E therefore only links out to the NUFORC databank. Written permission for bulk use would be requested from support@nuforc.org before any future ingest.
• Launch Library 2 — free API of recent and upcoming orbital launches, used as a context layer.
• CelesTrak — Starlink TLE catalog reachability and satellite count, plus the TLEs used by the “Was it Starlink?” checker. v1 does not compute overflight geometry for every radar pin.
• World alerts — headlines and outbound links only (no article bodies) from GDELT DOC 2.0, ReliefWeb Disasters RSS, USGS significant earthquakes, GDACS alerts, BBC World, Al Jazeera, The Guardian World, NPR World, and UN News. Official Reuters and AP RSS feeds were not reachable from this box. Items are de-duplicated across sources and tagged by severity.
• US Skies / Europe Skies — anonymous OpenSky Network /api/states/all snapshots (non-commercial terms, credit on the tabs). Emergency squawks 7700, 7600 and 7500 are flagged; 7700 and 7500 also enter the critical-alert queue. Alaska and Hawaii are included with the continental US. Military-looking callsigns are a prefix heuristic, not an official ID. EASA and EUROCONTROL public RSS items that mention airspace restrictions are listed when they match; live NOTAM feeds are not freely available without an account, and FAA news RSS was blocked from this box.
• GPS interference — the public OpenSky state vector does not include NIC/NACp, so this site does not derive a jamming heatmap. The GPS jam tab links and embeds GPSJAM (John Wiseman) with credit. GPSJAM’s dataset is not copied or republished.

Tools

• Was it Starlink? — you enter a city or coordinates and a time in America/Chicago. The page computes Starlink train and ISS look angles in the browser with SGP4 from CelesTrak TLEs, then checks Launch Library 2 launches and reentries in the same window. A shareable URL stores the query in the hash. Results are approximate.
• Emergency squawk scoreboard — today’s 7700 / 7600 / 7500 counts for the US and Europe versus a rolling baseline from stored history, with a sparkline, composed as a card you can screenshot.

Flags and heuristics

An X item is flagged viral at 1,000 likes or 50,000 impressions, and trending at 200 likes. Likely-explanation tags on non-official items are keyword and launch-window scores (Starlink train, launch, balloon, drone, aircraft, birds, unverified, unknown). Official AARO wording always wins and is labeled official, with AARO’s own confidence (high, moderate, or unresolved). Heuristic tags are not determinations.

The viral “jellyfish” posts

The two seeded X posts are the 14–15 Nov 2026 (CT) posts from @anonymoushadoww about a claimed “MQ-9 Reaper Drone Recorded JellyFish UAP in Afghanistan 2024.” At the time they were read they had about 1,200 likes and about 73,000–77,000 impressions each — viral under this site’s threshold, but not an 11,000-like post. No higher-engagement original with that exact framing was found in that search. The claim is logged as unverified: the footage has circulated from an anonymous “Ghost” source, the U.S. withdrawal from Afghanistan was completed in August 2021, and no official AARO confirmation of a 2024 Afghanistan Reaper jellyfish event was found for this snapshot. The well-documented official “jellyfish” case on this site is the 2017 Al Taqaddum, Iraq aerostat video, which AARO assessed as a balloon cluster.

Run it

From the project folder: python3 fetcher/fetch_all.py then ./scripts/serve.sh. Optional: python3 fetcher/fetch_all.py --watch 1800 to refresh every 30 minutes. To add X posts later, drop them in data/inbox/x_posts.json and run the fetcher again.

SIGHT-E is not affiliated with the U.S. Department of Defense, AARO, NUFORC, or the existing sight-E energy company. Official text is paraphrased conservatively from public AARO pages; go to the source links for the full record.