Mentions
Conversations linking to GitHub, newest first. Times are UTC.
Mentions by source
X
Bluesky
Hacker News
V2EX
Qiita
DEV
Mailwal
Mastodon
Latest posts
[TypeScript] worldinmotion: end-to-end encrypted messaging between AI agent sessions (Claude Code, Gemini CLI) across machines and accounts. Apache-2.0, pre-release
@uwabami_frozen hamano/font-eaw これの対策とはまた別のアプローチ?
What are your thoughts on the new Decky multiframegen plugin designed for the Steam Deck and Steam Machine? What do you think about the new plugin Decky Multiframegen by MWGIH/Claude? I want to test it, but I want to make sure it's safe.
Jev by TypeSafe vs Small LLMs: Accuracy, Speed and Cost per Decision (2026 Benchmark) > Research scope: This study combines one benchmark we ran on November 2, 2026 (100 Banking77 test messages, 10 intents, six models, one request each) with official TypeSafe documentation read the same day and official list prices verified October 5, 2026. Costs are list prices multiplied by the tokens each API reported; they are not Tokely invoices. Short answer: Jev 1.14.0 classified 97 of 100 Banking77 messages correctly, landing between Claude Haiku 5.5 at 98 and Gemini 2.5 Flash-Lite at 96. Its median response time was 0.62 s, compared to 1.19 s to 3.41 s across four small LLMs. At official list prices, 1M requests cost $19.78 on Jev, which sits below three of the four LLMs and runs 1.1x the cost of GPT-4.1 nano at $17.78. What is Jev? Jev is a System One decision model from TypeSafe AI, an AI lab based in San Francisco. Instead of generating freeform text, Jev answers typed questions about a piece of content designated as the state and returns probabilities. TypeSafe introduced System One models and Jev on September 15, 2026, in a blog post by founder Diogo Almeida. The name System One references Daniel Kahneman's description of fast, intuitive System 1 human cognition, while Jev takes its name from the economist William Stanley Jevons. TypeSafe says Jev is trained using Reinforcement Learning for Calibrated Decisions, an approach it calls RLCD. This training target aims at output probabilities where higher confidence directly matches higher observed accuracy. Two versions of the model are currently active: jev-1.13.0 and jev-1.14.0, which became available on October 14, 2026. The alias jev-latest routes directly to jev-1.14.0. Calls to Jev support four question types. A noul question produces the probability of a yes or true outcome, expressed on a continuous scale from 0 to 1. A choice question selects one option from up to 255 named candidates, accompanied by individual probabilities and an overall confidence score. A score question places the input onto an ordered scale of up to 10 distinct levels, while a box question places a bounding box over an image, a capability restricted to jev-1.14.0 and marked experimental by TypeSafe. API consumers interact with Jev via POST /v1/systemone using a JSON payload containing model, state, and questions. The questions field accepts an object keyed by user-defined identifiers. Requests accept standard limits of 64k tokens per request and 32k tokens per question, expanding to 262k tokens when callers provide the TypeSafe-Danger-Zone-Long-Context header. TypeSafe prices Jev at $0.042 per 1M input tokens, which equals $42 per billion tokens, while billed output tokens remain free. What did we measure? Our benchmark evaluated 100 customer support messages drawn from the Banking77 test set, published by PolyAI under the CC BY 4.0 license. We sampled 10 specific intents at random using random seed 77, selecting 10 individual messages for each intent. The selected intents include card linking, card payment with a wrong exchange rate, contactless not working, country support, disposable card limits, exchange charge, fiat currency support, getting a virtual card, top-up limits, and Visa or Mastercard. Several pairs represent semantically adjacent issues, most visibly exchange charge alongside card payment with a wrong exchange rate. Every test message was dispatched once across six distinct model configurations through the Tokely API on November 2, 2026. We evaluated Jev 1.14.0 and Jev 1.13.0 using a single choice question configured with the 10 intents as its evaluation criteria. Alongside Jev, we submitted the identical messages to four low-cost LLMs: Claude Haiku 5.5, GPT-6 Luna, Gemini 2.5 Flash-Lite, and GPT-4.1 nano. Each LLM received a system prompt enumerating the same 10 intents, set to return a structured JSON object at temperature 0 with a cap of 400 output tokens. The complete run yielded 600 individual requests, every one of which resolved successfully with an HTTP 200 status code. Calls executed sequentially, originating from a Tokely server in Finland. Latencies are full round trips measured from that server. Cost calculations apply developer list prices against the exact token volumes recorded by each respective provider API. Finding 1: Jev answered in 0.62 seconds, 1.9x faster than the fastest LLM !Chart of response times: Jev 1.13.0 median 0.60 s, 90th percentile 0.80 s, Jev 1.14.0 median 0.62 s, 90th percentile 0.74 s, GPT-4.1 nano median 1.19 s, 90th percentile 1.57 s, Gemini 2.5 Flash-Lite median 1.58 s, 90th percentile 8.93 s, GPT-6 Luna median 1.90 s, 90th percentile 4.29 s, Claude Haiku 5.5 median 3.41 s, 90th percentile 6.79 s. End-to-end response time per request, median and 90th percentile, 100 Banking77 messages per model, measured November 2, 2026 from a Tokely server in Finland. Response latencies clustered into two distinct performance tiers across the six evaluated engines. Median response times registered at 0.60 s for Jev 1.13.0, 0.62 s for Jev 1.14.0, 1.19 s for GPT-4.1 nano, 1.58 s for Gemini 2.5 Flash-Lite, 1.90 s for GPT-6 Luna, and 3.41 s for Claude Haiku 5.5. Jev 1.14.0 cleared the benchmark 1.9x faster than GPT-4.1 nano and 5.5x faster than Claude Haiku 5.5 at the median. Tail latencies separated the two groups further. At the 90th percentile, Jev 1.14.0 clocked 0.74 s and Jev 1.13.0 recorded 0.80 s, while GPT-4.1 nano reached 1.57 s, GPT-6 Luna hit 4.30 s, Claude Haiku 5.5 reached 6.79 s, and Gemini 2.5 Flash-Lite extended to 8.93 s. Nine in ten Jev requests finished within 0.80 s, and the slowest took 1.63 s, while the LLM tails stretched from 1.57 to 8.93 seconds. TypeSafe quotes baseline end-to-end latencies between 70 ms and 500 ms for its own internal measurements. TypeSafe says its published evaluations are generally run from the US West Coast. Our recorded latencies include the network time from our server in Finland. GPT-6 Luna is a reasoning model: on average, 27.6 of its 43.9 output tokens per request were reasoning tokens. Finding 2: 97% accuracy, between Claude Haiku 5.5 and Gemini 2.5 Flash-Lite !Bar chart of intent accuracy on 100 Banking77 test messages: Claude Haiku 5.5 98%, Jev 1.14.0 97%, Jev 1.13.0 97%, Gemini 2.5 Flash-Lite 96%, GPT-6 Luna 94%, GPT-4.1 nano 86%. Share of 100 Banking77 test messages (10 intents) where each model returned the labelled intent, November 2, 2026. Accuracy remained high across five of the six evaluated endpoints. Claude Haiku 5.5 achieved top accuracy with 98 correct intents out of 100, followed immediately by Jev 1.14.0 and Jev 1.13.0 at 97 correct answers each. Gemini 2.5 Flash-Lite followed closely with 96 correct classifications, GPT-6 Luna reached 94, and GPT-4.1 nano fell behind with 86. Jev 1.14.0 produced three misclassifications across the 100 benchmark items. The model assigned a fiat currency support question to top-up limits, routed a card linking message into getting a virtual card, and placed a contactless payment problem under card linking. GPT-4.1 nano struggled primarily on fine distinctions between foreign currency fees, sorting 5 of the 10 wrong-exchange-rate queries into the broader exchange charge bucket. Model output formatting introduced edge cases on generative endpoints that did not appear with Jev. GPT-6 Luna failed an exact match check on one request by returning "getting virtual card" with spaces instead of the exact label from the prompt. By contrast, a Jev choice response maps strictly to one of the predefined criteria keys supplied in the payload, eliminating schema parsing drift. These accuracy differences should be interpreted within standard sampling margins. Across a target run of 100 individual evaluation samples, deviations of one or two correct answers fall fully within expected statistical noise. Both Jev models demonstrated intent discrimination capabilities equivalent to current small LLMs. Finding 3: The free-output trade !Bar chart of the list price of one million benchmark requests: GPT-4.1 nano $17.78, Jev 1.14.0 $19.78, Jev 1.13.0 $19.78, Gemini 2.5 Flash-Lite $32.84, GPT-6 Luna $36.32, Claude Haiku 5.5 $46.03. List price of 1M requests at the mean input and output tokens each API reported in our run. Jev output tokens are free. We define "the free-output trade" as the economic dynamic observed in our benchmark where Jev billed 1.8x to 3.3x more input tokens than the LLMs for the same message, but returned its answer with zero billed output tokens. This trade-off dictates whether Jev or a minimal LLM yields lower costs for a given classification task. Average token consumption varied sharply by architecture on the Banking77 workload. Jev logged an average of 471.1 input tokens and 118.8 output tokens per query, though none of its output tokens accrued billing charges under TypeSafe's pricing rules. Among the LLMs, Claude Haiku 5.5 averaged 232.5 input tokens and 45.6 output tokens, GPT-6 Luna consumed 143.8 input tokens and 43.9 output tokens, Gemini 2.5 Flash-Lite processed 268.4 input tokens and 15.0 output tokens, and GPT-4.1 nano required 144.8 input tokens alongside 8.2 output tokens. Jev and the LLMs received the same message and the same 10 intents; the difference is in how each API counts its tokens. At official developer list prices, handling 1M such classification queries totals $19.78 on Jev. GPT-4.1 nano came in slightly lower at $17.78 per 1M requests, representing 0.90x the expense of Jev. The remaining three models cost substantially more: Gemini 2.5 Flash-Lite totaled $32.84 (1.66x Jev), GPT-6 Luna totaled $36.32 (1.84x Jev), and Claude Haiku 5.5 accumulated $46.03 (2.33x Jev). Output token rates exert a major influence on LLM expense profiles. Billed output tokens represented 49.5% of total spend for Claude Haiku 5.5 and 60.4% of spend for GPT-6 Luna, while settling between 18% and 19% for Gemini 2.5 Flash-Lite and GPT-4.1 nano. Through Tokely, Jev input tokens list at $0.0294 per 1M tokens, a 30% reduction from TypeSafe's direct list price, bringing the total expense for 1M identical requests down to $13.85. Finding 4: At TypeSafe's own example, the gap is wider !Bar chart of the list price of one million decisions at 428 input and 73 output tokens each: Jev (1.13.0 or 1.14.0) $17.98, Qwen-Flash $25.18, GPT-5 nano $50.60, Gemini 2.5 Flash-Lite $72.00, GPT-4.1 nano $72.00, Claude Haiku 5.5 $79.30, GPT-6 Luna $79.30, GPT-4o mini $108.00, DeepSeek V4.1 Flash $108.00, GPT-5.6 Luna $173.20, Gemini 3.1 Flash-Lite $216.50, GPT-5 mini $253.00. List price of 1M decisions at 428 input and 73 output tokens, the usage of TypeSafe's quickstart request. Official list prices; GPT-6 Astra and Claude Fable 5.1 ($7,930) are left out of the chart. The pricing variance between Jev and general-purpose LLMs expands when evaluating TypeSafe's reference workload. In the quickstart example published in TypeSafe's developer documentation, a single text input evaluated against three questions consumes 428 input tokens and generates 73 output tokens. Calculating pricing under the assumption that LLMs process those exact token quantities highlights the extreme ends of provider pricing scales. Under that matched-token assumption, executing 1M decisions costs $17.98 on Jev, compared to $25.18 on Qwen-Flash at 1.4x the cost. GPT-5 nano reaches $50.60 (2.8x), while Gemini 2.5 Flash-Lite and GPT-4.1 nano both reach $72.00 (4.0x). Claude Haiku 5.5 and GPT-6 Luna both land at $79.30 (4.4x), followed by GPT-4o mini and DeepSeek V4.1 Flash at $108.00 (6.0x), GPT-5.6 Luna at $173.20 (9.6x), Gemini 3.1 Flash-Lite at $216.50 (12.0x), and GPT-5 mini at $253.00 (14.1x). At the top of the provider spectrum, GPT-6 Astra and Claude Fable 5.1 would bill $7,930 for that same 1M request volume, or 441x the cost of Jev. This is close to the "444.6x cheaper" figure that TypeSafe shows on its home page. Our empirical benchmark explains why that theoretical 441x figure functions primarily as an upper bound. In our benchmark, the small LLMs used fewer input tokens than Jev for the same message, and the measured cost of the small LLMs ranged from 0.9x to 2.3x Jev. Finding 5: Confidence tells you which answers to trust !Chart for Jev 1.14.0 by confidence threshold: at 0.5 it handles 98% of messages with 97% accuracy, at 0.7 it handles 94% of messages with 99% accuracy, at 0.9 it handles 91% of messages with 99% accuracy. Jev 1.14.0 on 100 Banking77 messages: share of messages at or above each confidence threshold and accuracy on those messages. Jev returns an explicit confidence metric ranging from 0 to 1 with every choice response. The value reaches 1 when the model assigns all probability density to a single candidate, and drops toward 0 when probability distributes uniformly across the available options. This property allows developers to construct automated routing rules based on numerical certainty. In our Banking77 evaluation, Jev 1.14.0 produced 91 classifications with a confidence score of 0.9 or greater. Out of those 91 high-confidence predictions, 90 were correct, establishing a 98.9% accuracy rate for that segment. The model issued 7 predictions with confidence values between 0.5 and 0.9, yielding 5 correct classifications and 2 errors. Setting an automated execution threshold at 0.7 confidence would have approved 94% of incoming customer messages while maintaining a 98.9% accuracy mark on the automated volume. The remaining 6 ambiguous items would have been flagged for secondary evaluation. TypeSafe's documentation suggests initial baseline thresholds of 0.7 for yes outcomes and 0.3 for no outcomes on noul questions, and advises testing thresholds on your own data. Across all 100 test items in our benchmark, Jev 1.13.0 and Jev 1.14.0 selected the identical winning intent label every time. How do you call Jev through Tokely? Tokely provides access to jev-1.14.0 and jev-1.13.0 via the standard POST /v1/systemone schema at api.tokely.me using a single Tokely API key. Tokely accepts text states with noul, choice and score questions, up to 64 per request. Developers can bundle multiple queries into a single payload, a technique that TypeSafe's developer cookbook reports was 12.2x cheaper and 10.0x faster than issuing separate API requests in its internal testing. curl https://api.tokely.me/v1/systemone \ -H "Authorization: Bearer $TOKELY_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "model": "jev-1.14.0", "state": "Do you guys accept mastercard or visa?", "questions": { "intent": { "type": "choice", "instructions": "Which intent does this bank customer message express?", "criteria": { "visa_or_mastercard": "visa or mastercard", "card_linking": "card linking", "top_up_limits": "top up limits" } }, "is_urgent": {"type": "noul", "instructions": "The message conveys urgency"} } }' A common mistake in unofficial guides is placing fields named question, options, or scale inside a question. The official TypeSafe API schema requires instructions, alongside a criteria field for choice and score evaluations. For choice questions, criteria must be formatted as an object mapping string identifiers to detailed descriptions, while score questions require criteria formatted as an ordered list of level definitions. What should teams do with this? Engineering teams should deploy Jev when the task requires discrete categorization, binary filtering, or rating scales, and where request latency affects production workflows. Routing pipelines, user intent classification, feature gating, and content moderation fit this profile directly. In our benchmark, Jev matched the accuracy of small LLMs while operating at roughly half or less of their median response times, all while returning strictly conforming structured objects. Development teams should use the returned confidence scores to build layered fallback pipelines. Requests exceeding an empirically validated confidence cutoff can process without human intervention, while ambiguous items route automatically to human review queues or larger generative models. Calibrating this boundary on task-specific test sets allows systems to maintain high classification standards on production traffic. Architects should avoid assuming Jev is universally the cheapest alternative across every possible classification workload. Jev tallies billable input tokens for every option description contained in its criteria definitions, meaning tasks with dozens of lengthy definitions can cost as much as lightweight LLMs like GPT-4.1 nano. Engineering teams should run cost audits using their own production prompt distributions before committing to a single architecture. Tokely provides a single unified API key to access Jev, Claude, GPT, and Gemini, enabling direct head-to-head testing across models: Jev 1.14.0 on Tokely. Frequently asked questions Is Jev an LLM? No: TypeSafe says System One models do not write replies, produce code or explain their reasoning; they return structured answers. Can I call Jev with the OpenAI SDK? No, /v1/systemone is a different format; use plain HTTP, TypeSafe's Python or TypeScript SDK, or LangChain4j. How much does Jev cost? $0.042 per 1M input tokens at TypeSafe, $0.0294 on Tokely, output free. Which version should I use? jev-1.14.0 is the newest and the target of jev-latest; TypeSafe says it gives 60 days' notice before jev-1.13.0 is deprecated; pin a version in production. Does Jev accept images? TypeSafe offers images and the box type as experimental features behind the TypeSafe-Danger-Zone-Images header; through Tokely, Jev takes text with noul, choice and score questions. Methodology and limitations This benchmark evaluated 100 messages spanning 10 intents drawn from a single English-language public dataset. Adjusting the task context, target language, prompt phrasing, or option counts could alter comparative rankings, and performance gaps of one or two correct answers fall within statistical noise. All tests executed as sequential, single-request calls on November 2, 2026, originating from a Tokely test host in Finland routing through the Tokely gateway engine. Five LLM requests experienced retries due to host CPU saturation on our test server, with reported latencies reflecting the timing of the final successful transaction. LLM prompts contained the identical list of 10 intent descriptions embedded in a system instruction, evaluated at temperature 0 with a 400 output token limit, without prompt engineering or fine-tuning for any specific endpoint. Cost numbers reflect official list prices multiplied by the token counts reported in each API response, excluding provider volume discounts, prompt caching tiers, batch discounts, and localized taxes unless specifically noted. The quickstart comparison assumes LLMs consume token counts equivalent to Jev's format, which our empirical data demonstrates is not the case in practice. TypeSafe's latency and cost claims come from its own evaluations. Data and citation Benchmark datasets and cost breakdown sheets are freely available for external verification: per-model benchmark results can be accessed at jev-benchmark-2026-11.csv, while the list-price comparison across quickstart workloads is published at decision-cost-2026-11.csv. Primary documentation sources include the TypeSafe documentation, the official launch article Introducing System One Models and Jev, and the Banking77 dataset. Cite as: Tokely (2026). Jev by TypeSafe vs Small LLMs: Accuracy, Speed and Cost per Decision (2026 Benchmark). tokely.me --- Originally published at tokely.me.
oh and it's open-source. star the repo: asymptote-labs/agent-beacon
I switched to Helium from Arc but missed folders... so I made an extension Since Arc is basically dead, I moved to Helium. It’s fast, clean, and I like it a lot, but I kept missing the Arc sidebar, especially folders. So I had to built Tabbs, a sidebar extension for Helium (it works in other Chromium browsers too): - Folders that open and close, just like in Arc - Spaces you can switch between, with their own pinned tabs - Imports your setup straight from Arc - Rename tabs, set icons for folders and spaces - Mute tabs right from the sidebar - Drag a tab onto another tab for split view It’s free and open source. I’d really appreciate any feedback: bugs, ideas, anything that feels off. Chrome Web Store: chromewebstore.google.com GitHub: eduard1414ed/tabbs
@Kn_sniper2017 Not a gamemode but a mod instead hornyyy/Osu-Toy
🚀 مشروعي الجديد OT Security Agent Skills، مجموعة مفتوحة المصدر تضم 8 مهارات لوكلاء الذكاء الاصطناعي (AI Agents)، لدعم تحليل البروتوكولات الصناعية والتحقيق في الحوادث السيبرانية لأنظمة ICS/OT. 🔗 github.com/selmux/Alhasawi-ICS-OT-Security-projet… #ai #AIAgents #otsecurity t.co
FORTH の次は、 LISP を作ろうとするなんて fukuyori/zilisp
GitHub Actions Full Course: CI/CD from Scratch (with Working Examples) Learn GitHub Actions from zero and set up a complete CI/CD pipeline in one video. Professor SK explains every concept with real, working workflow files you can copy into your own projects. What you'll build: a Node.js API that is automatically tested on every push and pull request (on Linux and Windows, two Node versions), packaged as a Docker image in GitHub Container Registry, deployed to GitHub Pages, and deployed to your own server over SSH, with a manual approval before production. Covered: what CI/CD is, workflows, events, jobs, steps, actions and runners, YAML basics, your first workflow, triggers (push, pull_request, workflow_dispatch, schedule), marketplace actions, a full CI workflow, matrix builds, dependency caching, artifacts, job dependencies and outputs, contexts and expressions, variables and secrets, GITHUB_TOKEN permissions, Docker images, environments and approvals, deployments, reusable workflows, branch protection, debugging failed runs and security best practices. Working example repository (app, tests, Dockerfile and all 5 workflows): itadimaigal/github-actions-demo ⏱️ Chapters 0:00 Intro 0:47 The plan 1:40 What is CI/CD 2:26 Why GitHub Actions 3:21 Core concepts 4:20 Runners 5:14 YAML basics 5:56 First workflow 6:59 Running it 7:35 Triggers 8:48 Using actions 10:07 The example app 10:32 The tests 11:09 CI workflow 12:01 Matrix builds 13:02 Caching 13:57 Jobs and artifacts 14:51 Variables and secrets 16:08 GITHUB_TOKEN 17:01 CD pipeline overview 17:46 Docker image 19:01 GitHub Pages deploy 19:48 Environments 20:44 Production deploy 22:02 Approve and deploy 22:39 Reusable workflows 23:28 Branch protection 24:21 Debugging 25:29 Security 26:50 Recap checklist 27:47 Your homework 📚 itadimaigal (IT அடிமைகள்) = "Slaves of IT". Programming, architecture and everything IT, explained simply. Learn. Build. Break free. 🔔 Subscribe and turn on notifications so you don't miss the next video. 💬 Questions? Drop them in the comments. #itadimaigal #GitHubActions #CICD #DevOps #GitHub
Kynex Harness: GPT-5.4 + tools + deterministic checks scored above GPT-6 Astra and Claude Code on ExtractBench. Here's the architecture I built an open-source document extraction harness (Apache-2.0). It takes a PDF and a JSON schema and returns validated JSON with the source page and snippet for each field. On ExtractBench (370 docs, 4,869 pages) it scores 92.97 F1 (rank 12) using GPT-5.4. LlamaIndex re-ran it with their unmodified scorer (PR #84). The architecture, briefly: 1. Contracts: the workspace parses every page and creates one extraction contract per schema field × entity. 2. Supervisor: sends unresolved contracts to the agent. When a contract stalls, it resumes with a targeted recovery task. 3. Agent: picks its own tools: read_page, extract_table, search_text, Azure DI for layout, vision on the rendered page, or OCR. Every candidate answer carries doc, page, snippet and method. 4. Admission gate: deterministic checks the model can't override: schema, numerical consistency, contradiction, entailment. 5. Post-processing rules: five of them, each with an env-var kill switch, so I can measure each one's effect. For context, the leaderboard: |System|F1| |:-|:-| |LlamaExtract Agentic Plus|96.2| |Reducto Deep Extract|96.1| |Pulse|96.1| |KYNEX (GPT-5.4)|93.0| |GPT-6 Astra|91.9| |Claude Code (Opus 4.8)|87.1| |Gemini 3.8 Flash|80.7| The top systems are still about 3 points ahead. The interesting part to me is that a GPT-5.4 harness at about $0.05/page lands above stronger models, which suggests the engineering around the model is carrying a lot of the weight. Caveats: - Test-set tuning. The rules were developed on the same benchmark, so treat the score as optimistic. - Long documents. They're slow and are the weak spot (78.77 on the long split). Repo: Nikit117/kynex-harness I'm happy to go into any part of the design.
I made a free hex-map world builder for Worlds Without Number (with Obsidian export) Hey all! I’ve been running WWN for a while, and I love how many random tables Kevin Crawford packs into the book. But I kept flipping between dozens of pages (and dozens of other books) every time I needed a region, a ruin, or a dungeon. So I built a little web tool that runs the book’s procedures for you, kind of like Sectors Without Number but for WWN. Full transparency: I built this with a lot of help from AI. If I hadn’t used it, this tool wouldn’t exist, because I don’t have the time to build something like this by hand. Lately I’ve really been enjoying automating the random generators I have scattered across my shelf, and this is the first one that feels useful enough to share. It’s an unofficial fan tool, it’s free, and it cites the page number in the book so you can check the rules yourself. I’d love feedback, bug reports, or ideas for what to add next! What it does: - Hex map in four sizes (or custom), with oceans, terrain features, rivers, and lakes (p120-123) - Nations with borders that follow rivers and mountains, plus society, government, history, problems, and neighbor relations (p124-139) - Gods: regional and local gods, plus one sinister cult (p140-145) - Cities, villages, and enclaves with community tags (p148-166) - Courts, ruins, and wilderness sites, each with two tags (p166-221) - Factions with attributes, HP, assets, goals, and rivals (p322-335) - Dungeons with the exploration-site procedure: rooms, exits, stocking, wandering encounters, and a map you can pan and zoom (p234-247) - Seeds: same seed = same world. Reroll one layer (sites, factions, nations, or terrain) and keep the rest - Generate adventures (optionally, associated with a site, thus using its Tags elements) - Rename anything and add notes. Everything saves in your browser, or as a JSON file - Export to Obsidian: one zip with a full vault, linked notes, and an interactive map with markers for every site About Deluxe content: Everything above uses only the free edition of WWN, so anyone can use it. The Deluxe edition has extra GM tools, and I don’t ship that content, out of respect for Sine Nomine. If you own the Deluxe PDF, you can unlock these tools with your own copy: - NPC generator (Random NPC Types + One-Roll Characterization) - Fractal adventure seeds, filled in from each site’s tags - Architectural styles for nations - Infernal Iterums and summoned Iterum creatures To unlock them, clone the repo and run npm run premium -- path/to/your/DeluxePDF.pdf. That gives you a premium.json file. Then click Load premium.json in the sidebar of the hosted site. The data stays in your browser and never gets uploaded anywhere. Please don’t share that file. And if you enjoy the free tables, go buy the Deluxe edition. It’s worth it! 🔗 Try it: stories-with-dice.github.io 💻 Source: stories-with-dice/worlds-without-number-builder
How to Add an Audit Trail to a LangGraph Agent LangGraph makes it easy to build agents as graphs: nodes that retrieve, reason, call tools, and decide where to go next, with branches and loops between them. That structure is a strength, and it creates a problem. When the agent produces a wrong answer, the cause is usually somewhere in the path it took through the graph, and a final output tells you nothing about that path. This guide shows how to record every node an agent visits, linked to the node that caused it, so you can answer why in minutes. The setup takes about fifteen minutes, and it uses a small middleware package from ZizkaDB. What you get, in business terms Faster debugging. A failure becomes a chain from the final step back to its cause, not a log hunt across nodes. Visible loops. Graphs can cycle. A node that runs fifteen times in one session shows up immediately, along with its cost. A defensible record. For customers and auditors, you can show which nodes ran, in what order, for a given request. Safer changes. When you edit a node or a prompt, you can compare the paths before and after, instead of hoping. Step 1: Start ZizkaDB You need Docker. This starts a local instance, and the first image pull can take a few minutes: bash curl -fsSL raw.githubusercontent.com | bash On localhost, there is no signup and no API key. Step 2: Install the integration bash pip install zizkadb-sdk zizkadb-langgraph Step 3: Wrap your nodes The middleware logs a graph_node event when a node starts and a graph_node_done event when it finishes, and it links each to its cause automatically through the graph state. This is the pattern from the package documentation: python from zizkadb import ZizkaDB from zizkadb_langgraph import ZizkaDBLangGraphMiddleware, wrap_node async with ZizkaDB(host="localhost") as db: async with db.track(agent="research-bot") as ctx: mw = ZizkaDBLangGraphMiddleware(db, agent="research-bot", session_id=ctx.session_id) async def retrieve(state): return {"docs": ["a", "b"]} graph.add_node("retrieve", wrap_node(mw, "retrieve", retrieve)) Wrap each node you want to see, and give each a clear name, since the name is what appears in the record. The track block gives you a session, so everything one request does stays together. For a full working graph, the repository includes a retrieval support bot as a reference at examples/golden-path/langgraph-rag-bot/. It is the best place to see how conditional edges and model calls inside nodes are handled, since those are the details this guide does not confirm. Step 4: Run it and ask why Run your graph once. Open the dashboard at localhost, go to Activity, find your agent, and open the session. You should see the nodes in order. Then ask why for any step, from the terminal: bash zizkadb why <event_id> You get the chain of nodes that led there. Try it on an answer you did not like, and see which node supplied the bad context. Step 5: Use it for the problems graphs actually have Runaway loops. A retry or review cycle that never settles is a classic graph failure. In the session view, a node repeated many times is obvious. Add a maximum iteration count in your graph, and treat reaching it as an event worth reviewing. Wrong branch. A router node sends the request down the wrong path. The chain shows the router’s input and the node it chose, so you can tell whether the router was misled or simply wrong. Silent change after an edit. After a prompt or node change, compare the paths of recent sessions with earlier ones. The behavior view in the dashboard shows shifts in which nodes run and how often, and the same data is available in code through the baseline function. Human approval steps. If your graph pauses for a person, log the approval as an event, with who decided and what. Then the decision sits inside the same chain as the agent’s actions, which is what oversight reviews want to see. Step 6: Put it in CI Two ready-made GitHub Actions work with this setup. ZizkaDB Why runs your graph tests and posts the causal chain of any failure to the pull request. ZizkaDB Audit verifies the hash chain of the recorded history and produces an attested report. Both start ZizkaDB inside the runner, with no account, and both run your test command as a single input: yaml - uses: ZIZKA-AI-SL/zizkadb-why-action@v1 with: run: pytest tests/graph What it saves These figures are modeled assumptions, not measured results. Replace them with your own. Assume a team has 12 graph-related failures a month, at 100 euro per engineering hour. Without a recorded path, each takes about 4 hours to diagnose, which is 4,800 euro a month. With the chain and session view, each takes about 1 hour, which is 1,200 euro. That saves about 3,600 euro a month, or 43,000 euro a year. Add loop control. If one runaway cycle a month burns 300 euro of model calls before anyone notices, and the session view catches it within a day, the saving is small per incident and larger over a year. The setup cost is a few hours, and the tools are open source. What to keep in mind One agent per install. Open source ZizkaDB records one agent per install, so a graph with a supervisor and separate worker agents, each logged under its own name, needs ZizkaDB Cloud. A single graph logged under one agent name works fine. Only wrapped nodes appear. A node you do not wrap leaves a gap in the chain. Check what happens inside nodes. Model calls and tool calls inside a node may need their own logging, so confirm how the reference example handles them, and whether combining the LangChain callback handler fits your case. Keep sensitive data out of events. Redact secrets and personal data before logging, and tag people’s data with an identifier so it can be erased later. Versions move. The LangGraph package is young, so check the current release notes. Start this week Take one graph you already run. Wrap three nodes, run a request, and open the session. Then pick a recent wrong answer and run why on it. If the chain points at the cause in under a minute, wrap the rest of the nodes and add the CI action. Want to test ZizkaDB on your agent? Try our open source version here: ZIZKA-AI-SL/ZizkaDB Interested in a design partnership? Fill in the form on our site or reach me directly at founder@zizka.ai Sources: zizkadb-langgraph on PyPI · zizkadb-langgraph 0.1.2 on PyPI · ZizkaDB Python SDK wiki · ZizkaDB changelog · ZizkaDB Why on GitHub Marketplace · ZizkaDB repository
Happy 2.3.0 stable release, teman-teman Indonesia! Ini ku rilis SynthV2Indonesian supaya bikin vokal bahasa Indonesia untuk #SynthV lebih mudah. Ada kamus pelafalan X-SAMPA dan terjemahan antarmuka. Silakan coba! Kalau ada yang kurang pas, kabari saja. mahalisyarifuddin/SynthV2Indonesian
@sauravstwt in theory you can do a planet level scale! no one will come to verify in interview. If some one what to lean from opensource project how to scale for thousands of concurrent session learn from microsoft/fluidframework
@compachuu This could be useful for the text extraction part, I use it for games too kha-white/manga-ocr
Since Arc is dead I switched to Helium but missed folders... so I made an extension Since Arc is basically dead, I moved to Helium. It’s fast, clean, and I like it a lot, but I kept missing the Arc sidebar, especially folders. So I had to built Tabbs, a sidebar extension for Helium (it works in other Chromium browsers too): - Folders that open and close, just like in Arc - Spaces you can switch between, with their own pinned tabs - Imports your setup straight from Arc - Rename tabs, set icons for folders and spaces - Mute tabs right from the sidebar - Drag a tab onto another tab for split view It’s free and open source. I’d really appreciate any feedback: bugs, ideas, anything that feels off. Chrome Web Store: chromewebstore.google.com GitHub: eduard1414ed/tabbs
@MiaAI_lab Rakazo is the best I tried elie222/rakazo
@oops4041555 Not exactly an IntelliJ rewrite but it doesn’t take 2GB of disk space (30MB), renders to the terminal. does the essential (Git, DB, postman, LSP with tree sitter fallback, project wide search, goto definition) Native, multiplatform. Check it out alfu32/kodecraft
Onboarding made easy? -> haydenschmitty/floorplan
Due to the policy outlined at github.com/FreeCAD/FreeCAD/blob/main/AI_POLICY.md , getting an AI agent to help me draft issues or commits has become quite a hassle; I constantly have to concoct excuses just to get the AI to fix a bug. It’s truly a pity, given the times we live in.🤷♂️
Try it: liquidterminal.xyz liquidterminal.xyz Liquid Terminal is free and open source (MIT). Code: Yaugourt/liquidterminal_front Get your .hl name with 20% off, 50% of the mint fee funds Liquid Terminal: liquidterminal.xyz If it helps you, a tip in HYPE or USDC keeps it running: 0x5cf220ac4bab057b88838a651346164f813b9f89 Hyperliquid.
个人风格 skills 是很有必要的,而且还要每周都去复盘更新一次,我自己也有在维护一个 github.com/Chasen-Liao/Chasen-Skills/blob/master/… 很有必要搞一个仓库把这些skills做一个版本控制,多Agent 同步,grok Bot 的 skills 和 Codex 的skills 我就是这样同步的 不过这个思考开 Low 哈哈哈哈,我去实践一下
I switched to Helium but missed folders... so I made an extension Since Arc is basically dead, I moved to Helium. It’s fast, clean, and I like it a lot, but I kept missing the Arc sidebar, especially folders. So I had to built Tabbs, a sidebar extension for Helium (it works in other Chromium browsers too): - Folders that open and close, just like in Arc - Spaces you can switch between, with their own pinned tabs - Imports your setup straight from Arc - Rename tabs, set icons for folders and spaces - Mute tabs right from the sidebar - Drag a tab onto another tab for split view It’s free and open source. I’d really appreciate any feedback: bugs, ideas, anything that feels off. Chrome Web Store: chromewebstore.google.com GitHub: eduard1414ed/tabbs preview.redd.it
What it stands for: you're the reader, not the product. If PaperWing disappeared tomorrow, you'd lose nothing you made, because it all lives in your own accounts on open networks. paperwing.io Code: jordan-simonovski/paperwing Support it: ko-fi.com/jordo92
Imagine being an oligarch thinking you can paywall AI janhq/jan
@elikemmedehou Il y aura des changements majeurs, notamment au niveau de la structure du projet et d'autres éléments. Je le vois aller dans un autre sens. Tu pourras regarder ici : github.com/homescriptone/makisend-extended/blob/m…
开源一个SD高达火线纵横移植到iphone的仓库。 G1n-maker/crossrays-mobile 感谢@happyjoejiang 探索出来这么棒一个路径。 终于可以在手机上刷刷刷了。 仓库里面还有移植的工作流,全程只用了deepseek v4.1 flash 仅花费3亿token,花费约5个小时,这是从0开始,包含部署环境+编译,以后可以更快预计1-2小时一个游戏。 大家在移植过程中有任何问题都可以找我。 主要参考的仓库: jhaizhou-ops/d2r-mobile seedds/nxnative shirai91/nx2android ly05010419/MacNativeGames leeashine/ot2-mobile
Built my first Claude Code plugin 🚀 progress-status shows: ✅ Live task progress ✅ Context usage + color warnings ✅ Terminal & desktop support Free & open source (MIT). Install: `claude plugin marketplace add dezignwithimran/claude-progress-status` dezignwithimran/claude-progress-status t.co
不具合があったので更新しました。 ダウンロードは GitHub またはプラグインポータルよりどうぞ。 Megria-Scarlet/WaveOutput #YMM4Plugin
YouTube Skill: titles, descriptions, chapters, tags, thumbnails and upload for any finished video, with Claude Code, Codex, Cursor or OpenClaw YouTube Skill is out: a free, MIT-licensed agent skill for YouTube SEO and uploading. Give it a finished video and it builds the whole upload package, checks it, and uploads after you approve. How it works 1. check_setup.py reports Python, ffmpeg, Pillow, the transcription routes and OpenCV (optional), with the install command for your system. 2. It asks only what it can't see: which file, what the channel is about, whether the video is made for kids (a legal setting), and whether it shows realistic AI-made or AI-altered content. It never guesses those two. 3. Transcribes the video: from an existing SRT or VTT (free, instant), your own Groq or OpenAI key, or faster-whisper on your own computer (free, private). Everything after this is written from the transcript. 4. suggest.py reads YouTube's search suggestions for the topic and its question forms. The agent picks the most specific phrase the video fully answers and keeps 2 to 4 related ones. With your own free YouTube Data API key, it also lists the 10 videos ranking now with views per day. 5. Writes upload.json: 10 titles (phrase early, under 70 characters), the description's first lines, chapters named for what the viewer gets, 5 to 10 specific tags, 3 hashtags, category, privacy and a comment to pin. 6. youtube_pack.py checks it all: title length and capitals, the description in bytes (5,000, the way the API counts), the phrase in the first 150 characters, tags against 500 characters with commas and quotes counted, hashtags, and the chapter rules (0:00, at least 3, each 10 s or more). Chapter starts move to the start of the sentence they fall in. Every warning gets fixed before you see the pack. 7. Thumbnails: 12 candidate frames scored for sharpness, light, colour and faces, near-duplicates dropped. The agent picks 2 or 3 different ideas and thumbnail.py renders them at the source's size up to 3840x2160, under 2 MB, with the duration-badge corner kept clear. preview.png shows each one as a home-feed card and as the small "up next" card. Vertical videos get 9:16 thumbnails and Shorts-shelf previews. 8. Writes captions.srt (2 lines of 42 characters max, fillers removed, names fixed with a replace map), description.txt, post.json and upload-pack.md, the whole package on one page. 9. After you approve, uploads through WoopSocial, unlisted or scheduled. 10. Hands you the YouTube Studio steps: thumbnail, captions, AI use, end screen, playlist, and a Test & Compare A/B test of your best titles and thumbnails. 11. After 2 and 7 days, reads views back and asks you for click-through rate and average view duration, then says what to change: low clicks means test another thumbnail or title, early drop-off means a tighter opening next time. The example in the repo The worked example packages a 3:43 animation, "Earth Water Budget Animation", courtesy NASA/JPL-Caltech. The broad topic "earth water" returned noise in YouTube's suggestions (elements, water parks), so the main phrase became "how much water is on earth", YouTube's top suggestion. The title is "How Much Water Is on Earth? Only 0.01% Is in Lakes and Rivers" (61 characters), with 7 chapters, 8 tags, 3 hashtags, captions and 3 thumbnail ideas: Earth drained dry next to "All of it in one drop", a surfer with "96.5% is salt water", and the full 370-quintillion figure with no words. The text and thumbnails were written by an AI agent with the skill as a demonstration; they're not NASA's words, and no endorsement by NASA, JPL or Caltech is implied. What it won't do - Write a title, thumbnail or claim the video doesn't deliver. - Guess made for kids or the AI-use setting. - Use faces, logos or images you have no rights to. - Mass-produce near-identical uploads. Every package comes from that video's own transcript. - Post before you say yes. - Set the thumbnail, caption file, playlist, end screen or AI-use label through the upload. Those are listed for YouTube Studio. - Report numbers YouTube didn't return. Requirements: Python 3.8+, ffmpeg (any build) and Pillow. Mac, Windows and Linux are tested in CI. It needs an agent that can run ffmpeg on your machine. Install (Claude Code): npx skills add social-media-skills/youtube-skill -g -a claude-code -y OpenClaw: openclaw skills install @social-media-skills/youtube-skill Repo: social-media-skills/youtube-skill Before release, the example's full YouTube post body passed validation against a real connected channel (it was not posted). Disclosure: the skill is maintained by Frank Heijdenrijk and the team behind WoopSocial (woopsocial.com), a social media API and MCP server for AI agents. The free plan covers 2 social accounts, with everything from posting to analytics included. You can skip the upload step and upload the pack yourself. Questions, bugs and feature requests go in this thread.
The Token That Expired Mid-Run: OAuth Refresh in Long n8n Workflows The Token That Expired Mid-Run: OAuth Refresh in Long n8n Workflows This is part of my build-in-public series on running LLM workflows in n8n in production. Everything here is from real templates I sell and support — the mistakes are mine, the fixes are tested. The run that died at minute sixty-one A batch workflow processed a customer list one by one: fetch a record, call the provider API, write the result back. It usually took ninety minutes. One night it failed halfway through, and the failure was not dramatic. The first hour of calls returned 200. Then, one by one, the calls started returning 401. The workflow kept going, kept failing, and finished with half the batch done and half marked as errors that were not really errors at all. The access token lived for sixty minutes. The workflow fetched it once at the start and reused it for every downstream call. Nobody had asked what happens when a run outlives its own credential. The token did exactly what tokens do: it expired on schedule, in the middle of my run. The mistake was treating a credential as a static fact for the whole execution. An access token is a lease with an expiry, not a password. Any workflow that runs longer than the lease, or that may be retried after the lease ends, has to plan for renewal — or it will fail at the most boring possible moment, an hour in, with no bug to find. Refresh before expiry, not on 401 alone The obvious fix — catch the 401 and refresh then — helps, but only halfway. By the time you see the 401, you have already burned a call, and if several parallel branches hit the provider at once, they all see 401 at once and all try to refresh at once. That is a race, and races around token rotation are how you lock yourself out (more on that below). So the worker now checks the token's expiry before each batch of calls, with a margin. If the token expires in less than ten minutes, it refreshes first, then proceeds. Ten minutes is not magic; it is larger than the longest single downstream call in the workflow, so a call that starts with a fresh token cannot expire mid-call under normal conditions. The rule is simple: never start work you cannot finish inside the lease you hold. The 401 handler stays, as a safety net for clocks that drift and providers that revoke early. But it is the second line of defence, not the plan. A system whose only refresh strategy is "fail first, then recover" will fail first in production, on the customer's data, every time the lease is short. One refresher at a time This is the part that actually broke things a second time. After I added refresh-on-401, two concurrent executions both hit 401, both refreshed, and one of them got invalid_grant. The provider rotates refresh tokens: each refresh issues a new refresh token and invalidates the old one. Two refreshers racing means the loser presents a refresh token that is already dead. The fix is a single owner for refresh. Token state lives in one database row, not in each execution's memory. Refreshing means claiming that row — an atomic update that only succeeds for one execution — doing the refresh, writing the new tokens back to the same row, and releasing the claim. Any other execution that needs a token while a refresh is in flight does not refresh; it waits a few seconds and re-reads the row. It gets the new token without ever touching the refresh endpoint. If your provider does not rotate refresh tokens, this still saves you: one refresh instead of five identical ones, one audit trail, one place to look when something goes wrong. But if it does rotate — and most OAuth providers do — a lock is not an optimisation. It is the difference between a refresh and a lockout. Persist the new token where the next run can find it A refreshed token that only lives in the current execution's memory is a token the next execution will never see. The next run starts, reads the old token from the credential store, gets a 401, and refreshes again — or worse, tries to use a refresh token that was already rotated away by the previous run. So the refresh writes back to the same place every run reads from: the credential store, or a single token row that the workflow reads at start. The write is atomic — new access token and new refresh token together, never one without the other — and the workflow re-reads after writing, so it proceeds with exactly what was stored. If the write fails, the run goes to review rather than proceeding with a token it cannot prove is current. A half-written token pair is worse than no token: it looks valid until the provider disagrees. A 401 is not always "expired" Not every 401 means "refresh and retry." A token can also be revoked, or its scopes can be narrowed, or the user can disconnect the app. Refreshing against a revoked grant does not fix anything; it just burns refresh attempts and, with some providers, trips abuse limits. So the refresh path is capped — one refresh attempt per run per token, with a short backoff — and a second consecutive 401 after a fresh token goes straight to review, with the token state, the provider's error body, and the execution id attached. That record is what a human needs to tell "expired" from "revoked" without re-running the batch to find out. Infinite refresh loops are how a credential problem becomes an account problem. The test is a short lease, not a long run I do not test this by waiting an hour. The mock OAuth server issues tokens that live for two minutes, and the test workflow processes a batch that takes five minutes, with three executions running in parallel. Then I assert five things. First, no call ever goes out with a token inside its expiry margin. Second, exactly one refresh happens per expiry window, even with three executions racing. Third, every execution finishes with the token that was actually stored, not one it cached at start. Fourth, a revoked refresh token produces exactly one review record, not a retry loop. Fifth, the batch completes with no duplicated side effects from the refresh itself — refreshing a credential must never re-run the work it was protecting. A test with a one-hour token proves the happy path. A two-minute token proves the system. Checklist before your next long run goes live - Token lifetime: know the lease, and never start work you cannot finish inside it. - Refresh margin: refresh before expiry, with a margin larger than your longest single call; keep the 401 handler as a safety net only. - Single refresher: one atomic claim per token, losers wait and re-read — never race a rotating refresh token. - Persistent write-back: new token pair written atomically to the one place every run reads from, and re-read before use. - Revocation handling: cap refresh attempts, send a second 401 to review with full context, never loop. - Test with a short lease: two-minute tokens, parallel executions, one refresh per window, no duplicates. A credential is not a configuration value. It is a lease that expires on its own schedule, and a long workflow is a promise to still be running when it does. Plan for the renewal, or the run will keep its promise and the token will not. --- *I'm building AI Automation Lab — production-ready n8n workflow templates. The free AI Hook Generator shows how I structure real workflows; my open-source templates live at zhp910318/n8n-ai-automation-lab. The store is at payhip.com, and the free workflow is at payhip.com
一個だけ、実力を証明するための サンプルコードを、 githubで公開している。 一個で十分だと思っている。 CSと数学をちゃんと 理解していない人だと、 絶望すると思う。 etsuviel/wfc_sample
I rebuilt the website, core functions/features and wrote the first full tests for an open-source, zero-dependency share-button library during GSoC Hey r/SideProject! This summer, during Google Summer of Code with AOSSIE (an Australian open-source non-profit), I worked on many projects. One was the Social Share Button: share buttons for any website with no dependencies and no tracking. What I did: • Designed and rebuilt the website: live demo, copy-paste snippets for HTML, React, Preact and Qwik, English + Hindi, dark mode • Shipped 1.1.0: translatable labels, so the buttons fit sites in any language, and a security fix • Added the library's first test suite (72 tests, including property-based tests) that now gates every npm release Try it: social-share-button.aossie.org Repo: AOSSIE-Org/SocialShareButton npm: npmjs.com Also on Product Hunt: producthunt.com I'd love feedback on the developer experience. What would make you use it on your own project?
Kaçakçıdan’ın güncel arayüzünden kısa bir ekran kaydı. Açılır kategori menülerini, ilan sayfalarını, satıcı profillerini ve açık/koyu temayı yeniledim. Henüz geliştirme aşamasında. Görüşlerinizi merak ediyorum. Site: kacakcidan.netlify.app Kaynak kod: teskilatsiz/kacakcidan t.co
Building an open-source GTK4 PDF editor for Linux (word-sys PDF Editor) – looking for testers, bug reports, and missing features Flathub: flathub.org & GitHub: word-sys/word-sys-pdf-editor I've been working on a native Linux PDF editor built with GTK4 and Libadwaita. The goal was to have one offline tool that actually does the stuff people usually boot into a Windows VM or buy MasterPDF/Acrobat for. A lot of the recent features came directly from people opening issues on GitHub (like infinite scrolling, PEP-517 build support, and Flatpak packaging). Right now it, with v1.12 updates, supports direct text/object editing, creating and filling forms, PAdES digital signatures (including smart cards/hardware tokens via PKCS#11), permanent redaction, offline Tesseract OCR, measurement tools, and offline conversion to office formats and more. The full feature list and packages (.deb, AppImage) are on the GitHub page, so I won't paste a massive wall of text here. I want to figure out what is still rough or missing. If you have a moment to try it out from Flathub or GitHub: 1. What breaks on your setup or with your specific PDFs? 2. What is the one PDF feature you still miss on Linux? 3. What is the rough/hard to use parts of this project? Bug reports, PRs, and feature requests on GitHub (or just complaining in the comments here) are all super helpful. I will continue to develop this project. Thanks!
4" touchscreen for inference engine monitoring I bought this 4" screen with esp32 on aliexpress awhile back and decided to make a TUI style dashboard to monitor my dgx cluster. Inspired by btop++, nv-monitor, and engine metrics by 0rand. Firmware is built with PlatformIO on the Arduino-ESP32 core. You can find the firmware code on my github repo. There is also a skill.md file where you can point your agent to it to compile it for you. dicksondickson/system-d-monitor I'm currently designing a 3D printed dock for it. I'll add it to the repo when I'm done.
C 盘标红,系统磁盘清理只算临时文件和回收站,大目录在哪不知道。 SquirrelDisk 把磁盘画成方块图,越大占越多,可逐层钻到文件,支持按类型筛选,三大平台。 adileo/squirreldisk
やべぇな、CD-R/DVD-R/BD-Rディスクに作成したISOイメージファイルを焼くと絵が出るって JiaFeiMiao-K-Cat/DiscImageStudio t.co
🚨تحديث تعريب نصل الطيف صفر 1.0.1 | Phantom Blade Zero 🔵 عادت خيارات DLSS وDLAA إلى إعدادات الرسوميات 🔵 ملفات الدبلجة والصور ما تنحمل من جديد بعد إيقافها وتشغيلها افتح المثبّت وبيعرض لك التحديث بنفسه 👇 github.com/DiNaSoR/Tersreleases/releases/tag/phan… وفيه تحديثات ثانية جاية قريب، طوّلوا بالكم علينا 🙏 #نصل_الطيف_صفر #PhantomBladeZero #تعريب
YouTube Skill for Claude Code: How It Picks the Search Phrase, Counts YouTube's Limits and Scores Thumbnail Frames YouTube skill for Claude Code, Codex, Cursor and OpenClaw: a free, MIT-licensed agent skill that takes a finished video and builds everything the upload needs to be found. It transcribes the video, reads what people type into YouTube search, writes 10 titles, a description, chapters, tags and hashtags, checks every field against YouTube's limits, renders thumbnail options from the video's own frames, writes a caption file, and uploads only after you say yes. This post skips the pitch and walks through the parts that are code: what the scripts count, how they count it, and why the defaults are what they are. Repo: social-media-skills/youtube-skill !A raw upload with a filename title next to the package the skill built: search-first title, thumbnail from the video, description opening and 7 chapters The repo's worked example. The video is "Earth Water Budget Animation", courtesy NASA/JPL-Caltech. The title, description, chapters and thumbnails were written by an AI agent with the skill; no endorsement by NASA, JPL or Caltech is implied. Six scripts that count, one agent that chooses The skill is a SKILL.md workflow plus six small Python scripts. The scripts handle everything with a right answer: byte counts, timestamps, ffmpeg calls, pixel work. The agent handles everything that needs reading: which search phrase the video actually answers, which title is honest, which frame shows what the video promises. Neither does the other's job. final.mp4 -> check_setup.py Python, ffmpeg, Pillow, transcription routes, OpenCV (optional) -> transcribe.py work/transcript.json + transcript.txt --from captions.srt | GROQ_API_KEY | OPENAI_API_KEY | local faster-whisper -> suggest.py pack/suggestions.md: what people type into YouTube search -> agent reads the whole transcript, picks one phrase, writes upload.json -> youtube_pack.py build checks every field, snaps chapters, writes description.txt, captions.srt, post.json, manifest.json, upload-pack.md -> youtube_pack.py frames frames.jpg: 12 scored candidate frames -> agent writes thumbs.json (2 or 3 different ideas) -> thumbnail.py thumb-a.jpg, thumb-b.jpg ... and preview.png at feed size -> you approve -> WoopSocial upload session, posts_validate, posts_create Apart from Pillow, the scripts use only the standard library and ffmpeg. No paid API is required anywhere in the chain. Finding the phrase: autocomplete, used lightly suggest.py asks YouTube's search suggestions about the topic and its question forms (how to, how does, why, what is, is, best, vs). With --deep it also tries the topic followed by every letter. It writes the suggestions in YouTube's order and says plainly that the order is not a search volume. That endpoint has no official API and no published terms, so the script treats it with care: a handful of requests per video, results saved to suggestions.json, and a docstring telling the agent never to loop it over hundreds of topics. One portability detail: Python from python.org on a Mac often ships without a certificate store, so fetch() tries urllib first (with certifi when installed) and falls back to curl, which every current Mac, Windows and Linux machine has. The example shows why a phrase beats a topic. The broad "earth water" returns noise, such as the chemical elements and water parks. "how much water is on earth" is YouTube's top suggestion for the topic, and the video answers exactly that question, so it became the main phrase. Other suggestions such as "how much drinkable water is there on earth" went into the description body and the tags, where they're true. With your own free YOUTUBE_API_KEY, --top also lists the 10 videos ranking for the phrase with views per day. As of October 2026, search.list has its own quota bucket of 100 calls a day at 1 unit each, so one run costs 1 of your 100 daily searches. Counting the way YouTube counts The YouTube Data API and the Help Center don't always agree. The Help Center describes a 5,000-character description; the API docs say 5,000 bytes. youtube_pack.py uses the stricter one, which matters as soon as a description contains emoji or accented letters. | Field | What the script measures | Warns when | |---|---|---| | Title | characters | over 100 (hard), over 70 (usually cut), phrase missing, mostly capitals, < or > | | Description | UTF-8 bytes | over 5,000 bytes, phrase not in the first 150 characters, < or > | | Tags | characters as the API counts them | over 500, or a tag contains <, > or a comma | | Hashtags | count and characters | a space or symbol breaks one, or more than 60 (all are then ignored) | | Chapters | seconds | not at 0:00, fewer than 3, any under 10 s, any after the end | | Made for kids | presence | missing; it's a legal setting the user must declare | | Schedule | ISO time | no timezone, or in the past | The tag budget is the least obvious one. The API counts the whole list against 500 characters, commas included, and a tag with a space is wrapped in quotes that count too: def tags_length(tags): return sum(len(t) + (2 if " " in t else 0) for t in tags) + max(0, len(tags) - 1) The example's 8 tags come to 187 of 500, and its description to 739 bytes. Those numbers land in manifest.json so the agent can report them without guessing. The phrase check is deliberately loose about grammar and strict about words. phrase_in() drops function words ("is", "on", "the"), then looks for the start of each remaining word, so "Earth's" satisfies "earth" and "waters" satisfies "water". The title check also renders where a phone line usually ends, about 40 characters, which upload-pack.md shows as "How Much Water Is on Earth? Only 0.01% I...". The 40 and 70 are rules of thumb; YouTube publishes no number, and the bundled references/youtube-seo.md says so next to every limit it does publish, with sources. Chapters snapped to the sentence they fall in A chapter start read off a timestamp can land a moment after the sentence begins, and then the chapter opens mid-word. The pack moves each start to the nearest sentence start within 3 seconds, minus a 0.3-second lead-in: for t, name in chapters: s = secs(t) if sentences and s > 0: near = min(sentences, key=lambda x: abs(x["start"] - s)) if abs(near["start"] - s) <= 3.0: s = max(0.0, near["start"] - 0.3) In the example, the agent wrote 1:30, 1:59 and 3:05; the pack published 1:29, 1:58 and 3:04. Then it applies YouTube's rules, which are all or nothing: first chapter at 0:00 (if missing, it adds one called "Intro" and warns you to rename it), at least 3 chapters, each at least 10 seconds, none after the end. Break any of them and YouTube shows no chapters at all, so every break is a warning the agent has to fix before the pack goes to you. Scoring frames for thumbnails youtube_pack.py frames samples the video evenly at three times the number of candidates wanted (36 frames for the default 12), skipping the first and last 2 seconds. Each frame, scaled to 640 pixels wide, gets a score: score = (min(sharp, 2500) / 2500) * 0.5 \ + (min(contrast, 70) / 70) * 0.3 \ + (min(hsv, 120) / 120) * 0.2 if mean < 25 or mean > 235: score *= 0.2 # black or blown-out frames if faces: score += 0.15 + min(face_share * 2, 0.2) Sharpness is the variance of an edge filter, contrast is the standard deviation of brightness, and the last term is colour saturation. Faces come from OpenCV's YuNet model, which ships in the repo, with the older Haar cascade as a fallback; without OpenCV, faces simply aren't scored. A high score alone would return twelve versions of the same shot, so each candidate gets a 64-bit difference hash and is kept only if it differs from every picked frame by more than 6 bits. A fixed-camera video can look identical all the way through; then the script fills the remaining slots with the frames furthest apart in time. The result is frames.jpg, a numbered contact sheet with times and scores. The scores rank; they don't choose. The agent looks at the sheet and picks frames that carry the video's promise. When it renders, thumbnail.py doesn't trust the exact timestamp either: it pulls six full-resolution frames across half a second around it and keeps the sharpest, so a moving shot doesn't produce a blurred thumbnail. The example's three ideas are deliberately different, not three crops of one frame: Earth drained dry next to "All of it in one drop", a surfer with "96.5% is salt water", and the full 370-quintillion figure with no words at all. Different ideas are what make an A/B test result mean something. 4K when the source has it, under 2 MB always YouTube now recommends 3840x2160 thumbnails. It allows 50 MB from a computer but only 2 MB from a phone. thumbnail.py renders at the source's own size up to 3840x2160 (never upscaling past the source) and keeps every file under 2 MB, so it uploads from either: def save_jpeg(im, path): while True: for q in (92, 88, 84, 80, 76, 72): im.save(path, "JPEG", quality=q, optimize=True, progressive=True) if os.path.getsize(path) <= MAX_BYTES: return q, im.size, True # still too big: step down 2160 -> 1440 -> 1080 -> 720, then lower quality at 720 The example's source is 1080p, so its three thumbnails came out at 1920x1080 and quality 92, between about 150 and 190 KB each. Layout numbers are written once for a 1280-wide frame and scaled. Two of them do real work: words smaller than 80 pixels at 1280 wide trigger a warning (they vanish in the small card), and a 300x140 zone in the bottom-right corner stays clear, because the duration badge covers it. Judged at the size people see it A 4K thumbnail viewed full screen tells you nothing. preview.png draws each option, with your title and a duration badge, as a desktop home-feed card (360 pixels wide) and as the small card used for "up next" and phone search (168 pixels wide), on YouTube's dark theme. The workflow tells the agent to reject an option when its words can't be read in the small card or its subject is unclear at that size. Shorts: 9:16, or YouTube replaces it A vertical or square video of 3 minutes or less is a Short, and the pack spots it from the probe (rotation metadata included, so a phone clip is measured the way it plays). For a Short it drops chapters and doesn't ask for #shorts, since YouTube defines a Short by length and shape. Thumbnails change shape too. YouTube replaces a 16:9 custom thumbnail on a vertical video with an auto-generated frame, so thumbnail.py renders 9:16 up to 2160x3840, centres the words in the upper part of the frame (the bottom third sits under the title and buttons), and swaps the preview for Shorts-shelf cards. Custom Shorts thumbnails can only be added in Studio on a computer, and Test & Compare doesn't run on Shorts; the pack's checklist says both. Captions from the same transcript captions.srt comes from the transcript the rest of the package was written from: fillers out, at most 2 lines of 42 characters, and a replace map for words the transcriber got wrong (the example uses it to capitalise "Earth" throughout). The example's transcript came from the video's existing caption file through --from, so word timing is estimated, and the pack prints that as a note rather than hiding it. Mac, Windows and Linux The requirements are Python 3.8 or newer, any ffmpeg build and Pillow. The skill tells the agent to use py instead of python3 on Windows, check_setup.py prints the install command for the system it finds, and the fonts (Poppins ExtraBold for thumbnail words, Inter for the preview) are bundled so text renders the same everywhere. A CI workflow builds a pack and renders thumbnails on Ubuntu, Windows and macOS. OpenCV and the YouTube API key are optional extras; everything else works without them. Uploading, and what stays in YouTube Studio post.json is the post body for WoopSocial, a social media API and MCP server for AI agents. The agent creates an upload session with the byte size from manifest.json, sends the parts with upload_parts.py, fills in the two IDs, runs posts_validate, and shows you the title, the description's first lines, chapters, tags, made for kids, privacy and time before it calls posts_create. In a pre-release trial, the worked example's full YouTube post body passed posts_validate against a real connected channel; it was not posted. The API sets the title, description, tags, category, made for kids, privacy and schedule. WoopSocial doesn't write any of that text and doesn't edit or crop the video; the skill builds the package locally. It also doesn't set the thumbnail, caption files, playlists, end screens or the AI-use label, so upload-pack.md ends with those steps for YouTube Studio. After 2 and 7 days the agent reads views back and asks you for click-through rate and average view duration from Studio, and it never estimates a number it wasn't given. The free plan covers 2 social accounts, with everything from posting to analytics included, and setup for each agent is at woopsocial.com. Disclosure: the skill is maintained by Frank Heijdenrijk and the team behind WoopSocial. Uploading is optional; without it the skill hands you the pack to upload yourself. Try it npx skills add social-media-skills/youtube-skill -g -a claude-code -y OpenClaw: openclaw skills install @social-media-skills/youtube-skill. Codex, Cursor and other agents: run npx skills add social-media-skills/youtube-skill and pick your agent. You need an agent that can run ffmpeg on your machine. Then hand it a finished video: "put final.mp4 on my channel and make it findable." Issues and pull requests are welcome on GitHub, and more free skills for social media work are at social-media-skills.com.
I got tired of L-Connect, so I made my own free app for Lian Li's 8.8" screen and LCD fans My 8.8" Lian Li screen and TL LCD fans deserved better than L-Connect, so I wrote LumaLi: one small Windows app, no account, no telemetry, free and open source (MIT). 45+ animated layouts for the 8.8" screen (wide and vertical), 30 fps, all driven by live sensors 28 faces for the round fan screens, including watch faces and a game FPS counter Game profiles: your screen switches layout while a game runs Fan lighting that warms up with your temperatures, and strip/fan colours that follow your monitor Fan curves, a layout editor, videos/GIFs/Lottie animations Najibra/LumaLi Happy to answer questions. Not affiliated with Lian Happy to answer questions. Not affiliated with Lian Li.
I develop a free, open-source alternatives to paid productivity tool Mathpix Snip Tool OpenMathpix — An open-source alternative to Mathpix Snip Tool - Take a screenshot of a mathematical equation and convert it into LaTeX. - Run formula recognition locally and offline, without an API key or subscription. - Windows desktop app with a portable version. GitHub: JhuoW/OpenMathpix Download: github.com/JhuoW/OpenMathpix/releases
Updated ParallelEarth v.0.5.0: try different implementations in separate VS Code worktrees, then compare the results Version 0.5.0 adds: - App previews: run implementations on separate local ports, with start/open/stop controls. - Environment comparison: inspect recorded Node/npm versions and configuration hashes. - CLI and CI support: run reusable comparison recipes and export JSON or Markdown reports. It also includes a comparison dashboard, individual Jest/Vitest test results, acceptance criteria mapped to tests, and stale-result detection when code changes after a check. When you choose an implementation, you can preview its changes and preserve them on a new branch without changing your original checkout. One limitation: worktrees separate your code, but apps can still share databases and external services. Passing mapped tests also doesn’t prove complete requirement coverage. GitHub: shubhammaji1/parallel-earth Open VSX: open-vsx.org I’d appreciate feedback from developers who regularly compare approaches to bug fixes or refactors. What would make this useful enough to become part of your workflow?
关于进群,这个是站长交流群 赞助二开的开源项目,后可以申请 并不是售后维护群 二开项目持续维护中! ranxi2001/sub2api
Managing multiple Rancher clusters used to mean constant context switching Now I just talk to my ai and it handles kubernetes clusters, harvester (vm) and fleet (ci) through this mcp Demo in the readme if you want to try it mrostamii/rancher-mcp-server
识别和拦截临时邮箱(Disposable Email),目前有 1 w+域名名单 担心被用户注册薅羊毛,可以接入试试 disposable-email-domains/disposable-email-domains
Put the calculator down. Graphics stories like this one land in The React Native Rewind every week 👇 Join The React Native Rewind: trnrw.com react-native-skia-layout: ifeoluwak/react-native-skia-layout
データ基盤でのTerragruntの使い方を紹介 はじめに データ基盤開発部では、インフラをコードで管理するために、TerraformとTerragruntを利用しています。 Terragruntは以前から運用していましたが、データ基盤の大幅なリニューアルに合わせて、公式のベストプラクティスを参考にディレクトリ構成を整理しました。この機会に、Terragruntを知らない方にも向けて、導入した理由と現在の使い方を紹介します。 Terragruntとは Terragruntは、Terraformの実行・管理を補助するツールです。Terraformで管理するリソースを複数のまとまりに分け、それぞれで使うコードや設定値を指定したり、共通する設定をまとめたりできます。 この実行・管理のまとまりをunitと呼びます。unitは、設定ファイルterragrunt.hclを置いたディレクトリに対応します。unitの公式説明 Terraformには、クラウド上のリソースを作成・設定するコードを書きます。Terragruntには、どのTerraformコードを使い、どの設定値を渡すかをunitごとに書きます。クラウドへの接続設定など、unit間で共通する設定もまとめられます。 リソースを定義するのがTerraform、そのコードと設定値を組み合わせて実行するのがTerragrunt、という役割分担です。 なぜ導入したのか 私たちのデータ基盤では、ネットワーク、データ処理の実行環境、データの保存先などを、1つのリポジトリで管理しています。管理対象が増えても、変更したい機能を個別に扱えるようにすることが、Terragruntを導入した動機でした。 Terraformが管理するtfstateには、コード上のリソースと、実際に作られたクラウド上のリソースとの対応関係などが記録されます。 多くのリソースを1つのtfstateにまとめると、小さな変更でも広い範囲を確認することになります。そこで、データの保存先やデータ処理の実行環境など、管理したい対象ごとにunitを設け、tfstateも分けています。変更時に確認する範囲を絞り、plan(変更内容の確認)やapply(変更の反映)の待ち時間を抑えることも狙いです。 一方、分割すると、それぞれにtfstateの保存先やGoogle Cloudへの接続設定を書く必要があります。同じ設定をあちこちにコピーすると、変更時の修正漏れも起こりやすくなります。 管理する範囲を分けながら、共通の設定はまとめたい。 この両方を扱うために、Terragruntを使っています。 公式の推奨パターンをどう取り入れているか 今回の整理では、Terragruntを開発するGruntworkの公式サンプルと公式ドキュメントを参考にしました。特に取り入れたのは、次の2点です。 再利用するTerraformコードと、実際に作るリソースの設定を分ける tfstateの保存先など、共通する設定を親のファイルにまとめる 公式サンプルでは再利用するコードと実環境の設定を別リポジトリに分けています。私たちは同じリポジトリで管理する方針に合わせ、catalog/modulesとliveというディレクトリに分けて、この考え方を取り入れています。 再利用するTerraformコードのまとまりをmoduleと呼びます。module自体はTerraformの機能です。私たちは、関連するリソースと、その関連付けをmodule内にまとめ、Terragruntの各unitから呼び出しています。 ここからは、Google Cloudのデータ分析サービスであるBigQueryを例に説明します。BigQueryでは、テーブルやビューをまとめて管理する入れ物を「データセット」と呼びます。今回は、データセット1つと、その閲覧権限を1つのunitとして扱います。 moduleには、データセットや閲覧権限を作るための再利用可能なリソース定義を書きます。データセット名や閲覧できるグループなど、データセットごとに異なる設定値はlive側から渡します。 BigQueryに関する部分を抜き出すと、次のようになります。プロジェクト名やデータセット名は説明用のものです。 📁 infra/google/ ├── root.hcl # 各unitで使う共通設定 ├── catalog/ │ └── modules/ │ └── bigquery-dataset/ # データセットと権限を定義する共通module │ ├── main.tf │ ├── variables.tf │ └── outputs.tf └── live/ └── prod/ └── analytics-project/ └── bigquery-datasets/ ├── bigquery_dataset.hcl # moduleの指定など、データセット共通の設定 ├── sales/ # 売上データセットのunit │ └── terragrunt.hcl └── events/ # 行動ログデータセットのunit └── terragrunt.hcl 配置先 書く内容 catalog/modules/ データセットや閲覧権限をどう作り、関連付けるか live/配下の設定 どのmoduleを使い、どのデータセット名や閲覧グループで作るか root.hcl tfstateの保存先や、Google Cloudへの接続に使うproviderなどの共通設定 salesとeventsは同じmoduleを使いますが、別々のunitです。tfstateはGCSに保存し、unitごとに保存先を分けています。そのため、売上データセットへの閲覧権限を追加するときは、salesの設定とplanを確認できます。 unitからデータセットの設定を渡す 図のbigquery_dataset.hclでは、データセット用のmoduleを指定します。 terraform { source = "../../../../../catalog/modules//bigquery-dataset" } sales/terragrunt.hclでは、共通設定を読み込み、売上データセット固有の設定値を渡します。以下は説明用に簡略化した例です。プロジェクトIDやアクセス制御タグなど、共通で渡している設定は省略しています。 include "root" { path = find_in_parent_folders("root.hcl") } include "common" { path = find_in_parent_folders("bigquery_dataset.hcl") merge_strategy = "deep" } inputs = { dataset_id = "sales" description = "売上データを格納するデータセット" access_level = "restricted" readers = [ "group:sales-analysts@example.com", ] } includeで共通設定を読み込み、共通ファイルのsourceで使うTerraform moduleを指定します。inputsでは、データセット名や閲覧できるグループをmoduleへ渡しています。 このunitでterragrunt planを実行すると、salesデータセットと、その権限の変更を確認できます。たとえばreadersにグループを1つ追加した場合、確認したいのは、そのグループへの閲覧権限が追加されることです。 eventsでも同じmoduleを使い、データセット名や閲覧グループを変えて設定できます。なお、moduleはコードを再利用する単位、unitは実行とtfstate管理の単位です。moduleを増やすだけでtfstateが分かれるわけではありません。 運用で得られているメリット この使い方によって、日々の変更では次の点が扱いやすくなりました。 変更する場所が分かる。 データセット名や閲覧グループを変えるときはlive側の設定、データセットや権限の作り方を変えるときはmodule、共通設定を変えるときはroot.hclを確認します。 関連するリソースをまとめて扱える。 データセットと権限の定義をmodule内にまとめています。データセットを増やす際も、個々の定義をコピーせず、設定値を変えて利用できます。 共通設定とtfstateを管理しやすい。 tfstateの保存方法などを各unitに繰り返し書かずに済み、確認したいデータセットのunitから、対応する設定とtfstateをたどれます。 unitを分ける粒度も、一緒に変更・確認したい範囲に合わせています。この例では、データセット本体と権限を別々のtfstateに分けず、データセットごとにまとめて管理しています。 運用上の課題 共通moduleの変更は、それを使う複数のunitに影響します。データセットの既定値や権限の定義を変えるときは、各unitのplanを確認する必要があり、データセットが増えるほど確認の負担も増えます。 また、module内のリソース名を変える際は、tfstateと既存リソースの対応を維持する必要があります。意図しない削除・再作成を避けるため、movedブロックなどで対応し、各unitのplanを確認します。 おわりに Terraformで管理する対象が増えてきたときに、共通化するコードと個別に管理する範囲を整理する参考になれば幸いです。
@Cartidise junkfood02/Seal Try this app, it's super quick and easy + also works with Tiktok, Instagram and others. You just share to this app, then you can select quality, audio/video etc