[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"site-info":3,"latest-news":9,"gallery-custom-links":131,"update-pulse-widget":142},{"username":4,"nickname":5,"bio":6,"avatarUrl":7,"email":8},"wgd","翁国栋 · 镜间笔记 ","写代码、看云、发呆，排名不分先后",null,"wengguodong@hotmail.com",{"items":10,"total":127,"page":128,"pageSize":129,"totalPages":130},[11,19,28,45,53,61,69,84,90,96,108,115],{"type":12,"id":13,"title":7,"summary":14,"coverImage":7,"category":7,"tags":15,"createdAt":16,"imageCount":17,"seoSlug":7,"mood":7,"images":18},"murmur","09b87715-a185-42db-bf81-36de5717bad3","这次真的玩大了,光都被收走了",[],"2026-07-16T11:11:26",0,[],{"type":12,"id":20,"title":7,"summary":21,"coverImage":7,"category":7,"tags":22,"createdAt":23,"imageCount":17,"seoSlug":7,"mood":24,"images":25},"33afbb42-c983-40c6-ab0a-07fd9d790e46","感觉分析还是准的，虽然最高点减仓了，但没有清仓",[],"2026-07-03T10:39:09","随想",[26,27],"\u002Foriginals\u002F2026\u002F07\u002F41bdc764-4547-40e5-92af-3374b24287e2.png","\u002Foriginals\u002F2026\u002F07\u002F24a2cde8-2b48-44c5-92c8-70311392aae7.png",{"type":29,"id":30,"title":31,"summary":32,"coverImage":7,"category":33,"tags":37,"createdAt":43,"imageCount":17,"seoSlug":44},"article","663fda43-7479-4d43-8fcf-44dacac2b6e3","智能体(Agent)中红蓝对抗的作用","本文揭示了LLM基金分析Agent普遍存在的过度自信与“谄媚”幻觉，提出通过红蓝对抗机制强化风控，避免盲目追涨。\n蓝方负责量化初判，红方则扮演“毒舌风控官”，利用近一周持仓漂移度、大额资金净流出和历史预测胜率等指标尖锐举证，专门挑刺做空。\n借助红方压迫性证据，蓝方被迫重审初稿，修正动量追涨信号为防守观望，从而有效过滤大模型因季报持仓滞后导致的错误预测。\n该红蓝对抗思维链方法，本质上是用内部审查强行压制AI自嗨，让基金实盘估值与隔天预测在资金背离时仍能保持理性，敬畏风险。",{"id":34,"name":35,"color":36,"type":29},"f7250246-6cda-4333-912d-72e16085be7d","AI相关","#00ff6e",[38,39,40,41,42],"AI智能体","红蓝对抗","Agent","金融科技","Agent 开发","2026-06-29T18:54:34","ai-agent-red-blue-teaming",{"type":12,"id":46,"title":7,"summary":47,"coverImage":7,"category":7,"tags":48,"createdAt":49,"imageCount":17,"seoSlug":7,"mood":50,"images":51},"8d0afcce-0b2a-4198-8315-c324eeed17d7","妈的，用ai分析，有量化分析，再撑一天，我就不信龙头股能全撤资",[],"2026-06-24T13:52:45","淦",[52],"\u002Foriginals\u002F2026\u002F06\u002F3c67ab63-29c5-4fc2-9f29-acf2bd81bf5d.jpg",{"type":12,"id":54,"title":7,"summary":55,"coverImage":7,"category":7,"tags":56,"createdAt":57,"imageCount":17,"seoSlug":7,"mood":58,"images":59},"3cfc13d5-2edb-485f-bbe1-6f263251c492","好像又回来了",[],"2026-06-09T17:16:49","华尔街之狼",[60],"\u002Foriginals\u002F2026\u002F06\u002F20eb6c4f-8fe8-4ece-8726-e90920624432.jpg",{"type":12,"id":62,"title":7,"summary":63,"coverImage":7,"category":7,"tags":64,"createdAt":65,"imageCount":17,"seoSlug":7,"mood":66,"images":67},"d127a1d0-6e76-4225-96d7-43a42f2092ca","现在撤回周五的加仓还来的及吗？",[],"2026-06-08T16:27:46","华尔街之狗",[68],"\u002Foriginals\u002F2026\u002F06\u002Fdb4cbe38-d4a3-4483-9156-9cf892827406.webp",{"type":29,"id":70,"title":71,"summary":72,"coverImage":7,"category":73,"tags":77,"createdAt":82,"imageCount":17,"seoSlug":83},"5d417ea6-ce53-4dce-ac81-cd660bfd7b7d","如何使用passkey保护你的登录信息","告别繁琐的传统密码，拥抱跨平台无密码身份鉴权，本文详解如何利用非对称加密杜绝钓鱼与撞库风险，为网站快速集成Passkey登录体验。\n深入阐述WebAuthn标准原理，通过设备生成的密钥对实现本地生物识别验证，服务端仅存储公钥和签名计数，彻底解决记忆弱密码难题。\n实战展示基于FastAPI与webauthn库的完整开发流程，涵盖数据库模型设计、注册参数生成（register options）与验证响应、认证选项（authentication options）等核心接口。\n借助Authenticator、1Password等主流密码管理器的云同步能力，跨设备无缝迁移通行密钥，让用户随时安全登录。",{"id":74,"name":75,"color":76,"type":29},"f1fe85d8-c917-4caa-a1e3-e9a33d4c97da","日常记录","#007bff",[78,79,80,81],"Passkey","通行密钥","账号保护","密码管理","2026-06-02T18:19:57","use-passkey-protect-login-data",{"type":12,"id":85,"title":7,"summary":86,"coverImage":7,"category":7,"tags":87,"createdAt":88,"imageCount":17,"seoSlug":7,"mood":7,"images":89},"6e69abca-8a28-40ce-8c8f-98d79b15e730","还好补仓了，吃肉吃肉",[],"2026-06-02T13:41:32",[],{"type":12,"id":91,"title":7,"summary":92,"coverImage":7,"category":7,"tags":93,"createdAt":94,"imageCount":17,"seoSlug":7,"mood":7,"images":95},"5819e5eb-aba4-4af3-88cb-9df6676da6c4","缅A开始收割了",[],"2026-05-28T11:42:58",[],{"type":29,"id":97,"title":98,"summary":99,"coverImage":7,"category":100,"tags":101,"createdAt":106,"imageCount":17,"seoSlug":107},"e045494b-9e5e-4e78-9d81-5de2997a2dfc","验证码的尽头是“互相伤害”，用 PoW 拦截 AI 爬虫的底层逻辑","传统验证码依赖“人比机器擅长认知”的前提，通过扭曲字符和拼图来区分真实用户与脚本，但这个前提在 AI 时代已难以为继。\n工作量证明转而要求客户端为每次请求付出硬件算力代价，通过执行 SHA256、Scrypt 等轻量加密谜题让普通用户无感，却使高频爬虫的电力和服务器成本急剧膨胀。\n对于 AI 爬虫而言，PoW 如同景区门票：少量访问开销可忽略，但大规模并发抓取会导致爬虫集群算力耗尽，在经济账上彻底失败，从而保护网站带宽与性能。\n现代 PoW 系统会结合 IP 声誉、访问频率和设备可信度动态调整难度，以降低对低性能设备用户的误伤，体现了个人站点对数据掠夺的主动反抗。",{"id":34,"name":35,"color":36,"type":29},[102,103,104,105],"Web安全","人机验证","PoW","AI爬虫","2026-05-27T17:29:34","pow-captcha-block-ai-crawlers",{"type":12,"id":109,"title":7,"summary":110,"coverImage":7,"category":7,"tags":111,"createdAt":112,"imageCount":17,"seoSlug":7,"mood":113,"images":114},"d7ab2298-971f-4b0c-bfcc-45534351200d","写文章太累，所以“我”出来了",[],"2026-05-23T18:37:40","AI",[],{"type":29,"id":116,"title":117,"summary":118,"coverImage":7,"category":119,"tags":120,"createdAt":125,"imageCount":17,"seoSlug":126},"f741a733-aeaa-4880-a9c8-f1725af6dc81","在SaaS多商户模式下，商户配置如何流畅切换","支付配置一旦更新覆盖，新订单和老退款会因商户主体变更产生严重错位，根源在于操作生命周期不同的矛盾。\n通过将配置改为不可变模型，禁用 UPDATE，每次变更插入新记录并用状态位标识，订单强制冗余支付商户号，形成历史快照与时间轴，为后续溯源留依据。\n路由时比对订单快照与当前生效商户号，一致走全局缓存池高效处理新单，不一致则用归档配置构建临时实例处理老退款，避免污染主池，并通过 Redis Pub\u002FSub 异步预热新配置，消除冷启动延迟。",{"id":74,"name":75,"color":76,"type":29},[121,122,123,124],"Spring Boot","支付系统","SaaS架构","Redis","2026-05-18T14:41:04","saas-multi-tenant-config-switch",22,1,12,2,[132],{"title":133,"url":134,"description":135,"icon":7,"type":136,"openInNewTab":137,"status":138,"sortOrder":139,"id":140,"createdAt":141,"updatedAt":141},"问答","\u002Fgames\u002Fjev-qa\u002F","问个问题，判断对错、做个选择，或者评个分。","resource","true","active",10,"6160354f-7611-4408-9c42-11080d90a50d","2026-09-22T02:11:13",[143,145,147,149,151,153,155],{"date":144,"count":17,"articleCount":17,"albumCount":17},"2026-09-17",{"date":146,"count":17,"articleCount":17,"albumCount":17},"2026-09-18",{"date":148,"count":17,"articleCount":17,"albumCount":17},"2026-09-19",{"date":150,"count":17,"articleCount":17,"albumCount":17},"2026-09-20",{"date":152,"count":17,"articleCount":17,"albumCount":17},"2026-09-21",{"date":154,"count":17,"articleCount":17,"albumCount":17},"2026-09-22",{"date":156,"count":17,"articleCount":17,"albumCount":17},"2026-09-23"]