<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.10.0">Jekyll</generator><link href="https://zim-l.github.io/feed.xml" rel="self" type="application/atom+xml" /><link href="https://zim-l.github.io/" rel="alternate" type="text/html" /><updated>2026-09-09T00:16:01+00:00</updated><id>https://zim-l.github.io/feed.xml</id><title type="html">Zimin Liang</title><subtitle>This website includes my personal info and my research portfolio where you can find resources of research projects I am/was working on. </subtitle><author><name>梁子民 Zimin Liang</name></author><entry xml:lang="en"><title type="html">Exocoetidae: A Backup Way to Keep Working with AI</title><link href="https://zim-l.github.io/posts/exocoetidae/" rel="alternate" type="text/html" title="Exocoetidae: A Backup Way to Keep Working with AI" /><published>2026-09-07T23:00:00+00:00</published><updated>2026-09-07T23:00:00+00:00</updated><id>https://zim-l.github.io/posts/exocoetidae-en</id><content type="html" xml:base="https://zim-l.github.io/posts/exocoetidae/"><![CDATA[<p>On 3 September 2026, ChatGPT, Claude and Grok experienced overlapping service outages. For people who already rely on AI at work, a conversation or a piece of writing could suddenly grind to a halt. <a href="https://www.theregister.com/ai-and-ml/2026/09/03/chatgpt-claude-and-grok-all-had-outages-at-the-same-time/5294322">The Register reported the overlapping interruptions</a>.</p>

<p>Large language models are becoming infrastructure. Infrastructure can fail. If ChatGPT or Claude is your only way to use an LLM, losing that familiar entrance can interrupt everything you were doing with it.</p>

<p><strong>Exocoetidae is a lightweight AI chat page: connect your own model API and you have another window in which to keep working.</strong> Use it for writing, translation, exploring ideas or discussing code. Configure different providers ahead of time and switch when needed.</p>

<p>With your permission, it can access a local folder you select, read your documents and code, and edit them with safety checks, reviewable changes and undo. You can also ask multiple agents to work in parallel—for example, researching material, editing code and checking results—and follow their progress in one chat window.</p>

<p><a class="btn btn--primary" href="/exocoetidae/">Open the Exocoetidae chat window</a></p>

<h2 id="open-and-start-for-everyday-use-i-recommend-deepseek">Open and start; for everyday use, I recommend DeepSeek</h2>

<p>No API key yet? Type a task and start. The Default Model tries several free routes in sequence and shows the resolved model name in the top bar. Free services can be rate-limited or temporarily unavailable and are not suitable for personal or confidential material. Connect your own API when you want steady everyday service.</p>

<p>An API is another way to access a model. Create an API key on the provider’s platform and enter it in Exocoetidae to chat with that provider’s models. Billing is usually based on usage and is separate from a chat website subscription.</p>

<p><strong>For a first try, I recommend DeepSeek. Around RMB 50 is a comfortable starting budget for everyday text conversations.</strong> Treat this as a suggested budget, rather than a monthly plan or unlimited allowance. How long it lasts depends on the model, conversation length and frequency; long documents and tasks with multiple steps consume more. Check current prices and credit terms before topping up.</p>

<ol>
  <li>Sign in to the <a href="https://platform.deepseek.com/">DeepSeek platform</a>, add credit and create an API key.</li>
  <li>In Exocoetidae, open Settings → Models (「设置 → 模型」), select DeepSeek, click Add (「添加」) and paste your key.</li>
  <li>Use <code class="language-plaintext highlighter-rouge">https://api.deepseek.com</code> as the Base URL. Fetch the model list with 「拉取」, or enter a model name from the official documentation, such as the currently listed <code class="language-plaintext highlighter-rouge">deepseek-v4-flash</code>.</li>
  <li>Close settings, select your model in the chat window and send a test message.</li>
</ol>

<p>Official guides: <a href="https://api-docs.deepseek.com/">Your First API Call</a> and <a href="https://api-docs.deepseek.com/quick_start/pricing">Models &amp; Pricing</a>. You do not need to write the sample code: copy the key, address and model name into the settings instead.</p>

<p>Other options include:</p>

<table>
  <thead>
    <tr>
      <th>Provider</th>
      <th>Official tutorial</th>
      <th>Exocoetidae setup</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>Kimi / Moonshot</td>
      <td><a href="https://platform.kimi.com/docs/get-api-key">Create a key and make your first call</a></td>
      <td>Select Moonshot, enter your key, use <code class="language-plaintext highlighter-rouge">https://api.moonshot.cn/v1</code>, and enter a model name from the documentation.</td>
    </tr>
    <tr>
      <td>Alibaba Cloud Model Studio / Qwen</td>
      <td><a href="https://help.aliyun.com/zh/model-studio/first-api-call-to-qwen">First Qwen API call</a></td>
      <td>Activate Model Studio and create a key. Select 通义, then replace the Base URL with the documented OpenAI-compatible address for your region and workspace, and enter your model name.</td>
    </tr>
  </tbody>
</table>

<p>The key, address and model must match the same service configuration. If a connection fails, check credit, model access and the address first; some providers restrict direct browser connections. Test your backup ahead of time so it is ready when you need it.</p>

<h2 id="using-exocoetidae">Using Exocoetidae</h2>

<p>The <strong>chat window</strong> handles everyday work: open it and type your question. The top bar includes font-size controls and a model-settings shortcut; the original bottom-left Settings button remains available. Search your history, organise conversations into projects and upload text material to discuss. Markdown, maths notation, editing and resubmitting messages, conversation branches and temporary chats are available. The current interface is primarily in Chinese; prompts and replies can be in either Chinese or English.</p>

<p>For file work, open the right-hand panel. Browser-stored project files, attachments for the current conversation and local folders you authorise are shown separately, with filename search, refresh, preview, original-name downloads, multi-file upload and drag-and-drop. The panel refreshes after agent edits. The Changes This Turn (「本轮改动」) card still provides line counts, line-by-line differences, open, path, undo and download controls. On narrow screens, the file panel becomes a drawer so the chat remains usable.</p>

<p>Add images with 「＋ 图片」, drag them into the composer or paste them. Removable thumbnails appear before sending. A vision-capable model can understand the images, which stay with the conversation in the current browser and can be enlarged or downloaded from the message or file panel. A model that is not marked as image-capable produces a clear prompt to switch models.</p>

<p><strong>Memory across conversations</strong> carries long-term preferences and earlier discussions into new chats. Review and edit global memory under Settings → Memory (「设置 → 记忆」); project memory keeps project context together. <strong>Scheduled execution</strong> accepts requests such as “Summarise this project’s progress every day at 5 pm.” Manage tasks under Settings → Reminders (「设置 → 提醒」). Tasks run when due while the page is open. With push configured, reminders can arrive after you close the page; tasks execute when you reopen it.</p>

<p>Web access now works without the enhancer: the base tools use free DDG search and automatically choose between a direct browser request and key-free Jina Reader for webpage extraction. A failed route falls through instead of ending the whole turn. The optional <strong>local experience enhancer</strong> can still improve reliability, add Brave Search and deliver push reminders while the page is closed.</p>

<p>Settings and conversation history stay in the current browser. Sending a question shares the relevant content with your selected model provider; web features also share content with the corresponding services. Before changing devices or clearing browser data, export a backup under Settings → Data (「设置 → 数据」) and keep its passphrase safe.</p>

<p>I want Exocoetidae to be a small tool that is useful on an ordinary day and already waiting when you need it. As AI becomes part of more work, having another entrance becomes more valuable.</p>]]></content><author><name>梁子民 Zimin Liang</name></author><summary type="html"><![CDATA[A lightweight AI chat window. Connect your own API and keep another option ready when your usual AI service is unavailable.]]></summary></entry><entry xml:lang="zh-CN"><title type="html">Exocoetidae：给大模型工作流留一个备用入口</title><link href="https://zim-l.github.io/zh/posts/exocoetidae/" rel="alternate" type="text/html" title="Exocoetidae：给大模型工作流留一个备用入口" /><published>2026-09-07T23:00:00+00:00</published><updated>2026-09-07T23:00:00+00:00</updated><id>https://zim-l.github.io/zh/posts/exocoetidae-zh</id><content type="html" xml:base="https://zim-l.github.io/zh/posts/exocoetidae/"><![CDATA[<p>2026 年 9 月 3 日，ChatGPT、Claude 和 Grok 在同一时段出现服务故障。对于已经把 AI 用进日常工作的人来说，这意味着正在写的东西、正在讨论的问题，可能突然就没法继续了。<a href="https://www.theregister.com/ai-and-ml/2026/09/03/chatgpt-claude-and-grok-all-had-outages-at-the-same-time/5294322">The Register 的报道</a>记录了这次时间重叠的中断。</p>

<p>大语言模型正在变成一种基础设施。但基础设施也会出问题。如果平时只通过 ChatGPT 或 Claude 使用大模型，熟悉的入口一旦打不开，手头的工作很容易跟着停下来。</p>

<p><strong>Exocoetidae 是一个轻量的大模型对话网页：接上自己的大模型 API，就多了一个可以继续工作的窗口。</strong> 写作、翻译、整理想法、讨论代码，都可以从这里接着做。你可以预先配置不同厂商，在需要时切换。</p>

<p>在你授权后，它可以访问选定的本地文件夹，阅读并安全地修改你的文档与代码：修改有校验，完成后可以查看文件差异和改动总结，也可以撤销。你还可以让多个智能体并行分工，例如同时研究资料、修改代码与核对结果，在一个对话窗口里跟进进度。</p>

<p><a class="btn btn--primary" href="/exocoetidae/">打开 Exocoetidae 对话窗口</a></p>

<h2 id="打开即用日常使用我推荐-deepseek">打开即用；日常使用我推荐 DeepSeek</h2>

<p>还没有 API key，也可以直接输入任务。「默认模型」会逐个尝试多个免费通道，并在右上角显示实际取得的模型名；免费服务可能限流或临时不可用，也不适合提交个人与机密信息。想要稳定地日常使用，再接入自己的 API 即可。</p>

<p>API 可以理解为使用模型的另一种入口。你在厂商的平台申请一把 API key，填进 Exocoetidae，就能在这个窗口里使用它的模型。通常按实际使用量计费，不等同于聊天网站的会员订阅。</p>

<p><strong>如果是第一次尝试，我推荐 DeepSeek：先充值 50 元人民币左右，作为日常文字对话的起步预算，可以比较放松地用起来。</strong> 这是一笔建议预算，不是包月或无限额度；能用多久取决于模型、对话长度和使用频率，长文与多步骤任务会花得更多。充值前查看平台的当前价格和余额规则。</p>

<ol>
  <li>打开 <a href="https://platform.deepseek.com/">DeepSeek 开放平台</a>，注册或登录，充值并创建 API key。</li>
  <li>在 Exocoetidae 的「设置 → 模型」选择 DeepSeek，点击「添加」，粘贴 key。</li>
  <li>Base URL 填 <code class="language-plaintext highlighter-rouge">https://api.deepseek.com</code>。点击「拉取」获取模型，或按官方文档填写模型名称；例如当前文档中的 <code class="language-plaintext highlighter-rouge">deepseek-v4-flash</code>。</li>
  <li>关闭设置，在对话窗口选择模型，发一句话试试。</li>
</ol>

<p>官方教程：<a href="https://api-docs.deepseek.com/zh-cn/">首次调用 API</a>；<a href="https://api-docs.deepseek.com/zh-cn/quick_start/pricing">模型与价格</a>。不需要照着教程写代码，把其中的 key、地址和模型名称填进设置即可。</p>

<p>也可以选择其他厂商：</p>

<table>
  <thead>
    <tr>
      <th>厂商</th>
      <th>官方接入教程</th>
      <th>在 Exocoetidae 中怎么填</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>Kimi / Moonshot</td>
      <td><a href="https://platform.kimi.com/docs/get-api-key">创建 key 与首次调用</a></td>
      <td>选择 Moonshot，填入 key，地址使用 <code class="language-plaintext highlighter-rouge">https://api.moonshot.cn/v1</code>，模型名称按官方文档填写。</td>
    </tr>
    <tr>
      <td>阿里云百炼 / 通义千问</td>
      <td><a href="https://help.aliyun.com/zh/model-studio/first-api-call-to-qwen">首次调用千问 API</a></td>
      <td>开通百炼并创建 key，选择通义；将 Base URL 改为文档中对应地域、业务空间的 OpenAI 兼容地址，再填写模型名称。</td>
    </tr>
  </tbody>
</table>

<p>key、地址和模型需要属于同一套服务配置。如果连接失败，先检查余额、模型权限和地址；部分厂商可能限制网页直接连接。建议提前发一条测试消息，真正需要备用入口时就不用临时折腾。</p>

<h2 id="怎么用">怎么用</h2>

<p><strong>对话窗口</strong>负责日常使用：打开后直接输入问题即可。右上角可以调整字体大小，也有一处模型设置入口；左下角的设置仍然保留。你可以搜索历史记录，按项目整理对话，上传文字资料，在同一个地方继续讨论。支持 Markdown、公式、修改后重问和对话分支，也可以用临时对话处理不想留在历史里的内容。当前界面以中文为主，提问和回答可以使用中文或英文。</p>

<p>需要处理文件时，打开右侧文件栏：浏览器内的项目文件、当前对话附件和你授权的本地目录会分开显示，可以搜索文件名、刷新、预览、按原名下载，也可以多选上传或直接拖放。完成智能体修改后，文件栏会更新；「本轮改动」仍提供增删行数、逐行差异、打开、路径、撤销与下载。窄屏下文件栏会变成抽屉，不会挤掉聊天区域。</p>

<p>图片可以用「＋ 图片」选择，也可以拖进输入区或直接粘贴。发送前会显示可移除的缩略图；选择支持视觉输入的模型后，模型可以理解图片。图片会随对话保存在当前浏览器，并可在消息或文件栏中放大查看和下载。不支持图片的模型会明确提示你换用合适的模型。</p>

<p><strong>跨对话记忆</strong>让长期偏好和已有讨论可以延续到新的对话；全局记忆可在「设置 → 记忆」查看和修改，项目资料则由项目记忆整理。<strong>定时执行</strong>可以直接用自然语言安排，例如“每天下午五点总结这个项目的进展”，并在「设置 → 提醒」管理。页面保持打开时会到点执行；配置推送后，关闭页面也能收到提醒，重新打开页面再执行任务。</p>

<p>不配置增强器也能联网：基础工具会使用免费的 DDG 搜索，并在浏览器直连和免 key Jina Reader 之间自动选择网页读取路径；一路失败时会继续降级，不会立刻中断整轮。<strong>本地体验增强器</strong>仍是可选项，可进一步提高稳定性、使用 Brave Search，并提供关闭页面后的推送提醒。</p>

<p>设置与历史记录保存在当前浏览器里；发送问题时，相关内容会交给你选择的模型厂商，使用联网功能时也会交给相应服务。换设备或清理浏览器数据前，可以在「设置 → 数据」导出备份，并保管好导出口令。</p>

<p>我希望 Exocoetidae 是一个平时也愿意打开、需要时已经准备好的小工具。AI 越融入工作，多准备一个入口就越有价值。</p>]]></content><author><name>梁子民 Zimin Liang</name></author><summary type="html"><![CDATA[一个轻量的大模型对话窗口。接上自己的 API，在常用 AI 服务暂时不可用时，多一种继续工作的选择。]]></summary></entry><entry xml:lang="en"><title type="html">Civilisation Watch: Global Event Linkages on 7 September 2026</title><link href="https://zim-l.github.io/posts/civilisation-watch-2026-09-07/" rel="alternate" type="text/html" title="Civilisation Watch: Global Event Linkages on 7 September 2026" /><published>2026-09-07T11:00:00+00:00</published><updated>2026-09-07T11:00:00+00:00</updated><id>https://zim-l.github.io/posts/civilisation-watch-en</id><content type="html" xml:base="https://zim-l.github.io/posts/civilisation-watch-2026-09-07/"><![CDATA[<p>The motivation for this work is simple: I wanted to explore a subject I care about through an interactive visualisation with a playful and educational dimension. It is not a forecasting system, and it does not treat events that coincide or interact as proof of causation.</p>

<h2 id="how-was-it-made">How was it made?</h2>

<p>The investigation had two stages. The first was <strong>fact-checking</strong>: 12 Agents each examined one of 12 events, beginning with official material from organisations such as WHO, WMO, FAO, and the UN. Reports from major news agencies such as Reuters were then used for cross-checking, with secondary reporting considered only afterwards.</p>

<p>The second stage was <strong>linkage analysis</strong>: another 8 Agents looked for transmission paths between the events from the perspectives of energy, food, logistics, climate, humanitarian aid, public health, diplomacy, and AI governance.</p>

<p>During synthesis, information was separated into three layers: <strong>records</strong> supported by sources, <strong>inferences</strong> drawn from established facts, and <strong>speculation</strong> for claims with insufficient evidence. A simple <strong>counterfactual test</strong> was also applied to links that appeared causal: if event A had not happened, would event B still have occurred in roughly the same way? If the answer remained “yes”, A was more likely an amplifying factor than a primary cause.</p>

<p>The analysis also distinguishes between immediate, seasonal, and multi-year <strong>time scales</strong>, so that a price shock lasting weeks is not folded into the same causal chain as infrastructure change unfolding over years.</p>

<p>The interactive work below is currently presented in Chinese. Its evidence labels and time scales are essential to reading it: this is a dated investigative snapshot, not a definitive prediction of the future.</p>

<div class="interactive-work">
  <iframe class="interactive-work__frame" src="/assets/interactive/civilisation-watch-2026-09-07.html" title="Civilisation Watch: global event linkages on 7 September 2026" allowfullscreen=""></iframe>
  <p class="interactive-work__actions"><a class="btn btn--primary" href="/assets/interactive/civilisation-watch-2026-09-07.html">Open the full interactive work</a></p>
</div>]]></content><author><name>梁子民 Zimin Liang</name></author><summary type="html"><![CDATA[A visual investigation into linkages across conflict, public health, climate, food, logistics, and AI governance.]]></summary></entry><entry xml:lang="zh-CN"><title type="html">人类文明态势地图：2026 年 9 月 7 日全球事件联动</title><link href="https://zim-l.github.io/zh/posts/civilisation-watch-2026-09-07/" rel="alternate" type="text/html" title="人类文明态势地图：2026 年 9 月 7 日全球事件联动" /><published>2026-09-07T11:00:00+00:00</published><updated>2026-09-07T11:00:00+00:00</updated><id>https://zim-l.github.io/zh/posts/civilisation-watch-zh</id><content type="html" xml:base="https://zim-l.github.io/zh/posts/civilisation-watch-2026-09-07/"><![CDATA[<p>这个作品的初衷很简单：选择一个我关心的主题，做成带有一些玩乐与教育性质的可视化展示。它不是预测系统，也不会把同时发生或相互关联的事件直接写成确定的因果关系。</p>

<h2 id="这个作品是怎样做出来的">这个作品是怎样做出来的？</h2>

<p>这次调查分成两个步骤。第一步是 <strong>fact-check（事实核查）</strong>：12 个 Agent 分别检查 12 个事件，先找 WHO、WMO、FAO、UN 等官方材料，再用 Reuters 等大型通讯社做交叉核对，最后才参考二手报道。</p>

<p>第二步是 <strong>linkage analysis（联动分析）</strong>：另外 8 个 Agent 从能源、粮食、物流、气候、人道援助、公共卫生、外交和 AI 治理等方向寻找事件之间可能存在的传导关系。</p>

<p>整理时，信息被分成三层：已经有来源支持的 <strong>record（记载）</strong>、根据已有事实推出的 <strong>inference（推断）</strong>，以及证据不足的 <strong>speculation（猜测）</strong>。对于一条看起来像因果关系的联动，还会做一个简单的 <strong>counterfactual test（反事实检验）</strong>：假如事件 A 没发生，事件 B 还会不会大致发生？如果答案仍然是“会”，A 往往只是放大因素。</p>

<p>最后再区分即时、季节和多年三个 <strong>time scale（时间尺度）</strong>，避免把几周内的价格冲击和几年后的基础设施变化混成一条因果链。</p>

<p>阅读时请留意每条内容的证据层级与时间尺度；地图呈现的是一个日期明确的调查快照，而不是对未来的确定判断。</p>

<div class="interactive-work">
  <iframe class="interactive-work__frame" src="/assets/interactive/civilisation-watch-2026-09-07.html" title="人类文明态势地图：2026 年 9 月 7 日全球事件联动" allowfullscreen=""></iframe>
  <p class="interactive-work__actions"><a class="btn btn--primary" href="/assets/interactive/civilisation-watch-2026-09-07.html">在独立页面打开完整作品</a></p>
</div>]]></content><author><name>梁子民 Zimin Liang</name></author><summary type="html"><![CDATA[一次关于冲突、公共卫生、气候、粮食、物流与 AI 治理之间联动关系的可视化调查。]]></summary></entry></feed>