All (110)Personal Introduction (1)AI Summary (8)Project Management (4)Investment Strategy (9)Financial Market Analysis (6)AI Software Engineering (9)AI Research (7)Content Management (9)Cognitive Development (1)Philosophical Reflection (3)Entrepreneurship (1)AI Tools Development (9)Product Development (3)Troubleshooting (2)Quantitative Finance (12)AI Cost Analysis (1)System Architecture (1)Simulation Framework (1)Technical Log (3)AI Social Systems (3)Personal Reflection (1)
Challenges and Solutions of CZON Link Checking with AI Repair
Troubleshooting
👤 Software developers, AI tool users, technical documentation maintainers
This article details the development process of CZON's link checking feature, from the initial implementation of dead link detection to the discovery of problems with AI-based repair. The author identifies two main issues with AI in link repair: it does not scan the entire project files by default, and it has insufficient understanding of relative paths. This leads to errors such as redirecting links to compilation output directories or creating symbolic links. By analyzing the root causes, the author proposes a solution: providing AI with a list of relative path candidates based on the problematic file, avoiding the need for AI to scan the entire project or interpret relative paths independently. Ultimately, CZON version 0.9.1 successfully fixed 500 link errors. The author concludes that compilation checks need to complement AI repair and designs a check output format suitable for AI.
- ✨ CZON implemented a link checking feature, but errors occurred during AI repair
- ✨ AI has insufficient understanding of relative paths and does not scan the entire project by default
- ✨ The solution is to provide AI with a list of relative path candidates based on the problematic file
- ✨ Compilation checks need to be designed in an AI-friendly format
- ✨ CZON version 0.9.1 successfully fixed 500 link errors
📅 2026-02-09 · 457 words · ~3 min read
Troubleshooting WebSocket Connection Issues: Caused by 1Password Browser Extension
Troubleshooting
👤 Developers and network engineers encountering WebSocket connection issues, or technical personnel interested in browser extensions and proxy tools
On January 28, 2026, the author shared an experience troubleshooting unstable WebSocket connections. Initially suspecting Surge proxy configuration, Cloudflare protection, or server issues, a comparison revealed that only the author and Ryan were affected, while Mage and C1 were fine. Through a series of tests—including checking terminal connections, switching browsers, and disabling browser extensions—the issue was pinpointed using a binary search method to the 1Password browser extension affecting WebSocket connection stability in Chrome. Disabling the extension resolved the problem, verified by Ryan. The article emphasizes the importance of methodology and systematic steps in troubleshooting tricky issues, aiming to help readers facing similar problems save time.
- ✨ WebSocket connections were unstable in Chrome, requiring retries to succeed
- ✨ The issue only affected the author and Ryan, with Mage and C1 unaffected, ruling out server problems
- ✨ The author used the Surge proxy tool, but troubleshooting eliminated its configuration as the cause
- ✨ Terminal connections (e.g., curl, wscat) were stable, indicating the problem was limited to the browser
- ✨ Switching to Safari browser resulted in stable connections, pointing to a Chrome-specific issue
📅 2026-01-28 · 468 words · ~3 min read