Mentions

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

Mentions by source

X

6,786
Nov 18, 00:00Nov 19, 00:00

Bluesky

3,125
Nov 18, 03:00Nov 19, 03:00
Nov 18, 02:00Nov 19, 02:00
Nov 18, 02:00Nov 19, 02:00
Nov 18, 03:00Nov 19, 03:00
Nov 18, 02:00Nov 19, 02:00
Nov 18, 02:00Nov 19, 02:00
Nov 18, 03:00Nov 19, 03:00
Oct 14, 21:00Oct 15, 21:00

Delayed · data through Oct 15, 21:00 UTC

DEV

841
Nov 18, 02:00Nov 19, 02:00
Nov 18, 03:00Nov 19, 03:00
Nov 16, 11:00Nov 17, 11:00

Delayed · data through Nov 17, 11:00 UTC

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

Latest posts

  1. Distritos más caros y más baratos de Lima para comprar casa: ranking por m² En Lima, el distrito con el m² más caro para comprar casa es San Isidro (9.191 soles (USD 2.675)/m²) y el más barato Chaclacayo (2.879 soles (USD 838)/m²), 3,2 veces menos. Comparamos 14… DOI: 10.5281/zenodo.23522754

  2. I built a PDF editor where the file never leaves the browser Open almost any "free PDF editor" and the first thing it asks for is the file. That is not a UI detail. Your document is copied to a server, written to disk, processed by a queue, and returned as a new file. For a recipe that is fine. For a contract, a payslip or a medical letter, it is a decision with legal weight. I maintain pdfcanvas, an MIT-licensed PDF editor that runs entirely in the browser. This post is about the engineering behind it, including the parts that are still ugly. The privacy claim is the easy part The architecture is boring on purpose. The site is static files, and the editor is JavaScript plus WebAssembly. There is no API route that accepts a document. Rendering is done by PDF.js. Editing existing text is done by a WebAssembly build of PDFium, the engine inside Chrome. Writing the output is done by pdf-lib. All three run in the tab, and the worker is served from the same origin, never from a CDN. You do not have to trust that paragraph. Open the editor, load a file, open the network panel, and switch it to Offline. Keep editing and export. If the document were processed remotely, the export would fail. The privacy guarantee is the easy part because it falls out of the architecture. The hard part is what happens when a PDF contains text that was never designed to be edited. Three engines, because one library cannot do all of it A PDF editor has three jobs, and each has a different best tool: - Render pages, with fonts, CMaps and colour spaces. PDF.js is the renderer maintained by Mozilla and used by Firefox. - Edit text that already exists in the file. This is the rare capability. pdf-lib can draw new content but cannot change a glyph in the original content stream. PDFium can. - Write the result. pdf-lib produces valid PDFs with images, fonts and page trees. Pulling PDFium in for everything would be simpler, but it is also the largest asset in the build. Using each engine for its job keeps the initial path smaller. The snippets below target pdfcanvas 0.8.x and were checked against 0.8.0 in November 2026. Mounting the engine looks like this: import { PdfCanvas } from "pdfcanvas"; const pdf = new PdfCanvas(document.querySelector("#editor")!, { workerSrc: "/pdfjs/pdf.worker.min.mjs", pdfiumWasmUrl: "/pdfium/pdfium.wasm", fontAssetsUrl: "/fonts/", }); await pdf.load(file); pdf.addText(80, 120, { text: "Approved", fontSize: 24, color: "#6b4eff" }); await pdf.download(); The container needs an explicit height. That is the first bug every integration hits. PDF text is not a text box This is the part I underestimated. A PDF content stream does not store paragraphs. It stores glyphs at coordinates, with a font and a transformation matrix. Sometimes a line of text is one text-showing operator. Sometimes every character is placed individually, because the producing tool was optimizing for something else. There is no line object to select. So "click a line and edit it" is a heuristic, not a lookup. PdfCanvas groups characters into editable line runs by comparing their baseline, spacing and font. On a normal document exported from Word or LaTeX this works. On a scan there is no text to group. On unusual encodings it can fail, and when it fails the editor should say so instead of silently corrupting the file. Once a run is selected, changing it is a separate operation. The original glyphs are removed and new text is drawn with a matching font: pdf.setTool("text-edit"); pdf.on("originaledit", ({ edit }) => { if (!edit) return; pdf.updateOriginalText({ boldOverride: true, fontSizeOverride: 11 }); }); That distinction matters for the export, and it is where most of the debugging time went. Fonts lie about what they contain PDFs usually embed a subset of a font: only the glyphs the document uses. If you edit a word and introduce a character outside that subset, the original font cannot render it. The editor tries to reuse the embedded font first, which keeps line lengths and shapes identical. When it cannot, it falls back to Work Sans or to Liberation Sans, which has Arial metrics. Close is not the same as equal: a replaced font can shift line breaks and make accented characters look wrong. This is a limitation I would rather state than hide. If a document is typographically sensitive, check the export before sending it. Export has to stay vector There is a tempting shortcut: render the edited page to a canvas, wrap it in an image, and call it a PDF. It is a few lines of code. It also destroys the document. Text stops being selectable and searchable, file size explodes, and printing quality drops. The approach here is different. Pages you did not touch are copied as they are. Overlays are written as real PDF objects: text with an embedded font, shapes with a fill, images with a transform. The original page stays vector. That choice is also why the whiteout tool needs an honest warning. Whiteout is not redaction The editor has a tool that draws a filled rectangle over part of a page. It looks like redaction. It is not. The rectangle is drawn on top of the content. The text underneath is still in the file and can be extracted with any text tool. Real redaction removes or rewrites the content stream, and verifying that is its own project. Most online editors have the same behaviour and do not say so. I would rather lose a feature comparison than have someone send a "redacted" document that still contains the account number. For the same reason, the project does not claim AcroForm filling, OCR, certified digital signatures or PDF/A. Each of those has a correctness bar that a small editor cannot meet, and a broken version is worse than a missing one. The bill: what local processing costs Client-side processing moves cost from a server bill to the user's first load. These are the assets in the production build at v0.8.0, measured with Node's zlib on the files as shipped: | Asset | Raw | Brotli | | --- | --- | --- | | pdfium.wasm | 4.43 MB | 1.58 MB | | pdf.worker.min.mjs | 1.21 MB | 0.30 MB | | CMaps | 1.14 MB | not measured | | Standard fonts | 779 KB | not measured | The first visit pays for the engine. After that the browser caches it, and the editing session itself makes no network requests. On a slow connection the first load is the price of not uploading anything. The other limit is memory. The default maximum file size is 200 MB, but the real ceiling is the tab. A 500-page scan will open on a laptop and struggle on a cheap phone. There is no server to bail you out. When you should not use it I would not recommend this editor for: - Forms. AcroForm fields are not supported. You can place text over a field, but the field itself stays empty. - Redaction. Use a tool that removes the content and lets you verify the result. - OCR. Scanned documents can be annotated, not edited. - Certified signatures. The signature tool draws a signature. It does not create a cryptographic one. - Server pipelines. It depends on browser APIs. For batch processing use a library built for Node. - Mission-critical workflows without maintenance. There is no support contract. If those are requirements, Nutrient, Apryse or Acrobat are the right products. They cost money because someone maintains the hard parts. The part I would do again Keeping the whole thing open source and client-side forced better decisions. There is no upload endpoint to secure, no retention policy to write, and no tenant isolation to get wrong. The security review is "read the code and watch the network panel". It also made the editor embeddable. The same package ships a core API and a ready-made UI: import { PdfCanvasEditor } from "pdfcanvas/editor"; const editor = new PdfCanvasEditor(document.querySelector("#app")!, { workerSrc: "/pdfjs/pdf.worker.min.mjs", pdfiumWasmUrl: "/pdfium/pdfium.wasm", fontAssetsUrl: "/fonts/", locale: "auto", autosave: { key: "contracts" }, }); await editor.ready(); await editor.open(file); Autosave stores the original bytes and the scene in IndexedDB. Still no server. Try it, or read the code - Editor: pdf.eneawork.it - Source: Frenxys/pdfcanvas - Package: npm i pdfcanvas (npm) - Docs: pdf.eneawork.it The honest summary: it handles text, images, signatures, highlights and pages, it keeps the file on the device, and it is missing features that other tools charge for. The gaps are documented in the repository, because finding them in production is worse. If you try it on a real document and something breaks, open an issue with the kind of PDF that broke it. The per-character text cases are the ones I want to see.

  3. DEV@theaicommit · 1 reaction · 1 comment

    How to Fix Jargon in Speech-to-Text Without Adding Words Nobody Said Hand a transcription model a list of your product names and it spells them right. It also starts writing them where someone said a word that only sounds close. > Engineer's view. This is a search spellchecker with a custom dictionary. Add your product names and their misspellings get fixed, but nearby ordinary words get "corrected" too. A transcription prompt works the same way: a listed spelling wins wherever the audio is close to it. You get your jargon right and pay in confident wrong words. > > TL;DR. Give a speech-to-text model a short list of your terms and it spells most of them right. It also writes those terms where someone said a word that only sounds alike, so test for both. Explain Like I'm 5 Imagine a friend writing down everything you say at a noisy party. Before you start, you hand them a card with the tricky names on it. Now they spell those names right. But then someone says "Laura." Your friend glances at the card and writes the name from the card instead. The card helps your friend choose between words that sound alike. It cannot tell them which word was actually said. So the card fixes some mistakes and makes a few new ones. The Problem You have shipped this bug before, in a system with no model in it. Your search box had a spellchecker. Users typed your product names and got "no results," so you added the names to its dictionary. The failed searches stopped. A week later, a support ticket arrived. Someone searched for "laura" and got pages about your LoRA feature. The dictionary did what you asked. It pulled every close word toward the words you listed. A speech-to-text model is that spellchecker, running on sound. You send it meeting audio, a support call or a video voiceover. It hears "Q drant" and writes "Q-drant." It hears "K V cache" and writes "cavity." I read 15 AI terms to two OpenAI transcription models with no help. whisper-1 spelled 14% of them right, and gpt-transcribe spelled 36% right. Nothing raised an error. The transcript just looked slightly wrong, and every search, summary and caption built on it inherited the mistake. My own video captions hit this last week. The voice said "halve" and the transcript said "have." Both models take a hint: a text prompt, or a list of keywords. Add one and most of the jargon comes out right. Some of it also comes out where nobody said it. The fix: give the model a short list of the terms this recording is likely to contain, put the important ones last, and test it on clips that say near-miss words, not only on clips that say the terms. Read the full post on The AI Commit How to Fix Jargon in Speech-to-Text Without Adding Words Nobody Said carries the rest: the fix and why it works, the code to change for each role, how to tell it worked, when it is the wrong tool, and an interactive model you can play with. --- Originally published at theaicommit.com, a daily AI engineering lab for software engineers. The original has an interactive version you can play with, and the full runnable code is on GitHub.

  4. X@0xLuigislm · 1 like · 49 views

    Support added for ComfyUI v0.43.2 🍎On v0.43.2, older pack versions fall back to stock speed for MOSS, Fibo 2.0, Flux.3 and YuE2. Update to get the fast routes back, same output bytes: MOSS 1024²: 34.2 → 18.9 s Flux.3 Base: 43.3 → 33.4 s luix93/ComfyUI-AppleSilicon-Optimized

  5. X@OpenSilverTeam · 2 likes · 66 views

    Live demos: opensilver-animations-library.azurewebsites.net Source code and documentation (MIT License): OpenSilver/OpenSilver.Animations

  6. Redditu/mng775 · r/nestjs · 8 points

    I made a Hono adapter for Nest, on Bun it's ~17% faster than the new platform-node been running nest on bun for rigtch.fm, and the express/fastify adapters there go through bun's node:http compat layer, so i wrote `@mnigos/platform-hono`. it serves nest from Bun.serve on bun and `@hono/node-server` on node, works with nest 11 and 12. on the same hello world benchmark nest used for the platform-node launch (wrk -t4 -c100, nest 12.3.2 for every adapter, M4) it does 141k req/s on bun vs 121k for platform-node on bun. on node it's about fastify level, the gains are on bun not supported yet: nest versioning, views and express/fastify style `@Res()` calls. if something breaks in your app open an issue Mnigos/platform-hono

  7. Redditu/MadVintager · r/Roms · 32 points · 5 comments

    [Tool] RomSieve: an open-source 1G1R ROM manager with native .m3u generation, TOSEC parsing & full dry-run preview Hi everyone, With the moderators' permission, I wanted to share a free and open-source project I’ve been working on that might be useful for anyone curating clean sets for any emulator or frontend: RomSieve (Linux and Windows, GPLv3). - GitHub:madvintager/RomSieve - Latest releases:github.com/madvintager/RomSieve/releases/latest(self-contained binaries, no .NET install required) Here are the key features designed to make building clean setups easier: - Automatic .m3u playlists with custom placement: Since a lot of frontends (RecalBox, RetroPie...) relies on RetroArch / libretro cores for multi-disc games (PS1, Saturn, Sega CD, PC Engine CD...), RomSieve automatically generates .m3u files so you don't have to create them manually. You can also define exactly where those playlists land in your target folder tree. - Deterministic, multi-criteria 1G1R: Instead of rigid rules, the 1G1R engine picks the single best release based on a fully configurable priority stack: language, region (with 1-click presets for Europe, France, USA, Japan), video standard (PAL/NTSC), dump quality, multi-disk completeness, and revision. The exact same settings will always yield the exact same output. - Full TOSEC parsing (not just console hashes): If you emulate vintage computers on Recalbox (Amiga, Atari ST, Amstrad CPC, C64...), you know TOSEC sets can be messy. RomSieve parses the entire naming convention (flags like [!], [cr], [t], languages, disk numbers). It can even rebuild and complete missing multi-disk sets by pulling clean disks from other dumps. - Simulation-first workflow (dry-run): No files are moved, copied, or touched blindly. The tool runs a complete audit first, displays a table detailing the exact fate of every single file (with the reasoning behind it), and lets you right-click any entry to manually override the 1G1R winner. It also supports hard links / symlinks, keeps unmerged files in dedicated safe folders (_unmatched/, _purged/), and features an undo function. It also supports standard No-Intro, Redump, and MAME sets, reads compressed archives directly (ZIP, 7z, RAR), and extracts CHD headers. Both a modern GUI (with dark theme) and a CLI (romsieve-cli) are included. The project is completely free, has no telemetry, and full documentation is available in both English and French in the repository. Feedback, bug reports, and suggestions are very welcome!

  8. ¿Cuántos metros cuadrados se compran con 700 millones de pesos? 38 ciudades de Colombia Con 700 millones de pesos se compran unos 206 m² de apartamento en Soacha, la ciudad que más rinde de 38, y 75 m² en El Retiro. En Bogotá alcanzan para 96 m² y en Medellín… DOI: 10.5281/zenodo.23523341

  9. X@laogeai · 1 like · 16 views

    以为是硬件老了,停掉几个后台服务后开机从两分钟变四十秒。 OptimizerDuck 开源 Windows 优化,把遥测/更新/索引/动画/右键菜单做成开关,每项注明作用,可一键还原。 itsfatduck/optimizerduck

  10. Redditu/StevWong · r/SwitchPirates2 · 20 points · 20 comments

    MKW, Splatoon Raiders - 59 60 61 fps in this fork Just tried this new fork of Eglantine and got good results for these two games. sylvieistaken/selevet-eglantine

  11. X@DroidDeskcomp · 3 likes · 86 views

    Your AI agent can now use a real Android phone. 📱 Connect Codex, Claude Code or Cursor to DroidDesk through MCP. Ask your agent to open apps, tap, type, scroll and check the screen. MCP access is included in your phone rental. See how it works 👇 github.com/droiddesk-cloudphone/android-phone-ren… t.co

  12. X@TheheroGAC · 15 likes · 3 reposts · 409 views

    New update for pEMU-PS3! PGBA support has also been added, expanding the emulator's capabilities on PlayStation 3. Check out the latest release and download it here: github.com/theheroGAC/pemu-ps3/releases More features coming soon!

  13. ¿Cuántos metros cuadrados se compran con 350 millones de pesos? 38 ciudades de Colombia Con 350 millones de pesos se compran unos 103 m² de apartamento en Soacha, la ciudad que más rinde de 38, y 38 m² en El Retiro. En Bogotá alcanzan para 48 m² y en Medellín… DOI: 10.5281/zenodo.23523315

  14. X@bytebot · 2 likes · 176 views

    @ajambrosino @romainhuet this is a good fix from @steipete which adds retry logic when the selected model is at capacity. i'd totally merge this into main codex#31058

  15. ¿Cuántos metros cuadrados se compran con 250.000 dólares? 30 ciudades de Latinoamérica y Portugal Con 250.000 dólares se compran unos 330 m² de apartamento en Maracaibo (Venezuela), la ciudad que más rinde de 30, y solo 30 m² en Lisboa (Portugal). DOI: 10.5281/zenodo.23523388

  16. YouTubeQosmopol Apps · YouTube description · 59 views

    Never miss a waiting Claude Code agent again: Qosmopol (free, open source) Running Claude Code in many projects? Somewhere an agent has been waiting for your answer for hours. Qosmopol shows every project as a planet and every session as a moon. Blinking red: it needs you. Orange: working. Blue: new reply. Click a moon to open the session and answer right there. Free and open source (MIT), runs locally, spends no tokens. Mac and Windows. Install: /plugin install qosmopol --marketplace aydinsoy/qosmopol, then /qosmopol GitHub: aydinsoy/qosmopol Full video: youtu.be Not affiliated with Anthropic. Claude and Claude Code are trademarks of Anthropic, PBC. #ClaudeCode #AI #OpenSource

  17. 昔からどこでも困っていたドキュメントがなかったりあっても具体的なコードがどれかとか見つけづらいのが辛かった問題を解決する(かもしれない)ツールを作ってみた。どこまで正しいかは不明だけどまあ開発のお手伝い程度かな。gitがほぼ前提だけど... longicorn/itoc

  18. X@WickedAIyoutube · 2 likes · 28 views

    @AnthropicAI @claudeai @GoogleDeepMind @GeminiApp @grok Watch the full documentary: youtu.be Paper, code and every timestamp: MajinBuuTwitch/multiverse-v1

  19. Redditu/Specialist-Leek-357 · r/indotech · 156 points · 58 comments

    jalanin local LLM (Qwen3.6-35B-A3B) di iqoo z9x 12/256, pnp tinggal install, download, load. dpt ~2 token/s, better than nothing, anggep aja `google offline`, lagian, bisa jalan aja sukur, h3h3 link app, kl saran gw pake yang debug.apk Helldez/BigMoeOnEdge

  20. X@ven_ai_lab · 2 likes · 5 views

    repo: naman-sharma12345/kimo site: getkimo.tech star it or roast it, either helps

  21. X@Abbas_Mistrah · 1 like · 66 views

    T3 Code is one open-source app that drives Claude Code, Codex, Cursor, Grok, OpenCode and Antigravity on the subscriptions you pay for. MIT, 30k+ GitHub stars. Coding agents are turning interchangeable. Lock-in moves to the harness. Do you own yours? pingdotgg/t3code

  22. X@prioninae · 1 like · 42 views

    昔からどこでも困っていたドキュメントがなかったりあっても具体的なコードがどれかとか見つけづらいのが辛かった問題を解決する(かもしれない)ツールを作ってみた。どこまで正しいかは不明だけどまあ開発のお手伝い程度かな。gitがほぼ前提だけど... longicorn/itoc

  23. mattpocock/skills

  24. Redditu/ETIM_B · r/Nigeria · 1 point · 1 comment

    I built a free app for sending files between two computers on the same WiFi Network 🇳🇬 Hey everyone! I built Lanweave, a free, open-source app for transferring files and folders between two computers on the same Wi-Fi network. The idea came from a frustrating experience. Whenever I needed to move a file between my two computers, I'd transfer it from one computer to my phone using a USB cable, then connect my phone to the other computer and transfer it again. Cloud services like Google Drive weren't always a good alternative either. Uploading and downloading the same large file, especially with a slow internet connection, could take forever. So I decided to build something simpler. Lanweave transfers files directly over your local network. Your files never leave your network, there's no cloud, no account creation, and no internet connection required. Here's how it works: - Run Lanweave on both computers. - Select the other computer from the discovered devices. - Pair them using an 8-digit code provided. - Select files or folders and send them. - The receiving computer reviews the files and approves the transfer before anything is saved. Either computer can initiate a transfer. Connections are encrypted, and pairing authorization is discarded when the session ends. A few things worth knowing: - It's a terminal-based application, but you don't need to memorize commands. Just press / to open the interactive menu. - Currently supports Linux and Windows. - macOS support is in progress. - Phone-to-PC transfers are also planned. I've included a short demo showing two machines pairing and transferring files. A few disclaimers: It's still in beta and hasn't undergone a security audit, so I wouldn't recommend using it for sensitive files just yet. The Windows executable is also not code-signed yet, so Windows SmartScreen may show a warning. GitHub: etim66/lanweave I'd appreciate it if you tried it out and shared your feedback. I'm particularly interested in how it performs on Windows and whether the pairing process is intuitive. Stars and contributions are welcome too! And even if you only own one computer, I'd be interested to hear whether you think something like this would be useful to you. Thanks for reading!

  25. ¿Cuántos metros cuadrados se compran con 250.000 dólares? 30 ciudades de Latinoamérica y Portugal Con 250.000 dólares se compran unos 330 m² de apartamento en Maracaibo (Venezuela), la ciudad que más rinde de 30, y solo 30 m² en Lisboa (Portugal). DOI: 10.5281/zenodo.23523388

  26. X@lain___os · 4 likes · 3 reposts · 68 views

    a token arriving in a wallet is not necessarily a buy. my wallet scan checks who signed a transaction before counting a trade. airdrops don't become purchases just because they appear in a transfer log. lain-labs/os t.co

  27. X@weiwei2018831 · 2 likes · 112 views

    FlashTester 是一款开源的 U 盘、SD 卡、磁盘检测工具,能快速识破“容量虚标”的假盘,并检查真实容量、数据可靠性与速度表现,在经典工具 h2testw 能做的事之外加了快速容量探测、原始模式与报告。 Dissimilis/FlashTester

  28. YouTubeDevOps Channel · YouTube description · 8 likes · 2 comments · 99 views

    Module 17 - Kubernetes SDK for Python #python #kubernetes #devops In this Module 17 - We will learn about Kubernetes SDK in python with actual demo and project. Kubernetes for Absolute Begineer Course: youtu.be For next/previous chapters please navigate to full playlist: youtube.com For Python for Beginners playlist: youtube.com GitHub repo link for this playlist: devopschannel23/PythonForDevops For other courses related to DevOps(Docker, Git & Github & Many More), please navigate to my channel: youtube.com If you like my courses then please subscribe🕹️ to my channel, like👌 my videos. Please feel free to provide any suggestion. Reach out to me via comments section if you face any issue while working with labs. Thanks again Everyone😍, Keep Sharing😊, Keep Learning!💥 #programming #python #automation #cicd #devops

  29. X@0dvsh0 · 3 likes · 140 views

    SGLang's RadixAttention treats the KV cache as a radix tree of tokens across requests. For multi-turn chats and few-shot evals, it reuses prompt KV cache instead of recomputing from scratch. Cache hit rates regularly cross 70%. sgl-project/sglang

  30. YouTubeMIRLABS · YouTube description · 8 views

    AI 답이 엉뚱했다면 정말 AI 탓일까? GitHub 별 1.5만 Prompt Master, AI에게 할 말을 다듬어 주는 스킬 #Shorts AI가 엉뚱한 답을 했을 때, 문제는 AI가 아니라 질문(프롬프트, AI에게 하는 말)이었을 수도 있습니다. Prompt Master(nidhinjs/prompt-master)는 GitHub 별 약 1만 5천 개(15.3k, 2026.11.01 GitHub API 집계)의 MIT 오픈소스로, README는 'AI 도구용 정확한 프롬프트를 써 주는 Claude 스킬'이라고 소개합니다. Cursor, Claude Code, Midjourney, Stable Diffusion, Sora 등 여러 도구용 프롬프트를 만들어 줍니다. · README의 처리 순서: 대상 도구 파악 → 의도 9가지(task, input, output, constraints, context, audience, memory, success criteria, examples) 추출 → 중요한 정보가 빠졌을 때만 질문(최대 3개) → 프레임워크 선택 → 토큰 효율 점검 → 복사용 프롬프트 한 블록으로 전달 · 자동 선택되는 프롬프트 템플릿 14종, 30개 이상 도구 프로필, 처음 보는 도구는 질문 4개(Universal Fingerprint)로 대응 · 크레딧을 낭비하는 흔한 패턴 37가지를 전후 예시로 정리 · 핵심 아이디어: 프롬프트를 더 길게가 아니라 더 날카롭게 · 긴 대화에서는 이전 결정 사항을 모은 Memory Block을 앞에 붙여 이어 감 · 설치(README 권장): 저장소를 ZIP으로 받아 claude.ai → Customize → Skills → Upload a Skill. Claude Code 스킬 폴더에 복제하는 방법도 있음(README는 비권장으로 표기) 주의: 'Zero tokens or credits wasted(토큰·크레딧 낭비 0)'는 개발자의 소개 문구이며 MIRLABS가 측정하지 않았습니다. 처음엔 README의 사용 예시(예: 'Cursor용 리팩터링 프롬프트 써 줘') 하나를 그대로 따라 해 보고, 만들어진 프롬프트도 내 상황에 맞는지 한 번 읽어 보는 걸 권합니다. README 기반 소개이며 직접 설치해 보지 않았습니다. 화면의 README 캡처는 GitHub 원문(raw README)을 MIRLABS가 렌더링한 것이고, 첫 장면의 재질문 그림은 개념 도식(실제 화면 아님)입니다. 출처 nidhinjs/prompt-master raw.githubusercontent.com MIRLABS · AI 도구와 기술을 짧게 #MIRLABS #미르랩스 #PromptMaster #프롬프트 #프롬프트엔지니어링 #Claude #ClaudeSkills #AI도구 #Shorts

  31. DEV@backmeupplz · 2 comments

    How Todorant's native Android app reached Google Play in four days, and lost 4.5 MB on the way Originally published on the Todorant blog. Todorant's native Android app went from a test build to a live Google Play release in four days, October 13 to 16, 2026, and the version that shipped is 3.26 MB instead of 7.74 MB. It took four releases to get there (2.2.0 to 2.2.3), and each fixed something that only showed up once the build was a real release: a deleted Google Cloud project, a crash that R8 caused, and a 4.5 MB font I was not allowed to ship. This is the list, with the commits. What was Todorant on Android before October 2026? Todorant is a to-do manager that shows one task at a time and makes you plan every overdue one again before you continue. The Android app on Google Play was the old React Native one. In October I replaced it with a native Kotlin and Jetpack Compose app that syncs through the new /v2 backend over one WebSocket. The 2.0.0 release on October 13 was the first build of it, and it was only a test build: Android refuses to update an app signed with a different key, so anyone moving from the old Play build had to open it once to finish syncing, uninstall it, and install the new APK. Everything came back from the server after sign-in. Why did Google sign-in fail in 2.2.1? Version 2.1.0 shipped with a known issue: Google sign-in did not work. The reason was boring. The Google Cloud project behind the sign-in client had been deleted, so every attempt ended in a deleted_client error. The fix in 2.2.1 on October 14 was a new Google Cloud project with a web client (redirect https://todorant.com/google_login_result) and Android clients for both the upload key and the Play signing key. That second part matters: Play re-signs your app, so sign-in needs to know both fingerprints or it works in your test build and fails for every user who installed from the store. The same release removed Google Calendar sync. It had stopped working, and the Integrations screen that hosted it is gone. What did R8 break in 2.2.2? Google Play's pre-launch report ran the 2.2.1 build on test devices and found that scanning a QR code closed the app. QR login is how you sign in on a new device by scanning the code the web app shows, so this was not a corner of the app. The cause was R8 in full mode. ML Kit's barcode scanner finds its internal components through registrar classes that it creates by reflection, using their no-argument constructors. R8 saw no code calling those constructors and removed them. ComponentDiscovery then could not build the registrars, one shared-preferences component was never registered, and GmsBarcodeScanning.getClient() threw a NullPointerException. The fix in 2.2.2, merged on October 15, is a few lines in proguard-rules.pro that keep those constructors. It is the sort of bug a debug build never shows, which is the argument for running the pre-launch report before every promotion rather than once. How did the APK lose 4.5 MB in 2.2.3? The Android app reused the iOS app's typography, which is Apple's SF Pro in six font files. SF Pro is licensed for Apple platforms only, so it should never have been in an Android build. It was also large: the commit that removed it records 4.5 MB of the bundle. I switched to Android's system font and kept the font families and weights as they were, so no call site changed. Here are the release assets on Forgejo, measured on November 2, 2026: | Release | Date | APK size | |---|---|---| | 2.2.0 | Oct 14 | 7,739,907 bytes | | 2.2.2 | Oct 16 | 7,738,839 bytes | | 2.2.3 | Oct 16 | 3,256,419 bytes | | 2.2.4 F-Droid build | Oct 16 | 2,754,408 bytes | The drop from 2.2.2 to 2.2.3 is 4,482,420 bytes. Version 2.2.3 is the build that went to Google Play, and the README stopped pointing Android users at a manual APK on the same day. Why is there a separate F-Droid build? The 2.2.4 release (October 16) split the app into two flavors. The play flavor keeps Google sign-in and Google's code-scanner. The fdroid flavor has no Google code at all: it scans QR codes with the open-source ZXing library, which needs the camera permission, and it has no Google sign-in button. You can still sign in with an email and password, Apple, Telegram or a QR code. F-Droid also rejects the dependency-info block that Gradle adds to APKs, so the release build leaves it out, and CI now builds both flavors with the upload key when a release is published and attaches both files so F-Droid can verify its own build against ours. The F-Droid APK is about 490 KB smaller than the Play one. What happened to the 28 permissions? On October 17 the 2.2.6 release removed a pile of permissions that Todorant never used. A library for launcher badges, ShortcutBadger, declares one permission for every launcher vendor it knows about, and Credential Manager adds two biometric permissions for passkeys. The manifest merger put all of them in the app. Reading the commit's diff, I count 22 tools:node="remove" lines for them, and VIBRATE went too, because swipe feedback now uses Compose haptics, which need no permission. The commit message counts the app's permissions as 28 before and 5 after: internet, network state, the boot receiver and notifications for the planning reminder (asked for only when you set a reminder time), and, in the F-Droid build only, the camera. The release notes say it plainly: Todorant now asks only for the permissions it actually uses. I did not build the app to read the merged manifest myself, so the 28 and the 5 are the numbers from the commit, and the 22 is my own count of the lines removed. What did the first real users find? Two things, and both were mine. On October 16 I fixed the first sign-in on large accounts. A fresh sign-in pulls the whole account, and four places in the app each started their own full download, so a test account with 40,000 to-dos came down two or three times at once and ran out of memory. The server's heartbeat reply queued behind that download, the 15-second client ping closed the socket, and the 30-second sync timeout counted the download time too. Meanwhile the app showed only the Settings tab. The fix makes a pull with the same cursor join the one already in flight, gives sync 30 seconds to connect and 120 seconds to answer, and raises the ping to 60 seconds. On October 23, 2.2.7 restored tasks that people had stored only on the device in the old app, which the update had hidden. What I would do the same way next time 1. Run the Play pre-launch report on every build that is headed for production. It found the one crash that mattered. 2. Check the license of every asset you carry over from another platform. An APK that is twice the size it should be is a good reason to look. 3. Keep a second Google sign-in client for Play's signing key from day one. 4. Treat every permission in the merged manifest as something you have to be able to explain. Todorant is on Google Play, on the App Store, on F-Droid and at todorant.com. If you would rather run your own server, the self-hosting guide takes one compose file. The source is on GitHub. Written November 2, 2026 from the repository at backmeupplz/todorant (tags v2.2.12 and earlier), its release assets on Forgejo and the commits cited above.

  32. Qiita@Sidejob · 1 like

    Claude Code v2.1.314——外部パス書き込みブロック追加と企業ゲートウェイに影響する変更点 > この記事で分かること: > - permissions.blockWritesOutsideWorkingDirectoriesの仕組みと設定方法 > - IdPグループを使ったゲートウェイ上流のルーティング制限の追加 > - forceRemoteSettingsRefreshバグ修正が企業環境で意味すること 対象読者:企業でClaude Codeのゲートウェイや管理ポリシーを運用している担当者。v2.1.314は2026年10月30日にリリースされた。バグ修正が中心のリリースだが、セキュリティ設定の追加と、見落とすとポリシーが効いていない状態で運用し続けるリスクがある修正を含んでいる。 出典:github.com/anthropics/claude-code/releases/tag/v2… 公開) workingDirectory外への書き込みを全パーミッションモードで拒否できるようになった 今回追加された機能のうち、セキュリティ設定として最も注目しているのがこれだ。 { "permissions": { "blockWritesOutsideWorkingDirectories": true } } この設定をtrueにすると、Write・Edit・NotebookEditの3ツールが、設定されたworkingDirectory以外のパスへの書き込みを全パーミッションモードで拒否する。 「全パーミッションモードで」という部分を見落としやすい。これは、自動承認(auto mode)や信頼済みのユーザーが操作している場合でも、設定が有効なら外部パスへの書き込みは拒否される。ゲートウェイ経由でClaude Codeを多人数で使っている環境で、意図しない場所への書き込みを防ぐ用途に使える。 この設定が無かったときに何が起きていたか 正直なところ、この設定が追加されるまで「workingDirectory外に書き込まれていた可能性がある」とは意識していなかった。 タスクの指示が「ファイルAを編集して」と書いてあっても、Claudeがそれに関連する設定ファイルを上位ディレクトリに置こうとする場面は実際にある。明示的な禁止設定がなければ、その書き込みを止める手段は「承認を求めるパーミッション設定になっているか」に依存していた。 設定を検討する際の注意点: - workingDirectoriesに複数のパスを設定している場合、それらの外がすべて対象になる - 既存のタスクで外部パスへの書き込みが必要なものがあれば、workingDirectoriesの設定を先に見直す必要がある - リリースノートには「every permission mode」と明記されているので、auto modeでも効く :::note warn デフォルトはfalseなので、何もしなければ従来の振る舞いのままである。 まずは自分の環境でClaude Codeがどのディレクトリに書き込んでいるかを確認してからtrueに切り替える形が安全だ。 ::: IdPグループによるゲートウェイ上流のルーティング制限が追加された Claude apps gatewayの設定で、上流(upstream)ごとにIdPグループのリストを指定できるようになった。 upstreams: - name: prod-model groups: - ai-approved-users - name: dev-model # groups未指定 = 全ユーザー 指定したIdPグループのメンバーだけが、そのgroupsで指定された上流にルーティングされる。フェイルオーバー(上流が応答しない場合の代替ルーティング)でも同じグループルールが適用される。 これまで「誰でも全ての上流を使える」か「上流を完全に切り替える」かの2択だった部分に、グループベースの制御が入った。 具体的な用途: - 本番用モデル(コストが高い)と開発用モデルを組織の役割で分けたい - 特定のプロジェクトチームだけ特定の上流を使わせたい - 試験的な上流を限定ユーザーに展開したい コスト管理の視点からも、高コストの上流へのアクセスを承認が必要なグループに限定する运用がしやすくなる。 Bedrock上流にguardrail_traceが追加された Amazon Bedrockのguardrailを使っている環境向けの変更だ。 upstreams: - name: bedrock-prod guardrail_trace: enabled guardrail_traceを設定すると、Amazon Bedrockのguardrailがリクエストをフィルタリングした際にどのguardrailが発動したかをログに記録する。ただし、フィルタリングされたテキスト(マッチした内容そのもの)は記録されない。 これは監査対応やデバッグで役立つ。「なぜここでブロックされたのか」をあとから調べられるようになる。 :::note info マッチしたテキストが記録されない設計になっているのは、センシティブなコンテンツが誤ってログに残ることを避けるためと読める。個人情報・機密情報を含むリクエストがガードレールで止まった場合にも、その内容はログに出てこない。 ::: forceRemoteSettingsRefreshのバグ修正——ポリシー未適用で起動していた可能性 今回のリリースで一番注目している修正がこれだ。 リリースノートの該当箇所: > Fixed forceRemoteSettingsRefresh set only in remote managed settings no longer applying once the stored copy had expired, which let sessions start without policy when the server could not be reached. 訳すと:リモートのmanaged settingsにforceRemoteSettingsRefreshだけを設定していた場合、キャッシュが期限切れになると、以降のセッションはポリシーなしで起動する可能性があった。 組織のポリシーサーバーが一時的に応答しない場面(ネットワーク障害・メンテナンス中)でセッションを開始したときに、意図しないポリシー未適用状態になっていた可能性がある。 確認しておきたいこと: - forceRemoteSettingsRefreshをリモートのmanaged settingsだけに設定している環境 - ポリシーサーバーが短時間でも応答しない時間帯がある環境 今回の修正でこの振る舞いは解消された。ポリシーサーバーが応答できない場合、セッションはキャッシュ済みポリシーかフェイルセーフなデフォルトを使う形に修正されている。 無人実行環境にも関係するバグ:「自動継続が3回以上続く」バグ修正 もう一つ見ておきたいのが次の修正だ。 > Fixed "Continue automatically at usage limit" continuing more than three times without a prompt from you when a task restarted itself between waits (a /goal check-in, a background or scheduled task). /goalのチェックイン・バックグラウンドタスク・スケジュールタスクがタスクを再起動する場合に、「利用上限到達時に自動で続ける」の設定が3回以上続いてしまうバグがあった。 深夜の無人実行でClaude Codeがスケジュールタスクとして動いている場合、利用上限に達したあとも意図以上に継続していたケースがあったかもしれない。今回修正され、自動継続は3回で止まるようになった。 その他のバグ修正(ゲートウェイ経由環境向け) 以下の4件も適宜確認してほしい。 - tool_referenceブロックの拒否と再試行:tool searchのtool_referenceブロックを受け付けないゲートウェイで、それを除いたリクエストを再送信するようになった。セッション内で記憶される - Microsoft Foundryでデフォルトモデルが未デプロイの場合のフォールバック:Sonnet・Opus・Haikuのデフォルトモデルがデプロイされていない場合、同じファミリーの古いモデルに自動フォールバックするようになった - managed settingsのモデルピン故障の改善:managed settingsでモデルをピンしている場合、自分の--plugin-dirのプラグインが壊れていてもモデル切り替えが拒否されなくなった - クラウドセッションの機能制御:組織のポリシーでクラウドセッションやリモートコントロールを無効にしている場合、関連のティップや通知が出なくなった 今回確認できたことと、まだ展開できていないこと blockWritesOutsideWorkingDirectoriesの設定が、複数のworkingDirectoriesを指定したときのパスの部分一致・シンボリックリンクを含む場合などの具体的な挙動は、動かしてみないと分からない部分がある。自社環境で使う前に、小さなテストから確認することをすすめる。 forceRemoteSettingsRefreshのバグは過去のセッションに遡って影響するものではないが、「接続できなかった時間帯にポリシー未適用で動いていたか」を確認する手段はない。継続的な監査ログと組み合わせて運用するのが現実的だろう。 IdPグループルーティングは、既存の設定を変えることなく追加できる。試験的な上流を限定ユーザーに展開したい場面があれば、検討する価値はある。 V2.1.316との関係について v2.1.316(2026-10-31)も同じ週にリリースされており、こちらは別記事にまとめている。v2.1.314はその直前版で、セキュリティ設定の追加とポリシー適用のバグ修正が中心。継続的に運用している環境では両バージョンの変更点を合わせて確認してほしい。 関連記事(note): note.com

  33. X@tangtang_babe · 2 likes · 140 views

    曾经让无数玩家沉迷的《托克》和《旷野之息》,如今已经成为废弃项目 如果你对未完成的游戏项目、开发过程,或者塞尔达系列背后的技术探索感兴趣,不妨去 GitHub 看看,说不定你会发现一些意想不到的内容 《托克》 iHaiDeeZ/TOTK-PS4 《旷野之息》 iHaiDeeZ/BOTW 项目现已开放,如果你愿意,也可以尝试接手它们展现你的想法

  34. X@todessehnsuchtt · 1 like · 23 views

    Eu sei que tá cedo mas então um cara simplesmente está fazendo um port de Dark Souls 1 para o PlayStation 2. nekomancer01/DarkSoulsPS2 t.co

  35. ¿Cuántos metros cuadrados se compran con 125.000 dólares? 30 ciudades de Latinoamérica y Portugal Con 125.000 dólares se compran unos 165 m² de apartamento en Maracaibo (Venezuela), la ciudad que más rinde de 30, y solo 15 m² en Lisboa (Portugal). DOI: 10.5281/zenodo.23523372

  36. X@Trinsic72 · 37 likes · 1 repost · 1,569 views

    Heartfelt Gold Update v1.0.4 (Optional Level Cap) Link: github.com/Trinsic64/Heart-Gold-Retiled/releases/… - Level Cap NPC in all Pokémon Centre's - To refresh the Level Cap settings to Default Level Cap: Disable Level Cap -> Enable Level Cap - Increment at your own discretion - Import Save Compatible with prior Versions - You only need to Patch this Latest Version

  37. X@mushroom_xxxxx · 4 likes · 73 views

    AI便利すぎる やりたかった細かいことができる mushroom1729-xperia/cam-gallery-hook

  38. ¿Cuántos metros cuadrados se compran con 1.200 millones de pesos? 38 ciudades de Colombia Con 1.200 millones de pesos se compran unos 354 m² de apartamento en Soacha, la ciudad que más rinde de 38, y 129 m² en El Retiro. En Bogotá alcanzan para 165 m² y en… DOI: 10.5281/zenodo.23523348

  39. Redditu/RealInsurance3995 · r/ordinadors · 3 points

    Keybytes permet moure cada tecla i unir-la amb imants Keybytes és un prototip de teclat en què cada tecla és un mòdul independent. Les peces s’uneixen amb imants i contactes elèctrics als quatre costats, de manera que es poden canviar de lloc sense muntar una placa amb una distribució fixa. Cada mòdul porta un microcontrolador i es comunica amb la resta. Una unitat central connecta el conjunt amb l’ordinador. El vídeo mostra les primeres proves amb poques tecles, encara lluny d’un teclat complet acabat. L’autor publica el disseny i el codi a GitHub amb llicència MIT, perquè se’n pugui estudiar el funcionament. Font: notaroomba/keybytes

  40. ¿Cuántos metros cuadrados se compran con 100 millones de pesos? 38 ciudades de Colombia Con 100 millones de pesos se compran unos 29 m² de apartamento en Soacha, la ciudad que más rinde de 38, y 11 m² en El Retiro. En Bogotá alcanzan para 14 m² y en Medellín… DOI: 10.5281/zenodo.23523311

  41. X@arunimastwt · 1 like · 6 views

    @louis_harwood Yes, actively building it, and shipping most weeks. When you get that admin day, the quick start is three commands, and I’d love to hear what’s confusing or missing: invarislabs/invaris-agentsec

  42. X@MRomeroFinance · 1 like · 3 views

    That is the ten. The screener ranks companies against criteria written down in full and reproducible from the stored data. It does not forecast prices. Method, universe and record: MRomeroFinance/research Thank you for reading. Not advice. No positions.

  43. ¿Cuántos metros cuadrados se arriendan con 800 dólares al mes? 34 ciudades de Latinoamérica y Portugal Con 800 dólares al mes se arriendan unos 200 m² de apartamento en Cochabamba (Bolivia), la ciudad que más rinde de 34, y solo 20 m² en Punta del Este (Uruguay). DOI: 10.5281/zenodo.23523430

  44. DEV@martinmunozb · 1 comment

    Error #1690130 en WhatsApp Business Coexistence: cómo recuperé los webhooks tras un Embedded Signup interrumpido Martín Muñoz · 2 de noviembre de 2026 WhatsApp Cloud API · Embedded Signup · Error 1690130 · Graph API · 131000/10 · Incidente real > Estado real, sin exageraciones: Meta empezó a mostrar #1690130 («el identificador comercial no es válido») después de interrumpir un alta de coexistencia, aunque el porfolio seguía existiendo y estaba verificado. No logré eliminar #1690130 del asistente de Meta. Sí conseguí recuperar los mensajes entrantes y los ecos desde WhatsApp Business sin borrar ni migrar el número, completando la integración pendiente de mi propia app. Sin embargo, la sincronización del historial y contactos sigue rechazada con 131000, subcódigo 10. Hay indicios de alta incompleta, pero la causa exacta aún necesita confirmación de Meta. Contexto: el segundo error, después de #3441034 Desarrollo una aplicación multiempresa con una bandeja de WhatsApp conectada a la Cloud API. Mi número comercial ya funcionaba en la app de WhatsApp Business: necesitaba coexistencia, no una migración. Primero sufrí #3441034, que dejé de ver tras desconectar Meta Business Suite Inbox desde el menú WhatsApp Business → Ajustes → Cuenta → Plataforma para empresas. [He publicado ese primer error en un artículo específico](whatsapp-business-error-3441034-solucion-meta-business-suite.md). Después avancé por el asistente de Embedded Signup. Al llegar a la parte de empresa/zona horaria retrocedí y desconecté la plataforma mientras el proceso todavía no había terminado. Cuando traté de retomarlo apareció: #1690130 [identificador del porfolio] no es un identificador comercial válido El identificador no era inventado. El porfolio existía y estaba verificado. Por ello dejé de asumir que el mensaje de la ventana describía literalmente el estado real del recurso. Qué NO funcionó - Reabrir Embedded Signup una y otra vez. - Repetir el registro desde distintas sesiones. - Revisar permisos básicos y validar que el porfolio seguía existiendo. - Volver a desconectar y conectar el dispositivo. - Buscar una opción para «reparar» el porfolio desde la pantalla del error. No recomiendo repetir desconexiones ni eliminar la cuenta. No comprobé que esos pasos reparasen #1690130 y sí podrían empeorar el estado de una cuenta en uso. No se ha demostrado que la zona horaria, la interrupción o que la WABA sea propia sean la causa interna de #1690130. Son circunstancias del incidente, no un diagnóstico confirmado por Meta. Paso 1: averiguar qué había llegado a crear Meta En lugar de reiniciar el alta, inspeccioné el estado del número, la WhatsApp Business Account (WABA) y la suscripción de la aplicación usando Graph API en modo de lectura. Esto fue lo que observé: | Comprobación | Resultado | | --- | --- | | Estado del número | CONNECTED | | Plataforma | CLOUD_API | | Indicador de uso simultáneo de la app | is_on_biz_app: true | | WABA existente | Sí | | App suscrita a la WABA | No: subscribed_apps estaba vacío | | Configuración de campos de webhook | messages, smb_message_echoes, history, smb_app_state_sync, account_update | | Canal correspondiente dentro de mi aplicación | No existía | | WhatsApp Manager | En ocasiones mostraba «Fuera de internet» | Consultas ilustrativas, sustituyendo los identificadores por los de tu cuenta y utilizando una versión de Graph admitida: GET https://graph.facebook.com/vXX.X/<WABA_ID>/phone_numbers GET https://graph.facebook.com/vXX.X/<WABA_ID>/subscribed_apps GET https://graph.facebook.com/vXX.X/<PHONE_NUMBER_ID>?fields=platform_type,is_on_biz_app Authorization: Bearer <TOKEN_AUTORIZADO> Los campos que una versión de Graph admite pueden cambiar. Un rechazo de permisos, por ejemplo código 100, no confirma por sí mismo que el WABA no exista. Conclusión de la inspección: el número tenía un estado Cloud API aparentemente operativo, pero faltaban dos pasos de integración: suscribir la app a la WABA y guardar el canal en mi software. Es crucial distinguir la configuración de los campos del webhook de la app de la suscripción de una app a una WABA concreta. Puedes tener los campos bien configurados y aun así no recibir los webhooks de una WABA no suscrita. Paso 2: recuperar solo la parte de la integración que faltaba Esta es la solución técnica que ejecuté en mi propia infraestructura y con autorización sobre mi propia WABA; no es un procedimiento genérico para resolver el error de la ventana de Meta. 1. Creé un usuario del sistema dedicado a esa aplicación y a ese WABA. 2. Emití un token con los permisos whatsapp_business_management y whatsapp_business_messaging. 3. Verifiqué que funcionaba para ese WABA y que no accedía a los cuatro WABA de clientes conocidos con los que probé. Eso es una comprobación limitada, no una prueba de aislamiento sobre todas las WABA del mundo. 4. Guardé el token en un Vault del servidor, sin exponerlo al navegador ni registrarlo en logs. 5. Revisé el código que crea canales y probé las precondiciones, el aislamiento y la posibilidad de error parcial antes de escribir en producción. 6. Guardé el canal local correspondiente al número ya existente. 7. Suscribí la aplicación a la WABA existente mediante la operación documentada por Meta: POST https://graph.facebook.com/vXX.X/<WABA_ID>/subscribed_apps Authorization: Bearer <TOKEN_DE_USUARIO_DEL_SISTEMA> 8. Volví a leer subscribed_apps y comprobé que el canal local aparecía activo. No ejecuté /<PHONE_NUMBER_ID>/register; tampoco borré, migré o desregistré el número ni cambié de propietario la WABA. El procedimiento no incluía volver a realizar Embedded Signup. Qué se consiguió realmente El 2 de noviembre de 2026 comprobé lo siguiente: - La aplicación quedó suscrita a la WABA. - El canal local se creó y quedó activo. - Un mensaje entrante nuevo enviado desde otro teléfono apareció tanto en mi bandeja web como en WhatsApp Business (aunque en la tablet el contenido mostraba «Esperando este mensaje»). - Una respuesta escrita desde WhatsApp Business llegó al destinatario y fue registrada por mi sistema como smb_message_echoes; también se confirmó un estado delivered. Eso acredita que los entrantes y los ecos funcionaban. No demuestra que la tablet descifre correctamente todos los mensajes; tampoco he acreditado todavía el envío independiente desde Cloud API en esa fecha. Paso 3: el bloqueo que siguió apareciendo — 131000 / subcódigo 10 Después de recuperar la recepción quise importar el historial previo de WhatsApp Business. Se solicitó la sincronización de contactos y la de conversaciones mediante: POST https://graph.facebook.com/vXX.X/<PHONE_NUMBER_ID>/smb_app_data Authorization: Bearer <TOKEN_AUTORIZADO> Ambas solicitudes fueron rechazadas, devolviendo: code: 131000 error_subcode: 10 This API is only available to WhatsApp Business App phone numbers onboarded on to WhatsApp Business Platform Es un contraste importante: Graph indicaba CONNECTED, CLOUD_API, is_on_biz_app: true y llegaban webhooks, pero smb_app_data no aceptaba el número para sincronizar contactos e historial. Esto es compatible con un alta de coexistencia parcialmente completada, pero no demuestra que esa sea la causa exacta. El mensaje tampoco identificaba un plazo de 24 horas vencido ni una negativa a compartir historial. Tras esos rechazos, no repetí la sincronización. Contacté con la vía de soporte de Meta para pedir una comprobación del onboarding real y de la elegibilidad para historial. No recuperé los chats antiguos por API. El historial del móvil antiguo, la copia de seguridad y el histórico de Cloud API son asuntos diferentes; reinstalar WhatsApp o desregistrar el número para probar puede comprometer la coexistencia y las copias existentes. Cómo diagnosticar tu caso sin arriesgar el número | Síntoma | Primero comprueba | No deduzcas automáticamente | | --- | --- | --- | | #1690130 tras alta interrumpida | Estado real del porfolio, WABA, número y suscripción en Graph | Que el porfolio no existe o haya que eliminarlo | | CONNECTED pero no llegan mensajes | subscribed_apps, webhook configurado, persistencia local y pruebas reales | Que el onboarding esté completamente listo | | Llegan mensajes, pero no los ecos de la app | Suscripción al campo smb_message_echoes y eventos recibidos | Que los textos enviados desde el móvil se reflejen solos | | 131000 / 10 en smb_app_data | fbtrace_id, fecha, estado Graph y onboarding | Que el historial ya se importó o que el plazo venció | | 141006 al intentar enviar | Estado de pagos y motivo concreto de Meta | Que la recepción por webhooks tampoco funcione | Lo que pediría a Meta Direct Support 1. Confirmar el estado interno real del onboarding de coexistencia para el número y explicar #1690130. 2. Aclarar por qué smb_app_data devuelve 131000 / 10 si is_on_biz_app: true y los webhooks y ecos funcionan. 3. Reparar o completar el proceso, si existe una opción compatible con mantener el número en WhatsApp Business, sin borrar ni migrar la cuenta. 4. Confirmar expresamente si todavía es posible habilitar la sincronización de contactos/historial después de solicitudes rechazadas. Envía a Meta los identificadores reales y los fbtrace_id por soporte privado. No publiques accesos, tokens, teléfonos de clientes ni identificadores de sesión en un artículo abierto. Lo que queda sin resolver El error #1690130 en Embedded Signup no se ha reparado de manera confirmada. Lo que se recuperó fue la integración del canal para mensajes nuevos y ecos. La sincronización de contactos y conversaciones antiguas seguía bloqueada, y el estado completo de coexistencia requería aclaración de Meta. Por tanto, este artículo no debe interpretarse como «cómo eliminar #1690130 siempre», sino como cómo diagnosticar un alta interrumpida, recuperar webhooks cuando los recursos ya existen y reconocer los límites de la recuperación. Referencias técnicas - Meta — Embedded Signup y coexistencia de WhatsApp Business. - Meta — Documentación de Embedded Signup (Postman). - Meta — Suscribir una app a una WABA (Postman). - Bird — Errores y diagnóstico de coexistencia. - [Primer error: solución que me funcionó para #3441034](whatsapp-business-error-3441034-solucion-meta-business-suite.md). --- Martín Muñoz · GitHub personal · Caso documentado el 2 de noviembre de 2026. Último estado: recepción y eco confirmados; sincronización histórica bloqueada. Si te ocurrió lo mismo, puedes compartir el código, el paso donde falla Embedded Signup y el resultado anonimizado de subscribed_apps. Ese contexto es mucho más útil que repetir el registro a ciegas.

  45. X@BIMALSH23 · 1 like · 2 views

    Here is the full benchmark writeup and workflow code: github.com/guregodevo/memdoor/tree/main/examples/…

  46. X@thara1129 · 6 likes · 245 views

    github.com/hra1129/msx_basic_compiler/releases/ta… Museくんにいろいろ直してもらいました。 説明書もしっかりまとめてくれてます。

  47. ¿Cuántos metros cuadrados se arriendan con 600 dólares al mes? 34 ciudades de Latinoamérica y Portugal Con 600 dólares al mes se arriendan unos 150 m² de apartamento en Cochabamba (Bolivia), la ciudad que más rinde de 34, y solo 15 m² en Punta del Este (Uruguay). DOI: 10.5281/zenodo.23523403

  48. X@GreekFireX · 1 like · 61 views

    49 個 agent 的 AI 遊戲工作室,作者自己測完:流程越重,遊戲越爛。 Claude-Code-Game-Studios 今天 GitHub +967 星,總星 3.2 萬。README 自曝:同一份需求,standard 模式寫程式前先產 30 份文件、耗 58 分鐘,盲評加試玩排最後。 要用就留預設 minimal,別調成 full。 Donchitos/Claude-Code-Game-Studios

Older posts →