ESP32-S3 Bench Guide
ESP32-S3 N16R8 bench guide: live pinout, lessons, simulators and the bench log.
Paste a YouTube history video. Get every historical claim checked against 32 academic, archival, and fact-checking sources.
Translation pending
EducationPython · JavaScriptGitHub @yairdomnitz-svgOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
History fact checker powered by Grok
Translation pending
Taken from the repository README
Loading the full README. The saved excerpt is shown below.
An AI-powered site that fact-checks historical claims made in YouTube videos, using Grok (xAI)
constrained to a fixed list of academic, archival, and fact-checking domains.
There is no build step: the CSS and JS are served as-is. Both pages reference
them as /styles.css?v=, where the hash is derived from the contents of
the CSS, the JS and the logo at startup, so a deploy invalidates a visitor's
cached copy automatically.Read the full README ↗The full README is unavailable right now. Read it at the original link. The saved excerpt is shown below.
An AI-powered site that fact-checks historical claims made in YouTube videos, using Grok (xAI)
constrained to a fixed list of academic, archival, and fact-checking domains.
There is no build step: the CSS and JS are served as-is. Both pages reference
them as /styles.css?v=, where the hash is derived from the contents of
the CSS, the JS and the logo at startup, so a deploy invalidates a visitor's
cached copy automatically.Read the full README ↗