ESP32-S3 Bench Guide
ESP32-S3 N16R8 bench guide: live pinout, lessons, simulators and the bench log.
翻譯準備中
尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證Production marketing site for Uoink.
翻譯準備中
取自儲存庫 README
正在載入完整 README。
檢視完整 README ↗Production marketing site for Uoink, the local-first YouTube layer for any AI.
Built with Next.js App Router and deployed to Vercel. The product repo lives at github.com/ryanbiddy/uoink; this repo is only the marketing site.
npm install
npm run dev
Open http://localhost:3000.
npm run build
The site uses output: "export" for static deployment.
content/release.json supplies the product version and verified MCP counts to the site and both release-content scripts. Static discovery cards and crawler text must match it; check-launch-content.cjs checks those copies.
python scripts/sync-mcp-from-release.py <product-checkout> --ref v3.11.2
node scripts/check-launch-content.cjs
The sync script reads committed files with git show, parses Python ASTs without importing product code, and checks stdio names against .mcpb/manifest.json. It defaults to the product ref in content/release.json; --ref <git-ref> selects another ref. It updates the counts in content/release.json and writes the site's tool catalog and manifest.
For 3.11.2, the catalog was generated with --ref v3.11.2, which resolves to the release merge commit a02f1029e7e027bff3d739a8d7150ba3a15771b7. The tool content is the same as the earlier pre-tag sync; only the source commit changed. The inventory remains 91 tools over stdio and 91 in the HTTP registry, with 35 in core mode. Both transports advertise flattened tool schemas; the server still checks the exact schema. The public changelog keeps 3.11.2 and earlier releases separate. Earlier dates are preserved; no 3.9.0 publication date is asserted.
3.11.2 adds a Mac preview for Apple Silicon on macOS 15 or later: Uoink-3.11.2-macos-arm64.dmg, signed with a Developer ID and notarized by Apple, plus a separate Claude Desktop bundle, uoink-3.11.2-macos.mcpb. Intel Macs are not supported. app/content/product-status.ts holds every Mac string the site renders. The release also stops a failed index write from wedging the helper, refreshes re-captured older items in place, refuses MCP stdio requests over 64 KiB with their own request ID, and trims captions that run past the video. The Windows installer is still unsigned, and the Chrome Web Store listing is not live.
The tool inventory line in public/llms-full.txt names release commit a02f1029e7e027bff3d739a8d7150ba3a15771b7. check-launch-content.cjs checks it against the generated manifest's source commit. The Windows installer is 390,126,021 bytes; the release checksums are in public/llms-full.txt. Until the release numbers replace the placeholders here and in public/llms-full.txt, and installerSizeBytes in content/release.json is set, check-launch-content.cjs runs every other check and then fails, listing each placeholder.
For 3.11.1, Agent Install 27 passed 11/11 isolated-install checks, including stdio inventories of 91 full / 35 core / 91 modern tools, Claude Code 2.1.310 (haiku) connecting with 91 tools and calling get_schema_version, helper writes surviving a restart, and GET / redirecting to /dashboard. The full receipt scope is listed on the agent setup and changelog pages. Codex CLI was not re-tested in receipt 27.
Earlier 3.11.0 testing: Claude Code 2.1.308 listed all 91 tools and called one, and Codex CLI 0.153.4 called two tools. In 3.10.0 testing, Claude Code also ran with the skill and CLI only, and the plugin loaded its skill and started MCP, but its tool calls were not run end to end. Claude Desktop and Cursor retain their earlier MCP testing status. Gemini CLI, pi, and the remaining connection recipes are not yet tested. Stdio works without the Uoink helper running. Start Uoink from the Start menu for the dashboard, browser button, and monitored-playlist polling.
For Claude Desktop on Windows, download and open uoink-3.11.2.mcpb. Enter the full path to your Uoink folder when asked; Desktop does not expand %LOCALAPPDATA%. Reinstall the bundle and restart Desktop after updating.
On the Mac preview, open uoink-3.11.2-macos.mcpb instead and select the installed Uoink.app. For other clients, link /Applications/Uoink.app/Contents/Helpers/uoink into a folder on your PATH and run uoink connect <client>, which prints a config with the installed app's paths. MCP clients on a Mac are not yet tested.
For Claude Code, run this in PowerShell. The expanded paths are absolute:
claude mcp add --scope user --transport stdio uoink -e PYTHONIOENCODING=utf-8 -e PYTHONUTF8=1 -- "$env:LOCALAPPDATA\Uoink\python\python.exe" "$env:LOCALAPPDATA\Uoink\uoink_mcp.py"
For Cursor and other stdio clients, add this server config. Replace %LOCALAPPDATA% in both paths with your full local app-data directory, then restart the client:
{
"mcpServers": {
"uoink": {
"command": "%LOCALAPPDATA%\\Uoink\\python\\python.exe",
"args": [
"%LOCALAPPDATA%\\Uoink\\uoink_mcp.py"
],
"env": {
"PYTHONIOENCODING": "utf-8",
"PYTHONUTF8": "1"
}
}
}
}
Cursor is reported to send only the first 40 tools to its agent. Add "UOINK_MCP_TOOLSET": "core" to the server env to keep the previous 35-tool set and stay under that cap. Omit it for every tool. Consent gates are unchanged.
ChatGPT and claude.ai use copy and paste only. Uoink does not connect to the ChatGPT app over MCP.
Connect this repo to Vercel and let it auto-detect Next.js. Production canonical is uoink.app; the legacy video domain redirects there.
The family resolutions govern the site: rust #C2410C actions, cream #FFF4EC primary button text and reversed marks, blue #002C9B links on cream, muted #5C4A40, and hairlines #EBD5C5. Every focusable element gets a 2 px rust focus ring with a 2 px offset. Eyebrows use uppercase Inter 700 at 12 px with 0.08em tracking. Wordmarks use the shared SVG paths. The family strip has a 0.8 x cap-height gap and a muted middle dot. The yellow detail is #FFD23F at every size and on every ground. The favicon, dark theme decision, and app-art outline remain unchanged.