Forked from Zachary Skalko's Pen HTML 5 Microphone Visualizer.
| https://developers.google.com/web/updates/ | |
| https://dev.to/t/webcomponents | |
| https://developer.mozilla.org/en-US/ | |
| https://medium.com |
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <meta charset="utf-8"> | |
| <meta name="viewport" content="width=device-width"> | |
| <title>JS Bin</title> | |
| <style id="jsbin-css"> | |
| #visualizer { | |
| background-color: #ddd; | |
| } |
| import ethers, { | |
| Contract, | |
| providers as Providers, | |
| utils as Utils, | |
| Wallet, | |
| ContractFactory | |
| } from "ethers" | |
| import path from "path" | |
| import fs from "fs" |
-
Install Termux, an Android terminal emulator that provides a Linux execution environment and various tools.
-
Update system packages in Termux:
$ pkg update -y
A pattern for building personal knowledge bases using LLMs.
This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.
Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.
