| { | |
| "window.zoomLevel": 2, | |
| "workbench.startupEditor": "none", | |
| "explorer.compactFolders": false, | |
| "workbench.iconTheme": "material-icon-theme", | |
| "editor.fontSize": 18, | |
| "workbench.colorTheme": "OM Theme (Default Dracula Italic)", | |
| "code-runner.executorMap": { | |
| "python": "clear ; python -u", | |
| }, |
Currently in no particular order. Most of these are kind of ancient.
Where's all the modern documentation? So much of what I've turned up searching is other folks complaining about having few options beyond reading source code.
The OREILLY books, while dated, seem to be some of the best available. Note that these can be read with a 7-day trial. Do this! At least get through the introduction section and first chapter of each to see if it's what you're after.
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.
原作：Super Sudokoid: Dark Inversion - The M
原作者であり、また翻訳版の作成を許可してくださった The M 氏に感謝します。 また、翻訳に関してフィードバックをくださったぬぼんば様に感謝します。
亜空間航行中、（よくあることだが）近くの惑星からの救難信号を受信した。信号の発信源である惑星は、私が持っている星図には載っていない。しかし、シップのコンピューターは、この惑星こそが複雑なパズルと超兵器で知られている古代パズロ族の失われた故郷であると断言している。恐る恐る、その惑星へ航路を設定した。
現在の最新バージョンは1.0.5 JP rev3です。
| <!DOCTYPE html> | |
| <html lang="en"> | |
| <head> | |
| <meta charset="utf-8"> | |
| <title></title> | |
| <link href="style.css" rel="stylesheet" /> | |
| </head> | |
| <body> | |
| <script src="http://ajax.googleapis.com/ajax/libs/jquery/1/jquery.min.js"></script> |
Well, CHIP & PocketCHIP shipped with the now ancient Debian 8 (jessie) and really old kernel 4.4. There's a big security risk if you take your device online in any meaningful way.
Not just that, the software support from various app developers stopped a long time ago.
Refer to this release schedules and this page for LTS support information
| # CLAUDE.md | |
| Trailmark — an iOS app for logging hikes, backed by a Node.js REST API. | |
| - `ios/` — SwiftUI app, iOS 17+, native components only | |
| - `api/` — Node 22, TypeScript, Express, Postgres 16 (Kysely) | |
| - `packages/contracts/` — zod schemas + generated OpenAPI. Single source of truth for both sides. Change the contract first, then the server, then the client. | |
| Nested rules live in `api/CLAUDE.md` and `ios/CLAUDE.md`. Longer workflows (release, migration, security review) are skills in `.claude/skills/` — do not paste them here. |