Mentions

@rezkhere @shushant_l @asymptotelabs Thanks Rez! Definitely check it out and lmk what you think :) Asymptote-Labs/agent-beacon

听 YouTube Music，网页广告多、桌面版套 Electron？ limusic 是 Rust + Tauri 原生桌面端：无 Electron、无广告，libmpv 无缝播放加同步歌词。 适合每天听 YouTube Music 的人，先装上试。 你听歌用网页版还是客户端？ #音乐 #桌面应用 @grok SimoHypers/limusic

@ginacostag_ @shushant_l @asymptotelabs Thanks Gina! Would love your feedback on Beacon: Asymptote-Labs/agent-beacon

Repo link - ranxianglei/billion-context

设计稿想让 AI 改，还得导出导入来回倒？ doop 是 paper.design 的开源平替：人和 agent 同屏画布，agent 走内置 MCP 直改，帧是真 HTML，可点原型免导出。 适合让 AI 参与产品设计的人，先开画布同屏试。 会让 agent 改设计稿吗？ #AI设计 #开源工具 @grok kgoedecke/doop

Qwen 3.6 35B A3B 400+ t/s prefill on 24GB M4 Pro with less than 6GB memory footprint Check it out davide-troiani/moeshift

Windows向け・Python 3が必要。 既存モデルの自動特定はCivArchiveで一致した場合のみ。トリガーワードなども配布元に情報がある場合に取得できます。 無料・オープンソース（GPL-3.0）。 GitHub： Tomat0223/AbyssBeacon Reddit： reddit.com

🚀 New Lichii (Eglantine Fork) build is out! ✅ Up to 2x FPS, most games hit 60 FPS (Pokopia, Switch Resorts & more) ✅ Graphics & speedup fixes ✅ Fire Emblem: Fortune's Weave now playable ✅ .nup support (game + updates + DLC in 1 file) ⭐ Star it: zortos293/Eglantine

Actuator-Aware Observer Inputs for Cascade ADRC of Quadrotors Under Rotor Lag, Measurement Delay and Sensor Noise Xuan-Quy Dao, Ngoc-Bich Le, Le-Minh Nguyen arxiv.org [𝚌𝚜.𝚁𝙾] 💬Code: Quang61123/actuator-aware-cascade-adrc t.co

Hex GitHub Overview: Local Voice Dictation with On-Device Transcription hex by anomalyco: anomalyco/hex Hex is an open-source local voice dictation project that captures microphone audio, runs speech recognition on the device, and inserts the resulting text into the active window. This overview follows that processing path from the microphone to the clipboard and a simulated paste, then covers Apple M-series, AVX2, and Vulkan requirements across macOS, Windows, and Linux. It also explains microphone and Accessibility permissions, the platform shortcut hold threshold, offline model use after initial setup, Bluetooth microphone trade-offs, and the input/output choices that shape dictation behavior. A sample transcription result illustrates the final text insertion, while the closing section points to custom vocabulary rules, deterministic text transformations, and the official repository documentation. TimeStamps: 0:00 Local Voice Dictation on Your Hardware 0:22 From Microphone to Active Window 0:49 Hardware and Platform Requirements 1:43 Latency and Distribution Model 2:23 Microphone and Accessibility Permissions 2:46 Local Capture and Text Injection 3:41 Bluetooth Input Trade-offs 4:23 Transcription Output and Customization 4:58 Repository and Project Context 🎙️ Local microphone capture and on-device transcription 🖥️ Platform requirements, permissions, and active-window text insertion 🎧 Bluetooth input trade-offs and shortcut behavior 🧩 Custom vocabulary, transformations, and repository context Hex’s core workflow is a clear local-dictation loop: hold the platform shortcut, speak, release, and send the transcript to the focused editor. The practical takeaway is to match hardware and permissions to the operating system, use a suitable microphone path, and consult the repository for configuration details. #Hex #VoiceDictation #LocalAI [de-DE] YNAS ynp_6f410b1dbe40e748 Cinematic Privater automatisierter Staging-Upload. Paketidentität: ynp_6f410b1dbe40e748; Ausgabe: cinematic. [es-US] Descripción general de Hex en GitHub: Dictado de voz local con transcripción en el dispositivo Hex de anomalyco: anomalyco/hex Hex es un proyecto de dictado de voz local de código abierto que captura el audio del micrófono, realiza el reconocimiento de voz en el dispositivo e inserta el texto resultante en la ventana activa. Esta descripción general sigue el proceso desde el micrófono hasta el portapapeles y una simulación de pegado, y luego aborda los requisitos de Apple M-series, AVX2 y Vulkan en macOS, Windows y Linux. También explica los permisos de micrófono y accesibilidad, el umbral de retención de atajos de teclado de la plataforma, el uso del modo sin conexión después de la configuración inicial, las ventajas y desventajas del micrófono Bluetooth y las opciones de entrada/salida que determinan el comportamiento del dictado. Un ejemplo de transcripción ilustra la inserción final del texto, mientras que la sección final remite a las reglas de vocabulario personalizadas, las transformaciones de texto deterministas y la documentación del repositorio oficial. Marcas de tiempo: 0:00 Dictado de voz local en tu hardware 0:22 Del micrófono a la ventana activa 0:49 Requisitos de hardware y plataforma 1:43 Latencia y modelo de distribución 2:23 Permisos de micrófono y accesibilidad 2:46 Captura local e inserción de texto 3:41 Ventajas y desventajas de la entrada Bluetooth 4:23 Salida de transcripción y personalización 4:58 Repositorio y contexto del proyecto 🎙️ Captura de micrófono local y transcripción en el dispositivo 🖥️ Requisitos de la plataforma, permisos e inserción de texto en la ventana activa 🎧 Ventajas y desventajas de la entrada Bluetooth y comportamiento de los atajos de teclado 🧩 Vocabulario personalizado, transformaciones y contexto del repositorio El flujo de trabajo principal de Hex es un ciclo de dictado local claro: mantén pulsado el atajo de teclado de la plataforma, habla, suelta y envía la transcripción al editor seleccionado. En resumen, asegúrate de que el hardware y los permisos coincidan con el sistema operativo, usa una ruta de micrófono adecuada y consulta el repositorio para obtener detalles de configuración. #Hex #DictadoDeVoz #IALocal [fr-FR] YNAS ynp_6f410b1dbe40e748 cinématique Téléchargement de l'environnement de test d'automatisation privé. Identifiant du package : ynp_6f410b1dbe40e748 ; sortie : cinématique. [hi] Hex GitHub अवलोकन: ऑन-डिवाइस ट्रांसक्रिप्शन के साथ लोकल वॉयस डिक्टेशन anomalyco द्वारा विकसित hex: anomalyco/hex Hex एक ओपन-सोर्स लोकल वॉइस डिक्टेशन प्रोजेक्ट है जो माइक्रोफ़ोन से ऑडियो कैप्चर करता है, डिवाइस पर स्पीच रिकग्निशन चलाता है और परिणामी टेक्स्ट को सक्रिय विंडो में सम्मिलित करता है। यह अवलोकन माइक्रोफ़ोन से क्लिपबोर्ड और एक सिम्युलेटेड पेस्ट तक की प्रक्रिया को दर्शाता है, फिर macOS, Windows और Linux पर Apple M-सीरीज़, AVX2 और Vulkan की आवश्यकताओं को कवर करता है। यह माइक्रोफ़ोन और एक्सेसिबिलिटी अनुमतियों, प्लेटफ़ॉर्म शॉर्टकट होल्ड थ्रेशहोल्ड, प्रारंभिक सेटअप के बाद ऑफ़लाइन मॉडल के उपयोग, ब्लूटूथ माइक्रोफ़ोन के लाभ-हानि और डिक्टेशन व्यवहार को प्रभावित करने वाले इनपुट/आउटपुट विकल्पों की भी व्याख्या करता है। एक नमूना प्रतिलेखन परिणाम अंतिम टेक्स्ट सम्मिलन को दर्शाता है, जबकि समापन खंड कस्टम शब्दावली नियमों, नियतात्मक टेक्स्ट रूपांतरणों और आधिकारिक रिपॉजिटरी दस्तावेज़ीकरण की ओर इशारा करता है। टाइमस्टैम्प: 0:00 आपके हार्डवेयर पर स्थानीय ध्वनि श्रुतलेख 0:22 माइक्रोफ़ोन से सक्रिय विंडो तक 0:49 हार्डवेयर और प्लेटफ़ॉर्म आवश्यकताएँ 1:43 विलंबता और वितरण मॉडल 2:23 माइक्रोफ़ोन और अभिगम्यता अनुमतियाँ 2:46 स्थानीय कैप्चर और टेक्स्ट इंजेक्शन 3:41 ब्लूटूथ इनपुट के फायदे और नुकसान 4:23 प्रतिलेखन आउटपुट और अनुकूलन 4:58 रिपॉजिटरी और प्रोजेक्ट संदर्भ 🎙️ स्थानीय माइक्रोफ़ोन कैप्चर और डिवाइस पर प्रतिलेखन 🖥️ प्लेटफ़ॉर्म आवश्यकताएँ, अनुमतियाँ और सक्रिय विंडो में टेक्स्ट सम्मिलन 🎧 ब्लूटूथ इनपुट के फायदे और नुकसान और शॉर्टकट व्यवहार 🧩 कस्टम शब्दावली, रूपांतरण और रिपॉजिटरी संदर्भ हेक्स का मूल कार्यप्रवाह एक स्पष्ट स्थानीय श्रुतलेख लूप है: प्लेटफ़ॉर्म शॉर्टकट को दबाए रखें, बोलें, छोड़ें और प्रतिलेख को लक्षित संपादक को भेजें। व्यावहारिक रूप से, हार्डवेयर और अनुमतियों को ऑपरेटिंग सिस्टम से मिलाना, उपयुक्त माइक्रोफ़ोन पथ का उपयोग करना और कॉन्फ़िगरेशन विवरण के लिए रिपॉजिटरी से परामर्श करना महत्वपूर्ण है। #Hex #VoiceDictation #LocalAI [id] Sinematik YNAS ynp_6f410b1dbe40e748 Unggahan staging otomatisasi pribadi. Identitas paket: ynp_6f410b1dbe40e748; output: sinematik. [it] YNAS ynp_6f410b1dbe40e748 cinematic Caricamento di automazione privata. Identità del pacchetto: ynp_6f410b1dbe40e748; output: cinematografico. [pt-BR] YNAS ynp_6f410b1dbe40e748 cinemático Upload de teste de automação privada. Identificação do pacote: ynp_6f410b1dbe40e748; saída: cinemática.

A research team built an open-source AI classroom. OpenMAIC can turn a topic or document into a lesson with AI teachers, classmates, quizzes, a whiteboard, and interactive simulations. Mindblowing! Bookmark 👉 THU-MAIC/OpenMAIC t.co

Qwen3.5-2B at 620 tok/s inside Chrome: model-specific WebGPU kernels, 6.6× WebLLM on the same model I built a browser LLM engine that's specialized per model rather than generic: Rust compiled to wasm, plus hand-written WGSL kernels for Qwen3.5-2B (Gated DeltaNet + gated attention) and MiniCPM5-2B. Same model, same chat prompts, greedy, Chrome 156: ||webyIQ|WebLLM 0.2.87|transformers.js 4.3| |:-|:-|:-|:-| |RTX 5080 generation|620 tok/s (417 without speculation)|94|31| |RTX 5080, ~1k-token prompt|0.20 s|0.81 s|~129 s| |AMD 2-CU iGPU generation|37 tok/s|4.7|crashed| What's in it: - fused int4 (GPTQ, group 32) × int8 GEMV/GEMM, with dot4I8Packed and subgroups; - a decode loop that stays on the GPU (argmax on GPU, pipelined readback); - speculative decoding with Qwen3.5's built-in MTP head. Drafts are verified on the GPU, so the output is identical to greedy. It turns itself off where it doesn't pay, e.g. on the iGPU; - weights at +2.4% WikiText perplexity vs bf16, 1.1 GB. Fun side effect: at this speed a 2B model can drive web pages through the DOM at 0.2–0.4 s per step. There's a browser-agent demo and a side-panel extension for Chrome/Edge. Caveats: it's a prototype, tested on Windows, and Safari/mobile are untested. Demo: rtx527896828.github.io · Code (Apache-2.0): rtx527896828/webyIQ · Weights: huggingface.co

@Teknium Thanks! Added the details to the existing GitHub issue (same bug on iOS): hermes-agent#147726

给你们看看好玩的👿👿👿 我制作了APP可以控制任何跳蛋，支持82个品牌，并且制作了王者荣耀联动功能👿👿👿 打王者掉血就震动，死了就超级震动，看看谁还说打不过👿 并且支持远程控制和一些其他的小功能 ，快来下载吧github.com/wellshrcn/GameToysTool/releases/downlo… t.co

Picking a winner fairly in a browser spin wheel: modulo bias, rejection sampling and a shuffle bag > This article was written with the help of AI and checked against the site's real code. The test code was run before publishing. A spin wheel looks like a physics toy, but the animation has nothing to do with the result. In the wheel I work on, the winner is chosen first. Then the wheel is told where to stop. That split makes the code simple, and it moves the fairness question to one small function. Here is how that function works, including a change we made because true randomness can look broken. Step 1: Choose the winner without bias The usual snippet is this: const winner = Math.floor(Math.random() * entries.length); For a party game this is fine. But Math.random() isn't meant to be a secure source of randomness, and if your wheel picks giveaway winners, you want a better answer when someone asks how it works. The browser has one built in: crypto.getRandomValues(). It gives you random integers, so the tempting next step is %: const buf = new Uint32Array(1); crypto.getRandomValues(buf); const winner = buf[0] % n; // slightly biased This has modulo bias. To see it, shrink the numbers. A random byte has 256 possible values. Split them across 7 entries with % 7, and you get this: | Entry | 0 | 1 | 2 | 3 | 4 | 5 | 6 | |---|---|---|---|---|---|---|---| | Byte values that land on it | 37 | 37 | 37 | 37 | 36 | 36 | 36 | 256 doesn't divide evenly by 7, so the first four entries get a small edge. With 32-bit numbers the edge is tiny, but removing it takes only two lines. The fix is rejection sampling. Throw away the leftover values at the top of the range and draw again: function randInt(n) { const limit = Math.floor(2 ** 32 / n) * n; const buf = new Uint32Array(1); do { crypto.getRandomValues(buf); } while (buf[0] >= limit); return buf[0] % n; } limit is the largest multiple of n that fits in the range. Every value below it maps evenly onto the entries. The loop almost never runs twice. Step 2: Make the wheel land on the winner Now the wheel needs to stop on the chosen slice. On a canvas, angle 0 points right and angles grow clockwise, so "the top" is 1.5π. If slices are drawn starting at the wheel's rotation, the middle of slice i sits at rotation + (i + 0.5) * slice. Solve for the rotation that puts it at the top: const slice = (Math.PI * 2) / n; const target = Math.PI * 1.5 - (winner + 0.5) * slice; Landing dead center every time looks fake, so add a random nudge that stays inside the slice. Our wheel uses up to 40% of a slice either way: const jitter = (randInt(1000) / 1000 - 0.5) * 0.8 * slice; Then add a few whole turns so it looks like a real spin, and use the shortest forward distance to the target so it never runs backward: const delta = ((target + jitter - rot) % (Math.PI * 2) + Math.PI * 2) % (Math.PI * 2); const end = rot + delta + Math.PI * 2 * (5 + randInt(3)); Step 3: Ease out, then stop when it looks stopped A quartic ease-out gives the slow, tense finish: const e = 1 - Math.pow(1 - p, 4); // p goes from 0 to 1 over the spin rot = start + (end - start) * e; There's a catch. The last part of a quartic ease is so slow that the wheel looks finished a moment before the animation is. If your confetti waits for p === 1, the celebration feels late. So we end the spin once the remaining turn is too small to see, about half a degree: if ((end - start) * (1 - e) < 0.009) p = 1; If the user asked for reduced motion (prefers-reduced-motion), the spin is cut to 600 ms and the confetti is skipped. Step 4: When true randomness feels broken With independent draws and 10 entries, the same entry wins twice in a row 10% of the time. That's correct math, but on a party wheel it looks broken: "It picked Sam again?" So on lists of 5 or more, our wheel uses a shuffle bag. Each entry goes in the bag, picks come out without replacement, and the bag refills when it's empty: function shuffleBag(n) { let left = []; return function next() { if (!left.length) left = Array.from({ length: n }, (_, i) => i); return left.splice(randInt(left.length), 1)[0]; }; } This is a real trade-off, and it should be stated openly: - Spins are no longer independent. If you've seen 9 of 10 entries win, you know exactly what's next. - Looking at one spin without knowing the earlier ones, each entry still has the same chance. - For one draw, like a single giveaway winner on a fresh list, nothing changes. - Number ranges and lists under 5 entries stay independent, because a bag would feel wrong there. Rolling 1 to 6 should be able to repeat. Choose based on what the wheel is for. If you need strictly independent draws, skip the bag. Test the part that matters You can't check fairness by looking at the animation, but you can test the picker: import test from 'node:test'; import assert from 'node:assert/strict'; test('randInt is roughly even', () => { const n = 7, runs = 700000, counts = Array(n).fill(0); for (let i = 0; i < runs; i++) counts[randInt(n)]++; for (const c of counts) { assert.ok(Math.abs(c - runs / n) < (runs / n) * 0.02); } }); This can't detect tiny bias, and that isn't its job. It catches the real bugs: off-by-one errors, a wrong limit, or a slice that never wins. Try it The helpers above are in a small MIT-licensed repo: BestSpinnerWheel/fair-pick. To see them in a working wheel, ours is at bestspinnerwheel.com. View source if you like: it's a static page, and your entries stay in your browser. If you've solved the "random doesn't feel random" problem another way, I'd like to hear how.

Code, every attempt and the videos: shayansanjideh/paper-plane-bench

Convertí la barra de acceso rápido y el inventario de Minecraft en un lanzador de aplicaciones para mi escritorio. Los corazones indican la memoria RAM disponible, el indicador de comida muestra el nivel de batería, el número de nivel representa el uso de la CPU y la barra de experiencia (XP) se va llenando a medida que avanza el día. Presiona la tecla «E» en el escritorio para abrir el inventario de supervivencia, donde verás a tu personaje en 3D; haz clic en cualquier casilla para abrir una aplicación. Las aplicaciones que están abiertas presentan el efecto visual de «encantamiento». Es un proyecto gratuito y de código abierto, exclusivo para Windows. Se trata de un proyecto hecho por fans, no oficial y sin afiliación con Mojang. GitHub: github.com/Jpsb3/MinecraftHotbar/releases

You might also be interested in: godot-proposals#14652

CNC Studio for 3018;s I have created a CNC design program for 3018's similar to easel, I would like some feedback for future versions. Available for free on github: centar2007/CNC-Studio

Mobile Suit Gundam Battle Operation - Code Fairy (PS4) | PS4RT Preview Hey everyone! Just wanted to share a quick update on PS4RT and what I've been working on recently. I'm still developing a native Linux port of Mobile Suit Gundam Battle Operation: Code Fairy (PS4). I've successfully played through the first few missions so far, and things are progressing nicely! There's still more testing and polishing to do before I'm comfortable releasing it, but I wanted to share a short gameplay preview of its current state. I also have a couple of other announcements: 1. Windows Ports for Star Ocean 5 and Sakura Wars (v1.01) Thanks to the efforts of two community contributors, both games now have Windows versions available! - u/DiamondDogz - github.com/DiamondDogz/Sakura-Wars-PS4RT-Windows/… - u/Hoverbike51 - github.com/Hoverbike51/Star-Ocean-Integrity-and-F… Huge thanks to both of them for their work in bringing these ports to another platform! 2. PS4RT Now Has a Website and Discord! I've also put together a dedicated website for PS4RT, where you can find the existing ports, their respective repositories, and available releases. The website also includes an invitation to a new Discord server, where I hope to discuss the ports, report issues, share feedback, or follow development. I hope to continue expanding the collection as more games become playable through PS4RT. Website: https://ps4rt.dev/ As always, thanks to everyone who has been following the projects, testing releases, and contributing. There's still plenty of work ahead, but it's exciting to see the project continue to grow!

DG-Dock for win 11 = Ready to download Hi everyone! I made this dock for Windows 11, and I hope you like it. I don’t have a coding background. I’m just a designer, and I built the app using vibe coding. It took me about 3 weeks. If you find any issues, please let me know, and I’ll do my best to improve it. You can try it now from GitHub! Dippy1234/DG-Dock If you like my work, feel free to support me.

I made a Claude Code skill that replaces pitch decks with a clickable prototype + an animated walkthrough. The landing page is one of the outputs I kept building throwaway prototypes to explain ideas at work instead of slides, because "here's the screen, here's the click" lands better than bullet points. So I turned it into a skill. You describe a feature or an internal tool in Claude Code. The skill writes two things into your repo: a Next.js prototype with mock data, and a short animated presentation that explains the idea and then tours the prototype with a spotlight and a cursor. It works from a screenshot of an existing product too, if you want the style matched. `npm run share` builds it locally and uploads the static files to an unlisted link. The landing page is itself a talk in that format, so you can see what it produces before installing anything: neoslides.dev (arrow keys, or let it play). Install: paste `Install neoslides by following neoslides.dev into Claude Code, start a new session, then ask it to pitch something. Limitations: the prototype is a mock, nothing connects to real systems, and the quality tracks how clearly you describe the idea. Skill and template are MIT: maksspace/neoslides Curious what kinds of ideas people throw at it and where it falls over.

The trigger can be an ordinary path like .../anthropic/... The authors' fix is at run time: sandbox the agent, least privilege, and allow-list or confirm high-risk commands before they execute. Code (no checkpoints): safety-research/agentic-backdoor

Godot needs an unified type system. What if tell you the OO architecture is being touched? idk if what you have in mind is like this, but check it out: godot#123136 I know Variant is a constant source of overhead. Still, steps in the right direction. JIT is probably more of a wish.

Just pushed an update that brings the VCS Launcher to Linux as an AppImage. Next few updates are going to focus on broken missions, camera controls and hopefully some graphical bug fixes. github.com/gothamor/gta-vcs-recomp/releases/tag/v…

@haibnu Bi bakmakta fayda var 🙂‍↔️ @uiverse_io uiverse-io/galaxy

2/ The Canopy Dev Skill. We released an @OpenAI and @AnthropicAI skill that plans your app, implements it, and debugs it with you. Now you can more effectively write onchain apps with your favorite development agents. Use it now: canopy-network/canopy-dev-skill

Build & optimize a .NET + metal llm inference engine for qwen 3.6 35b. SO FAR it reaches 1.6k prefill speed. LittleLittleCloud/llm-bootstrap-qwen3.6-35b-dotnet-metal t.co

finally got around to rooting and changing the horrendous LG webos homescreen with: lasharor/cleanyourtv-WebOS t.co

For all DCS user I made a better discord rich presence NeiloF16/DCS-Rich-Presence t.co

Okay, so i was cold mailing the other day and got bored after doing 3 mails (ts is boring ) so i kind of automated the process, and here is the demo : 😋😋😋 oka bye. coldmail-cpw0.onrender.com shataksha45-shiiii/Cold-Mail t.co

I built a gesture app for macOS 26. Here's how it works and how launch week went I'm Roman, and last Friday I launched Qesture, a menu bar app for macOS 26 that adds gestures for windows and spaces to the trackpad and mouse. This post covers how it works under the hood, two things macOS taught me along the way, and what launch week looked like, with real numbers. !Space Grid: spaces arranged in a grid, picked with a four-finger hold What it does I wanted my trackpad and mouse to do more with windows and spaces, without reaching for the keyboard or Mission Control. So Qesture adds: - Space Grid. macOS keeps spaces in one row; Qesture treats that row as a grid. Four-finger swipes up and down jump a whole row, and holding four fingers opens an overlay where you slide to pick any space. - A window switcher that shows windows instead of apps, on Command-Tab and on a three-finger swipe. While it's open, W, M, H and Q close, minimize, hide or quit. - Mouse: smooth scrolling with its own direction, actions for the middle and side buttons, and a middle-button drag between spaces. - Trackpad extras: a three-finger tap for middle click, two-finger swipes on a title bar to tile a window, press and slide with three fingers to move one, Force Click actions, and a five-finger radial menu. !The window switcher shows windows, not apps How it works It's Swift with some C, and each feature sits on a different macOS API: - Trackpad touches come from the private MultitouchSupport framework. It reports raw finger positions on every frame, which is what you need for gestures macOS doesn't offer, like a four-finger hold or a five-finger rest. - Mouse and keyboard input goes through CGEvent taps. - Moving and tiling windows uses the Accessibility API. - Previews in the switcher and the grid use ScreenCaptureKit. - Instant space switching uses jurplel's MIT-licensed InstantSpaceSwitcher. Because of the private framework, Qesture can't be in the Mac App Store. It's signed with Developer ID and notarized, and I sell it from my own site through Stripe. The flip side is that any macOS update can break part of it, so I test every beta. Licensing works offline. A purchase gives you an Ed25519-signed license token, and the app checks the signature on the Mac, so it keeps working for 30 days without internet. There's no analytics in the app: it goes online only for license and update checks. Two things macOS taught me Event taps get switched off. If an event tap's callback takes too long, macOS disables the tap and sends it kCGEventTapDisabledByTimeout instead of events. For a gesture app, that means mouse features silently stop working. Every tap in Qesture handles that event and turns itself back on. The real lesson is to keep tap callbacks short and do the heavy work somewhere else. Accessibility can't see other spaces. The switcher builds its list from CGWindowListCopyWindowInfo and adds details from each app's Accessibility windows. But the Accessibility API only lists an app's windows on the current space. The switcher has a setting to leave out windows of hidden apps, and my first version checked it inside the Accessibility branch, so windows of hidden apps on other spaces still showed up. The fix was to check whether the app is hidden before that branch, plus a test for windows Accessibility doesn't report. Launch week, with numbers I launched everywhere on Friday, October 30: - Product Hunt: 2 upvotes. Without an audience to bring along, a launch there doesn't get far. - Show HN: didn't happen. HN currently restricts Show HN posts from new accounts, and mine had 1 karma. I've emailed the moderators. - Reddit: posts from my low-karma account were removed by spam filters, and r/macapps asks for karma in the subreddit first. - MacRumors forums: the thread was held for moderation because the account was new, then approved. - Directories like AlternativeTo, SaaSHub and MacUpdate: most are still in review days later. - Peerlist: launched on Monday, November 2. The site counts visits without cookies. The Cloudflare Worker that serves it writes the page, the referrer's host and the country to Workers Analytics Engine, and it doesn't store IP addresses or user agents. Since I started counting on the evening of November 1, there have been about 170 visits from people, 12 DMG downloads, and the first sale, on November 2. Most visits arrive with no referrer at all, so I can't tell exactly where they came from. Links opened from apps and chats look like that. What I'd do differently: 1. Build accounts before launch day. HN and Reddit both hold back new accounts, and that's where a lot of Mac developers and users are. A few weeks of normal participation first would have opened both. 2. Submit to directories early. Most take days or weeks to review, so they don't help on launch day unless you send them well before. 3. Tag every link. A ?ref= parameter on each link I post is the only way to see where visits come from, since most arrive without a referrer. Try it Qesture needs macOS 26 or later. There's a 14-day free trial with every feature, with no account or card. After that it's a one-time $9.99, and for launch it's 30% off until November 30, applied at checkout. 👉 qesture.com I'd like to hear which gesture you'd add, and anything that feels laggy or clashes with your setup. I'll answer in the comments. An AI assistant drafted this post from the Qesture code and launch data, and I reviewed it before publishing.

⭐️iOpenMoHAA-PS3 v0.1.0.0b released by @kadorna1 🔷3 independent game packages: 🔸Allied Assault 🔸Breakthrough 🔸Spearhead 🔷BSP surface streaming 🔷Renderer and memory work 🔷DualShock 3 aim assist across all titles 📥github.com/kadorna1/iopenmohaa-ps3/releases

Web抽出が成功しても、要約が正しいとは限らない：原典照合で確認する3点 Webページを取得して、LLMが使いやすい形に整える。そんな処理を組み込むとき、HTTP 200やJSONの成功フラグが返れば、次の工程へ進めたくなります。 ただ、取得できたことと、要約が原文の意味を保っていることは別です。 原文にある一節を引用していても、隣にある利用条件や、末尾に加わった追記を落とすことがあります。 この記事では、公開ページの抽出結果で実際に確認した3つの例を整理し、引用の存在だけを調べる短いJavaScriptを書きます。 対象は、Webの抽出結果を調査や記事作成へつなぐ開発者です。自動ファクトチェックや、サービスの安全性を判定する仕組みを作る記事ではありません。 成功フラグが答えている範囲を決める ここで扱う実例は、Public Source Extractorを通して、実験的なfirecrawl-keyless provider（外部の抽出サービスを利用する仕組み）から得た結果です。 以下は2026年10月30日〜11月1日に行った、異なる公開URLの個別観測です。同じ条件で繰り返した精度試験ではありません。 対象 抽出結果で気になった点 原典で確認した点 Zennのガイドライン 宣伝全般を禁止するような要約になった 宣伝を主目的にした投稿を避ける話と、末尾の短い案内を区別している Zennの新着ページ移行のお知らせ 移行の計画を挙げ、完了の追記を明示しなかった 計画を説明した本文の後に、移行完了の追記がある SpecsightのFAQ コード非保存の説明から、プライバシーや安全性の保証に踏み込む表現になった コードの送信、一時的な複製、分析後に残す情報が別々に説明されている 原典は、Zennのガイドライン、移行のお知らせ、SpecsightのFAQです。2026年11月3日の本文確認でも、表に挙げた区別を確認しました。 3件とも取得処理のokはtrueでした。それでも、利用条件や時点については原典へ戻って判断する必要がありました。 これは各サービスの不具合を報告するものではなく、抽出後の生成文をどう読むか、という話です。CLI本体のバグや、providerで必ず起きる性質とも断定できません。 1. 限定条件を落としていないか 「一部の用途に使える」が「どの用途にも使える」に変わると、短い要約ほど大きな違いになります。 例えば、料金ページの原文に、無料枠の説明と商用利用の条件が並んでいる場合です。 無料枠に関する一節だけを抜き出せば、引用自体は実在していても、商用利用できるという結論の裏付けにはなりません。 読むときは、結論に関係する次の要素を原文の前後で確かめます。 対象者や用途が限定されていないか。 例外や有料プランなどの条件が省かれていないか。 原文の推奨が、要約では義務や禁止に変わっていないか。 Zennの例でも、宣伝が主目的の投稿と、技術記事の末尾に置く短い案内を一つにまとめると、原文より強いルールになります。 必要なのは、禁止という単語の有無だけでなく、何を、どの範囲で説明しているかの確認です。 引用の存在だけなら、小さなコードで調べられる 引用が渡された文字列に含まれるかは、自動で調べられます。 ただし、関数名も戻り値も、意味を検証したようにはしません。 次は架空の料金・移行案内だけを使う例です。Node.jsで実行でき、外部通信や追加パッケージはありません。 コードをexample.mjsという名前のファイルに入れ、ターミナルでそのファイルがあるディレクトリからnode example.mjsを実行します。動作確認はNode.js v22.22.1で行いました。 function quotePresence(source, quote) { if (typeof source !== 'string' || source.length === 0) return 'unknown'; if (typeof quote !== 'string' || quote.trim().length === 0) return 'unknown'; return source.includes(quote) ? 'found' : 'not_found'; } const source = [ 'The free plan is limited to personal, non-commercial evaluation.', 'Commercial use requires a paid plan.', 'Update: the migration is complete.', ].join('\n'); console.log(quotePresence(source, 'Commercial use requires a paid plan.')); console.log(quotePresence(source, 'Commercial use is free.')); console.log(quotePresence(source, '')); console.log(quotePresence(null, 'Commercial use requires a paid plan.')); console.log(quotePresence(source, 'The free plan')); console.log(quotePresence(source, 'commercial use requires a paid plan.')); 出力は次のようになります。 found not_found unknown unknown found not_found 空の引用を先に除外しているのは、includes('')がtrueになるためです。 原文を取得できなかった場合も、引用がなかったと判定せず、unknownにします。 5行目のfoundに注目してください。 The free planという抜粋は実在しますが、「商用でも無料」という主張が正しいかは、この関数では分かりません。そもそも関数へ要約文を渡していないのです。 また、これは大文字小文字、空白、表記差を吸収しない部分文字列の一致です。 最後のnot_foundのように、表記が違うだけでも見つかりません。not_foundは、渡した文字列の中で一致しなかったという結果であり、引用が捏造された証明ではありません。 逆にfoundも、原典全体を取得できたことや、主張の正しさを保証しません。 文字列処理の仕様はECMAScriptのString.prototype.includesで確認できます。 2. 計画と完了の追記を混ぜていないか お知らせページには、最初の計画を残したまま、後から進捗を追記することがあります。 その場合、古い段落との引用一致だけでは、現在の状態を確かめたことになりません。 今回のZennのお知らせにも、移行予定の説明と、その後の完了追記が同じページにありました。 要約が予定に触れていても、末尾まで読み直すと、現在の案内に必要な情報が変わります。 日付を一つだけ持つと、この違いが見えにくくなります。少なくとも、次の3つは分けて考えます。 時刻 何を表すか 元ページの公開・更新日時 発信元が示す日時。更新日時が表示されないページもある 抽出ツールが結果に付ける日時 ツールの実装によって意味が異なる 重要な主張を原典で確認した日時 自分の確認記録。確認した範囲も一緒に残す 例えばPublic Source Extractorの公開版0.1.1の実装では、fetched_atは成功結果を組み立てる際のUTC日時です。 元ページの更新日時でも、provider側のキャッシュが新しいことの証明でもありません。 結果に今日の日付があっても、要約が今日読める全追記を含むとは限らない。その前提で、結論に使う箇所と後続の追記を確かめます。 3. 「保存しない」を「送信しない」に広げていないか 安全性に関する説明では、動詞を一つにまとめないことが大切です。 「保存しない」「外部へ送らない」「学習に使わない」は、それぞれ確認する内容が違います。 さらに、ソースコードと、そこから作られた仕様やメタデータでは、残る情報の範囲が異なる場合もあります。 Specsightの例では、FAQの非保存という説明だけでなく、外部モデルへの送信、一時環境での処理、処理後に残す情報まで読む必要がありました。 ここで確認できるのはベンダー自身の説明であり、こちらが実通信やサーバーの保存状態を監査したわけではありません。 要約に安全そうな一文があっても、それを導入許可や「情報が外へ出ない」という保証にはしません。 入力データ、送信先、一時処理、保持する情報を分け、原典に書かれていない部分は不明のまま残します。 自動確認と、人が読む確認を分ける 抽出結果を使う前の手順は、次の程度から始められます。 取得結果にURLと処理結果があるかを確認する。 結論に使う主張を一つ選び、対応する原文と前後の条件を読む。 ページ末尾の追記と、時刻フィールドの意味を確かめる。 主張の範囲が変わったら要約を直し、確認できない部分は不明とする。 URLや日時の形式、引用の文字列一致は自動確認を助けます。 一方で、引用が結論を支えているか、限定条件が残っているかは別の確認です。今回のコードから公開可否を返さないのも、そのためです。 3件の観測からproviderの誤り率を推定することはできません。 次に同じURLを抽出して、同じ結果が返るという保証もありません。手元で再現できるのは、上に載せた架空文の文字列処理と、その限界です。 まとめ 引用が原文にあっても、その引用が要約の結論を支えているとは限りません。 限定条件、後から加わった追記、保存・送信・保証の範囲を原典で読み直し、文字列の一致だけで判断を終えないようにします。 筆者はPublic Source Extractorを開発しています。公開URLの入力を第三者provider経由で処理するexperimentalなツールで、原文の意味を保証するものではありません。 文章・説明用コードの作成と検証にはAIを補助として使用しています。

@ryangrowthh It’s open source You can just read the algorithm xai-org/x-algorithm

github.com/wnfs-wg

I'm seeing @charliermarsh cooking on my timeline astral-experiments/imre  👀👀👀👀👀 t.co

CWIST: A lightweight C web framework focused on simple, predictable conventions I did this for fun, and it is definitely not a good portfolio to get a job as a C programmer. 😄 I was a bit tired of seeing yet another toy project built with NextJS + Tailwind CSS + generic bloated docker setups, so I wanted to build something different for my own small services like my dev blog. Anyway, let's talk about "why keep it simple?" Here is the basic example from CWIST's readme: #include <cwist/app.h> static void hello(cwist_http_request *req, cwist_http_response *res) { (void)req; cwist_sstring_assign(res->body, "Hello from CWIST!"); } int main(void) { cwist_app *app = cwist_app_create(); cwist_app_get(app, "/", hello); cwist_app_listen(app, 8080); cwist_app_destroy(app); return 0; } Some might argue that isn't the simplest way to write C. They might prefer something like this: #include <cwist.h> static void hello(cwist_http_app *app) { cwist_sstring_assign(app->res->body, "Hello from CWIST!"); } static void setApp(cwist_http_app *app) { CWIST_APP_CREATE(app); app->get.append(app->get, "/", hello); app->ipv4.port = 8080; } int main(void) { CWIST_APP_LISTEN(app); CWIST_APP_DESTROY(app); return 0; } Sure, that style has its own perks. But notice how some fields are raw struct members, some are macros in ALL CAPS, and some are functions. It gets messy fast. Personally, sticking to unified naming conventions across the board makes C code much easier to read and maintain. Also, clear public functions like cwist_app_* work a lot better with modern tooling. Whether you use an LSP for completion or use LLMs to scaffold boilerplate, direct struct mutations tend to cause frequent hallucinations and broken guesses. Explicit function names stay predictable. The second style also ends up needing extra helper code under the hood. While CWIST's main() might look a bit explicit, each step is just a clean wrapper function. You can snap things together like Lego bricks. To be clear, this is not trying to replace mature frameworks like Drogon. If you need something battle-tested for enterprise production, CWIST is not there yet since it hasn't gone through extensive third-party security audits. That said, every commit still goes through sanitizers, cppcheck, HTTP soak testing, HTTPS C100k benchmarks, WASM/WASI smoke tests, and HTTP/2 tests. I did consider adding HTTP/3 support, but it ended up borrowing too heavily from lsquic, so I shelved that for now. It's not claiming to be the fastest C framework in existence, but the performance is solid enough for personal sites and lightweight microservices. C4Punks has several contributors, but people are busy with work so I handle most of the maintenance and releases right now. Managing all the modules and refactoring can be exhausting, but it's been a fun ride. Contributions, feedback, and documentation fixes are always welcome: github.com/c4punks/CWIST/issues Thanks for reading!

Furby connect emulator test (static glitch) This is earlier footage of me testing the emulator. During testing, I executed the address sequence 13 00 21 00 00 81, which caused the firmware to halt. More about the emulator: FurbLord/furbulator

An old manual can look readable yet be impossible to search. Tesseract turns page images into text. Useful when you're hunting for one detail in a long scan. The output still needs checking. tesseract-ocr/tesseract

cvise: Super-parallel Python port of C-Reduce

Dá pra entender o Brasil sem economês. O Brasil em Gráfico explica dados do IBGE, Banco Central, ANP e Aneel com perguntas simples. E é aberto: o próximo dado pode ser seu. Contribua 👇 andersonvalentim/brasil-em-grafico #DadosAbertos #CódigoAberto t.co

@anitviber @lvwerra The published prototype is built around one GitHub repository. Feishu is an optional message source alongside GitHub, so adding chat doesn’t remove that dependency: deepseek-ai/dsh-superagent-prototype

just submitted omacast to the omarchy plugins repo! omarchy-plugin-marketplace#13705

had a great time at @OpenAIDevs DevDay Exchange London on sunday. shipped two things: game master: say a rule out loud and the game rewrites itself rashad-h/game-master coffee run: ai agents racing to deliver a coffee (with my team) AxENSRennes/openai-hackathon t.co

@CupOJoseph I recommend service accounts for this amiller/awesome-google-service-accounts

@Verdana86 @lvwerra In this prototype, workers can subscribe to related issue/PR threads, and the main session can pass a short note from another ticket. That’s its documented cross-ticket context mechanism: github.com/deepseek-ai/dsh-superagent-prototype/b…

@dingyi alienator88/pearcleaner 这个也不错 还支持pkg卸载