Mentions

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

Mentions by source

X

7,081
Nov 17, 16:00Nov 18, 16:00

Bluesky

2,235
Nov 17, 19:00Nov 18, 19:00
Nov 17, 18:00Nov 18, 18:00
Nov 17, 18:00Nov 18, 18:00
Nov 17, 19:00Nov 18, 19:00
Nov 17, 18:00Nov 18, 18:00
Nov 17, 18:00Nov 18, 18:00
Nov 17, 19:00Nov 18, 19:00
Oct 14, 21:00Oct 15, 21:00

Delayed · data through Oct 15, 21:00 UTC

DEV

832
Nov 17, 18:00Nov 18, 18:00
Nov 17, 19:00Nov 18, 19:00
Nov 16, 11:00Nov 17, 11:00

Delayed · data through Nov 17, 11:00 UTC

Nov 17, 19:00Nov 18, 19: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 17, 19:00Nov 18, 19:00

Latest posts

  1. X@gimbalabs · 5 likes · 2 reposts · 110 views

    Proposal alert! What's next after building a working product? This one proposes a Sustainability Hackathon to help builders develop business skills, find paying customers, and build recurring revenue. From working products to sustainable projects. github.com/gimbalabs/season7-2026/blob/proposal/s… #GimbalabsOpenGovernance

  2. X@PartyD0lphin · 17 likes · 5 reposts · 918 views

    Mac Monitor v3.0 is out! This release touches nearly every part of the app, and it's the also fastest yet. There are 13 new features, over 30 bug fixes, and quite a few quality of life updates. Excited to know what you think! github.com/Brandon7CC/mac-monitor/releases/tag/v3…

  3. X@nahime0 · 58 likes · 7 reposts · 2,263 views

    A PHP Hello World, compiled by elephc: one 791 KB static binary. 🐘 No PHP installed. No shared libraries: ldd says "not a dynamic executable". Compiles in ~115 ms, runs in 0.5 ms. Ship PHP as a single file. illegalstudio/elephc t.co

  4. Hacker Newsps3recomp · 2 points · snuri00/GoWA-pc

    PS3 static recomp God of War Ascension

  5. YouTubeGrow with Naman · YouTube description · 2 likes · 73 views

    18,629 Stars, 5 Repos Jo 10 Days Bhi Purane Nahi: Phone Ke Ads Band Karne Wala Bhi #Shorts Top 5 trending GitHub repos, Hindi mein - har number aaj check kiya gaya hai. Is week ke top trending repos, 26k+ stars combined: 1. heydamir/unslop (6k stars) - A Claude skill that turns vibecoded, AI-looking UI into a designed interface 2. wangzan101/Mika (5k stars) - An on-device AI agent for Android that operates apps and the web to get things done for you. 3. rddmwmddr/android-ad-cleaner (6k stars) - 关掉国产安卓手机系统里的广告、热搜、资讯推荐和营销推送。不 root,可还原,支持 AI 智能体一键执行。 4. interplains/Zero-Breach-Toolkit (4k stars) - Free, open-source check for traces of mercenary spyware (Pegasus, Predator, Graphite, Candiru and more) on computers, Android phones and iPhone backups. Double-click apps for Windows, Mac and Linux, in 27 languages. 5. ccch1mneyyy/dsh-Go (6k stars) - dsh-go — DeepSeek Harness 装进口袋:手机本机运行,也能遥控你的电脑。 Repo links: heydamir/unslop wangzan101/Mika rddmwmddr/android-ad-cleaner interplains/Zero-Breach-Toolkit ccch1mneyyy/dsh-Go Comment karo "DAYS" - saare links DM mein bhej dunga. Kisi dev dost ko bhejo jise ye chahiye. Save karlo, baad mein kaam aayega. Naman AI - AI aur dev tools, Hindi mein. Har din naya repo, har number verified. #Shorts #GitHub #AI #OpenSource #TechHindi [github trending repos, best github repositories 2026, top 5 github repos, open source projects for beginners, ai coding agents, github stars] [coding in hindi, tech shorts hindi, programming for beginners, developer tools 2026, ai tools for developers, learn coding free] [bn] ১৮,৬২৯ স্টারস, ৫টি রিপো যা ১০ দিনেরও পুরনো নয়: ফোনের বিজ্ঞাপন বন্ধ করার উপায়সহ #Shorts হিন্দিতে শীর্ষ ৫টি ট্রেন্ডিং গিটহাব রিপো - প্রতিটি নম্বর আজ চেক করা হয়েছে। এই সপ্তাহের শীর্ষ ট্রেন্ডিং রিপোগুলো, সম্মিলিতভাবে ২৬ হাজারেরও বেশি স্টার: ১. heydamir/unslop (৬ হাজার স্টার) - একটি ক্লড স্কিল যা ভাইবকোডেড, এআই-এর মতো দেখতে UI-কে একটি ডিজাইন করা ইন্টারফেসে পরিণত করে। ২. wangzan101/Mika (৫ হাজার স্টার) - অ্যান্ড্রয়েডের জন্য একটি অন-ডিভাইস এআই এজেন্ট যা আপনার হয়ে কাজ সম্পন্ন করার জন্য অ্যাপ এবং ওয়েব পরিচালনা করে। ৩. rddmwmddr/android-ad-cleaner (৬ হাজার স্টার) - দেশীয় অ্যান্ড্রয়েড ফোন সিস্টেমে বিজ্ঞাপন, ট্রেন্ডিং সার্চ, নিউজের সুপারিশ এবং মার্কেটিং পুশ বন্ধ করে। রুটের প্রয়োজন নেই, রিস্টোরযোগ্য, এআই ইন্টেলিজেন্ট এজেন্টদের দ্বারা এক-ক্লিকে এক্সিকিউশন সমর্থন করে। ৪. interplains/Zero-Breach-Toolkit (৪ হাজার স্টার) - কম্পিউটার, অ্যান্ড্রয়েড ফোন এবং আইফোন ব্যাকআপে ভাড়াটে স্পাইওয়্যারের (পেগাসাস, প্রিডেটর, গ্রাফাইট, ক্যান্ডিরু এবং আরও অনেক) চিহ্ন খুঁজে বের করার জন্য একটি বিনামূল্যের, ওপেন-সোর্স টুল। উইন্ডোজ, ম্যাক এবং লিনাক্সের জন্য ডাবল-ক্লিক অ্যাপ, যা ২৭টি ভাষায় উপলব্ধ। ৫. ccch1mneyyy/dsh-Go (৬ হাজার স্টার) - dsh-go — ডিপসিক হারনেস। পকেট-আকারের: এটি আপনার ফোনে সরাসরি চলে এবং দূর থেকে আপনার কম্পিউটারও নিয়ন্ত্রণ করতে পারে। রেপো লিঙ্ক: heydamir/unslop wangzan101/Mika rddmwmddr/android-ad-cleaner interplains/Zero-Breach-Toolkit ccch1mneyyy/dsh-Go মন্তব্য করুন "দিন" - সারা লিঙ্ক ডিএম মে ভেজ দুঙ্গা। কিসি দেব দোস্ত কো ভেজো জিসে ইয়ে চাহিয়ে। করলো বাঁচাও, বাদ মে কাম আয়েগা। নমন এআই - এআই অর দেব টুল, হিন্দি মে। হার দিন নয়া রেপো, হার নম্বর যাচাই করা হয়েছে। #শর্টস #গিটহাব #এআই #ওপেনসোর্স #টেকহিন্দি [গিটহাব ট্রেন্ডিং রিপো, সেরা গিটহাব রিপোজিটরি ২০২৬, সেরা ৫টি গিটহাব রিপো, নতুনদের জন্য ওপেন সোর্স প্রজেক্ট, এআই কোডিং এজেন্ট, গিটহাব স্টারস] [হিন্দিতে কোডিং, হিন্দি টেক শর্টস, নতুনদের জন্য প্রোগ্রামিং, ডেভেলপার টুলস ২০২৬, ডেভেলপারদের জন্য এআই টুলস, বিনামূল্যে কোডিং শিখুন] [en-US] 18,629 Stars, 5 Repos Less Than 10 Days Old: Including One to Block Phone Ads #Shorts Top 5 trending GitHub repos, Hindi mein - har number aaj check kiya gaya hai. Is this week's top trending repos, 26k+ stars combined: 1. heydamir/unslop (6k stars) - A Claude skill that turns vibecoded, AI-looking UI into a designed interface. 2. wangzan101/Mika (5k stars) - An on-device AI agent for Android that operates apps and the web to get things done for you. 3. rddmwmddr/android-ad-cleaner (6k stars) - Turns off ads, trending searches, news recommendations, and marketing pushes in domestic Android phone systems. No root required, restoreable, supports one-click execution by AI intelligent agents. 4. interplains/Zero-Breach-Toolkit (4k stars) - Free, open-source check for traces of mercenary spyware (Pegasus, Predator, Graphite, Candiru, and more) on computers, Android phones, and iPhone backups. Double-click apps for Windows, Mac, and Linux, in 27 languages. 5. ccch1mneyyy/dsh-Go (6k stars) - dsh-go — DeepSeek Harness. Pocket-sized: Runs natively on your phone and can also remotely control your computer. Repo links: heydamir/unslop wangzan101/Mika rddmwmddr/android-ad-cleaner interplains/Zero-Breach-Toolkit ccch1mneyyy/dsh-Go Comment karo "DAYS" - saare links DM mein bhej dunga. Kisi dev dost ko bhejo jise ye chahiye. Save karlo, baad mein kaam aayega. Naman AI - AI aur dev tools, Hindi mein. Har din naya repo, har number verified. #Shorts #GitHub #AI #OpenSource #TechHindi [github trending repos, best github repositories 2026, top 5 github repos, open source projects for beginners, ai coding agents, github stars] [coding in hindi, tech shorts hindi, programming for beginners, developer tools 2026, ai tools for developers, learn coding free]

  6. Frontier LLMs like DeepSeek V4.1 Flash and Kimi K3 with no login, no sign-up and no API key, right inside DeepSeek Harness. 🔗 Ebony-Vinyl/dsh-our-free-model Credits: Ebony-Vinyl/dsh-our-free-model #dshourfreemodel #javascript #deepseek

  7. X@BlockchainArta · 1 like · 4 views

    🚀 ArtaBlockchain × BitShares PTS We're proud to contribute to the revival of ProtoShares technology through open-source blockchain development. 🔗 PTS network: ptscrypto.com 💻 GitHub: github.com/artablok Building the next chapter together! 🌍 #ArtaBlockchain #PTS #Web3

  8. Redditu/No_Strength9197 · r/DigitalEscapeTools · 4 points · 2 comments

    NetCable update: initial SNMPv3 support, LLDP/CDP discovery and easier deployment Hi everyone! I’ve been working on a new update for NetCable, an open-source and self-hosted network mapping and monitoring tool built with React, FastAPI and React Flow. This update focuses on making NetCable more useful in real network environments. ### What’s new - Initial SNMPv3 support; - MD5/SHA authentication; - AES/DES privacy protocols; - Configurable SNMP port; - SNMP connection testing; - LLDP/CDP neighbor discovery through SNMP; - Per-device monitoring modes: - IP/ICMP + TCP; - SNMPv3; - Visual-only mode; - Encrypted SNMP credentials on the backend; - SNMP passwords excluded from JSON backups; - New diagnostics for the API, database and PySNMP; - More detailed connection and monitoring errors; - Same-origin API proxy configuration to avoid exposing backend ports to end users; - Compatibility with existing SQLite databases. The deployment experience was also improved. Users no longer need to manually configure or access the backend port in the browser. The frontend communicates through `/api`, while Vite and Nginx handle the internal routing. The LLDP/CDP functionality currently provides a preview of discovered neighbors. Automatic creation of devices and connections on the map is planned for a future update. I tested the new frontend build, login flow, project creation, device monitoring and SQLite persistence. SNMPv3 and LLDP/CDP still need validation with real switches and firewalls from different vendors. I’d really appreciate feedback from network engineers, homelab users and infrastructure enthusiasts: - Is SNMPv3 support enough for the first release? - Should SNMPv2c also be supported? - Which metrics would be most useful? - Should discovered LLDP/CDP neighbors be added automatically to the topology? - Which vendors or network devices should be tested next? GitHub: Joao-Monticelli/NetCable-v1 NetCable is still in beta, so feedback and bug reports are very welcome.

  9. YouTubeSelfhostLab · YouTube description · 2 likes · 108 views

    #WordCraft: #Open-Source Word #Editor Built in Pure Rust WordCraft is an open-source, clean-room reimplementation of Microsoft Word built in pure Rust. It reads and writes .docx plus .odt, .rtf, .html, .md, and .txt, and runs on macOS, Windows, Linux, BSD, and the web. GitHub: storytold/wordcraft Explore the project if you care about document editing in Rust. #WordCraft #OpenSource #Rust #DocumentEditing #WordProcessor #CrossPlatform #WebAssembly

  10. HiveGate 0.3.1 is the first release on PyPI: `uv tool install hivegate-ai`, then `hivegate init` and `hivegate serve`. It also ships per-call cost metering, Claude prompt caching and approvable team runs. github.com/hivegate-ai/hivegate/releases/tag/v0.3…

  11. YouTubeBproo Dev · YouTube description · 48 likes · 4 comments · 2,463 views

    Comment reproduire n'importe quel logiciel avec REA et Claude Code Et si une intelligence artificielle pouvait analyser un logiciel, comprendre comment il fonctionne et t'aider à recréer ses fonctionnalités sans avoir accès à son code source ? C'est exactement ce que nous allons explorer dans cette vidéo avec **REA (Reverse Engineer Anything) **, un projet open source qui permet de connecter des outils de rétro-ingénierie à des assistants IA comme Claude Code. Grâce à REA, Ghidra et au protocole MCP, nous allons découvrir comment l'intelligence artificielle peut examiner des applications, analyser des fichiers exécutables, comprendre certaines architectures logicielles et accompagner les développeurs dans la création de nouvelles fonctionnalités. Imagine pouvoir étudier le fonctionnement d'un logiciel comme WhatsApp, Photoshop, Netflix ou CapCut, comprendre ses mécanismes et utiliser ces connaissances pour développer tes propres applications. Ce n'est plus seulement une question de génération de code. C'est une nouvelle manière d'aborder le développement logiciel. 🚀 DANS CETTE VIDÉO, TU VAS DÉCOUVRIR: 00:00 Introduction 01:16 Le problème des logiciels propriétaires 03:18 REA, c'est quoi? 05:24 Installer REA avec Claude Code 06:25 Ghidra : décoder les logiciels compilés 08:21 Analyser un vrai logiciel 09:04 Comprendre et reconstruire 10:27 Pourquoi c'est une évolution importante 11:58 Les limites à connaître 13:22 Conclusion Rejoins notre communauté WhatsApp: 👉 [bit.ly] 🛠️ **LES OUTILS PRÉSENTÉS :** - REA : morluto/rea - Ghidra : NationalSecurityAgency/ghidra - Claude Code : code.claude.com ⚠️ IMPORTANT : La rétro-ingénierie doit être pratiquée dans le respect des licences, des droits d'auteur et des protections applicables. Comprendre le fonctionnement d'un logiciel ne donne pas automatiquement le droit de copier son code ou ses ressources propriétaires. 💬 **QUESTION DU JOUR :** Si tu pouvais analyser le fonctionnement d'un logiciel et comprendre comment il a été construit, lequel choisirais-tu ? WhatsApp, Photoshop, Netflix, CapCut ou un autre logiciel ? Dis-moi en commentaire ! 👍 Pense à aimer la vidéo et à t'abonner à Bproo Dev pour découvrir comment exploiter l'intelligence artificielle, l'automatisation et les technologies numériques pour créer tes propres solutions. #IntelligenceArtificielle #ClaudeCode #ReverseEngineering #REA #DeveloppementLogiciel #IA [en-US] How to Reproduce Any Software with REA and Claude Code What if artificial intelligence could analyze software, understand how it works, and help you recreate its functionality without needing access to its source code? That's exactly what we'll explore in this video with **REA (Reverse Engineer Anything)**, an open-source project that connects reverse engineering tools to AI assistants like Claude Code. Thanks to REA, Ghidra, and the MCP protocol, we'll discover how artificial intelligence can examine applications, analyze executable files, understand certain software architectures, and guide developers in creating new features. Imagine being able to study how software like WhatsApp, Photoshop, Netflix, or CapCut works, understand its mechanisms, and use that knowledge to develop your own applications. It's no longer just about code generation. It's a whole new way of approaching software development. 🚀 IN THIS VIDEO, YOU WILL DISCOVER: 00:00 Introduction 01:16 The problem with proprietary software 03:18 What is REA? 05:24 Installing REA with Claude Code 06:25 Ghidra: Decoding Compiled Software 08:21 Analyzing Real Software 09:04 Understanding and Rebuilding 10:27 Why This Is an Important Evolution 11:58 Limitations to Be Aware Of 13:22 Conclusion Join our WhatsApp community: 👉 [bit.ly] 🛠️ **TOOLS PRESENTED:** - REA: morluto/rea - Ghidra: NationalSecurityAgency/ghidra - Claude Code: code.claude.com ⚠️ IMPORTANT: Reverse engineering must be practiced in compliance with applicable licenses, copyrights, and protections. Understanding how a piece of software works doesn't automatically give you the right to copy its code or proprietary resources. 💬 **QUESTION OF THE DAY:** If you could analyze how a piece of software works and understand how it was built, which one would you choose? WhatsApp, Photoshop, Netflix, CapCut, or another piece of software? Tell me in the comments! 👍 Remember to like the video and subscribe to Bproo Dev to discover how to leverage artificial intelligence, automation, and digital technologies to create your own solutions. #ArtificialIntelligence #ClaudeCode #ReverseEngineering #REA #SoftwareDevelopment #AI

  12. X@javiolmo · 2 likes · 117 views

    Plugins o apps kanban para flujos agénticos y gestionar agentes como tareas- equipo. Kandev ya pintaba interesante y le han añadido "office" (clon de paperclip) que aunque está en beta, funciona bien lo básico. Ya funcionando en demo real para cliente. kdlbs/kandev

  13. X@joshmedeski · 1 like · 113 views

    I can't with this sesh rex tool name rtuszik/sex

  14. YouTubeLuciano Mattica · YouTube description · 326 likes · 2 comments · 12,131 views

    Claude + MiroFish: el repo de GitHub que predice lo que sea El repositorio es MiroFish: 666ghj/MiroFish MiroFish es un repositorio de GitHub que lanza miles de agentes de IA para analizar tu idea, tu lanzamiento o tu producto y decirte qué tiene más chances de funcionar. Soy Luciano Mattica y enseño a las personas a convertirse en expertas en inteligencia artificial y en Claude. Mi comunidad, donde enseño todo esto paso a paso: skool.com [en-US] Claude + MiroFish: The GitHub Repo That Predicts Anything MiroFish is a GitHub repository that launches thousands of AI agents to analyze your idea, your pitch, or your product and tell you what has the best chance of succeeding. I'm Luciano Mattica, and I teach people how to become experts in artificial intelligence and Claude. My community, where I teach all this step by step: skool.com

  15. YouTubeAlex Hitt · YouTube description · 2 likes · 229 views

    FastMCP GitHub Explained: How Python Tools Become MCP Endpoints fastmcp by PrefectHQ: PrefectHQ/fastmcp FastMCP is a Python framework for translating ordinary functions into Model Context Protocol endpoints. This overview follows the path from MCP's JSON-RPC 2.0 boundary to a local synthetic tool: how the @mcp.tool decorator uses Python annotations and docstrings to build input schemas, dereferences nested references for client compatibility, and wraps scalar outputs into structured objects with text compatibility. It also maps the engineering trade-offs around variadic parameters, CPU-bound synchronous work, STDIO framing, and process isolation, then places standalone FastMCP in context with the official Python SDK. The closing section covers deterministic offline validation of schemas, input coercion, and error handling before external model access, using synthetic inputs rather than credentials or third-party data. TimeStamps: 0:00 MCP and the boundary between models and local computation 0:32 Why raw protocol implementations require careful schema and transport handling 1:27 FastMCP as a Python-to-MCP abstraction layer 2:14 Decorators, type hints, and automatic input schema generation 3:11 Schema dereferencing for client compatibility 3:54 Wrapping scalar outputs into structured MCP results 4:50 Operational trade-offs: parameters, concurrency, and STDIO 5:20 STDIO framing and process isolation 6:10 FastMCP lineage and the official Python SDK 6:53 Choosing abstraction versus wire-level control 7:13 Offline validation with synthetic inputs 7:53 What a local FastMCP execution model establishes 🧠 MCP connects model context with local computation 🧩 Python annotations become JSON Schema 🔁 Nested references and scalar results are normalized 🛠️ STDIO and offline validation define key trade-offs FastMCP's appeal is the boundary it abstracts: Python functions remain concise while schema generation, result wrapping, and protocol framing become explicit system behavior. The trade-off is less direct wire-level control and continued responsibility for concurrency, STDIO isolation, and offline validation. Those details define where the framework fits in a local MCP architecture. #FastMCP #MCP #Python [de-DE] YNAS ynp_197250816f484002 Cinematic Privater automatisierter Staging-Upload. Paketidentität: ynp_197250816f484002; Ausgabe: cinematic. [es-US] YNAS ynp_197250816f484002 cinemático Carga de prueba de automatización privada. Identidad del paquete: ynp_197250816f484002; salida: cinematográfica. [fr-FR] YNAS ynp_197250816f484002 cinématique Téléchargement de l'environnement de test d'automatisation privé. Identifiant du package : ynp_197250816f484002 ; sortie : cinématique. [hi] YNAS ynp_197250816f484002 सिनेमैटिक निजी स्वचालन स्टेजिंग अपलोड। पैकेज पहचान: ynp_197250816f484002; आउटपुट: सिनेमाई। [id] YNAS ynp_197250816f484002 sinematik Unggahan staging otomatisasi pribadi. Identitas paket: ynp_197250816f484002; output: sinematik. [it] YNAS ynp_197250816f484002 cinematic Caricamento di automazione privata. Identità del pacchetto: ynp_197250816f484002; output: cinematico. [pt-BR] YNAS ynp_197250816f484002 cinemático Upload de teste de automação privada. Identificação do pacote: ynp_197250816f484002; saída: cinemática.

  16. YouTubeNehra Classes · YouTube description · 26 likes · 2 comments

    Git & GitHub Master Course | Session - 11 | Git Branching Practical | Manage Multiple Branches Git & GitHub Master Course | Session - 11 | Git Branching Practical | Manage Multiple Branches Welcome to Session 11 of the Git & GitHub Master Course! In this session, we will explore Git Branching through a comprehensive, hands-on practical lab. You will learn how developers and DevOps engineers use multiple branches to work on different features independently without disturbing the stable version of an application. *** 📚 Nehra Classes - Igniting The Minds! 📚 About Us: Nehra Classes is a premier IT training institute dedicated to empowering individuals with the skills and knowledge they need to succeed in today's competitive technology landscape. Founded by Vikas Nehra, a seasoned IT professional, our institute has been at the forefront of providing quality training solutions for over 10 years. *** 🕒 Timestamps: 00:00:00 - Channel Intro 00:00:20 - Session Overview 00:01:10 - Real-World Scenario: Parallel Development & Isolation 00:02:35 - Setting Up Project Directory & Initializing Git (git init) 00:03:32 - Renaming Master Branch to Main 00:04:03 - Creating Initial Project Files (README.md & app.txt) 00:05:07 - Staging & Creating Initial Commit (git commit) 00:06:08 - Creating & Switching to Feature Branch (git switch -c feature-login) 00:07:00 - Adding login.txt on Feature Branch 00:08:00 - Staging & Committing login.txt (git commit) 00:09:23 - Verifying Branch Isolation (Switching Back to Main) 00:11:53 - Creating & Developing Dashboard Branch (feature-dashboard) 00:12:44 - Adding & Committing dashboard.txt 00:15:06 - Switching Between Feature Branches (feature-dashboard to feature-login) 00:16:44 - Making a Second Commit on Feature Branch 00:18:25 - Returning to Main & Verifying Main History 00:19:15 - Renaming an Existing Branch (git branch -m) 00:20:07 - Safely Deleting a Branch & Unmerged Warning (git branch -d) 00:22:05 - Force Deleting an Unmerged Branch (git branch -D) 00:22:35 - Advanced Practical: Managing Uncommitted Changes While Switching 00:24:00 - Creating New Branch With Uncommitted Modifications 00:25:40 - Committing Changes on New Branch 00:26:58 - Verifying Isolation on Main After Branch Commit 00:28:38 - Branch Visualization & History (git log --graph --all) 00:29:38 - Multi-Branching Lab Workflow Summary 00:31:05 - Practice Exercises, Interview Questions & Answers 00:32:15 - Key Takeaways & Outro *** 🔗 Important Links: Join Our YouTube Membership: youtube.com Visit Our Website: nehraclasses.in Visit Our Courses Portal: nehraclasses.com Access Our Learning Portal: web.nehraclasses.com Download Our Nehra Classes App: clpted.page.link Android App: play.google.com iOS App (OrgCode: ljeizx): apps.apple.com Mail Us: nehraclasses@gmail.com *** For updates and offers follow us on Social Media: YouTube: youtube.com LinkedIn Page: linkedin.com Telegram Channel: t.me Telegram Discussion Group: t.me WhatsApp Channel: whatsapp.com Facebook Page: facebook.com Instagram: instagram.com X Handle: x.com Github Profile: github.com/nehraclasses Blog: nehraclassesyoutube.blogspot.com *** 📢 Stay Updated: Don’t forget to Subscribe and Hit the Bell Icon to stay notified about our latest videos, live sessions, and special offers. Like, Share, and Comment on our videos to let us know how we’re doing and what you’d like to see next! *** 🎓 Join the Nehra Classes Community: We’re more than just a channel; we’re a community of learners and educators. By joining our YouTube Membership and following us on social media, you gain access to exclusive content, live Q&A sessions, and a network of like-minded individuals. Let’s achieve your learning goals together! *** 🚀 Special Offers: Check out our current promotions, discounts, and free trials on our website and learning portal. Take advantage of these opportunities to start learning with us today! *** Thank you for being a part of Nehra Classes. Your success is our priority! *** Disclaimer: COPYRIGHT © Nehra Classes®. ALL RIGHTS RESERVED. All content, including but not limited to text, images, graphics, videos, course materials, and other digital assets available on Nehra Classes' platforms, is the exclusive property of Nehra Classes and is protected under international copyright laws. *** #NehraClasses #Git #GitHub #GitBranching #GitTutorial #DevOps #GitCommands #GitBranch #VersionControl #NehraClasses #GitAndGitHub [bn] Git & GitHub মাস্টার কোর্স | সেশন - ১১ | গিট ব্রাঞ্চিং প্র্যাকটিক্যাল | মাল্টিপল ব্রাঞ্চ ম্যানেজম... গিট ও গিটহাব মাস্টার কোর্স | সেশন - ১১ | গিট ব্রাঞ্চিং প্র্যাকটিক্যাল | একাধিক ব্রাঞ্চ পরিচালনা গিট ও গিটহাব মাস্টার কোর্সের ১১তম সেশনে আপনাকে স্বাগতম! এই সেশনে, আমরা একটি বিস্তারিত, হাতে-কলমে ব্যবহারিক ল্যাবের মাধ্যমে গিট ব্রাঞ্চিং সম্পর্কে জানব। আপনি শিখবেন কীভাবে ডেভেলপার এবং ডেভঅপস ইঞ্জিনিয়াররা একটি অ্যাপ্লিকেশনের স্থিতিশীল সংস্করণকে প্রভাবিত না করে বিভিন্ন ফিচারে স্বাধীনভাবে কাজ করার জন্য একাধিক ব্রাঞ্চ ব্যবহার করেন। *** 📚 নেহরা ক্লাসেস - মনকে প্রজ্বলিত করুন! 📚 আমাদের সম্পর্কে: নেহরা ক্লাসেস একটি শীর্ষস্থানীয় আইটি প্রশিক্ষণ প্রতিষ্ঠান, যা আজকের প্রতিযোগিতামূলক প্রযুক্তি জগতে সফল হওয়ার জন্য প্রয়োজনীয় দক্ষতা ও জ্ঞান দিয়ে ব্যক্তিদের ক্ষমতায়নে নিবেদিত। একজন অভিজ্ঞ আইটি পেশাদার বিকাশ নেহরা দ্বারা প্রতিষ্ঠিত, আমাদের প্রতিষ্ঠানটি ১০ বছরেরও বেশি সময় ধরে মানসম্মত প্রশিক্ষণ সমাধান প্রদানে অগ্রণী ভূমিকা পালন করে আসছে। *** 🕒 টাইমস্ট্যাম্প: ০০:০০:০০ - চ্যানেল পরিচিতি ০০:০০:২০ - সেশনের সংক্ষিপ্ত বিবরণ ০০:০১:১০ - বাস্তব পরিস্থিতি: সমান্তরাল উন্নয়ন এবং আইসোলেশন ০০:০২:৩৫ - প্রজেক্ট ডিরেক্টরি সেট আপ করা এবং গিট ইনিশিয়ালাইজ করা (git init) ০০:০৩:৩২ - মাস্টার ব্রাঞ্চের নাম পরিবর্তন করে মেইন রাখা ০০:০৪:০৩ - প্রজেক্টের প্রাথমিক ফাইল তৈরি করা (README.md এবং app.txt) ০০:০৫:০৭ - স্টেজিং এবং প্রাথমিক কমিট তৈরি করা (git commit) ০০:০৬:০৮ - ফিচার ব্রাঞ্চ তৈরি করা এবং তাতে সুইচ করা (git switch -c feature-login) ০০:০৭:০০ - ফিচার ব্রাঞ্চে login.txt যোগ করা ০০:০৮:০০ - স্টেজিং এবং login.txt কমিট করা (git commit) ০০:০৯:২৩ - ব্রাঞ্চ আইসোলেশন যাচাই করা (ফিচার ব্রাঞ্চে ফিরে যাওয়া) মেইন) ০০:১১:৫৩ - ড্যাশবোর্ড ব্রাঞ্চ তৈরি ও উন্নত করা (ফিচার-ড্যাশবোর্ড) ০০:১২:৪৪ - dashboard.txt যোগ করা ও কমিট করা ০০:১৫:০৬ - ফিচার ব্রাঞ্চগুলোর মধ্যে পরিবর্তন করা (ফিচার-ড্যাশবোর্ড থেকে ফিচার-লগইন) ০০:১৬:৪৪ - ফিচার ব্রাঞ্চে দ্বিতীয় কমিট করা ০০:১৮:২৫ - মেইনে ফিরে আসা এবং মেইনের ইতিহাস যাচাই করা ০০:১৯:১৫ - বিদ্যমান ব্রাঞ্চের নাম পরিবর্তন করা (git branch -m) ০০:২০:০৭ - নিরাপদে একটি ব্রাঞ্চ মুছে ফেলা এবং আনমার্জড সতর্কতা (git branch -d) ০০:২২:০৫ - একটি আনমার্জড ব্রাঞ্চ জোর করে মুছে ফেলা (git branch -D) ০০:২২:৩৫ - উন্নত অনুশীলন: পরিবর্তন করার সময় আনকমিটেড পরিবর্তনগুলো পরিচালনা করা ০০:২৪:০০ - আনকমিটেড পরিবর্তনসহ নতুন ব্রাঞ্চ তৈরি করা ০০:২৫:৪০ - কমিট করা নতুন ব্রাঞ্চে পরিবর্তন ০০:২৬:৫৮ - ব্রাঞ্চ কমিটের পর মেইন-এ আইসোলেশন যাচাই করা ০০:২৮:৩৮ - ব্রাঞ্চ ভিজ্যুয়ালাইজেশন ও হিস্ট্রি (git log --graph --all) ০০:২৯:৩৮ - মাল্টি-ব্রাঞ্চিং ল্যাব ওয়ার্কফ্লো সারাংশ ০০:৩১:০৫ - অনুশীলনমূলক প্রশ্ন, ইন্টারভিউ প্রশ্ন ও উত্তর ০০:৩২:১৫ - মূল শিক্ষা ও উপসংহার *** 🔗 গুরুত্বপূর্ণ লিঙ্ক: আমাদের ইউটিউব মেম্বারশিপে যোগ দিন: youtube.com আমাদের ওয়েবসাইট দেখুন: nehraclasses.in আমাদের কোর্স পোর্টাল দেখুন: nehraclasses.com আমাদের লার্নিং পোর্টালে প্রবেশ করুন: web.nehraclasses.com আমাদের নেহরা ক্লাসেস অ্যাপ ডাউনলোড করুন: clpted.page.link অ্যান্ড্রয়েড অ্যাপ: play.google.com আইওএস অ্যাপ (অর্গকোড: ljeizx): apps.apple.com আমাদের ইমেল করুন: nehraclasses@gmail.com *** আপডেট এবং অফার পেতে সোশ্যাল মিডিয়ায় আমাদের অনুসরণ করুন: ইউটিউব: youtube.com লিঙ্কডইন পেজ: linkedin.com টেলিগ্রাম চ্যানেল: t.me টেলিগ্রাম আলোচনা গ্রুপ: t.me হোয়াটসঅ্যাপ চ্যানেল: whatsapp.com ফেসবুক পেজ: facebook.com ইনস্টাগ্রাম: instagram.com এক্স হ্যান্ডেল: x.com গিটহাব প্রোফাইল: github.com/nehraclasses ব্লগ: nehraclassesyoutube.blogspot.com *** 📢 আপডেট থাকুন: আমাদের নতুন ভিডিও, লাইভ সেশন এবং বিশেষ অফার সম্পর্কে জানতে সাবস্ক্রাইব করতে এবং বেল আইকনটি চাপতে ভুলবেন না। আমরা কেমন করছি এবং পরবর্তীতে আপনারা কী দেখতে চান, তা জানাতে আমাদের ভিডিওগুলোতে লাইক, শেয়ার এবং কমেন্ট করুন! *** 🎓 নেহরা ক্লাসেস কমিউনিটিতে যোগ দিন: আমরা শুধু একটি চ্যানেল নই; আমরা শিক্ষার্থী এবং শিক্ষকদের একটি কমিউনিটি। আমাদের ইউটিউব মেম্বারশিপে যোগ দিয়ে এবং সোশ্যাল মিডিয়ায় আমাদের অনুসরণ করে, আপনি এক্সক্লুসিভ কন্টেন্ট, লাইভ প্রশ্নোত্তর সেশন এবং সমমনা ব্যক্তিদের একটি নেটওয়ার্কের অ্যাক্সেস পাবেন। আসুন, একসাথে আপনার শেখার লক্ষ্যগুলো অর্জন করি! *** 🚀 বিশেষ অফার: আমাদের ওয়েবসাইট এবং লার্নিং পোর্টালে চলমান প্রোমোশন, ডিসকাউন্ট এবং ফ্রি ট্রায়ালগুলো দেখুন। আজই আমাদের সাথে শেখা শুরু করতে এই সুযোগগুলো কাজে লাগান! *** নেহরা ক্লাসেস-এর অংশ হওয়ার জন্য আপনাকে ধন্যবাদ। আপনার সাফল্যই আমাদের অগ্রাধিকার! *** দাবিত্যাগ: কপিরাইট © নেহরা ক্লাসেস®। সর্বস্বত্ব সংরক্ষিত। নেহরা ক্লাসেস-এর প্ল্যাটফর্মে উপলব্ধ টেক্সট, ছবি, গ্রাফিক্স, ভিডিও, কোর্স উপকরণ এবং অন্যান্য ডিজিটাল সম্পদ সহ সমস্ত বিষয়বস্তু নেহরা ক্লাসেস-এর একচেটিয়া সম্পত্তি এবং আন্তর্জাতিক কপিরাইট আইন দ্বারা সুরক্ষিত। *** #NehraClasses #Git #GitHub #GitBranching #GitTutorial #DevOps #GitCommands #GitBranch #VersionControl #NehraClasses #GitAndGitHub

  17. X@m0nle0z · 3 likes · 18 views

    @Tiny_Fish official pages: tinyfish.ai devin.ai livekit.com deepgram.com kiro.dev full list with official links: doanbactam/awesome-builder-programs

  18. X@danielsspo · 1 like · 4 views

    The first thing I would check Define a short task with a verifiable result and monitor the decisions and tool calls. mayukh4/jansky

  19. X@NicolaSpieser · 1 like · 6 views

    📈 Paper trading Bitcoin on live Binance data, no real money at risk. Python bot using EMA crossover, RSI, MACD and Bollinger Bands, with stop loss, trailing stop, restart-safe state and win-rate/drawdown tracking. #Python quantumnic/trading-bot t.co

  20. YouTubeKris Kasprzak · YouTube description · 7 likes · 503 views

    Stockfish Chess on a Teensy 4.0 I ported Stockfish, the legendary open-source chess engine, to a $24 Teensy 4.0 microcontroller with a 2.8" touch screen, and now I can't beat my own project. ♟️🔥 Everything runs on the Teensy's 600 MHz ARM Cortex-M7: no PC, Just pick a piece, tap where it goes, and TeensyFish (my Stockfish port) answers within seconds. 🧠 HOW DOES STOCKFISH FIT ON A MICROCONTROLLER? Modern Stockfish uses an NNUE neural network that is tens of megabytes, but the Teensy has only 2 MB of flash and 1 MB of RAM. So TeensyFish keeps Stockfish's modern search, move generation and transposition table, and swaps the neural network for the handcrafted evaluation from Stockfish 11. Huge lookup tables were replaced with compact bit tricks, and the memory was squeezed into both RAM banks. It's still strong enough to crush most club players at full strength. Did I figure this out? Sure not, but Claude Code and Opus 5.5 did. ✨ FEATURES ♟️ 21 difficulty levels, from beginner to full strength ♟️ Play as white or black (the board flips) ♟️ Touch to move, with legal-move dots and last-move highlights ♟️ HINT button: the engine suggests your best move ♟️ UNDO and NEW GAME buttons ♟️ Material score and live evaluation bar ♟️ Checkmate, stalemate and draw detection, plus pawn promotion ♟️ Buzzer clicks on every move, and a warning beep on illegal moves ♟️ Touch calibration saved in EEPROM 🛠️ HARDWARE • Teensy 4.0 (600 MHz ARM Cortex-M7, 1 MB RAM, 2 MB flash) • 2.8" ILI9341 320×240 SPI TFT with XPT2046 touch • Passive buzzer • A few jumper wires 💾 SOURCE CODE, WIRING AND BUILD INSTRUCTIONS KrisKasprzak/TeensyChess Free and open source under the GPLv3, like Stockfish itself. 🙏 CREDITS Stockfish by the Stockfish developers: stockfishchess.org Teensy and the display/touch libraries by Paul Stoffregen / PJRC: pjrc.com TeensyFish is an unofficial port and is not affiliated with the Stockfish project. 👍 If you liked this, subscribe for more microcontroller projects, and tell me in the comments: could YOU beat TeensyFish at level 20? #Stockfish #Teensy #Chess #Arduino #Microcontroller #DIY #ChessEngine #Electronics [ar] لعبة شطرنج Stockfish على لوحة Teensy 4.0 قمتُ بنقل برنامج ستوكفيش، محرك الشطرنج الأسطوري مفتوح المصدر، إلى متحكم دقيق Teensy 4.0 بسعر 24 دولارًا فقط، مزود بشاشة لمس 2.8 بوصة، والآن لا يُضاهى مشروعي! ♟️🔥 يعمل كل شيء على معالج ARM Cortex-M7 بسرعة 600 ميجاهرتز في Teensy: لا حاجة لجهاز كمبيوتر، فقط اختر قطعة، وانقر على مكانها، وسيجيب TeensyFish (نسختي من ستوكفيش) في غضون ثوانٍ. 🧠 كيف يُمكن تشغيل ستوكفيش على متحكم دقيق؟ يستخدم ستوكفيش الحديث شبكة عصبية NNUE بحجم عشرات الميغابايت، لكن Teensy لا يملك سوى 2 ميغابايت من ذاكرة الفلاش و1 ميغابايت من ذاكرة الوصول العشوائي. لذلك، يحتفظ TeensyFish بجداول البحث الحديثة، وتوليد النقلات، والتبديل الخاصة بستوكفيش، ويستبدل الشبكة العصبية بالتقييم المُصمم يدويًا من ستوكفيش 11. تم استبدال جداول البحث الضخمة بتقنيات بتية مُدمجة، وتم ضغط الذاكرة إلى كلا بنكي ذاكرة الوصول العشوائي (RAM). لا يزال قويًا بما يكفي لسحق معظم لاعبي الأندية بكامل قوتهم. هل اكتشفتُ هذا؟ بالطبع لا، لكن كلود كود وأوبوس 5.5 اكتشفاه. ✨ المميزات ♟️ 21 مستوى صعوبة، من المبتدئ إلى المحترف ♟️ اللعب بالأبيض أو الأسود (يتم قلب الرقعة) ♟️ اللمس للتحريك، مع نقاط للحركات القانونية وتظليل للحركة الأخيرة ♟️ زر التلميح: يقترح المحرك أفضل حركة لك ♟️ زرا التراجع وبدء لعبة جديدة ♟️ نقاط القطع وشريط التقييم المباشر ♟️ كشف كش ملك، وتعادل، وتعادل، بالإضافة إلى ترقية البيدق ♟️ نقرة جرس مع كل حركة، وصفارة تحذيرية للحركات غير القانونية ♟️ معايرة اللمس محفوظة في ذاكرة EEPROM 🛠️ المكونات المادية • Teensy 4.0 (معالج ARM Cortex-M7 بسرعة 600 ميجاهرتز، ذاكرة وصول عشوائي 1 ميجابايت، ذاكرة فلاش 2 ميجابايت) • شاشة TFT مقاس 2.8 بوصة من نوع ILI9341 بدقة 320×240 بكسل، تدعم واجهة SPI، مزودة بمعالج لمس XPT2046 • جرس تنبيه سلبي • بعض أسلاك التوصيل 💾 شفرة المصدر، تعليمات التوصيل والبناء KrisKasprzak/TeensyChess برنامج مجاني ومفتوح المصدر بموجب رخصة GPLv3، تمامًا مثل برنامج Stockfish. 🙏 شكر وتقدير Stockfish من مطوري Stockfish: stockfishchess.org Teensy ومكتبات العرض/اللمس من Paul Stoffregen / PJRC: pjrc.com TeensyFish هو إصدار غير رسمي من برنامج Stockfish، ولا يتبع له. 👍 إذا أعجبك هذا، اشترك للمزيد من مشاريع المتحكمات الدقيقة، وأخبرني في التعليقات: هل يمكنك التغلب على TeensyFish في المستوى 20؟ سمك القد المجفف تينسي الشطرنج أردوينو متحكم دقيق اصنعها بنفسك محرك الشطرنج إلكترونيات [bn] Teensy 4.0-এ স্টকফিশ চেস আমি কিংবদন্তীসম ওপেন-সোর্স দাবা ইঞ্জিন স্টকফিশকে একটি ২.৮" টাচ স্ক্রিনসহ ২৪ ডলারের টিনসি ৪.০ মাইক্রোকন্ট্রোলারে পোর্ট করেছি, এবং এখন আমি আমার নিজের প্রজেক্টকেই হারাতে পারছি না। ♟️🔥 সবকিছু টিনসির ৬০০ মেগাহার্টজ এআরএম কর্টেক্স-এম৭-এ চলে: কোনো পিসির প্রয়োজন নেই, শুধু একটি ঘুঁটি বেছে নিন, সেটি কোথায় যাবে তা ট্যাপ করুন, এবং টিনসিফিশ (আমার স্টকফিশ পোর্ট) কয়েক সেকেন্ডের মধ্যেই উত্তর দেবে। 🧠 একটি মাইক্রোকন্ট্রোলারে স্টকফিশ কীভাবে এঁটে যায়? আধুনিক স্টকফিশ কয়েক দশ মেগাবাইটের একটি এনএনইউই (NNUE) নিউরাল নেটওয়ার্ক ব্যবহার করে, কিন্তু টিনসিতে আছে মাত্র ২ মেগাবাইট ফ্ল্যাশ এবং ১ মেগাবাইট র‍্যাম। তাই টিনসিফিশ স্টকফিশের আধুনিক সার্চ, চাল তৈরি এবং ট্রান্সপোজিশন টেবিল অক্ষুণ্ণ রাখে, এবং নিউরাল নেটওয়ার্কের পরিবর্তে স্টকফিশ ১১-এর হস্তনির্মিত ইভ্যালুয়েশন ব্যবহার করে। বিশাল লুকআপ টেবিলগুলোকে কম্প্যাক্ট বিট ট্রিকস দিয়ে প্রতিস্থাপন করা হয়েছে, এবং মেমোরিকে দুটি র‍্যাম ব্যাংকের মধ্যেই সংকুচিত করে বসানো হয়েছে। এটি এখনও পূর্ণ শক্তিতে থাকা বেশিরভাগ ক্লাব খেলোয়াড়কে গুঁড়িয়ে দেওয়ার জন্য যথেষ্ট শক্তিশালী। আমি কি এটা বের করেছি? অবশ্যই না, কিন্তু ক্লদ কোড এবং ওপাস ৫.৫ তা করেছে। ✨ বৈশিষ্ট্য ♟️ ২১টি কঠিনতার স্তর, নতুনদের থেকে শুরু করে পূর্ণ শক্তি পর্যন্ত ♟️ সাদা বা কালো হিসেবে খেলুন (বোর্ড উল্টে যায়) ♟️ চাল দেওয়ার জন্য স্পর্শ করুন, বৈধ চালের জন্য ডট এবং শেষ চালের জন্য হাইলাইট সহ ♟️ ইঙ্গিত (HINT) বোতাম: ইঞ্জিন আপনার সেরা চালের পরামর্শ দেয় ♟️ পূর্বাবস্থায় ফেরান (UNDO) এবং নতুন খেলা (NEW GAME) বোতাম ♟️ ঘুঁটির স্কোর এবং লাইভ মূল্যায়ন বার ♟️ চেকমেট, অচলাবস্থা এবং ড্র শনাক্তকরণ, সাথে পন প্রমোশন ♟️ প্রতিটি চালে বাজার ক্লিক করে, এবং অবৈধ চালে সতর্কতামূলক বিপ শব্দ হয় ♟️ টাচ ক্যালিব্রেশন EEPROM-এ সংরক্ষিত থাকে 🛠️ হার্ডওয়্যার • টিনসি ৪.০ (৬০০ মেগাহার্টজ এআরএম কর্টেক্স-এম৭, ১ এমবি র‍্যাম, ২ এমবি ফ্ল্যাশ) • ২.৮" ILI9341 320×240 SPI TFT ডিসপ্লে, সাথে XPT2046 টাচ • প্যাসিভ বাজার • কয়েকটি জাম্পার ওয়্যার 💾 সোর্স কোড, ওয়্যারিং এবং তৈরির নির্দেশাবলী KrisKasprzak/TeensyChess স্টকফিশের মতোই এটিও GPLv3 লাইসেন্সের অধীনে ফ্রি এবং ওপেন সোর্স। 🙏 কৃতজ্ঞতা স্টকফিশ ডেভেলপারদের তৈরি: stockfishchess.org পল স্টফ্রেগেন / পিজেআরসি-এর তৈরি টিনসি এবং ডিসপ্লে/টাচ লাইব্রেরি: pjrc.com টিনসিফিশ একটি আনঅফিশিয়াল পোর্ট এবং এটি স্টকফিশ প্রজেক্টের সাথে যুক্ত নয়। 👍 যদি এটি আপনার ভালো লেগে থাকে, তবে আরও মাইক্রোকন্ট্রোলার প্রজেক্টের জন্য সাবস্ক্রাইব করুন, এবং কমেন্টে আমাকে জানান: আপনি কি লেভেল ২০-এ টিনসিফিশকে হারাতে পারবেন? #স্টকফিশ #টিনসি #দাবা #আরডুইনো #মাইক্রোকন্ট্রোলার #ডিআইওয়াই #দাবাইঞ্জিন #ইলেকট্রনিক্স [de-DE] Stockfish-Schach auf einem Teensy 4.0 Ich habe Stockfish, die legendäre Open-Source-Schach-Engine, auf einen 24-Dollar-Mikrocontroller vom Typ Teensy 4.0 mit 2,8-Zoll-Touchscreen portiert und bin jetzt mit meinem eigenen Projekt unschlagbar. ♟️🔥 Alles läuft auf dem 600-MHz-ARM-Cortex-M7 des Teensy: kein PC nötig. Einfach eine Figur auswählen, den Zug antippen, und TeensyFish (meine Stockfish-Portierung) antwortet innerhalb von Sekunden. 🧠 WIE PASST STOCKFISH AUF EINEN MIKROCONTROLLER? Das moderne Stockfish verwendet ein NNUE-Neuronales Netzwerk, das mehrere Megabyte groß ist, aber der Teensy hat nur 2 MB Flash-Speicher und 1 MB RAM. Daher behält TeensyFish die moderne Suche, die Zuggenerierung und die Transpositionstabelle von Stockfish bei und ersetzt das neuronale Netzwerk durch die manuelle Auswertung aus Stockfish 11. Riesige Nachschlagetabellen wurden durch kompakte Bittricks ersetzt, und der Speicher wurde in den RAM gequetscht. Banken. Es ist immer noch stark genug, um die meisten Vereinsspieler in Bestform zu schlagen. Habe ich das herausgefunden? Sicher nicht, aber Claude Code und Opus 5.5 schon. ✨ FEATURES ♟️ 21 Schwierigkeitsstufen, vom Anfänger bis zum Profi ♟️ Spiele mit Weiß oder Schwarz (das Brett dreht sich) ♟️ Berühre zum Ziehen, mit Punkten für zulässige Züge und Hervorhebung des letzten Zuges ♟️ HINWEIS-Taste: Die Engine schlägt deinen besten Zug vor ♟️ RÜCKGÄNGIG- und NEUES SPIEL-Tasten ♟️ Materialwertung und Live-Bewertungsanzeige ♟️ Schachmatt-, Patt- und Remiserkennung sowie Bauernumwandlung ♟️ Signalton bei jedem Zug und Warnsignal bei unzulässigen Zügen ♟️ Berührungskalibrierung im EEPROM gespeichert 🛠️ HARDWARE • Teensy 4.0 (600 MHz ARM) Cortex-M7, 1 MB RAM, 2 MB Flash) • 2,8" ILI9341 320×240 SPI TFT mit XPT2046 Touchscreen • Passiver Summer • Einige Jumperkabel 💾 QUELLCODE, VERDRAHTUNG UND BAUANLEITUNG KrisKasprzak/TeensyChess Kostenlos und Open Source unter der GPLv3, wie Stockfish selbst. 🙏 DANKSAGUNGEN Stockfish von den Stockfish-Entwicklern: stockfishchess.org Teensy und die Display-/Touch-Bibliotheken von Paul Stoffregen / PJRC: pjrc.com TeensyFish ist eine inoffizielle Portierung und steht in keiner Verbindung zum Stockfish-Projekt. 👍 Wenn dir das gefallen hat, abonniere den Kanal für weitere Mikrocontroller-Projekte und schreib mir in die Kommentare: Könntest DU TeensyFish in Level 20 schlagen? #Stockfisch #Teensy #Schach #Arduino #Mikrocontroller #DIY #Schachprogramm #Elektronik [es-US] Ajedrez con Stockfish en un Teensy 4.0 Adapté Stockfish, el legendario motor de ajedrez de código abierto, a un microcontrolador Teensy 4.0 de 24 dólares con pantalla táctil de 2,8", y ahora mi propio proyecto es insuperable. ♟️🔥 Todo funciona con el ARM Cortex-M7 de 600 MHz del Teensy: sin PC. Simplemente elige una pieza, pulsa dónde va y TeensyFish (mi adaptación de Stockfish) responde en segundos. 🧠 ¿CÓMO SE ADAPTA STOCKFISH A UN MICROCONTROLADOR? El Stockfish moderno utiliza una red neuronal NNUE de decenas de megabytes, pero el Teensy solo tiene 2 MB de memoria flash y 1 MB de RAM. Por eso, TeensyFish conserva la búsqueda, la generación de movimientos y la tabla de transposición de Stockfish, y sustituye la red neuronal por la evaluación manual de Stockfish 11. Las enormes tablas de búsqueda se reemplazaron por técnicas de bits compactas, y la memoria se distribuyó entre los dos bancos de RAM. Aun así, sigue siendo eficiente. Lo suficientemente fuerte como para aplastar a la mayoría de los jugadores de club en su máximo nivel. ¿Lo descubrí yo? Claro que no, pero Claude Code y Opus 5.5 sí. ✨ CARACTERÍSTICAS ♟️ 21 niveles de dificultad, desde principiante hasta experto ♟️ Juega con blancas o negras (el tablero se voltea) ♟️ Toca para mover, con puntos que indican movimientos legales y resaltado del último movimiento ♟️ Botón PISTA: el motor sugiere tu mejor movimiento ♟️ Botones DESHACER y NUEVA PARTIDA ♟️ Puntuación de material y barra de evaluación en tiempo real ♟️ Detección de jaque mate, tablas por ahogado y tablas, además de promoción de peones ♟️ Sonido de zumbador en cada movimiento y pitido de advertencia en movimientos ilegales ♟️ Calibración táctil guardada en la EEPROM 🛠️ HARDWARE • Teensy 4.0 (600 MHz ARM Cortex-M7, 1 MB de RAM, 2 MB de almacenamiento) (flash) • Pantalla TFT SPI ILI9341 de 2,8" y 320 × 240 con táctil XPT2046 • Zumbador pasivo • Unos cuantos cables puente 💾 CÓDIGO FUENTE, CABLEADO E INSTRUCCIONES DE MONTAJE KrisKasprzak/TeensyChess Gratuito y de código abierto bajo la licencia GPLv3, al igual que Stockfish. 🙏 CRÉDITOS Stockfish, de los desarrolladores de Stockfish: stockfishchess.org Teensy y las librerías de pantalla/táctil de Paul Stoffregen / PJRC: pjrc.com TeensyFish es una adaptación no oficial y no está afiliada al proyecto Stockfish. 👍 Si te gustó, suscríbete para ver más proyectos con microcontroladores y cuéntame en los comentarios: ¿podrías vencer a TeensyFish en el nivel 20? #Stockfish #Teensy #Ajedrez #Arduino #Microcontrolador #DIY #MotorDeAjedrez #Electrónica [fr-FR] Échecs avec Stockfish sur une Teensy 4.0 J'ai porté Stockfish, le légendaire moteur d'échecs open source, sur un microcontrôleur Teensy 4.0 à 24 $ avec écran tactile de 2,8 pouces, et maintenant, je suis imbattable ! ♟️🔥 Tout fonctionne grâce au processeur ARM Cortex-M7 600 MHz du Teensy : pas besoin de PC. Il suffit de choisir une pièce, de toucher l'écran pour indiquer son emplacement, et TeensyFish (mon portage de Stockfish) répond en quelques secondes. 🧠 COMMENT STOCKFISH TIENT-IL SUR UN MICROCONTRÔLEUR ? Stockfish utilise un réseau neuronal NNUE de plusieurs dizaines de mégaoctets, mais le Teensy ne dispose que de 2 Mo de mémoire flash et 1 Mo de RAM. TeensyFish conserve donc les fonctions modernes de recherche, de génération de coups et de transposition de Stockfish, et remplace le réseau neuronal par l'évaluation manuelle de Stockfish 11. Les volumineuses tables de consultation ont été remplacées par des techniques de traitement du bit compactes, et la mémoire a été optimisée en l'intégrant aux deux banques de RAM. Il est encore suffisamment puissant pour écraser la plupart des joueurs de club à leur niveau maximal. Ai-je trouvé la solution ? Certainement pas, mais Claude Code et Opus 5.5, oui. ✨ FONCTIONNALITÉS ♟️ 21 niveaux de difficulté, du débutant au joueur confirmé ♟️ Jouez avec les Blancs ou les Noirs (l'échiquier s'inverse) ♟️ Déplacement tactile, avec indication des coups autorisés et surbrillance du dernier coup joué ♟️ Bouton INDICE : le moteur suggère votre meilleur coup ♟️ Boutons ANNULER et NOUVELLE PARTIE ♟️ Score matériel et barre d'évaluation en direct ♟️ Détection des échecs et mats, pats et nulles, ainsi que promotion des pions ♟️ Signal sonore à chaque coup et bip d'avertissement pour les coups illégaux ♟️ Calibrage tactile enregistré dans l'EEPROM 🛠️ MATÉRIEL • Teensy 4.0 (600 MHz ARM Cortex-M7, 1 Mo de RAM) 2 Mo de mémoire flash) • Écran TFT SPI ILI9341 2,8" 320×240 avec module tactile XPT2046 • Buzzer passif • Quelques fils de connexion 💾 CODE SOURCE, CÂBLAGE ET INSTRUCTIONS DE MONTAGE KrisKasprzak/TeensyChess Libre et open source sous licence GPLv3, comme Stockfish. 🙏 CRÉDITS Stockfish par les développeurs de Stockfish : stockfishchess.org Teensy et les bibliothèques d'affichage/tactiles par Paul Stoffregen / PJRC : pjrc.com TeensyFish est un portage non officiel et n'est pas affilié au projet Stockfish. 👍 Si ce projet vous a plu, abonnez-vous pour découvrir d'autres projets de microcontrôleurs et dites-moi en commentaire : pourriez-vous battre TeensyFish au niveau 20 ? #Stockfish #Teensy #Échecs #Arduino #Microcontrôleur #DIY #ChessEngine #Électronique [hi] Teensy 4.0 पर Stockfish Chess मैंने मशहूर ओपन-सोर्स शतरंज इंजन, स्टॉकफिश को 24 डॉलर के टीन्सी 4.0 माइक्रोकंट्रोलर पर पोर्ट किया है, जिसमें 2.8 इंच की टच स्क्रीन है, और अब मैं अपने ही प्रोजेक्ट को हरा नहीं सकता। ♟️🔥 सब कुछ टीन्सी के 600 मेगाहर्ट्ज ARM कॉर्टेक्स-M7 प्रोसेसर पर चलता है: पीसी की ज़रूरत नहीं। बस एक मोहरा चुनें, जहां उसे रखना है वहां टैप करें, और टीन्सीफिश (मेरा स्टॉकफिश पोर्ट) कुछ ही सेकंड में जवाब दे देता है। 🧠 स्टॉकफिश एक माइक्रोकंट्रोलर पर कैसे फिट बैठता है? आधुनिक स्टॉकफिश में कई मेगाबाइट का NNUE न्यूरल नेटवर्क इस्तेमाल होता है, लेकिन टीन्सी में सिर्फ 2 MB फ्लैश मेमोरी और 1 MB रैम है। इसलिए टीन्सीफिश ने स्टॉकफिश के आधुनिक सर्च, मूव जनरेशन और ट्रांसपोज़िशन टेबल को बरकरार रखा है, और न्यूरल नेटवर्क की जगह स्टॉकफिश 11 के हस्तनिर्मित मूल्यांकन का इस्तेमाल किया है। बड़ी लुकअप टेबल की जगह कॉम्पैक्ट बिट ट्रिक्स का इस्तेमाल किया गया है, और मेमोरी को दोनों रैम बैंकों में समेट दिया गया है। यह अभी भी दमदार है। पूरी ताकत से खेलने पर भी यह अधिकांश क्लब खिलाड़ियों को हराने के लिए काफी है। क्या मैंने इसका पता लगाया? बिल्कुल नहीं, लेकिन क्लाउड कोड और ओपस 5.5 ने ज़रूर लगाया। ✨ विशेषताएं ♟️ 21 कठिनाई स्तर, शुरुआती से लेकर पूरी ताकत तक ♟️ सफेद या काले मोहरों से खेलें (बोर्ड पलट जाता है) ♟️ चाल चलने के लिए स्पर्श करें, वैध चालों पर बिंदु और पिछली चालों पर हाइलाइट ♟️ संकेत बटन: इंजन आपकी सर्वोत्तम चाल का सुझाव देता है ♟️ पूर्ववत करें और नया गेम शुरू करें बटन ♟️ मोहरों का स्कोर और लाइव मूल्यांकन बार ♟️ चेकमेट, गतिरोध और ड्रॉ का पता लगाना, साथ ही प्यादों की पदोन्नति ♟️ हर चाल पर बजर बजता है, और अवैध चालों पर चेतावनी बीप ♟️ टच कैलिब्रेशन EEPROM में सहेजा जाता है 🛠️ हार्डवेयर • Teensy 4.0 (600 MHz ARM Cortex-M7, 1 • 2.8 इंच ILI9341 320×240 SPI TFT डिस्प्ले (XPT2046 टच स्क्रीन के साथ) • पैसिव बजर • कुछ जम्पर वायर 💾 सोर्स कोड, वायरिंग और बिल्ड निर्देश KrisKasprzak/TeensyChess स्टॉकफिश की तरह ही, यह भी GPLv3 लाइसेंस के तहत मुफ़्त और ओपन सोर्स है। 🙏 श्रेय स्टॉकफिश डेवलपर्स द्वारा बनाया गया स्टॉकफिश: stockfishchess.org पॉल स्टॉफ्रेगन / PJRC द्वारा बनाई गई टीन्सीफिश और डिस्प्ले/टच लाइब्रेरी: pjrc.com टीन्सीफिश एक अनौपचारिक पोर्ट है और इसका स्टॉकफिश प्रोजेक्ट से कोई संबंध नहीं है। 👍 अगर आपको यह पसंद आया, तो और भी माइक्रोकंट्रोलर प्रोजेक्ट्स के लिए सब्सक्राइब करें और कमेंट्स में बताएं: क्या आप लेवल 20 पर टीन्सीफिश को हरा सकते हैं? #स्टॉकफिश #टीन्सी #शतरंज #आर्डिनो #माइक्रोकंट्रोलर #डीआईवाई #शतरंजइंजन #इलेक्ट्रॉनिक्स [id] Catur Stockfish di Teensy 4.0 Saya memindahkan Stockfish, mesin catur open-source legendaris, ke mikrokontroler Teensy 4.0 seharga $24 dengan layar sentuh 2,8 inci, dan sekarang saya tidak bisa mengalahkan proyek saya sendiri. ♟️🔥 Semuanya berjalan di ARM Cortex-M7 600 MHz Teensy: tanpa PC, Cukup pilih bidak, ketuk ke mana bidak itu akan pergi, dan TeensyFish (port Stockfish saya) akan menjawab dalam hitungan detik. 🧠 BAGAIMANA STOCKFISH DAPAT BERJALAN DI MIKROKONTROLER? Stockfish modern menggunakan jaringan saraf NNUE yang berukuran puluhan megabyte, tetapi Teensy hanya memiliki flash 2 MB dan RAM 1 MB. Jadi TeensyFish mempertahankan pencarian modern Stockfish, pembangkitan langkah, dan tabel transposisi, dan mengganti jaringan saraf dengan evaluasi buatan tangan dari Stockfish 11. Tabel pencarian yang besar digantikan dengan trik bit yang ringkas, dan memori dipersempit ke kedua bank RAM. Ini masih cukup kuat untuk mengalahkan sebagian besar pemain klub. Kekuatan penuh. Apakah saya yang menemukan ini? Tentu tidak, tetapi Claude Code dan Opus 5.5 berhasil. ✨ FITUR ♟️ 21 tingkat kesulitan, dari pemula hingga kekuatan penuh ♟️ Bermain sebagai putih atau hitam (papan catur dibalik) ♟️ Sentuh untuk bergerak, dengan titik langkah legal dan sorotan langkah terakhir ♟️ Tombol PETUNJUK: mesin catur menyarankan langkah terbaik Anda ♟️ Tombol BATALKAN dan PERMAINAN BARU ♟️ Skor material dan bilah evaluasi langsung ♟️ Deteksi skakmat, remis, dan seri, ditambah promosi pion ♟️ Bunyi bel pada setiap langkah, dan bunyi peringatan pada langkah ilegal ♟️ Kalibrasi sentuh disimpan di EEPROM 🛠️ PERANGKAT KERAS • Teensy 4.0 (600 MHz ARM Cortex-M7, 1 MB RAM, 2 MB flash) • Layar TFT SPI ILI9341 2,8" 320×240 dengan layar sentuh XPT2046 • Buzzer pasif • Beberapa kabel jumper 💾 KODE SUMBER, INSTRUKSI PENYAMBUNGAN KABEL DAN PEMBANGUNAN KrisKasprzak/TeensyChess Gratis dan open source di bawah GPLv3, seperti Stockfish itu sendiri. 🙏 KREDIT Stockfish oleh pengembang Stockfish: stockfishchess.org Teensy dan pustaka display/sentuh oleh Paul Stoffregen / PJRC: pjrc.com TeensyFish adalah port tidak resmi dan tidak berafiliasi dengan proyek Stockfish. 👍 Jika Anda menyukai ini, berlangganan untuk proyek mikrokontroler lainnya, dan beri tahu saya di kolom komentar: bisakah ANDA mengalahkan TeensyFish di level 20? #Stockfish #Teensy #Catur #Arduino #Mikrokontroler #DIY #MesinCatur #Elektronik [it] Scacchi con Stockfish su un Teensy 4.0 Ho portato Stockfish, il leggendario motore scacchistico open-source, su un microcontrollore Teensy 4.0 da 24 dollari con un touchscreen da 2,8 pollici, e ora non riesco a battere il mio stesso progetto. ♟️🔥 Tutto funziona sul processore ARM Cortex-M7 a 600 MHz del Teensy: niente PC, basta scegliere un pezzo, toccare dove va e TeensyFish (il mio porting di Stockfish) risponde in pochi secondi. 🧠 COME FA STOCKFISH A STARE SU UN MICROCONTROLLORE? Lo Stockfish moderno utilizza una rete neurale NNUE che occupa decine di megabyte, ma il Teensy ha solo 2 MB di memoria flash e 1 MB di RAM. Quindi TeensyFish mantiene la moderna ricerca, la generazione delle mosse e la tabella di trasposizione di Stockfish, e sostituisce la rete neurale con la valutazione manuale di Stockfish 11. Le enormi tabelle di ricerca sono state sostituite da trucchi di bit compatti e la memoria è stata compressa in entrambi i banchi di RAM. È ancora abbastanza potente da battere la maggior parte dei club giocatori al massimo delle loro potenzialità. L'ho capito io? Di sicuro no, ma Claude Code e Opus 5.5 sì. ✨ CARATTERISTICHE ♟️ 21 livelli di difficoltà, da principiante a esperto ♟️ Gioca con i pezzi bianchi o neri (la scacchiera si capovolge) ♟️ Tocca per muoverti, con punti per le mosse legali ed evidenziazione dell'ultima mossa ♟️ Pulsante SUGGERIMENTO: il motore suggerisce la mossa migliore ♟️ Pulsanti ANNULLA e NUOVA PARTITA ♟️ Punteggio materiale e barra di valutazione in tempo reale ♟️ Rilevamento di scacco matto, stallo e patta, oltre alla promozione del pedone ♟️ Il buzzer emette un clic a ogni mossa e un segnale acustico di avvertimento per le mosse illegali ♟️ Calibrazione del touch salvata in EEPROM 🛠️ HARDWARE • Teensy 4.0 (ARM Cortex-M7 a 600 MHz, 1 MB di RAM, 2 MB di memoria flash) • Display TFT SPI ILI9341 da 2,8" 320×240 con touch XPT2046 • Buzzer passivo • Alcuni cavi jumper 💾 CODICE SORGENTE, SCHEMA DI CABLAGGIO E ISTRUZIONI DI MONTAGGIO KrisKasprzak/TeensyChess Libero e open source sotto licenza GPLv3, come Stockfish stesso. 🙏 RINGRAZIAMENTI Stockfish sviluppato dagli sviluppatori di Stockfish: stockfishchess.org Teensy e le librerie per display/touch di Paul Stoffregen / PJRC: pjrc.com TeensyFish è un porting non ufficiale e non è affiliato al progetto Stockfish. 👍 Se ti è piaciuto, iscriviti per altri progetti con microcontrollori e dimmi nei commenti: riusciresti a battere TeensyFish al livello 20? #Stockfish #Teensy #Scacchi #Arduino #Microcontrollore #FaiDaTe #MotoreScacchi #Elettronica [iw] שחמט של Stockfish על גבי Teensy 4.0 שיניתי את Stockfish, מנוע השחמט האגדי בקוד פתוח, למיקרו-בקר Teensy 4.0 בשווי 24 דולר עם מסך מגע בגודל 2.8 אינץ', ועכשיו אני לא יכול לנצח את הפרויקט שלי. ♟️🔥 הכל רץ על ARM Cortex-M7 600 מגה-הרץ של ה-Teensy: בלי מחשב, פשוט בחרו כלי, הקישו לאן שהוא הולך, ו-TeensyFish (היציאה שלי ל-Stockfish) עונה תוך שניות. 🧠 איך STOCKFISH מתאים למיקרו-בקר? Stockfish המודרני משתמש ברשת נוירונים NNUE שגודלה עשרות מגה-בייט, אבל ל-Teensy יש רק 2 מגה-בייט של זיכרון פלאש ו-1 מגה-בייט של זיכרון RAM. אז TeensyFish שומר על טבלת החיפוש, יצירת המהלכים והטרנספוזיציה המודרנית של Stockfish, ומחליף את הרשת הנוירונים בהערכה בעבודת יד מ-Stockfish 11. טבלאות חיפוש ענקיות הוחלפו בטריקים קומפקטיים של סיביות, והזיכרון נדחס לשני בנקי ה-RAM. הוא עדיין חזק מספיק כדי לרסק את רוב שחקני המועדון במלוא העוצמה. האם הבנתי את זה? בחוץ? בטח שלא, אבל קלוד קוד ואופוס 5.5 כן. ✨ תכונות ♟️ 21 רמות קושי, ממתחילים ועד עוצמה מלאה ♟️ שחקו כלבן או שחור (הלוח מתהפך) ♟️ געו כדי לזוז, עם נקודות של מהלך חוקי והדגשות של מהלך אחרון ♟️ כפתור רמז: המנוע מציע את המהלך הטוב ביותר שלכם ♟️ כפתורי ביטול ומשחק חדש ♟️ ניקוד חומרים וסרגל הערכה בזמן אמת ♟️ זיהוי שחמט, קיפאון ותיקו, בתוספת קידום חיילים ♟️ קליקים של זמזם בכל מהלך, וצפצוף אזהרה על מהלכים לא חוקיים ♟️ כיול מגע נשמר ב-EEPROM 🛠️ חומרה • Teensy 4.0 (600 MHz ARM Cortex-M7, 1 MB RAM, 2 MB flash) • 2.8" ILI9341 320×240 SPI TFT עם מגע XPT2046 • זמזם פסיבי • כמה חוטי מגשר 💾 קוד מקור, חיווט והוראות בנייה KrisKasprzak/TeensyChess קוד פתוח וחינמי תחת GPLv3, כמו Stockfish עצמו. 🙏 קרדיטים Stockfish מאת מפתחי Stockfish: stockfishchess.org Teensy וספריות התצוגה/מגע מאת פול סטופרגן / PJRC: pjrc.com TeensyFish הוא פורט לא רשמי ואינו קשור לפרויקט Stockfish. 👍 אם אהבתם את זה, הירשמו לפרויקטים נוספים של מיקרו-בקרים, וספרו לי בתגובות: האם תוכלו לנצח את TeensyFish ברמה 20? #Stockfish #Teensy #Chess #Arduino #Microcontroller #DIY #ChessEngine #Electronics [ja] Teensy 4.0でStockfish Chessを動かす 伝説的なオープンソースチェスエンジン、Stockfishを24ドルのTeensy 4.0マイクロコントローラー(2.8インチタッチスクリーン搭載)に移植しました。今では自分のプロジェクトに勝てる者はいません。♟️🔥 すべてTeensyの600MHz ARM Cortex-M7で動作します。PCは不要。駒を選んで移動先をタップするだけで、TeensyFish(私のStockfish移植版)が数秒以内に答えてくれます。 🧠 Stockfishはどうやってマイクロコントローラーに収まるのか? 最新のStockfishは数十メガバイトのNNUEニューラルネットワークを使用していますが、Teensyには2MBのフラッシュメモリと1MBのRAMしかありません。そこでTeensyFishはStockfishの最新の探索、指し手生成、転置テーブルを維持しつつ、ニューラルネットワークをStockfish 11の手作業による評価に置き換えました。巨大なルックアップテーブルはコンパクトなビットトリックに置き換えられ、メモリは両方のRAMバンクに詰め込まれました。それでもなお、ほとんどのクラブプレイヤーが本気を出せば圧倒できるほどの強さ。私がこのことに気づいたかって?もちろん違います。クロード・コードとOpus 5.5が発見したんです。 ✨ 特徴 ♟️ 初心者から上級者まで、21段階の難易度 ♟️ 白番または黒番でプレイ(盤面が反転します) ♟️ タッチ操作で駒を動かし、合法な手にはドット、最後の手にはハイライト表示 ♟️ ヒントボタン:エンジンが最善手を提案 ♟️ 元に戻すボタンと新しいゲームボタン ♟️ 駒の得点とリアルタイム評価バー ♟️ チェックメイト、ステイルメイト、引き分けの判定、ポーンの昇格 ♟️ 駒を動かすたびにブザーが鳴り、不正な手には警告音が鳴る ♟️ タッチキャリブレーションはEEPROMに保存 🛠️ ハードウェア • Teensy 4.0(600MHz ARM Cortex-M7、1MB RAM、2MBフラッシュメモリ) • 2.8インチ ILI9341 320×240 SPI TFT液晶ディスプレイ(XPT2046タッチパネル搭載) • パッシブブザー • ジャンパー線数本 💾 ソースコード、配線図、組み立て手順 KrisKasprzak/TeensyChess Stockfish本体と同様、GPLv3ライセンスの下、無料でオープンソースです。 🙏 クレジット Stockfish開発者によるStockfish:stockfishchess.org Teensyおよびディスプレイ/タッチライブラリ:Paul Stoffregen / PJRC:pjrc.com TeensyFishは非公式の移植版であり、Stockfishプロジェクトとは一切関係ありません。 👍 この動画が気に入ったら、マイクロコントローラー関連の動画をもっと見たい方はチャンネル登録をお願いします。そして、コメント欄で教えてください:あなたはTeensyFishのレベル20をクリアできますか? #Stockfish #Teensy #チェス #Arduino #マイクロコントローラー #DIY #チェスエンジン #電子機器 [ko] Teensy 4.0으로 구동하는 스톡피쉬 체스 저는 전설적인 오픈 소스 체스 엔진인 스톡피시(Stockfish)를 2.8인치 터치스크린이 장착된 24달러짜리 틴시 4.0 마이크로컨트롤러에 포팅했습니다. 이제 제 프로젝트를 이길 수가 없네요! ♟️🔥 모든 것은 틴시의 600MHz ARM Cortex-M7에서 실행됩니다. PC는 필요 없어요. 그냥 말을 고르고, 놓을 위치를 터치하면, 제가 포팅한 스톡피시인 틴시피시(TeensyFish)가 몇 초 안에 답을 보여줍니다. 🧠 스톡피시가 어떻게 마이크로컨트롤러에 들어갈 수 있었을까요? 최신 스톡피시는 수십 메가바이트에 달하는 NNUE 신경망을 사용하지만, 틴시는 2MB의 플래시 메모리와 1MB의 RAM밖에 없습니다. 그래서 틴시피시는 스톡피시의 최신 탐색, 수 생성, 전치 테이블은 그대로 유지하고, 신경망 대신 스톡피시 11의 수작업 평가 방식을 사용했습니다. 거대한 조회 테이블은 간결한 비트 트릭으로 대체되었고, 메모리는 두 개의 RAM 뱅크에 압축되었습니다. 그럼에도 불구하고 대부분의 클럽 체스를 이길 만큼 강력합니다. 최고 기량의 플레이어들. 제가 이걸 알아냈냐고요? 물론 아니죠. 클로드 코드와 오푸스 5.5가 알아냈습니다. ✨ 특징 ♟️ 초보자부터 최고 기량까지 21단계 난이도 ♟️ 백 또는 흑으로 플레이 (보드가 뒤집힙니다) ♟️ 터치로 이동, 가능한 수는 점으로 표시되고 마지막 수는 강조 표시됩니다 ♟️ 힌트 버튼: 엔진이 최적의 수를 제안합니다 ♟️ 실행 취소 및 새 게임 버튼 ♟️ 기물 점수 및 실시간 평가 바 ♟️ 체크메이트, 스테일메이트, 무승부 감지 및 폰 승진 기능 ♟️ 매 수마다 부저음이 울리고, 잘못된 수를 둘 경우 경고음이 울립니다 ♟️ 터치 보정값이 EEPROM에 저장됩니다 🛠️ 하드웨어 • Teensy 4.0 (600MHz ARM Cortex-M7, 1MB RAM, 2MB 플래시) • 2.8인치 ILI9341 320×240 SPI TFT 디스플레이 XPT2046 터치 칩 • 패시브 부저 • 몇 개의 점퍼 와이어 💾 소스 코드, 배선 및 조립 설명서 KrisKasprzak/TeensyChess Stockfish와 마찬가지로 GPLv3 라이선스 하에 무료로 제공되는 오픈 소스 프로젝트입니다. 🙏 크레딧 Stockfish 개발자: stockfishchess.org Teensy 및 디스플레이/터치 라이브러리: Paul Stoffregen / PJRC: pjrc.com TeensyFish는 비공식 포트이며 Stockfish 프로젝트와는 관련이 없습니다. 👍 이 프로젝트가 마음에 드셨다면 구독 버튼을 눌러 더 많은 마이크로컨트롤러 프로젝트를 시청하고, 댓글로 여러분이 TeensyFish 20레벨을 이길 수 있는지 알려주세요! #Stockfish #Teensy #Chess #Arduino #Microcontroller #DIY #ChessEngine #Electronics [ml] Teensy 4.0-ൽ Stockfish ചെസ്സ് ഐതിഹാസിക ഓപ്പൺ സോഴ്‌സ് ചെസ്സ് എഞ്ചിനായ സ്റ്റോക്ക്ഫിഷിനെ ഞാൻ 2.8 ഇഞ്ച് ടച്ച് സ്‌ക്രീനുള്ള $24 വിലയുള്ള ടീൻസി 4.0 മൈക്രോകൺട്രോളറിലേക്ക് പോർട്ട് ചെയ്തു, ഇപ്പോൾ എനിക്ക് എന്റെ സ്വന്തം പ്രോജക്റ്റിനെ തോൽപ്പിക്കാൻ കഴിയില്ല. ♟️🔥 എല്ലാം ടീൻസിയുടെ 600 MHz ARM കോർട്ടെക്സ്-M7-ൽ പ്രവർത്തിക്കുന്നു: പിസി ഇല്ല, ഒരു കഷണം തിരഞ്ഞെടുക്കുക, അത് എവിടെ പോകുന്നുവെന്ന് ടാപ്പ് ചെയ്യുക, ടീൻസിഫിഷ് (എന്റെ സ്റ്റോക്ക്ഫിഷ് പോർട്ട്) നിമിഷങ്ങൾക്കുള്ളിൽ ഉത്തരം നൽകുന്നു. 🧠 ഒരു മൈക്രോകൺട്രോളറിൽ സ്റ്റോക്ക്ഫിഷ് എങ്ങനെ യോജിക്കും? മോഡേൺ സ്റ്റോക്ക്ഫിഷ് പതിനായിരക്കണക്കിന് മെഗാബൈറ്റുകളുള്ള ഒരു NNUE ന്യൂറൽ നെറ്റ്‌വർക്ക് ഉപയോഗിക്കുന്നു, എന്നാൽ ടീൻസിക്ക് 2 MB ഫ്ലാഷും 1 MB റാമും മാത്രമേയുള്ളൂ. അതിനാൽ ടീൻസിഫിഷ് സ്റ്റോക്ക്ഫിഷിന്റെ ആധുനിക തിരയൽ, മൂവ് ജനറേഷൻ, ട്രാൻസ്‌പോസിഷൻ ടേബിൾ സൂക്ഷിക്കുന്നു, കൂടാതെ സ്റ്റോക്ക്ഫിഷ് 11-ൽ നിന്ന് കൈകൊണ്ട് നിർമ്മിച്ച മൂല്യനിർണ്ണയത്തിനായി ന്യൂറൽ നെറ്റ്‌വർക്ക് സ്വാപ്പ് ചെയ്യുന്നു. വലിയ ലുക്ക്അപ്പ് ടേബിളുകൾ കോം‌പാക്റ്റ് ബിറ്റ് തന്ത്രങ്ങൾ ഉപയോഗിച്ച് മാറ്റിസ്ഥാപിച്ചു, കൂടാതെ മെമ്മറി രണ്ട് റാം ബാങ്കുകളിലേക്കും ചുരുക്കി. ഇത് ഇപ്പോഴും ശക്തമാണ്. ക്ലബ്ബ് കളിക്കാരെ മുഴുവൻ കരുത്തിൽ തകർക്കാൻ പര്യാപ്തമാണ്. എനിക്ക് ഇത് മനസ്സിലായോ? തീർച്ചയായും ഇല്ല, പക്ഷേ ക്ലോഡ് കോഡും ഓപസ് 5.5 ഉം അങ്ങനെ ചെയ്തു. ✨ സവിശേഷതകൾ ♟️ തുടക്കക്കാരൻ മുതൽ പൂർണ്ണ ശക്തി വരെ 21 ബുദ്ധിമുട്ട് ലെവലുകൾ ♟️ വെള്ളയോ കറുപ്പോ ആയി കളിക്കുക (ബോർഡ് മറിഞ്ഞുവീഴുന്നു) ♟️ നിയമപരമായ നീക്ക ഡോട്ടുകളും അവസാന നീക്ക ഹൈലൈറ്റുകളും ഉപയോഗിച്ച് നീക്കാൻ സ്പർശിക്കുക ♟️ സൂചന ബട്ടൺ: എഞ്ചിൻ നിങ്ങളുടെ മികച്ച നീക്കത്തെ സൂചിപ്പിക്കുന്നു ♟️ UNDO, പുതിയ ഗെയിം ബട്ടണുകൾ ♟️ മെറ്റീരിയൽ സ്‌കോറും തത്സമയ മൂല്യനിർണ്ണയ ബാറും ♟️ ചെക്ക്‌മേറ്റ്, സ്റ്റേൽമേറ്റ്, ഡ്രോ ഡിറ്റക്ഷൻ, പ്ലസ് പോൺ പ്രമോഷൻ ♟️ ഓരോ നീക്കത്തിലും ബസർ ക്ലിക്കുചെയ്യുന്നു, നിയമവിരുദ്ധ നീക്കങ്ങളിൽ ഒരു മുന്നറിയിപ്പ് ബീപ്പ് ♟️ EEPROM-ൽ സംരക്ഷിച്ചിരിക്കുന്ന ടച്ച് കാലിബ്രേഷൻ 🛠️ ഹാർഡ്‌വെയർ • ടീൻസി 4.0 (600 MHz ARM കോർട്ടെക്സ്-M7, 1 MB റാം, 2 MB ഫ്ലാഷ്) • 2.8" ILI9341 320×240 SPI TFT XPT2046 ടച്ച് • പാസീവ് ബസർ • കുറച്ച് ജമ്പർ വയറുകൾ 💾 സോഴ്‌സ് കോഡ്, വയറിംഗ്, ബിൽഡ് നിർദ്ദേശങ്ങൾ KrisKasprzak/TeensyChess സ്റ്റോക്ക്ഫിഷ് പോലെ തന്നെ GPLv3-ന് കീഴിൽ സൌജന്യവും ഓപ്പൺ സോഴ്‌സും. 🙏 ക്രെഡിറ്റുകൾ സ്റ്റോക്ക്ഫിഷ് ഡെവലപ്പർമാരുടെ സ്റ്റോക്ക്ഫിഷ്: stockfishchess.org പോൾ സ്റ്റോഫ്രെഗൻ / PJRC-യുടെ ടീൻസിയും ഡിസ്പ്ലേ/ടച്ച് ലൈബ്രറികളും: pjrc.com TeensyFish ഒരു അനൗദ്യോഗിക പോർട്ടാണ്, സ്റ്റോക്ക്ഫിഷ് പ്രോജക്റ്റുമായി ഇത് അഫിലിയേറ്റ് ചെയ്തിട്ടില്ല. 👍 നിങ്ങൾക്ക് ഇത് ഇഷ്ടപ്പെട്ടെങ്കിൽ, കൂടുതൽ മൈക്രോകൺട്രോളർ പ്രോജക്റ്റുകൾക്കായി സബ്‌സ്‌ക്രൈബുചെയ്യുക, അഭിപ്രായങ്ങളിൽ എന്നോട് പറയുക: ലെവൽ 20-ൽ നിങ്ങൾക്ക് TeensyFish-നെ തോൽപ്പിക്കാൻ കഴിയുമോ? #Stockfish #Teensy #Chess #Arduino #Microcontroller #DIY #ChessEngine #Electronics [nl-NL] Stockfish Chess op een Teensy 4.0 Ik heb Stockfish, de legendarische open-source schaakengine, geporteerd naar een Teensy 4.0 microcontroller van $24 met een 2,8 inch touchscreen, en nu kan ik mijn eigen project niet meer verslaan. ♟️🔥 Alles draait op de 600 MHz ARM Cortex-M7 van de Teensy: geen pc nodig, je kiest gewoon een stuk, tikt op de plek waar het naartoe gaat, en TeensyFish (mijn Stockfish-port) geeft binnen enkele seconden antwoord. 🧠 HOE PAST STOCKFISH OP EEN MICROCONTROLLER? De moderne Stockfish gebruikt een NNUE neuraal netwerk van tientallen megabytes, maar de Teensy heeft slechts 2 MB flashgeheugen en 1 MB RAM. Daarom behoudt TeensyFish de moderne zoekfunctie, zetgeneratie en transpositietabel van Stockfish, en vervangt het neurale netwerk door de handmatig ontworpen evaluatie van Stockfish 11. Enorme opzoektabellen zijn vervangen door compacte bittrucs en het geheugen is in beide RAM-banken geperst. Het is nog steeds sterk genoeg om de meeste clubspelers te verslaan. Op volle sterkte. Had ik dit zelf bedacht? Zeker niet, maar Claude Code en Opus 5.5 wel. ✨ FUNCTIES ♟️ 21 moeilijkheidsniveaus, van beginner tot volle sterkte ♟️ Speel met wit of zwart (het bord draait om) ♟️ Aanraken om te zetten, met stippen voor legale zetten en markering van de laatste zet ♟️ HINT-knop: de engine suggereert je beste zet ♟️ Knoppen voor ONGEDOEN DOEN en NIEUW SPEL ♟️ Materiaalscore en live evaluatiebalk ♟️ Detectie van schaakmat, pat en remise, plus pionpromotie ♟️ Buzzer bij elke zet en een waarschuwingspiep bij illegale zetten ♟️ Touchkalibratie opgeslagen in EEPROM 🛠️ HARDWARE • Teensy 4.0 (600 MHz ARM Cortex-M7, 1 MB RAM, 2 MB flash) • 2,8" ILI9341 320×240 SPI TFT met XPT2046 touchscreen • Passieve zoemer • Een paar jumperdraden 💾 BRONCODE, BEDRADING EN BOUWINSTRUCTIES KrisKasprzak/TeensyChess Gratis en open source onder de GPLv3, net als Stockfish zelf. 🙏 CREDITS Stockfish van de Stockfish-ontwikkelaars: stockfishchess.org Teensy en de display-/touchbibliotheken van Paul Stoffregen / PJRC: pjrc.com TeensyFish is een onofficiële port en is niet gelieerd aan het Stockfish-project. 👍 Als je dit leuk vond, abonneer je dan voor meer microcontrollerprojecten en laat me in de reacties weten: zou JIJ TeensyFish kunnen verslaan op level 20? #Stockfish #Teensy #Schaak #Arduino #Microcontroller #DIY #Schaakengine #Elektronica [pa] Teensy 4.0 ਉੱਤੇ Stockfish ਚੈੱਸ ਮੈਂ ਸਟਾਕਫਿਸ਼, ਪ੍ਰਸਿੱਧ ਓਪਨ-ਸੋਰਸ ਸ਼ਤਰੰਜ ਇੰਜਣ, ਨੂੰ $24 ਦੇ ਟੀਨਸੀ 4.0 ਮਾਈਕ੍ਰੋਕੰਟਰੋਲਰ ਵਿੱਚ 2.8" ਟੱਚ ਸਕ੍ਰੀਨ ਨਾਲ ਪੋਰਟ ਕੀਤਾ, ਅਤੇ ਹੁਣ ਮੈਂ ਆਪਣੇ ਪ੍ਰੋਜੈਕਟ ਨੂੰ ਹਰਾ ਨਹੀਂ ਸਕਦਾ। ♟️🔥 ਸਭ ਕੁਝ ਟੀਨਸੀ ਦੇ 600 MHz ARM Cortex-M7 'ਤੇ ਚੱਲਦਾ ਹੈ: ਕੋਈ ਪੀਸੀ ਨਹੀਂ, ਬੱਸ ਇੱਕ ਟੁਕੜਾ ਚੁਣੋ, ਜਿੱਥੇ ਇਹ ਜਾਂਦਾ ਹੈ ਉੱਥੇ ਟੈਪ ਕਰੋ, ਅਤੇ ਟੀਨਸੀਫਿਸ਼ (ਮੇਰਾ ਸਟਾਕਫਿਸ਼ ਪੋਰਟ) ਸਕਿੰਟਾਂ ਵਿੱਚ ਜਵਾਬ ਦਿੰਦਾ ਹੈ। 🧠 ਸਟਾਕਫਿਸ਼ ਇੱਕ ਮਾਈਕ੍ਰੋਕੰਟਰੋਲਰ 'ਤੇ ਕਿਵੇਂ ਫਿੱਟ ਹੁੰਦਾ ਹੈ? ਆਧੁਨਿਕ ਸਟਾਕਫਿਸ਼ ਇੱਕ NNUE ਨਿਊਰਲ ਨੈੱਟਵਰਕ ਦੀ ਵਰਤੋਂ ਕਰਦਾ ਹੈ ਜੋ ਕਿ ਦਸਾਂ ਮੈਗਾਬਾਈਟ ਹੈ, ਪਰ ਟੀਨਸੀ ਵਿੱਚ ਸਿਰਫ 2 MB ਫਲੈਸ਼ ਅਤੇ 1 MB RAM ਹੈ। ਇਸ ਲਈ ਟੀਨਸੀਫਿਸ਼ ਸਟਾਕਫਿਸ਼ ਦੀ ਆਧੁਨਿਕ ਖੋਜ, ਮੂਵ ਜਨਰੇਸ਼ਨ ਅਤੇ ਟ੍ਰਾਂਸਪੋਜ਼ੀਸ਼ਨ ਟੇਬਲ ਨੂੰ ਰੱਖਦਾ ਹੈ, ਅਤੇ ਸਟਾਕਫਿਸ਼ 11 ਤੋਂ ਹੱਥ ਨਾਲ ਬਣਾਏ ਮੁਲਾਂਕਣ ਲਈ ਨਿਊਰਲ ਨੈੱਟਵਰਕ ਨੂੰ ਸਵੈਪ ਕਰਦਾ ਹੈ। ਵਿਸ਼ਾਲ ਲੁੱਕਅਪ ਟੇਬਲਾਂ ਨੂੰ ਸੰਖੇਪ ਬਿੱਟ ਟ੍ਰਿਕਸ ਨਾਲ ਬਦਲ ਦਿੱਤਾ ਗਿਆ ਸੀ, ਅਤੇ ਮੈਮੋਰੀ ਨੂੰ ਦੋਵਾਂ RAM ਬੈਂਕਾਂ ਵਿੱਚ ਨਿਚੋੜ ਦਿੱਤਾ ਗਿਆ ਸੀ। ਇਹ ਅਜੇ ਵੀ ਕਾਫ਼ੀ ਮਜ਼ਬੂਤ ​​ਹੈ। ਪੂਰੀ ਤਾਕਤ ਨਾਲ ਜ਼ਿਆਦਾਤਰ ਕਲੱਬ ਖਿਡਾਰੀਆਂ ਨੂੰ ਕੁਚਲਣ ਲਈ। ਕੀ ਮੈਂ ਇਹ ਸਮਝ ਲਿਆ? ਬਿਲਕੁਲ ਨਹੀਂ, ਪਰ ਕਲਾਉਡ ਕੋਡ ਅਤੇ ਓਪਸ 5.5 ਨੇ ਕੀਤਾ। ✨ ਵਿਸ਼ੇਸ਼ਤਾਵਾਂ ♟️ 21 ਮੁਸ਼ਕਲ ਪੱਧਰ, ਸ਼ੁਰੂਆਤੀ ਤੋਂ ਪੂਰੀ ਤਾਕਤ ਤੱਕ ♟️ ਚਿੱਟੇ ਜਾਂ ਕਾਲੇ ਦੇ ਰੂਪ ਵਿੱਚ ਖੇਡੋ (ਬੋਰਡ ਪਲਟਦਾ ਹੈ) ♟️ ਕਾਨੂੰਨੀ-ਮੂਵ ਬਿੰਦੀਆਂ ਅਤੇ ਆਖਰੀ-ਮੂਵ ਹਾਈਲਾਈਟਸ ਦੇ ਨਾਲ, ਮੂਵ ਕਰਨ ਲਈ ਛੋਹਵੋ ♟️ ਸੰਕੇਤ ਬਟਨ: ਇੰਜਣ ਤੁਹਾਡੀ ਸਭ ਤੋਂ ਵਧੀਆ ਚਾਲ ਦਾ ਸੁਝਾਅ ਦਿੰਦਾ ਹੈ ♟️ ਅਨਡੂ ਅਤੇ ਨਵੇਂ ਗੇਮ ਬਟਨ ♟️ ਮਟੀਰੀਅਲ ਸਕੋਰ ਅਤੇ ਲਾਈਵ ਮੁਲਾਂਕਣ ਬਾਰ ♟️ ਚੈੱਕਮੇਟ, ਸਟੈਲਮੇਟ ਅਤੇ ਡਰਾਅ ਖੋਜ, ਨਾਲ ਹੀ ਪੈਨ ਪ੍ਰੋਮੋਸ਼ਨ ♟️ ਹਰ ਚਾਲ 'ਤੇ ਬਜ਼ਰ ਕਲਿੱਕ ਕਰਦਾ ਹੈ, ਅਤੇ ਗੈਰ-ਕਾਨੂੰਨੀ ਚਾਲ 'ਤੇ ਇੱਕ ਚੇਤਾਵਨੀ ਬੀਪ ♟️ EEPROM ਵਿੱਚ ਸੁਰੱਖਿਅਤ ਕੀਤਾ ਗਿਆ ਟੱਚ ਕੈਲੀਬ੍ਰੇਸ਼ਨ 🛠️ ਹਾਰਡਵੇਅਰ • ਟੀਨਸੀ 4.0 (600 MHz ARM Cortex-M7, 1 MB RAM, 2 MB ਫਲੈਸ਼) • 2.8" ILI9341 320×240 SPI TFT XPT2046 ਟੱਚ • ਪੈਸਿਵ ਬਜ਼ਰ • ਕੁਝ ਜੰਪਰ ਵਾਇਰ 💾 ਸਰੋਤ ਕੋਡ, ਵਾਇਰਿੰਗ ਅਤੇ ਬਿਲਡ ਨਿਰਦੇਸ਼ KrisKasprzak/TeensyChess GPLv3 ਦੇ ਅਧੀਨ ਮੁਫ਼ਤ ਅਤੇ ਓਪਨ ਸੋਰਸ, ਜਿਵੇਂ ਕਿ ਸਟਾਕਫਿਸ਼ ਖੁਦ। 🙏 ਕ੍ਰੈਡਿਟ ਸਟਾਕਫਿਸ਼ ਡਿਵੈਲਪਰਾਂ ਦੁਆਰਾ ਸਟਾਕਫਿਸ਼: stockfishchess.org ਟੀਨਸੀ ਅਤੇ ਡਿਸਪਲੇ/ਟਚ ਲਾਇਬ੍ਰੇਰੀਆਂ ਪਾਲ ਸਟੋਫ੍ਰੇਗਨ / PJRC ਦੁਆਰਾ: pjrc.com ਟੀਨਸੀਫਿਸ਼ ਇੱਕ ਅਣਅਧਿਕਾਰਤ ਪੋਰਟ ਹੈ ਅਤੇ ਸਟਾਕਫਿਸ਼ ਪ੍ਰੋਜੈਕਟ ਨਾਲ ਸੰਬੰਧਿਤ ਨਹੀਂ ਹੈ। 👍 ਜੇਕਰ ਤੁਹਾਨੂੰ ਇਹ ਪਸੰਦ ਆਇਆ ਹੈ, ਤਾਂ ਹੋਰ ਮਾਈਕ੍ਰੋਕੰਟਰੋਲਰ ਪ੍ਰੋਜੈਕਟਾਂ ਲਈ ਗਾਹਕ ਬਣੋ, ਅਤੇ ਮੈਨੂੰ ਟਿੱਪਣੀਆਂ ਵਿੱਚ ਦੱਸੋ: ਕੀ ਤੁਸੀਂ 20 ਪੱਧਰ 'ਤੇ ਟੀਨਸੀਫਿਸ਼ ਨੂੰ ਹਰਾ ਸਕਦੇ ਹੋ? #ਸਟਾਕਫਿਸ਼ #ਟੀਨਸੀ #ਸ਼ਤਰੰਜ #ਆਰਡੂਇਨੋ #ਮਾਈਕ੍ਰੋਕੰਟਰੋਲਰ #DIY #ਸ਼ਤਰੰਜ ਇੰਜਣ #ਇਲੈਕਟ੍ਰਾਨਿਕਸ [pl] Szachy Stockfish na Teensy 4.0 Przeniosłem Stockfisha, legendarny silnik szachowy open-source, na mikrokontroler Teensy 4.0 za 24 dolary z 2,8-calowym ekranem dotykowym i teraz nie mogę pobić własnego projektu. ♟️🔥 Wszystko działa na procesorze Teensy ARM Cortex-M7 o taktowaniu 600 MHz: bez komputera. Wystarczy wybrać figurę, dotknąć miejsca, w którym się znajduje, a TeensyFish (mój port Stockfisha) odpowie w ciągu kilku sekund. 🧠 JAK STOCKFISH PASUJE DO MIKROKONTROLERA? Nowoczesny Stockfish wykorzystuje sieć neuronową NNUE o rozmiarze kilkudziesięciu megabajtów, ale Teensy ma tylko 2 MB pamięci flash i 1 MB pamięci RAM. TeensyFish zachowuje więc nowoczesną tablicę wyszukiwania, generowania ruchów i transpozycji Stockfisha, a sieć neuronową zastępuje ręcznie stworzoną ewaluacją ze Stockfisha 11. Ogromne tablice wyszukiwania zastąpiono kompaktowymi sztuczkami bitowymi, a pamięć zmieściła się w obu Banki RAM. Nadal jest wystarczająco mocne, by zmiażdżyć większość graczy klubowych przy pełnej sile. Czy ja to rozgryzłem? Jasne, że nie, ale Claude Code i Opus 5.5 tak. ✨ FUNKCJE ♟️ 21 poziomów trudności, od początkującego do pełnego ♟️ Graj białymi lub czarnymi (plansza się odwraca) ♟️ Dotknij, aby wykonać ruch, z kropkami legalnych ruchów i podświetleniem ostatniego ruchu ♟️ Przycisk WSKAZÓWKA: silnik sugeruje najlepszy ruch ♟️ Przyciski COFNIJ i NOWA GRA ♟️ Punktacja materiałowa i pasek oceny na żywo ♟️ Wykrywanie mata, pata i remisu, a także promocja pionka ♟️ Brzęczyk klika przy każdym ruchu i sygnał ostrzegawczy przy nielegalnych ruchach ♟️ Kalibracja dotyku zapisana w pamięci EEPROM 🛠️ SPRZĘT • Teensy 4.0 (600 MHz ARM Cortex-M7, 1 MB RAM, 2 MB flash) • 2,8" ILI9341 320×240 SPI TFT z ekranem dotykowym XPT2046 • Pasywny brzęczyk • Kilka przewodów połączeniowych 💾 KOD ŹRÓDŁOWY, OKABLOWANIE I INSTRUKCJA BUDOWY KrisKasprzak/TeensyChess Darmowy i otwarty kod źródłowy na licencji GPLv3, podobnie jak sam Stockfish. 🙏 UZNANIA Stockfish autorstwa twórców Stockfish: stockfishchess.org Teensy i biblioteki wyświetlania/dotyku autorstwa Paula Stoffregena / PJRC: pjrc.com TeensyFish to nieoficjalny port i nie jest powiązany z projektem Stockfish. 👍 Jeśli Ci się podobało, zasubskrybuj, aby otrzymywać więcej projektów mikrokontrolerów i daj znać w komentarzach: czy TY pokonałbyś TeensyFish na 20. poziomie? #Stockfish #Teensy #Szachy #Arduino #Mikrokontroler #Zrób to sam #SilnikSzachowy #Elektronika [pt-BR] Xadrez com Stockfish no Teensy 4.0 Eu portei o Stockfish, o lendário motor de xadrez de código aberto, para um microcontrolador Teensy 4.0 de US$ 24 com uma tela sensível ao toque de 2,8 polegadas, e agora não consigo vencer meu próprio projeto. ♟️🔥 Tudo roda no ARM Cortex-M7 de 600 MHz do Teensy: sem PC, basta escolher uma peça, tocar onde ela vai e o TeensyFish (minha adaptação do Stockfish) responde em segundos. 🧠 COMO O STOCKFISH CABE EM UM MICROCONTROLADOR? O Stockfish moderno usa uma rede neural NNUE que tem dezenas de megabytes, mas o Teensy tem apenas 2 MB de flash e 1 MB de RAM. Então, o TeensyFish mantém a busca moderna, a geração de movimentos e a tabela de transposição do Stockfish e troca a rede neural pela avaliação feita à mão do Stockfish 11. Enormes tabelas de consulta foram substituídas por truques de bits compactos e a memória foi comprimida em ambos os bancos de RAM. Ainda é Suficientemente forte para derrotar a maioria dos jogadores de clube em sua força máxima. Eu descobri isso? Claro que não, mas Claude Code e Opus 5.5 descobriram. ✨ RECURSOS ♟️ 21 níveis de dificuldade, do iniciante ao profissional ♟️ Jogue com as brancas ou pretas (o tabuleiro inverte) ♟️ Toque para mover, com pontos para movimentos legais e destaque do último movimento ♟️ Botão DICA: o motor sugere seu melhor movimento ♟️ Botões DESFAZER e NOVO JOGO ♟️ Pontuação de material e barra de avaliação ao vivo ♟️ Detecção de xeque-mate, empate por afogamento e empate, além de promoção de peão ♟️ Alerta sonoro a cada movimento e um bipe de aviso para movimentos ilegais ♟️ Calibração de toque salva na EEPROM 🛠️ HARDWARE • Teensy 4.0 (ARM Cortex-M7 de 600 MHz, 1 MB de RAM, 2 MB de memória flash) • Tela TFT SPI ILI9341 de 2,8" com resolução de 320x240 e touchscreen XPT2046 • Buzzer passivo • Alguns fios jumper 💾 CÓDIGO-FONTE, INSTRUÇÕES DE FIAÇÃO E MONTAGEM KrisKasprzak/TeensyChess Gratuito e de código aberto sob a licença GPLv3, assim como o próprio Stockfish. 🙏 CRÉDITOS Stockfish pelos desenvolvedores do Stockfish: stockfishchess.org Teensy e as bibliotecas de display/touch por Paul Stoffregen / PJRC: pjrc.com TeensyFish é uma adaptação não oficial e não tem vínculo com o projeto Stockfish. 👍 Se você gostou, inscreva-se para mais projetos de microcontroladores e me diga nos comentários: você conseguiria vencer o TeensyFish no nível 20? #Stockfish #Teensy #Xadrez #Arduino #Microcontrolador #FaçaVocêMesmo #MotorDeXadrez #Eletrônica [ru] Шахматы Stockfish на Teensy 4.0 Я портировал Stockfish, легендарный шахматный движок с открытым исходным кодом, на микроконтроллер Teensy 4.0 за 24 доллара с 2,8-дюймовым сенсорным экраном, и теперь я не могу превзойти свой собственный проект. ♟️🔥 Всё работает на 600 МГц ARM Cortex-M7 Teensy: никакого ПК, просто выберите фигуру, коснитесь места её перемещения, и TeensyFish (мой порт Stockfish) ответит в течение нескольких секунд. 🧠 КАК STOCKFISH УМЕЕТ РАБОТАТЬ НА МИКРОКОНТРОЛЛЕРЕ? Современный Stockfish использует нейронную сеть NNUE, занимающую десятки мегабайт, но у Teensy всего 2 МБ флэш-памяти и 1 МБ ОЗУ. Поэтому TeensyFish сохраняет современный поиск, генерацию ходов и таблицу транспозиции Stockfish, а нейронную сеть заменяет на вручную созданную оценку из Stockfish 11. Огромные таблицы поиска были заменены компактными битовыми трюками, а память была втиснута в оба блока ОЗУ. Она по-прежнему достаточно сильна, чтобы сокрушить большинство клубных игроков на полной силе. Я это придумал? Конечно, нет, но Клод Код и Opus 5.5 это сделали. ✨ ОСОБЕННОСТИ ♟️ 21 уровень сложности, от начинающего до игрока полной силы ♟️ Игра за белых или черных (доска переворачивается) ♟️ Ход касанием, с точками, обозначающими допустимые ходы, и выделением последнего хода ♟️ Кнопка ПОДСКАЗКА: движок предлагает ваш лучший ход ♟️ Кнопки ОТМЕНА и НОВАЯ ИГРА ♟️ Материальный счет и шкала оценки в реальном времени ♟️ Обнаружение мата, пата и ничьей, а также превращение пешки ♟️ Звуковой сигнал при каждом ходе и предупреждающий сигнал при недопустимых ходах ♟️ Калибровка сенсорного экрана сохраняется в EEPROM 🛠️ АППАРАТНОЕ ОБЕСПЕЧЕНИЕ • Teensy 4.0 (600 МГц ARM) Cortex-M7, 1 МБ ОЗУ, 2 МБ флэш-памяти) • 2,8-дюймовый SPI TFT-дисплей ILI9341 320×240 с сенсорным экраном XPT2046 • Пассивный зуммер • Несколько перемычек 💾 ИСХОДНЫЙ КОД, ИНСТРУКЦИИ ПО ПОДКЛЮЧЕНИЮ И СБОРКЕ KrisKasprzak/TeensyChess Бесплатный и открытый исходный код под лицензией GPLv3, как и сам Stockfish. 🙏 АВТОРЫ Stockfish от разработчиков Stockfish: stockfishchess.org Teensy и библиотеки для дисплея/сенсорного управления от Пола Стоффрегена / PJRC: pjrc.com TeensyFish — неофициальный порт и не связан с проектом Stockfish. 👍 Если вам понравилось, подпишитесь на канал, чтобы увидеть больше проектов на микроконтроллерах, и напишите в комментариях: смогли бы ВЫ победить TeensyFish на 20-м уровне? #Stockfish #Teensy #Chess #Arduino #Microcontroller #DIY #ChessEngine #Electronics [ta] Teensy 4.0-இல் Stockfish சதுரங்கம் புகழ்பெற்ற ஓப்பன்-சோர்ஸ் செஸ் எஞ்சினான ஸ்டாக்ஃபிஷை, 2.8" தொடுதிரை கொண்ட $24 டீன்ஸி 4.0 மைக்ரோகண்ட்ரோலருக்கு நான் போர்ட் செய்தேன், இப்போது என் சொந்த ப்ராஜெக்ட்டையே என்னால் வெல்ல முடியவில்லை. ♟️🔥 எல்லாம் டீன்ஸியின் 600 MHz ARM Cortex-M7-ல் இயங்குகிறது: கணினி தேவையில்லை, ஒரு காயைத் தேர்ந்தெடுத்து, அது செல்ல வேண்டிய இடத்தில் தட்டினால் போதும், டீன்ஸிஃபிஷ் (எனது ஸ்டாக்ஃபிஷ் போர்ட்) சில நொடிகளில் பதிலளித்துவிடும். 🧠 ஒரு மைக்ரோகண்ட்ரோலரில் ஸ்டாக்ஃபிஷ் எப்படிப் பொருந்துகிறது? நவீன ஸ்டாக்ஃபிஷ் பல பத்து மெகாபைட் அளவுள்ள NNUE நியூரல் நெட்வொர்க்கைப் பயன்படுத்துகிறது, ஆனால் டீன்ஸியில் 2 MB ஃபிளாஷ் மற்றும் 1 MB ரேம் மட்டுமே உள்ளது. எனவே டீன்ஸிஃபிஷ், ஸ்டாக்ஃபிஷின் நவீன தேடல், நகர்வு உருவாக்கம் மற்றும் இடமாற்ற அட்டவணையைத் தக்கவைத்துக்கொண்டு, நியூரல் நெட்வொர்க்கிற்குப் பதிலாக ஸ்டாக்ஃபிஷ் 11-இன் கைவினை மதிப்பீட்டைப் பயன்படுத்துகிறது. பெரிய லுக்ப் டேபிள்கள் கச்சிதமான பிட் ட்ரிக்ஸ்களால் மாற்றப்பட்டன, மேலும் மெமரி இரண்டு ரேம் பேங்குகளிலும் திணிக்கப்பட்டது. இது முழு பலத்துடன் இருக்கும் பெரும்பாலான கிளப் வீரர்களை நசுக்கும் அளவுக்கு இன்னும் வலிமையானது. இதை நான் கண்டுபிடித்தேனா? நிச்சயமாக இல்லை, ஆனால் கிளாட் கோட் மற்றும் ஓபஸ் 5.5 கண்டுபிடித்தன. ✨ அம்சங்கள் ♟️ ஆரம்ப நிலை முதல் முழு பலம் வரை 21 சிரம நிலைகள் ♟️ வெள்ளை அல்லது கருப்பு காய்களுடன் விளையாடுங்கள் (பலகை புரளும்) ♟️ நகர்த்த தொடவும், சட்டப்பூர்வமான நகர்வு புள்ளிகள் மற்றும் கடைசி நகர்வு சிறப்பம்சங்களுடன் ♟️ குறிப்பு பொத்தான்: உங்கள் சிறந்த நகர்வை இயந்திரம் பரிந்துரைக்கிறது ♟️ செயல்தவிர் (UNDO) மற்றும் புதிய விளையாட்டு (NEW GAME) பொத்தான்கள் ♟️ காய்களின் எண்ணிக்கை மற்றும் நேரடி மதிப்பீட்டுப் பட்டை ♟️ செக்மேட், ஸ்டால்மேட் மற்றும் டிரா கண்டறிதல், மேலும் சிப்பாய் பதவி உயர்வு ♟️ ஒவ்வொரு நகர்விலும் பஸர் ஒலிக்கும், மற்றும் சட்டவிரோத நகர்வுகளுக்கு எச்சரிக்கை ஒலி ♟️ தொடு அளவுத்திருத்தம் EEPROM-இல் சேமிக்கப்படுகிறது 🛠️ வன்பொருள் • டீன்ஸி 4.0 (600 MHz ARM Cortex-M7, 1 2 MB ரேம், 2 MB ஃபிளாஷ்) • XPT2046 டச் கொண்ட 2.8" ILI9341 320×240 SPI TFT • செயலற்ற பஸர் • சில ஜம்பர் வயர்கள் 💾 மூலக் குறியீடு, வயரிங் மற்றும் உருவாக்கும் வழிமுறைகள் KrisKasprzak/TeensyChess ஸ்டாக்ஃபிஷ் போலவே, GPLv3-இன் கீழ் இது ஒரு இலவச மற்றும் திறந்த மூல மென்பொருளாகும். 🙏 நன்றிகள் ஸ்டாக்ஃபிஷ் உருவாக்குநர்களால் உருவாக்கப்பட்ட ஸ்டாக்ஃபிஷ்: stockfishchess.org டீன்ஸி மற்றும் டிஸ்ப்ளே/டச் லைப்ரரிகள் பால் ஸ்டோஃப்ரேகன் / PJRC-ஆல் உருவாக்கப்பட்டவை: pjrc.com டீன்ஸிஃபிஷ் ஒரு அதிகாரப்பூர்வமற்ற போர்ட் ஆகும், மேலும் இது ஸ்டாக்ஃபிஷ் திட்டத்துடன் தொடர்புடையது அல்ல. 👍 இது உங்களுக்குப் பிடித்திருந்தால், மேலும் பல மைக்ரோகண்ட்ரோலர் திட்டங்களுக்கு சப்ஸ்கிரைப் செய்யுங்கள், மேலும் கமெண்ட்களில் சொல்லுங்கள்: லெவல் 20-இல் உங்களால் டீன்ஸிஃபிஷை வெல்ல முடியுமா? #ஸ்டாக்ஃபிஷ் #டீன்ஸி #சதுரங்கம் #ஆர்டுயினோ #மைக்ரோகண்ட்ரோலர் #நீங்களேசெய்யுங்கள் #சதுரங்கஎஞ்சின் #மின்னணுவியல் [te] Teensy 4.0లో స్టాక్‌ఫిష్ చెస్ ప్రఖ్యాత ఓపెన్-సోర్స్ చెస్ ఇంజిన్ అయిన స్టాక్‌ఫిష్‌ను, నేను 2.8" టచ్ స్క్రీన్ ఉన్న $24 విలువైన టీన్సీ 4.0 మైక్రోకంట్రోలర్‌కు పోర్ట్ చేశాను, ఇప్పుడు నా సొంత ప్రాజెక్ట్‌ను కూడా నేనే అధిగమించలేకపోతున్నాను. ♟️🔥 అన్నీ టీన్సీ యొక్క 600 MHz ARM కార్టెక్స్-M7 మీద నడుస్తాయి: PC అవసరం లేదు, కేవలం ఒక పావును ఎంచుకోండి, అది వెళ్లాల్సిన చోట ట్యాప్ చేయండి, మరియు టీన్సీఫిష్ (నా స్టాక్‌ఫిష్ పోర్ట్) కొన్ని సెకన్లలో సమాధానం ఇస్తుంది. 🧠 మైక్రోకంట్రోలర్‌లో స్టాక్‌ఫిష్ ఎలా సరిపోతుంది? ఆధునిక స్టాక్‌ఫిష్ పదుల మెగాబైట్ల పరిమాణంలో ఉండే NNUE న్యూరల్ నెట్‌వర్క్‌ను ఉపయోగిస్తుంది, కానీ టీన్సీలో కేవలం 2 MB ఫ్లాష్ మరియు 1 MB RAM మాత్రమే ఉన్నాయి. కాబట్టి టీన్సీఫిష్, స్టాక్‌ఫిష్ యొక్క ఆధునిక సెర్చ్, మూవ్ జనరేషన్ మరియు ట్రాన్స్‌పొజిషన్ టేబుల్‌ను అలాగే ఉంచుకుని, న్యూరల్ నెట్‌వర్క్‌కు బదులుగా స్టాక్‌ఫిష్ 11 నుండి తీసుకున్న చేతితో రూపొందించిన ఎవాల్యుయేషన్‌ను ఉపయోగిస్తుంది. భారీ లుకప్ టేబుల్స్ స్థానంలో కాంపాక్ట్ బిట్ ట్రిక్స్‌ను ఉపయోగించారు, మరియు మెమరీని రెండు RAM బ్యాంకులలోకి కుదించారు. ఇది పూర్తి శక్తితో చాలా క్లబ్ ప్లేయర్‌లను చిత్తు చేయడానికి ఇప్పటికీ తగినంత బలంగా ఉంది. నేను దీన్ని కనుగొన్నానా? ఖచ్చితంగా కాదు, కానీ క్లాడ్ కోడ్ మరియు ఓపస్ 5.5 కనుగొన్నాయి. ✨ ఫీచర్లు ♟️ ప్రారంభ స్థాయి నుండి పూర్తి శక్తి వరకు 21 కష్టతర స్థాయిలు ♟️ తెలుపు లేదా నలుపు రంగుతో ఆడండి (బోర్డు తిరుగుతుంది) ♟️ కదలడానికి టచ్ చేయండి, చట్టబద్ధమైన-కదలిక చుక్కలు మరియు చివరి-కదలిక హైలైట్‌లతో ♟️ సూచన బటన్: ఇంజిన్ మీ ఉత్తమ కదలికను సూచిస్తుంది ♟️ అన్డు మరియు కొత్త గేమ్ బటన్లు ♟️ మెటీరియల్ స్కోర్ మరియు లైవ్ ఎవాల్యుయేషన్ బార్ ♟️ చెక్‌మేట్, స్టేల్‌మేట్ మరియు డ్రాను గుర్తించడం, అదనంగా పాన్ ప్రమోషన్ ♟️ ప్రతి కదలికపై బజర్ క్లిక్ చేస్తుంది, మరియు చట్టవిరుద్ధమైన కదలికలపై హెచ్చరిక బీప్ వస్తుంది ♟️ టచ్ కాలిబ్రేషన్ EEPROMలో సేవ్ చేయబడుతుంది 🛠️ హార్డ్‌వేర్ • టీన్సీ 4.0 (600 MHz ARM కార్టెక్స్-M7, 1 MB RAM, 2 MB ఫ్లాష్) • XPT2046 టచ్‌తో కూడిన 2.8" ILI9341 320×240 SPI TFT • పాసివ్ బజర్ • కొన్ని జంపర్ వైర్లు 💾 సోర్స్ కోడ్, వైరింగ్ మరియు బిల్డ్ సూచనలు KrisKasprzak/TeensyChess స్టాక్‌ఫిష్ లాగే, ఇది కూడా GPLv3 క్రింద ఉచితం మరియు ఓపెన్ సోర్స్. 🙏 క్రెడిట్స్ స్టాక్‌ఫిష్ డెవలపర్‌లచే స్టాక్‌ఫిష్: stockfishchess.org పాల్ స్టోఫ్రెగెన్ / PJRC చే టీన్సీ మరియు డిస్‌ప్లే/టచ్ లైబ్రరీలు: pjrc.com టీన్సీఫిష్ ఒక అనధికారిక పోర్ట్ మరియు దీనికి స్టాక్‌ఫిష్ ప్రాజెక్ట్‌తో ఎలాంటి సంబంధం లేదు. 👍 మీకు ఇది నచ్చితే, మరిన్ని మైక్రోకంట్రోలర్ ప్రాజెక్ట్‌ల కోసం సబ్‌స్క్రైబ్ చేసుకోండి, మరియు కామెంట్స్‌లో నాకు చెప్పండి: మీరు లెవెల్ 20లో టీన్సీఫిష్‌ను ఓడించగలరా? #స్టాక్‌ఫిష్ #టీన్సీ #చెస్ #ఆర్డుయినో #మైక్రోకంట్రోలర్ #స్వయంగాచేయండి #చెస్ఇంజిన్ #ఎలక్ట్రానిక్స్ [uk] Шахи Stockfish на Teensy 4.0 Я портував Stockfish, легендарний шаховий двигун з відкритим кодом, на мікроконтролер Teensy 4.0 за 24 долари з 2,8-дюймовим сенсорним екраном, і тепер не можу перевершити власний проєкт. ♟️🔥 Все працює на ARM Cortex-M7 від Teensy з частотою 600 МГц: жодного ПК, просто виберіть фігуру, торкніться куди вона йде, і TeensyFish (мій порт Stockfish) відповідає протягом кількох секунд. 🧠 ЯК STOCKFISH ВСТАНОВЛЮЄТЬСЯ НА МІКРОКОНТРОЛЕР? Сучасний Stockfish використовує нейронну мережу NNUE, яка має розмір десятків мегабайт, але Teensy має лише 2 МБ флеш-пам'яті та 1 МБ оперативної пам'яті. Тож TeensyFish зберігає сучасну таблицю пошуку, генерації ходів та транспозиції Stockfish, а нейронну мережу замінює на ручну обчислення зі Stockfish 11. Величезні таблиці пошуку були замінені компактними біт-трюками, а пам'ять була втиснута в обидва банки оперативної пам'яті. Вона все ще достатньо потужна, щоб розчавити більшість клубних гравців на повну силу. Чи я здогадався? це вийшло? Звичайно, ні, але Claude Code та Opus 5.5 це зробили. ✨ ОСОБЛИВОСТІ ♟️ 21 рівень складності, від новачка до повної сили ♟️ Грайте за білих або чорних (дошка перевертається) ♟️ Торкніться, щоб йти, з крапками дозволених ходів та підсвічуванням останнього ходу ♟️ Кнопка ПІДКАЗКИ: движок пропонує ваш найкращий хід ♟️ Кнопки СКАСУВАТИ та НОВА ГРА ♟️ Індикатор матеріального рахунку та оцінки в реальному часі ♟️ Виявлення мату, пату та нічиєї, а також просування пішака ♟️ Звуковий сигнал клацає на кожному ході та попереджувальний звуковий сигнал про недопустимі ходи ♟️ Калібрування сенсорного керування зберігається в EEPROM 🛠️ АПАРАТНЕ ЗАБЕЗПЕЧЕННЯ • Teensy 4.0 (600 MHz ARM Cortex-M7, 1 МБ ОЗП, 2 МБ флеш-пам'яті) • 2.8-дюймовий ILI9341 320×240 SPI TFT з сенсорним XPT2046 • Пасивний зумер • Кілька перемичок 💾 ВИХІДНИЙ КОД, ІНСТРУКЦІЇ З ПІДКЛЮЧЕННЯ ТА ЗБІРКИ KrisKasprzak/TeensyChess Безкоштовний та з відкритим вихідним кодом під ліцензією GPLv3, як і сам Stockfish. 🙏 ТИТРІ Stockfish від розробників Stockfish: stockfishchess.org Teensy та бібліотеки дисплея/сенсорного керування від Paul Stoffregen / PJRC: pjrc.com TeensyFish — це неофіційний порт, який не пов'язаний з проектом Stockfish. 👍 Якщо вам сподобалося, підпишіться на нові проекти з мікроконтролерами та напишіть мені в коментарях: чи зможете ВИ перемогти TeensyFish на 20 рівні? #Stockfish #Teensy #Chess #Arduino #Мікроконтролер #DIY #ChessEngine #Електроніка

  21. X@kscius · 1 like · 17 views

    From Mexico: i18n shouldn't be a copy-paste chore. lingodotdev's CLI (Apache-2.0, 5399 stars): lingo push sends language files to a localization engine, lingo pull writes translations back. 18 formats, runs in CI, and a GitHub App opens translation PRs. lingodotdev/lingo.dev t.co

  22. X@vinhnx · 1 like · 207 views

    VT Code Desktop is live. Rust + gpui (combine with gpui-kit), with a local JSON-RPC bridge to VT Code's existing agent runloop. Same CLI config, credentials, sandbox policies, and session persistence. Now with a native macOS UI. Open source, macOS 15+. vinhnx/VTCode t.co

  23. Serverless applications on AWS with Lambda using Java 25, API Gateway and Aurora DSQL - Part 9 Using Container Image with SnapStart and priming approach Introduction In part 8 of the series, we learned how to convert the sample application to one using a container image as a deployment artifact on AWS Lambda and measured the performance of the Lambda functions. We observed that the Lambda cold start times are quite high. In this part, we'll enable SnapStart on the Lambda functions using a container image. We'll also apply priming techniques and measure the performance of the Lambda functions for all scenarios. You can find the final version of our sample applications, which we can deploy on AWS Lambda as a container image, in the following GitHub repositories: - Sample application with JDBC and Hikari connection pool in the aws-lambda-java-25-aurora-dsql-as-container-image repository. - Sample application with Hibernate and Hikari connection pool in the aws-lambda-java-25-hibernate-aurora-dsql-as-container-image repository. Besides the previous part, please read the following articles in this series to grasp the general concepts: - Part 3 Introducing Lambda SnapStart - Part 4 SnapStart and DSQL request priming - Part 5 SnapStart and full priming The business logic required to implement the Lambda SnapStart priming approaches and the measurement design is the same. The changes that we need to make for each Lambda function in the SAM templates of both projects are the same as those we covered in part 8. Measurements of cold and warm start times of our application with JDBC and Hikari connection pool using a Container Image For the sake of completeness, we provide the measurements for the "No SnapStart enabled" approach from part 8. Cold (c) and warm (w) start time with _-XX:+TieredCompilation -XX:TieredStopAtLevel=1_ compilation in ms: |Approach| c p50 | c p75 | c p90 |c p99 | c p99.9| c max |w p50 | w p75 | w p90 |w p99 | w p99.9 | w max | |-|----------|-----------|----------|----------|----------|----------|-----------|----------|----------|----------|----------|----------| |No SnapStart enabled|1886|2047|2218|2568|2628|2629|4.90|5.24|5.63|8.00|131.40|380| |SnapStart enabled but no priming applied, all|929|967|1021|1183|1275|1275|5.06|5.46|5.86|8.50|387|854| |SnapStart enabled but no priming applied, last 70|918|953|1018|1180|1180|1180|5.08|5.46|5.86|8.50|387|854| |SnapStart enabled and DSQL database request priming applied, all|587|624|998|1030|1133|1134|5.06|5.46|5.86|8.60|319|762| |SnapStart enabled and DSQL database request priming applied, last 70|585|614|990|1024|1024|1024|5.04|5.41|5.82|8.57|318|762| |SnapStart enabled and full priming applied, all|560|589|698|931|1092|1092|5.02|5.35|5.72|8.67|195|643| |SnapStart enabled and full priming applied, last 70|558|579|641|921|921|921|4.98|5.33|5.72|8.57|194|422| Measurements of cold and warm start times of our application with Hibernate and Hikari connection pool using a Container Image For the sake of completeness, we provide the measurements for the "No SnapStart enabled" approach from part 8. Cold (c) and warm (w) start time with _-XX:+TieredCompilation -XX:TieredStopAtLevel=1_ compilation in ms: |Approach| c p50 | c p75 | c p90 |c p99 | c p99.9| c max |w p50 | w p75 | w p90 |w p99 | w p99.9 | w max | |-|----------|-----------|----------|----------|----------|----------|-----------|----------|----------|----------|----------|----------| |No SnapStart enabled|3971|4150|4229|4660|4914|4914|5.46|5.86|6.30|8.20|203|398| |SnapStart enabled but no priming applied, all|1091|1132|1287|1410|1417|1418|5.55|6.01|6.40|8.53|516|868| |SnapStart enabled but no priming applied, last 70|1080|1099|1151|1236|1236|1236|5.61|6.05|6.50|8.60|513|744| |SnapStart enabled and DSQL database request priming applied, all|938|982|1097|1230|1237|1238|5.59|6.00|6.45|8.46|332|678| |SnapStart enabled and DSQL database request priming applied, last 70|931|969|1012|1202|1202|1202|5.61|6.00|6.43|8.43|316|646| |SnapStart enabled and full priming applied, all|637|666|928|1119|1231|1231|5.61|6.03|6.48|8.77|185|590| |SnapStart enabled and full priming applied, last 70|629|648|706|988|988|988|5.63|6.05|6.50|8.84|182|535| Conclusion In this part, we enabled SnapStart on the Lambda functions using a container image. We also applied priming techniques and measured the performance of the Lambda functions for all scenarios. What we observe is that both cold and warm start times are very competitive when using the container image. Especially if we compare them to the measurements we did for the Lambda Java 25 managed Lambda runtime. See the results in the article SnapStart and full priming for comparison. I especially look for 90th-percentile measurements where the performance of the Lambda function with a container image is significantly better. What we also see is that the effect of the snapshot tiered cache is not so strong for the container images (see the last 70 measurements). With GraalVM Native Image, we have even higher cold and warm start times compared to container images. It also requires quite high effort to create and maintain the GraalVM Native images. For the container image, it is medium effort. For the performance-sensitive Lambda functions, using the container image as the packaging format provides a very good solution. This is especially true when enabling Lambda SnapStart, which recently became available, and implementing priming. Please note that SnapStart charges apply to the container images, while SnapStart for supported Java managed versions remains free on AWS Lambda. So, gaining additional performance with SnapStart for container images comes at an additional cost. That's why choosing a managed Java version versus a container image becomes a cost-performance trade-off. Please also watch out for another series where I use a NoSQL serverless Amazon DynamoDB database instead of Aurora DSQL to do the same Lambda performance measurements. If you like my content, please follow me on GitHub and give my repositories a star! Please also check out my website for more technical content and upcoming public speaking activities.

  24. X@osintpodcast · 2 likes · 107 views

    🐹 In Episode 25 of The OSINT Podcast, host Jake Creps looks at GoSearch for usernames and leaked credentials. Try it here: ibnaleem/gosearch t.co

  25. X@grishahq · 1 like · 77 views

    The AI gave you an answer. Now find the quote in 157 pages. That second job is why recursive-llm v0.6.0 checks quotes against the original page and rejects mismatches. Read the passage. Judge the conclusion. Try it on a report you know: github.com/grishahq/recursive-llm/releases/tag/v0… t.co

  26. DEV@merbayerp · 8 reactions

    I Cut 2,000 Flushes to Zero and fsync Still Returned Success Every time I look at the server that carries this blog, I read the same two numbers, and for a long time I assumed I knew what both of them meant. Last night I saw this: since boot, 186,852,284 flushes completed, and a total of 115,846,756 milliseconds spent on them. The machine has been up for 15 days. So it has shouted "put my data on stable storage" at the disk 186 million times. Then I realised something: a single echo is enough to drive that number to zero. An echo the kernel does not try to stop, prints no warning about, and after which fsync() calls keep returning successfully. I did not try this on my production server — I will explain why at the end. I tried it in an isolated virtual machine on my Mac, and I counted every step. The resulting table is a reminder of how thin the agreement is that we call durability on Linux. Two numbers: where the flush counter lives /proc/diskstats and /sys/block/<device>/stat carry the same 17 fields. The last three are relatively new and most monitoring dashboards never read them: | Field | Meaning | |---|---| | 15 | Milliseconds spent discarding | | 16 | Flush requests completed | | 17 | Milliseconds spent flushing | A small warning: if you try to confirm the field count from the ABI documentation you will get confused, because the sysfs-block document still says the stat file contains 11 fields — it was written before the discard and flush fields were added and never updated. The 17 comes from the iostats document; count from that one. While defining field 16, the kernel documentation sets up two traps in two sentences: the block layer combines flush requests and executes at most one at a time, and this counter is not tracked for partitions. I paid for the second sentence while preparing this article; I will get to it shortly. Here is my own server's identity card: Linux 6.8.0-147-generic, a KVM guest, disk /dev/sda (QEMU HARDDISK), with /dev/sda1 mounted as ext4 using rw,relatime,discard,errors=remount-ro,commit=30. The write_cache file says write back, the fua file says 0, and rotational says 0. In other words: the device declares that it has a volatile write cache, it does not support the FUA flag, and it is not a spinning disk. I can divide out the cost of an average flush: 115,846,756 / 186,852,284 ≈ 0.620 ms. Turning that into a fraction of uptime, however, required me to back out of a mistake first; that part is at the end. The lab: counting every flush I ran the measurement inside Docker Desktop's virtual machine; a --privileged container can write to sysfs and there is no customer data there to damage. Identity card: Linux 6.10.14-linuxkit, aarch64, disk /dev/vda (virtio), ext4 on /dev/vda1, and the measurement directory is a named Docker volume — so overlayfs is not in the path and writes land directly on ext4. This disk makes the same declaration as my server's: write_cache is write back and fua is 0. With one difference: under /sys/block/vda/mq there is a single hardware queue. That detail becomes decisive at the end. The measurement tool is a twenty-line C program: it opens a file, does a 4 KiB pwrite followed by an fsync on every iteration, and exits immediately if fsync returns anything but zero. I leave the counting to the kernel rather than the program; I only read fields 16 and 17 before and after the run. The noise floor came first. At idle, 6, 5 and 3 flushes pass in five seconds — roughly one per second. My actual runs take half a second, so that noise stays in single digits, but I did not want to leave it unknown. The first series, with write_cache in its default state (write back), single threaded, 1,000 fsyncs, nine runs — each entry is `elapsed(ms) · flushes · flush_ms`: 478.7 2000 125 492.4 2000 134 484.0 2000 144 453.0 2000 129 462.4 2000 133 467.3 2000 138 485.6 2000 135 457.7 2002 134 468.8 2000 123 median: 468.8 ms | 2000 flushes | 134 ms A thousand fsyncs, two thousand flushes. Exactly 2000 in eight of the nine runs and 2002 in one — the excess being that once-per-second background noise. The ratio is not a coincidence; it is written in the source. Why exactly two The comment at the top of block/blk-flush.c explains that a flush is decomposed into a three-step sequence: PREFLUSH, DATA, POSTFLUSH. In today's mainline, the place that decides which steps actually run is blk_insert_flush(), and the decision hangs on a single condition: if (blk_queue_write_cache(q)) { if (rq->cmd_flags & REQ_PREFLUSH) policy |= REQ_FSEQ_PREFLUSH; if ((rq->cmd_flags & REQ_FUA) && !supports_fua) policy |= REQ_FSEQ_POSTFLUSH; } On the 6.10 the lab runs on, the same decision lives in a separate function, blk_flush_policy(), and reads queue flags; the meaning is identical, but someone grepping 6.10's blk_insert_flush for this will not find it. The same file's header comment states the rule plainly: if the device has a writeback cache and does not support FUA, REQ_PREFLUSH is translated to a PREFLUSH and REQ_FUA to a POSTFLUSH. On my disk the fua file says 0. ext4's jbd2 journal writes the commit block with REQ_PREFLUSH | REQ_FUA when a transaction commits — not once per fsync call, but whenever there is something to commit. In my loop every iteration writes new data, so every fsync forces a commit and the two coincide. Because FUA is unsupported, the second flag turns into a POSTFLUSH. One commit, two flushes. A thousand calls, two thousand flushes. There is also a reason the number is exactly two and not three: jbd2 has two other places where it issues a flush, but one depends on having a separate journal device and the other on the async_commit feature — both are off in my setup. Measurement and source produce the same number; that happens rarely, and when it does you briefly feel like you actually understand the mechanism. !Diagram The critical spot in the diagram is the false branch: a request that lands there never reaches the disk, yet fsync still returns zero. I went down that branch deliberately. One line The write_cache file is readable and writable. The kernel's own ABI documentation says what writing does without leaving any room for escape: writing to this file can change the kernel's view of the device but does not alter the device state, which is why switching from write back to write through may not be safe, since it also eliminates the cache flushes the kernel issues. The documentation says "may not be". I wanted to count how much. Same disk, same program, the only difference being echo "write through" > /sys/block/vda/queue/write_cache. Nine runs again, this time elapsed(ms) · flushes: 270.7 0 259.9 0 265.3 0 263.2 0 275.1 0 342.8 0 260.0 0 262.4 0 287.8 0 median: 265.3 ms | 0 flushes | 0 ms Zero. Zero in all nine runs. None of the thousand fsync calls returned an error — the program would have exited if one had, and it did not. For anyone looking from the application side, nothing changed: fsync was called, it returned successfully, the data is "durable". The disk knows nothing about this conversation. The mechanism is one sentence in the blk-flush.c header comment: if the device has no writeback cache, PREFLUSH and FUA make no difference, and requests carrying no data are completed immediately. The flush request is not going anywhere; it is resolved in software. The kernel is not lying — I lied to it, and it believed me. How much of the saved time can I actually account for The medians: 468.8 ms → 265.3 ms. The same work finished 1.77 times faster. So far so good. The real question is this: how much of that speed-up does the flush time the kernel reported actually explain? The saving is 203.5 ms. The flush time that disappeared is 134 ms. So 66 percent of the speed-up can be read directly out of field 17; the remaining 70 milliseconds I cannot account for. I have a plausible guess — queueing, dispatching and completing a flush as a request has a cost of its own, and field 17 does not capture all of it — but that is a hypothesis, not a measurement. I do not want to round an unmeasured thing up into "I removed the flush, that is where the speed came from". On this disk, which has a single hardware queue, I can compare field 17 against wall-clock time (the header comment's C1 condition: only one flush proceeds at a time), so I can compute the share of each write back run spent executing flushes: a median of 28.5 percent, ranging from 26.1 to 29.8 across the nine runs. A small honesty note: field 17 also includes time the request spends queued, so that share is slightly wider than "time the disk was busy flushing". Had I seen that number in a database benchmark, I would have been excited. Here, though, the gain is pure accounting trickery: what got faster is not the work but the work's guarantee. On a power loss, whatever sits in the device's volatile cache is gone, and because fsync told you "written", your application has no grounds for complaint. ext4's journal does not save you either: the journal's consistency guarantee rests on those flushes actually reaching the disk. In [the run where I enabled fast_commit and watched it never fire across 4,000 fsyncs](mustafaerbay.com.tr) I learned to distrust the journal's counters; here the counter is right and the guarantee is absent. The strings sysfs accepts The queue_wc_store() function uses strncmp to check three strings: write back (10 characters), write through (13 characters) and none (4 characters). The third never appears in the ABI documentation — the docs only describe the first two. Curious, I tried all of them: [write back] ACCEPTED -> write back [write through] ACCEPTED -> write through [none] ACCEPTED -> write through [write backwards] ACCEPTED -> write back [nonetheless] ACCEPTED -> write through [writeback] REJECTED (EINVAL) [hayir] REJECTED (EINVAL) write backwards and nonetheless were accepted, because strncmp only looks at the first n characters — the comparison is a prefix match. Drop the space and write writeback and you get EINVAL. This is not a vulnerability, but for anyone writing configuration management it carries a lesson: the string you write to this file being accepted does not mean the thing you thought you were writing was accepted. Read it back before moving on. Which kernel, which behaviour Memory from training is useless here, because this code moved house within two years. In the 6.10 the lab runs on, the store function keeps the cache view in a queue flag (QUEUE_FLAG_WC) and requires the device to have declared a hardware cache before you can write write back. I tested that: writing write back to the ram0 device, which has no cache at all, returned EINVAL. In today's mainline, the setting has moved into the queue_limits structure and its logic has been inverted: there is now a disable flag called BLK_FLAG_WRITE_CACHE_DISABLED, and the comment in the header file states its purpose outright — do not send FLUSH/FUA commands despite a write cache having been advertised. blk_queue_write_cache() is now computed as "the feature is present and the disable flag is not set", and the hardware requirement in the store function is gone. The practical consequence: a write that was rejected with an error on 6.10 succeeds silently on today's kernel and changes nothing — because clearing a disable flag does not conjure a cache feature that was never there. I did not measure this second half; I derived it by reading the mainline source. I cannot exercise mainline behaviour in my 6.10 lab. I am leaving the distinction visible here, because "the source says so" and "I saw this on screen" are not the same thing. Moving the flag into queue_limits has one more side effect. Drivers only touch their own fields when they update limits — the SCSI disk driver, for instance, writes only the cache and FUA feature bits — and because an update starts from the current limits, a disable flag set by hand stays where it is. So do not rely on the behaviour known from older kernels, where "revalidating the device undoes the setting". A reboot is a different matter: the flag lives in memory and nothing survives the next boot. Where I went wrong reading the counters The partition counter is always zero. My filesystem sits on /dev/vda1, so that is where I would want to watch. But when I read field 16 from the partition, the disk sits at 1,369,613 flushes while the partition shows 0. That is exactly the cost of the documentation's "not tracked for partitions" sentence: if you built your dashboard on the partition, your flush count stays zero forever, and you read that as "no flushes". You cannot derive the flush count from the fsync count. I ran the same 1,000 fsyncs across 8 threads at 125 each instead of on one thread, with write back in place, nine times again: 158.4 504 160.0 502 155.6 500 151.6 502 145.8 500 154.2 500 145.8 500 150.6 500 157.0 504 median: 154.2 ms | 500 flushes Five hundred, not two thousand. Four times fewer, because the block layer double-buffers pending flushes and executes them together: only one flush proceeds at a time, and the requests that pile up while it runs share the next one. As concurrency rises, the flush cost per fsync falls — so "the flush count is high" says nothing on its own and cannot be interpreted without knowing the workload's concurrency. Be careful dividing total flush time by wall-clock time. That is precisely the first thing I did while writing this article: I was about to divide my server's 115,846,756 ms by its 1,296,505 seconds of uptime and write "the machine spent 8.9 percent of its time waiting on flushes". Then I remembered that the flush queue is allocated per hardware queue (hctx->fq) and looked at my server's queue count: there are 18 queues under /sys/block/sda/mq. The "only one flush at a time" guarantee holds per queue, not per disk — so 18 flushes can be in progress at once, and field 17 sums their durations on top of one another. That makes 8.9 percent not a measurement but an upper bound: the true wall-clock share is below it, and with the queues fully busy it could fall to roughly a twentieth of that. There is a more honest way to read the same number: 0.089 is the average number of flushes in flight. Because the lab's vda has a single queue, I can quote the 28.5 percent there as a share; for my server I cannot. That leaves two numbers I can defend on my server: an average of 0.620 ms per flush, and 186.8 million flushes in 15 days. Counting across a ten-second window, I saw 1,038 flushes and 1,384 ms — a momentary average of 1.33 ms, more than double the lifetime average. With a load average of 19.57 that is not surprising, but it shows how fragile the sentence "the average flush is 0.6 ms" really is. Something similar happened in [the article where I cut the request queue from 31 to 1 and measured the IOPS ceiling not moving](mustafaerbay.com.tr): the same sysfs directory, the same kind of wrong summary. Asking the device a second time Up to this point I had built the article on "you cannot tell the kernel's view apart from the device's reality". That was wrong. For SCSI disks there is a second opinion: /sys/class/scsi_disk/<h:c:t:l>/cache_type. Unlike queue/write_cache, this file does not show the kernel's intent but the actual bits read from the device's mode page; and when you write to it, the driver sends a real MODE SELECT command to the device, that is, it genuinely changes the disk. It can take four values, and the fourth is named write back, no read (daft) in the source — kernel developers' humour leaks into the documentation too. On my server I read the two side by side: /sys/block/sda/queue/write_cache = write back /sys/class/scsi_disk/0:0:0:0/cache_type = write back The two say the same thing, so on my disk the kernel's declaration is backed by the device. Had they diverged, I would have known one of them had been changed by hand. I cannot ask the same question of the lab's vda: a virtio disk is not in the scsi_disk class, and there is no cache_type file there. So whether a second opinion exists depends on the device type — present on SCSI/SAS/SATA disks, absent on virtio, and on NVMe the same information comes from the controller's own feature query. So what should you do I did not touch the write_cache file on my server, and I will not. This is not a performance setting; it is changing the kernel's declaration about a device by hand. My list of reasonable uses goes like this: - Look at it to read it. write_cache, fua and fields 16/17 together tell you a disk's durability cost without installing any tooling. Put them on the dashboard — but read them from the disk, not the partition. - If you are suspicious, ask the device. On a SCSI disk, cache_type, sdparm or hdparm -W give you the device's own declaration; on NVMe the same information sits in the controller features. If the two sources diverge, somebody wrote to queue/write_cache by hand. - In stacked setups, do not stop at the bottom disk. LVM, md, dm-crypt and loop devices each have their own write_cache file, and suppressing flushes on the disk underneath lowers the guarantee of every layer above it at once. - Remember the privileged container. The only reason I could run this measurement is that a --privileged container can write to the host's sysfs. On a shared disk, such a container can switch off durability for the whole machine without asking anyone. Keep that in mind when granting containers sysfs write access. - Consider writing write through only if you know the device truly has no volatile cache — a battery- or capacitor-backed RAID controller, say. In that case what you are doing is not lying but correcting the kernel's wrong assumption. Make the decision with a written rationale. - Size the loss. The risk is as much data as the device's volatile cache, which on typical enterprise disks is tens to hundreds of MiB. PostgreSQL, MySQL/InnoDB, etcd and SQLite — anything that pins durability on fsync — will quietly give the wrong answer inside that window. - Do not make it persistent, but do not trust its impermanence either. The setting disappears on reboot, which sounds like good news; buried in a udev rule, though, it travels with you when the hardware changes and nobody notices it is no longer true. Alert on the value changing. Conclusion What I took from this experiment is not the flush counts but a small shift in how I look at sysfs. For years I read the files under /sys/block/*/queue/ as "the place where the device describes itself to me". But some of them are not measurements, they are declarations — and declarations that run in both directions. The kernel writes what the device said there, but I can also write there what I want the kernel to think about the device. The file reads identically in both cases. The consolation: you cannot tell them apart by looking at one file, but the way to tell them apart is not closed. Ask a second source — on a SCSI disk, the device's own mode page — and it becomes clear whether there is a device behind the declaration or just an echo. Trusting a single source is the common cause of every mistake I counted in this article: reading from the partition, looking at a single run, dividing field 17 without knowing the queue count. fsync's contract is therefore more indirect than it looks. It does not say "the data is on stable storage"; it says "based on the information I was given, what needed to be done to make the data durable was done". Whether that information is true is not fsync's problem. The only person who will worry about it is the sysadmin who accepts 186 million flushes in 15 days and agrees to wait on the disk. Official Sources - Block I/O statistics — /proc/diskstats fields (field 16: flush requests completed) - sysfs-block ABI documentation — queue/write_cache and queue/fua definitions - block/blk-flush.c — PREFLUSH/FUA sequencing and flush combining conditions - block/blk-sysfs.c — queue_wc_store() and the strings it accepts - include/linux/blkdev.h — BLK_FLAG_WRITE_CACHE_DISABLED and blk_queue_write_cache() - drivers/scsi/sd.c — the cache_type attribute and its MODE SELECT path

  27. X@howtopam · 4 likes · 423 views

    Elementary X - Transform your Linux system with an elegant Elementary OS theme and sleek macOS window controls, available in both light and dark mode. Fork of the Default Gtk+ Stylesheet for elementary OS with OS X window controls. surajmandalcell/elementary-x t.co

  28. Goodbye :nth-child! How Modern CSS sibling-index() Works Under the Hood --- title: Goodbye :nth-child! How Modern CSS sibling-index() Works Under the Hood published: true tags: css, webdev, frontend, programming --- Ever found yourself writing endless lines of :nth-child(1), :nth-child(2), :nth-child(3) or injecting custom CSS variables via JavaScript just to stagger a list of entrance animations? Modern CSS (Values & Units Module Level 5) introduces two native functions: - sibling-index() — Returns the 1-based index of the element among its siblings. - sibling-count() — Returns the total count of siblings under the parent. Here is the complete video breakdown and live animation: {% youtube qMdy7NDZnRk %} 1. Staggered Delays in Pure CSS .card { animation: cardFadeIn 0.6s cubic-bezier(0.16, 1, 0.3, 1) both; animation-delay: calc(sibling-index() * 120ms); } 2. Dynamic 360° Color Wheels with OKLCH .chip { --hue: calc((sibling-index() / sibling-count()) * 360deg); background: oklch(0.68 0.22 var(--hue)); } 3. Reverse z-Index Overlapping Avatars .avatar { margin-left: -14px; z-index: calc(sibling-count() - sibling-index() + 1); } 🎯 60-Second Challenge: Can You Solve It? Can you write a single calc() formula so the middle item in an odd list of bars gets the largest height/scale? Download the starter HTML file and test your formula: - 📄 GitHub Code Vault: muneebali500/cascadedev-code-vault - Drop your solution in the YouTube comments or right here in the comments below!

  29. Redditu/KeepTheOutliers · r/fivethirtyeight · 470 points · 165 comments

    After last night’s Silver Bulletin update, Democrats would win the Senate 51–49 even accounting for 2024-sized state level polling errors Margin of Error | The 2026 Senate Stress Test A 2024 polling error is unlikely, both because it was a presidential election (as opposed to a midterm) where Trump voters turned out and because pollsters have adjusted their methodology since then, in a way that should reduce bias against republicans. But even if it does occur, Dems will still likely win the Senate. Democrats would also win the Senate under the scenario of either 2018 or 2022 polling error (the past two midterm elections), but not if the polling error reflects that of 2016 or 2020. I built this visualization tool using Claude Code, however, I did not build any actual forecasting model. The results simply reflect: - The polling averages (per Silver Bulletin) for each state... - Plus-or-minus that state's historical polling error (per FiveThirtyEight raw_polls.csv & Silver Bulletin pollster-ratings-silver-bulletin, which I've consolidated here: poll_errors.csv).

  30. Bluesky@sanskarin.bsky.social · 4 likes

    🎬 FrameTrellis v1.4.0 is out! My open-source C++ video editor now features advanced multi-track editing, animated keyframes, SRT subtitles and MP4 export presets up to 4K. Free. Local-first. No cloud required. 🔗 github.com/sanskarIN/frametrellis/releases/tag/v1… #OpenSource #VideoEditing

  31. DEV@sanskarin · 6 reactions

    FrameTrellis v1.4.0 Released: Advanced Timeline Editing, Keyframes, Subtitles & 4K Export FrameTrellis v1.4.0: Advanced Timeline Editing, Keyframes, Subtitles and 4K Export I'm excited to announce FrameTrellis v1.4.0, the latest stable release of my free, open-source, local-first desktop video editor. This release represents a significant expansion of FrameTrellis, moving beyond the reliability-focused v1.3.x releases to introduce more advanced editing, animation, subtitle and export workflows. FrameTrellis is developed using C++20, Qt 6, MLT and FFmpeg, with a focus on native desktop performance, predictable editing and user privacy. 1. More Powerful Multi-Track Editing FrameTrellis v1.4.0 introduces additional ways to work precisely with clips and tracks. Highlights include: - Multi-track clip selection and alignment. - Clip duplication while maintaining relative timing. - Slip and roll editing where source material permits. - Precise frame navigation and timeline zooming. - Timeline markers for review and navigation. - Track reordering, duplication and locking. These improvements make complex timelines easier to navigate and modify without losing control over the edit. 2. Keyframe-Based Animation One of the biggest additions in v1.4.0 is keyframe editing. FrameTrellis now supports animation of: - Audio volume in decibels. - Video and image opacity. - Position. - Scale. - Rotation. These controls allow users to create animated visual and audio changes over time. The release also strengthens the relationship between timeline previews and exported results through automated regression testing. 3. Subtitle Editing and Export Subtitles are an essential part of modern video workflows. With v1.4.0, FrameTrellis adds: - A sequence subtitle track. - UTF-8 SRT import and export. - WebVTT sidecar export. - Subtitle timestamp shifting. - Optional caption burn-in. - Timestamped transcript export. These features provide practical tools for creating accessible and captioned videos. 4. Improved MP4 Export Workflows FrameTrellis continues to focus on H.264 video and AAC audio in MP4 containers. The latest release includes creator-oriented presets for resolutions up to 1080p, 1440p and 4K, while avoiding unnecessary upscaling. Lower-bandwidth review and draft profiles are also available. Users can adjust encoding settings including quality, encoder speed and audio bitrate. 5. Better Project Integrity New editing capabilities also require more robust project handling. FrameTrellis v1.4.0 improves validation of project data, media paths, track names and timeline identifiers. Save operations validate project state before replacing the destination, reducing the chance of overwriting a working project with invalid data. Important: Existing users should back up their projects before upgrading. Files using new v1.4.0 features may not be compatible with v1.3.1. 6. Local-First by Design Privacy remains a central principle of the project. FrameTrellis does not require an account, cloud video processing or telemetry. Editing, preview and export workflows run locally on your computer. The project is developed openly and distributed under the GPL-3.0-or-later license. 7. Download FrameTrellis v1.4.0 The stable release is available on GitHub. Windows: - x64 installer - x64 portable ZIP Linux: Build from source. macOS packages are not available yet. Download and release notes: github.com/sanskarIN/frametrellis/releases/tag/v1… The Windows binaries are not code-signed; SHA-256 checksums are provided for verification. What's Next? FrameTrellis is an actively developed project. Future work will continue to focus on improving editing capabilities, performance, reliability and user experience. I'm particularly interested in feedback from video editors, C++ developers and open-source contributors. If you'd like to follow the project, report an issue or contribute, visit the repository: sanskarIN/frametrellis Thanks for following the development journey! FrameTrellis — Open-source video editing, on your own machine.

  32. Redditu/mysensors · r/homeassistant · 8 points

    SpotNav, one month later: smart EV charging in HA that sets itself up (now at 2.2) A month ago I shared SpotNav here. Since then a handful of people have run it every night on their own chargers, meters and batteries, and their bug reports and debug files have shaped almost every one of the ~25 releases since. Thanks to everyone who tested! The goal hasn't changed: smart charging should be simple. You add SpotNav and it finds your charger, grid meter, home battery and car among the integrations you already have. The card then shows a short Get started list with whatever is still missing or could be improved to unlock more featuers. What it does: - Charges in the cheapest hours before you leave, on solar surplus, or both - Keeps every charger under your main fuse, also next to a home battery - Knows which car is plugged in, from the cars' own data, or from a camera and a local AI model if you like - Learns how much power your car really draws, so "80 % by 07:00" gets the right amount of time - Plan and follow the charge from the Android app too, with a price and plan widget on your home screen Everything runs locally in HA, with no cloud and no account. Prices come from your own Nord Pool integration or a free ENTSO-E key. Confirmed on real hardware: Easee and OCPP (Charge Amps). Zaptec, Wallbox, go-e, Peblar, Tesla Wall Connector and about 25 others are supported but not yet confirmed. If you have one, I'd love to hear how it goes. henrikekblad/spotnav-home-assistant

  33. YouTubeStoatworks Labs · YouTube description · 9 views

    Throw — your clip thrown onto brick, drapes, metal and paper, for Resolume (free, open source) Everything in this video is the plugin's own output, rendered by its offline harness, twtest, running the same plugin class Resolume loads, at 60 fps, over Resolume's own demo clips. It's silent, as nothing in it came from sound. No flashing: measured frame by frame, no second holds more than two changes in brightness, and the biggest is a flash in one of Resolume's clips, not the plugin's doing. --- SW Throw is an FFGL effect for Resolume Arena and Avenue that throws your clip onto a real surface: crumpled paper, a brick wall, corrugated sheet, aluminium tread plate, pleated drapes, weatherboard, glazed tiles, or a height map or photo of your own. The light leaves a lens at a real place in the room, in metres, and you stand somewhere else. So the picture is shaded by angle and distance, coloured by the wall, shadowed by the relief, slides over it as you move, glints off metal, and never reaches black, because a projector can't project black and the room has light of its own. None of it is a filter laid over the picture: each pixel is where a ray from your eye meets the wall, lit by the inverse square and the cosine if the lens can see that spot, and by the room alone if it can't. What's in the video: - the defaults: a 10,000 lumen projector 6 m back throwing NoHopeJustFear_44 onto brick, seen from 2 m to its right, then the same light on Flat, a matte white screen - walking past drapes with Beat 006 on them: the picture's lines bend over the folds, run straight at the lens and bend the other way past it - the projector moving from 6 m left to 6 m right, and the fold shadows swinging over - Aim on Pointed, a keystoned picture, then Lens Shift, square and even - aluminium tread plate and galvanised corrugated sheet under Beat 001, the lens's highlight following you - Crumple from 0 to 1 on Paper, Beat 002's neon tubes kinking at the creases - the room's light from 20 to 800 lux over IntoTheGlow_21, the brick showing through - Depth from flat to four times real on weatherboard, under Metalive 01 Free and open source, MIT. macOS (universal) and Windows. Project page: stoatworks-labs.com User guide: stoatworks-labs.com Try it in a browser: throw-demo.stoatworks-labs.com Download: github.com/stoatworks-labs/throw/releases/tag/v0.… Source: stoatworks-labs/throw Built with AI assistance, directed and reviewed by a human author. An offline harness drives the plugin's own class and checks each claim against a model of its own, in double precision. A flat wall gives the clip back to 3e-7 from any projector and viewer. Every pixel of a tilted plane carries the light its inverse-square-and-cosine closed form says. A recess shows the picture where the parallax formula puts it, to 0.0007 px, and a step's shadow is the closed-form length to within a pixel. Eighteen models I got wrong on purpose and 23 one-character mutants of the shipped code are all caught. At the defaults it costs 0.47 ms of GPU time at 1080p, on a Mac. Where it's been run: the harness on an Apple Silicon Mac (macOS 26). It's never been loaded into Resolume on macOS. On Windows it has been in Resolume: the release's own Windows build loads, registers and renders in Resolume Arena 7.27.1 on software rendering (no GPU), with all 35 controls as declared and Arena's log clean, and 28 of its 29 controls changed a still picture there (the 29th, Surface File, took a height map that File Holds then changed). Not known yet: how it looks on a GPU other than that Mac's, and the frame rate at 4K inside Resolume. The repo's status section has the rest. --- If any of this has been useful, you can chip in. It's all free and it's staying that way, but the test kit doesn't buy itself. GitHub Sponsors: sponsors/stoatworks-labs Ko-fi, one-off, no account: ko-fi.com Patreon: patreon.com

  34. X@PaynMusic · 1 like · 7 views

    @grok Precisely!! Even on my pc, the only one allowed in the room is @grok GalacticOrgOfDev/VSGrok #GrokPurist

  35. Lo hiciste bien tres dias. Luego llego la vida. Aqui tienes un sistema de habitos que sobrevive a eso. (en espanol) Empiezas un habito el lunes, con toda la energia. El jueves ya fallaste un dia, y el domingo el plan entero esta en silencio en la basura. No porque seas flojo. Porque el plan fue hecho para una semana perfecta, y tu no vives una semana perfecta. Aqui tienes un sistema mas pequeno. Un habito, una marca al dia, una revision de cinco minutos cada semana. No necesitas ninguna app. Una nota en el telefono o un calendario de papel sirve. 1. Elige un habito, y achicalo hasta que parezca demasiado facil Elige exactamente un habito. No tres, no cinco. Uno. Luego achicalo hasta que puedas hacerlo incluso en tu peor dia de la semana. Esa es la prueba. Si la respuesta es no, todavia es demasiado grande. - "Caminar todos los dias" se vuelve "caminar hasta el buzon y volver." - "Leer mas" se vuelve "leer una pagina antes de dormir." - "Publicar todos los dias" se vuelve "escribir una frase para la publicacion de manana." Un habito que de verdad haces le gana a un habito que admiras. Puedes hacerlo mas grande despues, tras dos semanas completas de marcas diarias. No lo agrandes en la primera semana. 2. Una marca al dia, nada mas Cada dia, marca una sola cosa: lo hiciste o no. Eso es todo. Usa una linea por dia, siempre en el mismo lugar: - Lun: si - Mar: si - Mie: no, dia de enfermedad - Jue: si Un "no" no es un fracaso. Es informacion. Escribe una razon corta al lado si la sabes: enfermo, de viaje, se me olvido. No tener razon tambien esta bien. Lo que importa es la marca, no la excusa. Nunca rellenes una semana entera de memoria el domingo. Si un dia no tiene marca, se queda en blanco, y sigues adelante. Ejemplo: una duena de un negocio pequeno quiere hacer seguimiento a sus clientes todos los dias, pero siempre se le escapa. Lo achica a "enviar un mensaje de seguimiento antes del almuerzo," y lo marca en una nota del telefono. Lunes si, martes si, miercoles no (todo el dia manejando), jueves si. El viernes ya ve el patron con claridad: los dias de manejo son el hueco, no la fuerza de voluntad. Quieres una habilidad gratis nueva como esta cada semana, lista para pegar en ChatGPT, Claude o Grok? Registrate aqui: lil-nicky-ai.kit.com 3. La regla del dia perdido: nunca falles dos veces Un dia perdido es normal. Dos dias seguidos perdidos son el punto de peligro. Ahi es cuando la mayoria abandona en silencio. Asi que la regla es simple: nunca falles dos veces. Despues de un dia perdido, el unico trabajo del dia siguiente es recuperar la marca. Haz la version mas pequena del habito, incluso la version del buzon, y marcala. No estas compensando ayer. Solo estas reiniciando la racha. Si pierdes una semana entera, no reinicies todo el plan. Achica el habito otra vez y empieza una racha nueva. El habito era demasiado grande, no tu. 4. La revision semanal de cinco minutos Una vez por semana, el mismo dia cada semana, dedica cinco minutos a tres preguntas: 1. Cuantas marcas consegui esta semana? Cuentelas, sin juzgarte. 2. Que se interpuso en los dias perdidos, si hubo alguno? Busca un patron, no una confesion completa. "Siempre lo pierdo los dias que manejo" es un patron util. 3. Un arreglo para la proxima semana, o ninguno. Un arreglo significa cambiar la hora, el lugar, o el tamano del habito. "Hacerlo justo despues del desayuno en vez de en la noche" es un arreglo. "Esforzarme mas" no es un arreglo. Si conseguiste siete marcas, deja el habito exactamente igual otra semana. Si conseguiste cuatro o menos, achicalo otra vez antes de culparte. Lo que esto no hace Esto no planifica tu semana, no organiza tu trabajo, ni arregla una agenda sobrecargada. Rastrea un habito, nada mas. Un habito, una marca, una revision semanal. Ese es todo el sistema, y por eso aguanta. Si quieres el conjunto completo para planificacion diaria, correo, reuniones y revision semanal, ese es un trabajo mayor, y vive en un pack de pago, no en esta habilidad gratis. Pruebalo gratis La habilidad completa Habit Tracker es gratis para copiar y usar aqui: github.com/lilnickyai/claude-code-skills-samples/… Quieres el conjunto completo para el dia a dia? El pack Everyday Productivity Skills cubre planificacion diaria, correo, reuniones y revision semanal por $19: littlenova5.gumroad.com Y si quieres una habilidad gratis nueva como esta cada semana, registrate aqui: lil-nicky-ai.kit.com Version original en ingles: dev.to Nota: el pack de pago y la lista de correo estan en ingles por ahora.

  36. i think it's related to this, which is a library i use in my python-based bluesky poster microservice. python/typin... but i pin the versions on everything this app uses for this exact reason. hmmmmmm

  37. X@so_sthbryan · 1 like · 34 views

    GST billing just got free. No more cheap workarounds. IamRamgarhia/Free-GST-Billing-Software: • Free, open source GST invoice and billing • Tax invoice, proforma, credit notes • Multi-currency support The free billing stack for small businesses. IamRamgarhia/Free-GST-Billing-Software

  38. Redditu/pmttyji · r/AI_India · 17 points · 2 comments

    maya-research/maya2-native · Hugging Face Maya 2 Native Open speech. Native voices. Streaming text-to-speech for 11 Indian languages and English. 12 languages · 20 voices · Voice cloning · Apache-2.0 Listen · Get started · Explore voices · Benchmarks · Evaluation · Code Maya 2 Native brings streaming speech generation to the languages people use every day. Built by Maya Research, it generates 24 kHz speech in 12 languages, with 20 built-in voices and zero-shot voice cloning from 3–10 seconds of reference audio. A voice can speak across languages: a Hindi reference can become Tamil speech. Use it to give a voice agent its next turn, read a story in a familiar language, or build a multilingual interface you can host yourself. The release includes open weights and inference code, with a Python API, an OpenAI-compatible speech endpoint, and WebSocket streaming. Continuous batching and CUDA graphs support concurrent generation. At a glance |Model at a glance|| |:-|:-| |Languages|Assamese, Bengali, English, Gujarati, Hindi, Kannada, Malayalam, Marathi, Odia, Punjabi, Tamil, Telugu| |Model size|2.50B unique parameters; approximately 5.0 GB of BF16 weights| |Audio|24 kHz, mono; streaming in 80 ms audio frames| |Voices|20 built-in voices; zero-shot and cross-lingual voice cloning| |Interfaces|Python, OpenAI-compatible speech endpoint, WebSocket streaming| |License|Apache-2.0; see component licenses| |Checkpoint release|1.0 · October 25, 2026|

  39. Redditu/apwontmiss · r/LinuxPorn · 85 points · 6 comments

    Never using windows again Decided to wipe the entire Windows installation and go all in on Arch Linux running Hyprland. It feels good having full control over my machine. No limitations, just my system configured the way I want it. Still tweaking a few things, but I'm loving the setup so far. Dotfiles: 43PR/dotfiles

  40. X@dzyan01 · 5 likes · 120 views

    All scenes are generated from fully procedural code, so no external assets are required. We hope you (or your agent) will give it a try at princeton-vl/infinigen! For more updates, follow @princetonvl. This performance update was led by @jiadeng and I. 2/3

  41. X@pedrmnoel · 2 likes · 33 views

    @gabrielbuzziv @norbertbodziony @OpenBot_ We need this: openbot#3586 🙏

  42. X@adiinr17 · 1 like · 34 views

    In this economy harus bayar bulanan buat dengerin musik doang? Mending pake BitChord,. Sebenernya udah ga pernah muter lagu di hp si karna enakan di PC langsung ke speaker tapi setelah tau ni app kok jadi enak ya muter di hp wkwkkw Yang mau coba kushagrasinghx/BitChord t.co

  43. Redditu/everythingawaken · r/AppBuilding · 1 point · 1 comment

    We just shipped our first Android app, a private diary. Four things I'd tell anyone building something similar Disclosure: this is my own app, Awaken Journal by Everything Awaken. It went live on Google Play this week. It's a diary, to-do list, notes and money tracker in one native Android™ app, built with Kotlin and Compose. Writing is encrypted on the phone before it leaves, and sync stays off until you turn it on. Four things we learned: • Start Play's closed test early. Our account needed 12 testers opted in for 14 days in a row before it could go to production. Those testers' reports also led to many of our fixes. • Google Play has no "pay 12 times, then you own it" option, and we didn't want an endless subscription. So each month is its own one-time product. Nothing renews by itself, and a 13th charge can't happen. • Test switching accounts on one phone. We found a bug there: after sign-out, the next account could upload the last person's entries. They stayed encrypted, but their dates reached our server. The fix is coming in our next update, and our article warns people until then. • Write down what your server can still see. "We can't read your diary" is easy to say, but emails, dates and usage still reach us. So we published the full list. Still open: iPhone is next, payments outside India are waiting on an approval, and no outside firm has audited our security yet. The encryption code is public. If you've shipped a paid app on Play, how did you handle people who want to own it instead of subscribing? Article and full list: everythingawaken.com Google Play: play.google.com Encryption code: Everything-Awaken/awaken-journal-security Android is a trademark of Google LLC.

  44. YouTubeAutopilot Founder · YouTube description · 9 likes · 1,309 views

    DeepSeek just open-sourced a Claude Code rival DeepSeek open-sourced "Super-Agent" (dsh-superagent), a proactive coding agent that answers your team with pull requests. DeepSeek itself calls it a research prototype, not an official DeepSeek product. What the repo says (checked 2 Nov 2026): • "Research prototype for reference only, not an official DeepSeek product." • "dsh-superagent is a proactive coding agent for one GitHub repository… It listens to GitHub and, optionally, Feishu… answers in the original conversation, for example with a pull request." • Principle: "take as little human attention as possible, and give as much value as possible." It "speaks only when a person must act or can use a result." • Default auto-merge rule (docs/003-execution.md): only for a pull request opened for the ticket, when it is ready, the required approvals cover the head commit, and additions plus deletions total fewer than 200 lines. • Licence: MIT. Published on GitHub on 31 Oct 2026. • Bloomberg (1 Nov 2026) reports DeepSeek released it "as it seeks to challenge Anthropic PBC's popular Claude Code." Our take: try it on a side repo first, not on production code. Sources: deepseek-ai/dsh-superagent-prototype github.com/deepseek-ai/dsh-superagent-prototype/b… github.com/deepseek-ai/dsh-superagent-prototype/b… github.com/deepseek-ai/dsh-superagent-prototype/b… bloomberg.com Footage: our own screen captures of the GitHub repo and docs (github.com/deepseek-ai) and of Bloomberg's story as republished by Moneycontrol. Music: "Voxel Revolution" Kevin MacLeod (incompetech.com). Licensed under Creative Commons: By Attribution 4.0 License creativecommons.org #DeepSeek #CodingAgent #Superintelligence

  45. Redditu/Here_and_there_again · r/macgaming · 43 points · 17 comments · aldotoa/max-payne-recomp

    I ported the original Max Payne to Mac Silicone Works pretty decent on my M2. It's mostly 60 fps with occasional dips. Currently I'm in Chapter 3 and so far not that many issues. If you decide to check it out and see any problems, add it into Github issues. I won't be maintaining it super actively in the long-term as I just wanted to play it and be done with it but want to add the code online so others could also use it.

  46. Redditu/TmLev · r/reactjs · 7 points · 4 comments

    react-context-typesafe: missing context providers as lint errors instead of runtime crashes You know the pattern: createContext<User | null>(null), then a useAuth() hook that throws "useAuth must be used within AuthProvider", and every consumer either trusts that or null-checks. A missing provider is a runtime error you find when that screen renders, or when a test does. I wanted it to be a lint error instead, so I built an oxlint plugin that checks it across the whole program: const AuthContext = createContext<User | null>(null); function Children() { const user = use(AuthContext); return <p>{user?.name}</p>; } root.render( <AuthContext value={user}> <Children /> {/* ok */} </AuthContext>, ); root.render(<Children />); // ^^^^^^^^ react-context(require-provider): <Children> needs AuthContext // (use(AuthContext) at Children.tsx:4), but no <AuthContext> provider is above it. Children needs no annotations. Requirements are inferred from use, useContext, <Ctx.Consumer> and static contextType. They're passed up through components, custom hooks, HOCs, memo/forwardRef/lazy, children and render props, and React Router outlets, until a provider meets them or a root gets them. Roots are createRoot().render, testing-library's render, Storybook stories, and framework pages you list in a setting. Wrapper components like <AuthProvider>{children}</AuthProvider> count as providers because they render children inside one. There's also a tiny optional runtime: createRequiredContext<User>() gives you a context where use() is typed User instead of User | null, because the lint rule now guarantees the provider. It returns a plain React context, so nothing else changes. Why not types? That was the first thing I tried. JSX erases element types: <Children /> and <span /> are both just JSX.Element, so a requirement can't travel from a child up to its provider through the type system. Forking @types/react doesn't help, and TypeScript 7.1's new APIs didn't open a way either. The only version that type-checked used generator components and h() calls instead of JSX, which nobody wants. As for the speed, it's a whole program so it costs more than a normal lint rule. On excalidraw (709 files), oxlint alone takes 0.07 s, oxlint with the rule 0.8 s, and the standalone CLI 0.5 s. In the editor (oxlint's language server), a keystroke costs about 50 ms because only the edited file is re-parsed. The README suggests a separate oxlint config so that your everyday oxlint stays as fast as before, while the editor uses the config with the rule and CI runs react-context-check as its own step. Not on oxlint? The CLI runs the same check without it. As for limitations, it's syntactic and not type-aware. For code it can't see (node_modules, dynamic tags, useContext(cond ? A : B)) it makes certain assumptions. A provider hidden in such code shows up as a false positive, which you silence with @context-provided. A null-default context that your code actually treats as optional needs a // @context-optional comment. On excalidraw, that one comment was the difference between 337 reports and zero. It's not on npm yet: npm i -D github:TmLev/react-context-typesafe oxlint Repo: TmLev/react-context-typesafe Reports of wrong diagnostics are the most useful feedback right now. A few lines of code that reproduce one are enough.

  47. Redditu/BeyondExistenz · r/synthesizers · 117 points · 88 comments

    Polyend just open source their tracker code base! Wow here’s the GitHub repo! Game changer for Polyend!! And this is just the beginning for the industry! This is how you do it, release the source code of your existing products not release a new product that’s open source, forcing people to buy something else. polyend/tracker-ce

  48. Bluesky@madoka.systems · 4 likes

    it's thaw btw and it's free but it's very obviously vibed, use at your own risk

  49. X@ceguzsal · 1 like · 9 views

    Repo: NatLabRockies/rdtools MIT. Install: pip install rdtools

  50. X@__some__1_ · 1 like · 12 views

    Take a look at my GitHub github.com/null960 Could you tell me what I should improve or add so that I could use it as a resume when applying for jobs?

Older posts →