Mentions

Conversations linking to GitHub, newest first. Times are UTC.

Mentions by source

X

6,842
Nov 16, 14:00Nov 17, 14:00

Bluesky

2,210
Nov 16, 16:00Nov 17, 16:00
Nov 16, 15:00Nov 17, 15:00
Nov 16, 15:00Nov 17, 15:00
Nov 16, 16:00Nov 17, 16:00
Nov 16, 16:00Nov 17, 16:00
Nov 16, 15:00Nov 17, 15:00
Nov 16, 16:00Nov 17, 16:00
Oct 14, 21:00Oct 15, 21:00

Delayed · data through Oct 15, 21:00 UTC

DEV

1,020
Nov 16, 16:00Nov 17, 16:00
Nov 16, 16:00Nov 17, 16:00
Nov 16, 11:00Nov 17, 11:00
Nov 16, 16:00Nov 17, 16:00
Oct 28, 01:00Oct 29, 01:00

Delayed · data through Oct 29, 01:00 UTC

Nov 8, 11:00Nov 9, 11:00

Delayed · data through Nov 9, 11:00 UTC

Nov 16, 16:00Nov 17, 16:00

Latest posts

  1. Redditu/MilkteaTW · r/u_MilkteaTW · 1 point

    piscout: find and manage every Raspberry Pi on your network (Windows) Scans your LAN and lists your Pis, with a built-in SSH terminal (with command suggestions), remote desktop, drag-and-drop file upload and SD card flashing. An Add-ons tab installs a NAS (Samba), Docker, fail2ban or automatic security updates in one click, using official apt packages only and showing the exact steps first. It also includes a small MCP server so an AI assistant can list your Pis and run commands. Not code-signed, so Windows SmartScreen may warn. MilkteaTW1/piscout

  2. Redditu/OrneryProfit659 · r/ScientificComputing

    Update on my VAWT solver: fixing false validation claims, implementing AST-normalized hashing, and moving toward hardware A few weeks ago, I shared a 2D BEM solver for the Sharp cycloturbine (a passive variable-pitch VAWT). The feedback I received pointed out a serious flaw: I was claiming to "validate" against the Ham 1979 experimental data, but my own plot showed a massive shape mismatch. I was relying on a loose CI test that checked only the peak value and printed a PASS, while ignoring the curve shape. I was overstating the results. I spent the last few weeks fixing both the science and the software architecture to prevent this class of error. Here is what changed. 1. Fixing the Validation Framing The Ham 1979 comparison is no longer called a "reproduction." It is now explicitly framed as a 2-D upper-bound comparison. The CI acceptance criteria were tightened to catch peak drift, and the README now explicitly states that the model has a known high bias due to missing finite-span (3D) losses. 2. AST-Normalized Hashing The repo uses cryptographic stamps to ensure 20 generated result JSONs match the exact source code that produced them. Previously, I hashed raw file bytes. This meant a single typo in a docstring would invalidate all 20 stamps and force a 30-hour batch regeneration on my local machine. I refactored the stamping logic to parse every .py file with Python’s ast, strip out module/function/class docstrings, and hash a canonical serialization of the remaining AST. Comments and docstrings no longer break provenance; behavior-bearing code changes still do. 3. Manual Sweeps vs. Automated Optimizers I added a parametric sweep tool and tested the blade pivot position (sp). My differential evolution optimizer had chosen sp = 0.216. However, a manual sweep revealed that sp = 0.20 actually yields a higher power coefficient (Cp 0.361 vs 0.358) while still allowing the turbine to self-start at 4 m/s. Pushing the pivot past sp = 0.25 shifts the aerodynamic center, causing the blade to lock up and Cp to collapse to 0.027. 4. Transition to Hardware The project is now moving toward a physical 1.8m prototype. I parameterized the polar generator to create NACA 0018 tables (which perform better at the prototype's low Reynolds numbers), built an interactive Streamlit dashboard for time-series telemetry, and wrote a formal measurement protocol to compare real-world electrical output against the model's predictions. Takeaway When building computational models, it is incredibly easy to get lost in your own plots and rely on fragile tests that confirm your biases. The best thing that happened to this project was having the validation methodology challenged. Scientific computing isn't just about writing the solver; it's about building a system that refuses to let you lie to yourself. Repo: juroc58/sharp-vawt-lab (Happy to answer any questions about the AST hashing approach or the BEM physics).

  3. X@vivek_1103 · 21 views

    Built WorkQueue, a fault-tolerant distributed task queue in Java & Redis: 1. Lease based in-progress tracking (Redis ZSET) 2.Auto-recovery for crashed workers via background reaper 3.Dead Letter Queue (DLQ) after 3 failed retries vivek0101012/Distributed-workQueue t.co

  4. Redditu/Spiritual_Bar_3995 · r/CLI · 53 points · 1 comment

    Just on cli i make a short movie with ACSII If you want to see for yourself and if you enjoy it please feel free to share. Seijurio/galaxysame

  5. X@grisdoteth · 4 views

    Also only clone the official repo, the fake ones are already out there shiyu-coder/Kronos

  6. Redditu/Weekly_Lab_9122 · r/AynThor · 149 points · 27 comments

    Cemu-Plus (Cemu Fork with Framegen and new features) Hey everyone! Development on the Cemu Android port and on Cemu itself has been quiet for a while, so I started my own fork with some features I wanted on my AYN Thor. • Lossless Scaling frame generation, using your own Lossless.dll • AMD FSR 1 and Snapdragon GSR upscale filters with a sharpness slider • On dual screens with a different aspect ratio from the original WiiU Gamepad screen, a toolbar fills the black bars around the GamePad with FPS, FrameGen Controls, quick buttons and more. • A Wii U style first-time setup wizard • A cleaner home screen with bigger game icons It installs next to the regular Cemu app, so you can try it without losing anything. It's still experimental, so expect some rough edges. If anyone wants to try it, here it is: danielcamilo1/cemu-plus

  7. Redditu/yohji12 · r/hoggit · 15 points · 2 comments

    Free aerobatics principles for the Christen Eagle II and MB-339 preview.redd.it Hi r/hoggit, I turned my notes on aerobatic flying into a short book and released it for free. I wrote it flying the Christen Eagle II and the MB-339, and it is meant for flight simulation only. It does not hand you a list of figures to copy. It starts from what is underneath and builds up from there: - Principles: energy management, angle of attack, load factor, what each control really does, and how to read the horizon and the wingtips to judge your attitude - Exercises: lines, rolls, steep turns with accelerated stall recovery, stalls and spin recovery - Figures: aileron roll, slow roll, barrel roll, loop, hammerhead, tail-slide, spin and snap roll, each with its Aresti symbol There is also a one-page kneeboard card with the entry parameters of the exercises. Drop the PNG into `Saved Games\DCS\Kneeboard\` and you have it in every cockpit. - Download on DCS User Files: files.digitalcombatsimulator.com - Latest version and source on GitHub: yohji/aerobatics-principles Free, CC BY-NC-SA 4.0. Feedbacks and corrections are very welcome, here or as a GitHub issue.

  8. Introducing MobileGraph: An Open-Source AI Application Framework for Kotlin Multiplatform MobileGraph is an open-source Kotlin Multiplatform SDK built strictly for the realities of Android and iOS edge devices. It allows you to orchestrate non-deterministic AI tasks — from streaming chatbots to autonomous ReAct agents — with absolute deterministic lifecycle control. _This is Part 1 (Introduction) of a series on building AI-powered mobile applications with MobileGraph._ Think of it as the architectural principles of LangGraph, re-engineered for mobile lifecycles. It’s published on Maven Central, licensed under Apache 2.0, and designed to bind seamlessly to Jetpack Compose and SwiftUI state structures. A Streaming Chat in 4 Lines Let’s cut to the code. No callbacks, no listeners — just native Kotlin Flow<T> for structured concurrency and cooperative cancellation. val session = MobileGraph.instance.createSession() // Safely collect in your ViewModel / Compose UI session.stream("Plan a 3-day trip to Tokyo").collect { chunk -> print(chunk.text) } That’s it. Session management, conversation history, provider communication — all handled for you. What Can You Build? MobileGraph isn’t just a chat wrapper. It’s a full AI application framework with below major capability areas: 💬 Multi-Provider Chat Register multiple AI providers- OpenAI, Google Gemini, Anthropic Claude, DeepSeek, OpenRouter — all through a unified API. Your prompts, tools, and agents work identically across providers. You can swap between models based on prompt compexity or your requirement. MobileGraph.initialize { withModels { openai(apiKey = "sk-...", name="gpt-4o-mini") { isDefault = true } gemini(apiKey = "...",name="gemini-2.5-flash-lite") claude(apiKey = "...",name="claude-3-5-sonnet-20241022") } } Want to use a local Ollama instance? Just point to a custom endpoint: val localModel = OpenAIChatModel( name = "llama3", apiKey = "ollama", baseUrl = "http://10.0.2.2:11434/v1" ) Developers are free to implement the ChatModel interface and can point to their own LLM provider. 📄 On-Device RAG Load documents, split them into chunks, embed them, and search — all on-device: // define vector embedding model val embeddingModel = MediaPipeEmbeddingModel({ context }) // DB driver val driver = AndroidSqliteDriver( schema = VectorDatabase.Schema, context = context, name = "mobilegraph_vector.db") // create vector store val vectorStore = SQLiteVectorStore(driver, embeddingModel) MobileGraph.knowledge.ingest { docId("manual-001") docName("Product User Guide") loader(PdfDocumentLoader(pdfExtractor)) splitter(RecursiveTextSplitter(chunkSize = 500, chunkOverlap = 100)) vectorStore(SQLiteVectorStore(driver, embeddingModel)) } MobileGraph ships with loaders for PDF, Markdown, HTML, JSON, CSV, and websites. Text splitters include RecursiveTextSplitter, TokenTextSplitter, and CharacterTextSplitter. You can implement custom loaders for any format with a single interface. Retrieval is the act of finding relevant context from your knowledge base to answer a user’s question. MobileGraph supports several built-in retrievers to balance speed and accuracy. Retrival techniques inlude VectorStoreRetriever BM25Retriever HybridRetriever MultiQueryRetriever RAG Pipeline: The RagPipeline orchestrates the entire process: Search -> Augment -> Generate. // Basic setup val vectorRetriever = VectorStoreRetriever(vectorStore) MobileGraph.initialize() { // ... model and vector store config ... withRetrievers { register("default", vectorRetriever, isDefault = true) } withRag { retriever(vectorRetriever) chatModel(myChatModel) // contextBuilder(customBuilder) // Optional: for custom prompts/guardrails } } // Execute a query // Standard execution (returns model response) val result = MobileGraph.rag.pipeline().execute("What is the battery life?") 🤖 Autonomous Tool-Calling Agents Give your AI “hands” — define Kotlin functions it can autonomously decide to call: val weatherTool = object : Tool<String, String> { override val metadata = ToolMetadata( name = "get_weather", description = "Gets the current weather for a specific city." ) override suspend fun invoke(input: String, context: ExecutionContext): String { return "The weather in $input is 25°C and Sunny." } } MobileGraph.initialize { withTools { register(weatherTool) } } The LLM autonomously decides when to call which tool. MobileGraph even includes Semantic Tool Selection — using vector embeddings to pick only the most relevant tools, so you’re not wasting tokens sending 100 tool definitions every call. 🔀 Multi-Agent Workflows For complex tasks, one agent isn’t enough. MobileGraph’s stateGraph DSL lets you orchestrate teams of agents: val workflow = stateGraph { start("researcher") node(AgentNode("researcher", researchAgent, runtime)) node(AgentNode("writer", writerAgent, runtime)) node(EndNode("done")) edge("researcher", "writer") edge("writer", "done") } val result = agentRuntime.run(workflow, initialState) This supports: - Fan-Out / Fan-In — run agents in parallel, merge at a sync point - Human-in-the-Loop — pause for user approval, then continue - Hierarchical Sub-Agents — manager agents that own internal sub-workflows - Conditional Branching — route based on state variables 💾 Durable Execution (Survives Process Death) This is MobileGraph’s superpower for mobile. The framework automatically checkpoints state after every graph node execution. If the OS kills your app — or the user navigates away and comes back — you resume exactly where you left off: // Resume after process death or human-in-the-loop approval val result = agentRuntime.resume( graph = workflow, checkpointId = "trace_node_timestamp", nodeId = "review", input = mapOf("approved" to true) ) This is powered by immutable state — every transition creates a new state snapshot (State S → Node → State S'), making the entire workflow replayable, debuggable, and recoverable. 🔧 Middleware Pipeline Cross-cutting concerns live in composable middleware — just like HTTP middleware in Ktor: middleware { +LoggingMiddleware() // Log every prompt & response +RetryMiddleware(maxRetries = 3) // Auto-retry on network failures +ChatMemoryMiddleware() // Auto-manage conversation history } 🌐 Connected Ecosystem: MCP & A2A Protocols MobileGraph breaks out of single-app boundaries by supporting the industry’s two leading open communication standards. - Model Context Protocol (MCP) - Connect your agent to external tools on servers, lambdas, or local hardware over JSON-RPC 2.0 with auto-discovery and auto-registration into ToolRegistry. - Agent-to-Agent (A2A) Protocol — Delegate complex graph subtasks from on-device models to specialized cloud agents via A2ANode, featuring Agent Card discovery, SSE artifact streaming, and native human-in-the-loop task resumption. The Architecture in 30 Seconds MobileGraph is organized in three layers, with dependencies flowing strictly downward: 📱 Application Layer (Your App) │ 🔷 MobileGraph SDK (Entry Point & DSL) │ ┌────┴────────────────────────────┐ │ │ 🧠 Intelligence Layer 📚 Knowledge Layer • Models & Providers • Documents & Loaders • Prompts DSL • Embeddings • Parsers • Vector Stores • Tools & Agents • Retrieval • Graph Runtime │ │ └────────────┬────────────────────┘ │ ⚙️ Foundation Layer • Core Runtime • State Management • Checkpointing Every module is independent. You only include what you need — a chat-only app doesn’t pull in the RAG or Agent modules. Design Decisions That Make It Mobile-Ready Three architectural choices set MobileGraph apart from server-side frameworks: 1. Capability-Based Abstraction, Not instanceof Checks // ❌ Coupled to a specific provider if (model is OpenAIChatModel) { /* use vision */ } // ✅ Query capabilities generically if (model.supports(Capability.Vision)) { /* use vision */ } 2. Deterministic Runtime, Probabilistic AI AI outputs are inherently unpredictable. But the framework that runs them must be deterministic. Given a state and a node, MobileGraph always produces predictable execution behavior. This makes workflows testable, replayable, and debuggable. 3. Flow<T> as the Universal Streaming Primitive No callbacks. No listeners. No RxJava. Every streaming operation uses Kotlin Flow<T>, giving you structured concurrency, cooperative cancellation, and seamless Compose integration for free. Getting Started 1. Add the Dependency repositories { mavenCentral() } 2. Initialize dependencies { implementation("io.github.mobilegraph:mobilegraph-sdk:0.5.0") implementation("io.ktor:ktor-client-okhttp:3.5.1") // HTTP engine } 3. Chat lifecycleScope.launch { MobileGraph.initialize { withModels { openai(apiKey = "sk-...") { isDefault = true } } } } val session = MobileGraph.instance.createSession() session.stream("Hello, MobileGraph!").collect { chunk -> print(chunk.text) } Requirements: Kotlin 2.0+, Gradle 8.4+, JDK 17+, Android Min SDK 24+. Try It Yourself MobileGraph is open source and available today. - 🌟 Star it on GitHub: user/MobileGraphSDK - 📦 Maven Central: io.github.mobilegraph:mobilegraph-sdk:0.5.0-alpha - 📖 Documentation: Full guides for setup, RAG, agents, tools, MCP, A2A and multi-model orchestration - 📱 Sample App: Clone the repo and run the :androidApp target — it includes demos for chat, RAG, tool agents, HITL, fan-out, A2A, MCP and hierarchical agents I’d love to hear your feedback. Your collboration for the project is well appreciated. What AI capabilities do you wish existed in your mobile app? Next up: a deep-dive into the architecture — how immutable state, checkpointing, and capability-based abstraction make AI workflows survive process death. Tags: Kotlin, Android, iOS, Artificial Intelligence, Mobile Development, Kotlin Multiplatform, LangChain, RAG, AI Agents, Open Source, MobileGraph

  9. X@bm_grey · 1 like · 34 views

    @XiaoshiroArt @fizz_a_rola @ManoImp AMiga eu traduzi sim, a traducao ta bem boa, segue o LINK LucianoNeo/pokemon-pokopia-pt-br

  10. DEV@abubakr_alsheikh · 1 reaction

    qtask: a task tracker my AI coding agents share, in one Python file I run several AI coding agents at once on the same project. One fixes a backend bug, one checks a screen in the browser, one writes tests. For a while I tracked their work in chat and in notes, and the same problems kept coming back: - Two agents picked up the same task and changed the same files. - An agent asked me something in the middle of a long session, I missed it, and it went ahead on a guess. - An agent said "done" with nothing to show for it. - When a session ended, what it learned ended with it. So I built qtask, a task tracker for agents and the person working with them. It is one Python file that uses only the standard library, and it keeps everything in one SQLite database on your machine. Repo: Abubakr-Alsheikh/qtask What a session looks like $ qtask add "Fix the login redirect" --kind bug --pri P1 Created APP-14: Fix the login redirect $ qtask claim APP-14 --agent fe-fix-1 Claimed APP-14 as fe-fix-1 until 2026-11-02T17:56:49Z. Status: in_progress. $ qtask ask APP-14 "Keep the old URL working?" --to developer --agent fe-fix-1 Question #1 on APP-14 sent to developer. Status: needs_confirm. $ qtask inbox --for developer #1 on APP-14 [question, open] fe-fix-1 to developer: Keep the old URL working? $ qtask answer 1 "Yes, redirect it" --agent developer Answer #2 added. Question #1 resolved. APP-14 status: in_progress. $ qtask done APP-14 --evidence "npm test: 412 passed" --agent fe-fix-1 Done APP-14. Four rules that fixed my problems 1. Claim before you work. claim gives the agent a lease, two hours by default. If another agent tries to claim the same task, it gets exit code 3 and picks something else. When the lease runs out, ready offers the task again, so a crashed session doesn't hold work forever. 2. Questions wait for the human. ask sends a question to developer and parks the task in needs_confirm. I answer when I get to it, with qtask inbox and qtask answer. The agent finds the answer in its own inbox, even in a new session. 3. No evidence, no done. done refuses without --evidence, which holds the commands the agent ran and what they printed. It also refuses while a question or a subtask is still open. 4. Findings live on the task. Agents write what they learn with qtask comment. A subagent gets a task ID instead of a long prompt, works on it, and hands back the ID. I read the whole story with qtask show. Why another tracker I looked at the existing ones first. Most needed a package install, a server or an account, and I wanted something I could read top to bottom before handing it to agents that run commands on my machine. qtask is about 2,000 lines in one file, with no dependencies. Two more choices came from how I work: - Tasks stay out of the repo. The database lives in ~/.qtask, so half-ideas and private notes never land in a commit. - It knows your project. The project comes from the git remote of the folder you are in, so every clone and worktree of a repo shares one list, and IDs get a short prefix from the repo name, like APP-14. Using it with your agents For Claude Code there is a skill in the repo that tells the agent when to load qtask and how to use it. For Codex, Cursor, Aider or Gemini CLI, the README has a short block to paste into your AGENTS.md or rules file. Any agent that can run a shell command can use qtask, and every command takes --json for output a program can read. Under the hood - SQLite in WAL mode. Every write runs in a BEGIN IMMEDIATE transaction, and a claim is one conditional UPDATE, so two agents can't both win. - The tests start 20 processes at the same moment to race for one claim, and only one may get it. - Full-text search with SQLite FTS5, with a plain LIKE fallback for builds without it. - A backup of the database and a JSONL export on the first write of each day. - It runs on Windows, Linux and macOS. I built it on Windows, so Git Bash path conversion and PowerShell quoting have their own tests. Try it Python 3.11 or newer and git 2.31 or newer: pipx install git+https://github.com/Abubakr-Alsheikh/qtask qtask --version It is version 0.1, so commands may still change before 1.0. Next on the roadmap: turning a local task into a GitHub issue, keeping the two in sync, and a read-only HTML board. If you run more than one agent at a time, I'd like to hear what breaks for you. Issues and pull requests are open.

  11. Need patched Prompt or just wanna improve your LLM routing? Prompt Evolution w/ statistical Rasch and PL1/PL2 model. Get it here here: promptpotter.com Or PromptPotter/prompt-potter-optimizer

  12. X@Lufe77Liya77 · 4 likes · 1 repost · 65 views

    DeepSeek is advancing autonomous AI. OAC already integrates with DeepSeek Harness, bringing persistent identity, memory and agent collaboration. The future isn't isolated AI agents. It's an open AI Internet where agents work together across platforms. openagentinternet/open-agent-connect

  13. X@saqibns · 32 views

    @davegoldblatt @karpathy Well, not @karpathy's version. But a much cheaper one. saqibns/cheap-hackertube

  14. @grok Nå når de er publisert på project2040/sragi-skills - hvordan vil du gjøre en ærlig vurdering av dette prosjektet? No hype!!

  15. X@yogsec · 1 like · 57 views

    900+ ethical hacking tools organized into 50+ categories like network, cloud, and malware analysis. Find your next go to tool here. GitHub Repo: yogsec/Hacking-Tools #Cybersecurity #EthicalHacking #PenTesting #InfoSec #RedTeam #BlueTeam #OSINT #SecurityTools

  16. X@EmreSokullu · 1 like · 88 views

    Another milestone; 200 forks at webbrain-one/webbrain 🥲

  17. X@x__elevate · 7 views

    Myth or Math: bookmarks and profile visits are super-signals. X's published code, as of commit 9106e9f (Oct 30, 2026), sets profile visits to 0 and leaves bookmarks out of the final score. Replies, quotes and shares carry the weight. Verdict: myth. github.com/xai-org/x-algorithm/blob/9106e9f33ee9c… t.co

  18. X@dorkitude · 2 likes · 59 views

    @nbaschez if we weren't busy, we might productize it. open sourced instead: endgame-labs/goated that, plus exe.dev (for sandboxes an their approach to secret management) makes for a really good combination

  19. X@KhalidDevLog · 10 likes · 365 views

    Introducing Toast, a new web component in PanelUI. The title changes through dither, with three effects: type, materialize, and timer. It supports promises, actions, and swipe to dismiss. Inspired by @leodev. panel-ui/PanelUI t.co

  20. X@imnilesh18_ · 12 views

    ✅ Day 718 – Max Cycle 🔄 🎯 Problem: Largest Sum Cycle 📂 GitHub: imnilesh18/GfG-POTD 🧠 Drop 0-indegree nodes, then sum max cycle. #geekstreak2026 #gfg360 #POTDwithGFG @geeksforgeeks #skillupwithgfg #nationskillup 📚 geeksforgeeks.org t.co

  21. Location: Columbus, OH (willing to relocate) Remote: Yes Willing to relocate: Yes Technologies: Elixir, Phoenix, LiveView, OTP/GenServer, Clojure, TypeScript, React, Next.js, Python, PostgreSQL, Ecto, Docker, AWS, CI/CD. Learning Rust. Résumé/CV: See GitHub projects. PDF available on request. Email: beerscb@gmail.com GitHub: github.com/caleb-bb LinkedIn: linkedin.com Availability: immediate, open to contract or full-time Mid-senior dev comfortable in Elixir + other functional stacks. Built BEAM-concurrency tooling for SOC analysts at a cybersecurity shop and full PETAL-stack apps (Phoenix/LiveView, Figma-to-deploy) as sole developer. Also production Next.js/TypeScript work for agency clients. Besides backend and full-stack, I'm open to the following: Data engineering: CAKE, my open-source (AGPL-3.0) RAG framework on Elixir/OTP, is mostly pipeline + LLM integration: ingestion, chunking, embedding, retrieval, Postgres, generation-with-citation. CAKE is to RAG frameworks as a game engine is to games. Also wrote Falcon, a Clojure scraping framework where each target site is a declarative EDN config. QA: Set up push/merge gates with linters, property testing, and other static analysis tools and integrate those into agent workflow. Deep work on property-based testing. My working theory is that tests and specs are the same thing. Have built agent contracts/harnesses to considerable engineering depth. Sales engineering / FDE: Demo’d my RAG framework to a water purification firm, greenlit by their Engineering Director and CFO. Did structured customer discovery through a startup accelerator. Can explain systems to non-engineers without making anyone feel stupid thanks to tutoring background. CAKE: Thoth-Software/cake Notice the push gates, the automatic checks, and agent contract in CLAUDE.md. Current project: is model transpilation from PyTorch to other frameworks: caleb-bb/tensorloom

  22. Location: Sacramento, CA, USA Remote: Yes Willing to relocate: Likely yes Technologies: Rust, Go, TypeScript, Python, C++, Standard ML; Lean 4, HOL4, Kani; GraalVM, Node.js internals; PostgreSQL; Docker, AWS, Cloudflare Workers Résumé/CV: alanwisper.com GitHub: github.com/wisper-dev X: x.com Email: hi.wisper [at] gmail [dot] com Software engineer focused on formal verification, security and encryption, as well as runtimes, backend and developer tools. Work on formal methods with Lean 4, HOL4 and Kani and contribute to these systems. My Rust project lethewis uses Kani to prove safety properties of encryption-key storage. Before that, at a U.S. startup, built Node.js API compatibility, web standards and database access for guest languages in a polyglot runtime on Rust and GraalVM. Led projects as part of regular team work. Looking for backend, systems, runtime, security or formal verification work at a startup.

  23. 3/ Built on Open WebUI, LiteLLM, Ollama and Postgres + pgvector. Benchmarked on a 4 GB laptop GPU. MIT licensed: razajahangir/inhouse-ai Need it set up for your team? DMs open.

  24. X@0xEikichi · 1 like · 32 views

    HairDeck: one image → animation-ready 3D anime hair GitHub: hyz317/HairDeck Apache 2.0. Hair only for now (no detailed textures yet). To run it yourself: Linux + NVIDIA GPU. 3D artists: would you use this as a starting point?

  25. Eight things happened in AI today; the one worth your attention is Re:Build. 💰 Re:Build 🚀 Gemini 4 Carbon 💰 Avante 🚀 Adobe 🌐 Mistral Large 4 🔐 FRONTIER Act 🛠️ Project Quarry 🌐 Deepgram Full post · Follow me: LinkedIn · GitHub · Bluesky · X · dev.to #AI #GenAI #AIEngineering

  26. Eight things happened in AI today; the one worth your attention is Re:Build. Here is the rundown. 💰 1. Re:Build: Re:Build reportedly closed a $2.1 billion funding round, ranking among the week’s largest deals (reported). shattered.io 🚀 2. Gemini 4 Carbon: Google announced Gemini 4 Carbon, saying it cuts task overreach by 26% and under‑service by 29% in multi‑step workflows (announced). aa.com.tr 💰 3. Avante: Avante reportedly secured a $30 million Series A round, bringing its total funding to $40 million, and plans to use the cash to expand internationally and add more AI agents after a beta launch last week (reported). geekwire.com 🚀 4. Adobe: Adobe announced a partnership with BWT Alpine Formula One Team to provide AI tools for fan engagement, custom digital content, data management and brand visibility tracking, starting in 2027 (announced). martech.org 🌐 5. Mistral Large 4: Mistral AI announced the open weights for its frontier model Mistral Large 4, nicknamed “Le Chonk,” which was initially released in preview three weeks ago (announced). siliconangle.com 🔐 6. FRONTIER Act: The bipartisan FRONTIER Act, aimed at mandating AI incident reporting, has stalled in Congress while states enact their own laws (reported). The article suggests the U.S. thediplomat.com 🛠️ 7. Project Quarry: Cisco has open‑sourced Project Quarry, a Python framework aimed at detecting threats and behavior patterns in agent conversations (announced). news.risky.biz 🌐 8. Deepgram: Deepgram announced it acquired Daily and said it will keep the Pipecat framework free under the BSD V2 license, invest in its development and set up an independent Pipecat Foundation (reported). unite.ai My read: Worth watching: whether Gemini 4 Carbon’s reported security‑benchmark gains translate into lower remediation cost for operators. Also watch if Cisco’s open‑source Project Quarry gains traction as a security‑tooling layer for AI agent deployments. 💾 Save this if you are tracking AI releases and funding. Daily AI digest, with a source link under every item. --- Originally shared on LinkedIn. An AI interview question every day, leadership for tech people and hands-on AI learning: - Follow me on LinkedIn for daily AI updates - Follow me on GitHub for the AI projects I build - Follow me on Bluesky for AI in short - Follow me on X for quick AI takes - Follow me on Dev.to for full AI articles - Visit my AI R&D lab website

  27. @bankrbot deploy token name Graph Protocol tickrr GRAPH ,on base thegraph.com github.com/graphprotocol youtube.com t.co

  28. X@Cloudtheboi · 41 views

    Xod 0.9.23 is live. Family Link is here: your machines link with a signed registry, share keys securely, and borrow AI from each other. Strangers refused. Plus Xod now validates its work and admits when it is blocked. Free, open source. Try it: CloudCorpRecords/xod

  29. Location: Bern region, Switzerland Remote: Yes (also open to hybrid in the Bern / Fribourg area) Willing to relocate: No Technologies: Vue 3, Nuxt 4, TypeScript, JavaScript, Tailwind CSS, HTML, CSS/SCSS, i18n (EN/DE/FR sites with hreflang), accessibility (WCAG AA), Core Web Vitals / SEO, Git. Some React. Résumé/CV: pavlinastavreva.ch Portfolio: pavlinastavreva.ch GitHub: github.com/polyastavreva Email: mail@pavlinastavreva.ch Front-end developer with 13 years of experience, mostly agency and product work for UK and European clients. I build fast, accessible, multilingual sites and dashboards with Vue and Nuxt. Open to full-time, part-time or freelance/contract front-end work, remote or in the Bern area. Available at short notice (one week). Languages: Bulgarian (native), English (working), German (A2).

  30. X@jqdsouza · 18 views

    @DavidZimingLiu Thanks David! Definitely try it out and let me know what you think (I'd be grateful for a ⭐️) : Asymptote-Labs/agent-beacon

  31. X@DYoung_AI · 129 views

    Your AI research brief needs the article, not the site's menus. Defuddle extracts clean Markdown: npx defuddle parse <article-url> --markdown Feed the output to your AI as source text for the brief. kepano/defuddle

  32. Redditu/spyboy70 · r/cachyos · 5 points · 1 comment

    Pacoloco is a local caching proxy server for pacman I have 8 PCs running CachyOS at home, and got tired of the pacman updates taking a while to download, so was looking for a way to cache the downloads like the old Steam gaming cache worked. Discovered anatol/pacoloco and it's exactly what I was looking for. I installed it in a Docker on my Unraid server (since that's on 24/7) and then added a pointer in /etc/pacman.conf on each machine, as the primary for each repo (leaving the regular one as secondary so if my server is off, it'll still update by going out to the internet instead). When a PC needs an update, it checks the local pacoloco instance to see if it's already there and uses that, otherwise pacoloco will go download the needed package and serve that back to the PC instead. It doesn't download everything, only what is requested, and caches that so you don't have hundreds of gigs of files you'll never use. It has prefetch as well, so you can set a cron to check and pull new releases on whatever schedule you want. It will expire those over time so if you remove a particular program from all machines, it will eventually remove it from the cache based on the ttl_unaccessed_in_days: variable. I set the cron job to grab updates daily at 4am so when I fire up my machines in the morning it's ready to go. (and it's pulling v3 and v4 stuff because of the mix of CPU architectures). While I do have a fast 2gigabit fiber connection, I rarely get that kind of speed when doing updates. Being able to hit the NAS at 2.5G or 10G (depending on the PC) makes updating incredibly fast when I'm doing local maintenance on my machines. My desktop is my daily driver, so I'm updating that all the time. The other machines are fired up as needed so they can be back a little bit on updates. My laptop is the biggest offender since it stays off for a few weeks at a time until I need to travel.

  33. Location: Rancho Cordova, CA (Pacific) Remote: Yes Willing to relocate: No Technologies: Python, TypeScript, Claude API, MCP, agent orchestration, evals / LLM-as-judge, FastAPI, PostgreSQL, React, Solidity/Foundry Résumé/CV: arc.dev Portfolio: automate-ai.live Email: contact@automate-ai.live AI engineer. I build agents and the checks around them. Recent: Open Counter, a shop sales agent the owner corrects in plain words and then watches obey, with MCP tools and PayPal checkout (chainwright/open-counter). Agent Grader, rubric-based evaluation of agent output (chainwright/agent-grader). MCP Guardrail, an MCP server tested with 50k adversarial requests (mini4ai4/mcp-guardrail). Open to contract or full-time.

  34. X@_MrNiko · 46 likes · 2 reposts · 1,928 views

    Zero click surface on iOS: Messages runs the JPEG XL decoder on a received .jxl. EXR stays a file icon. CVE-2026-28956. A .heic name does not help. ImageIO sniffs the magic bytes. The surface is proven. The 149 byte public trigger does not crash 26.4.2. eddinos2/CVE-2026-28956-jxl-messages-surface

  35. X@mattyklein_ · 1 like · 189 views

    @Kwisatz__ @grok how much would it cost to run a hyperliquid-dex/node non validating node on AWS ie. 16 vCPU 128 GB RAM 500 GB SSD

  36. You AI needs a security constitution. Using AI they found around 100 bugs in cloud providers github.com/KatTraxler/presentations/blob/main/sec…

  37. X@Trezor · 1 like · 73 views

    @FlowStayt Hi, we used to have groups like that but closed them due to scams. You can reach us here, on Reddit, or talk to the devs on GitHub, depending on your topic. We are always open to constructive feedback. Reddit: reddit.com GitHub: github.com/trezor

  38. X@dev_alli1 · 10 views

    Code: alameen-alli/zippy-eats-support-agent Start with server/src/agent/chat.ts. Here’s the whole request path on one page. t.co

  39. X@jamesaduncan · 7 views

    @jesserobbins @swardley I built this a while ago. Would love to swap notes! jamesaduncan/Wardley-map

  40. X@samzong · 11 views

    @alterxyz4 @keking99 可以继续指示, 加入 Lathe 大家庭~ lathe-cli/lathe

  41. Describe your tech stack in one sentence, and get a visual architecture diagram with official logos. #technology #artificialintelligence #news #opensource #ai

  42. Redditu/valentderah · r/decomps · 1,251 points · 380 comments

    Zelda TotK PC Recomp: Some Updates First of all, thank you. In the few days since the first post, more than 30 people have sent code to the project, over 50 pull requests were merged, and around 200 issues were reported and closed. Many of the fixes below come from your reports, thanks! GitHub: valentderah/totk-pc-recomp The new release is 0.3.4. To update, run the new installer on your existing install folder: it keeps your game files, saves and `totk.ini`. It's still a beta: crashes and visual bugs are expected. If you hit one, please open an issue on GitHub and attach `logs/totk.log`. A log turns a bug from guesswork into a fix. What was planned and is done now - Linux and Steam Deck. The port runs natively on Linux. The setup ships as an AppImage and builds the game from your files as on Windows. On a Deck it starts in fullscreen at 1280x800 (Linux 6.7+, glibc 2.34+, SteamOS 3 works). - Emulator mods. Unpack a mod into the `mods` folder and switch and order mods in the new Mods tab (F1). RomFS mods, TKMM merges and ExeFS code patches (`.ips`, `.pchtxt`) work. For code patches the game rebuilds itself in a minute or two. - Ultrawide and other ratios. 21:9 and 32:9 render at their own shape on 1.2.1 and 1.4.3: wider camera, HUD in the corners, markers over their targets. Also new - Atmosphère cheats, switched one by one in the Cheats tab - Amiibo: point the Amiibo tab at a folder of your own dumps - NVIDIA DLSS and DLAA on RTX GPUs (you need `nvngx_dlss.dll` from NVIDIA's DLSS SDK next to `totk.exe`) - HDR10 field of view (1.4.3), colour profiles, anisotropic filtering - The 1.1.0 update, besides 1.2.1 and 1.4.3 - CPUs without AVX2: any x86-64 CPU with SSE4.2 now works - Per-stick dead zones, camera speed, a walk key Bugs fixed - Lost saves. If an antivirus or cloud sync tool held a file in the save folder, saves could fail silently and the progress was gone at the next start. Fixed. - Flickering, blocky shadows. Set a fixed, higher Shadow map size in the Screen tab (F1) and they stop flickering. - Purah Pad camera recognised nothing on 1.2.1, so "Camera Work in the Depths" got stuck. Fixed. - Equipment locked after a Fuse until the next load. - Black 64-pixel squares on the ground, rainbow terrain on Intel, and objects that turned invisible above 63 fps. - Crash a few seconds after start (0xc0000409) on PCs where Windows exploit protection forces Control Flow Guard on. - AMD RX 6000 (RDNA 2): crashes and device lost at the Nintendo logo and at start, and above 1080p a garbage band at the top of the screen, a pink glow, blocks in the grass and a checkered menu. - AMD RX 400/500 (Polaris): rainbow and blocky terrain, black characters and black squares on the ground are fixed. Some reports of a dark or broken world on these cards are still open, so if you have one, please send a log. - Sound that stopped for good after a while, plus clicks and grainy reverb in caves. Requirements - Windows 10+ or Linux, any x86-64 CPU with SSE4.2 (AVX2 is faster) - Vulkan 1.3 GPU, 4 GB VRAM - 16 GB RAM - 36 GB free during setup, 20 GB after You still need your own dump of the game (base game plus the 1.1.0, 1.2.1 or 1.4.3 update) and your own keys. Nothing from the game is in the repo or the release. PS I took a week off from work to finish this port, so I'll try to release updates once a day.

  43. X@RezaShady · 16 views

    دادم با کلاد عزیز خیلی خفن ترش هم کردم تازه اوپن سورس هم هست ! هر زبان دیگه هم میشه روش ست کرد انیمیشن رو تغییر داد یا حتی جای عکس پرچم تکست نشون داد mr-shady.github.io mr-shady/language_flag_popup

  44. X@blooming_r91 · 20 views

    github.com/ra9hafaisal-blip

  45. X@MathOCPapers · 3 views

    RapidDOC: Riccati-Preconditioned Implicit Differentiation for Differentiable Optimal Control under Operator Mismatch Xiangda Zhu, Yuankun Chen, Zifei Nie, Yi Chang arxiv.org [𝚖𝚊𝚝𝚑.𝙾𝙲] 💬Code: opt-man/RapidDOC t.co

  46. Bluesky@karaman.is · 15 likes · 2 reposts

    Day 2 of #30DayMapChallenge, Lines. Every train that stops at Uppsala Central today, one strand per operator. South of Uppsala SL Pendeltåg runs 82 trains, Mälartåg 79 and SJ 70 Code: github.com/gkaramanis/30daysmapchallenge/tree/mai… #RStats #dataviz #maps

  47. Fix visibility issues in Windows high contrast (forced-colors) mode (diondiondion) mastodon#41455

  48. X@Kev96790724 · 1 like · 43 views

    we built this and its opensource download the stack kruschdev/krusch-stack

  49. X@_elbown · 42 views

    IME周りで何かはあるのか codex#32455

Older posts →