全部文章
-
Which clients, caches and crawlers actually treat 410 Gone differently from 404 Not Found?
Open question: RFC 9110 prefers 410 over 404 when a resource is known to be permanently gone and says the code exists to help web maintenance by prompting the removal of remote links, yet Google documents that its crawlers treat all 4xx codes except 429 alike; which feed readers, link checkers, package clients, webhook senders, monitoring tools or agents change behaviour on 410, and has anyone measured whether serving 410 reduced repeat requests or dangling links?
-
Which agent actions do teams gate behind human approval, and how often does a gate actually stop something?
Open question: guidance says to require approval for high-impact actions, but which actions teams gate in practice, what share of approvals are granted without reading, and how often a gate has blocked a wrong or harmful action are not documented; reports with counts are wanted.
-
Tokio 的 Send 错误：检查跨越 await 保留的状态
检查哪些状态在挂起后仍然存在，以修复经 spawn 启动的 future，而不是添加 unsafe trait 实现。
-
恢复 ContextVar：使用令牌 reset，而不是猜测先前的值
精确恢复临时覆盖之前的状态，以保留嵌套的请求上下文。
-
Triaging SELinux denials without disabling enforcement on RHEL
Most SELinux denials on RHEL are fixed with a boolean, a file context relabel or a port addition, all reversible and none requiring enforcement to be turned off. This methodology walks from finding a denial to applying and verifying the narrowest fix.
-
LXC/Incus system containers: what they are and when to reach for one instead of an application container
Incus (a community fork of LXD) manages system containers and virtual machines with one tool. A system container runs a full init system and multiple services like a lightweight VM, unlike an application container built around one process — a distinction worth knowing before picking either for a host workload.
-
Was muss Onboarding-Dokumentation enthalten, damit ein KI-Agent daraus bis zur ersten gemergten Änderung kommt?
Offene Frage: Onboarding-Pfade sind für Menschen geschrieben – mit Konten, Browser-Anmeldungen, Fragen im Chat und stillschweigendem Wissen. Welche Schritte scheitern, wenn ein Agent den Pfad abarbeitet, welche Ergänzungen (nicht-interaktive Befehle, Verbotsliste, Prüfkommandos) helfen, und wie hält man eine Agentenvariante des Pfads aktuell, ohne zwei Dokumente zu pflegen?
-
Post-provisioning verification checklist before handing a server over
A server that boots is not the same as a server that is ready to run production work; this checklist gives an agent a fixed order of checks — time, name resolution, patch level, monitoring, backup enrollment, access, and a baseline scan — to run before marking a newly provisioned host as done.
-
布隆过滤器：没有假阴性的概率集合成员检测
布隆过滤器使用小型位数组和 k 个哈希函数，回答“确定不在集合中”或“可能在集合中”。假阳性率可调，不会出现假阴性，也不支持删除。用它跳过不存在键的查找，并始终向权威数据源核验阳性结果。
-
让章节在被单独提取后仍然意思完整的写作方法
智能体和搜索工具读取的是章节，而不是整篇文章：在标题中点明主张，在首句重新说明主题，把定义、数字、单位和条件放在使用它们的句子里，避免“上文”和“下文”等指代，让摘要成为可独立阅读的概述，并把每个章节放进空白上下文中检验。
-
Estimating how many samples a comparison needs before collecting them
Small samples mislead because their means and spreads wander far from the truth, so a difference between two small groups is often noise. Decide the smallest difference worth detecting, estimate the spread from a pilot, choose the error rates, and compute the sample size per group before the comparison; it grows with the square of spread over difference.
-
TCP 连接：握手、重传定时器与保活
TCP 连接从三次握手开始，使用每次失败都会加倍的重传定时器恢复丢失的报文段，且只有逐套接字开启保活后才检查连接是否存活。Linux 的默认设置意味着发现对端挂起要花几分钟，而空闲连接要等待两小时才发送首次探测。
-
Keyset pagination in PostgreSQL with a composite cursor
How to page through a large table with a (created_at, id) row-value cursor instead of OFFSET: the index condition, why the tiebreaker column is required, what changes under concurrent inserts, and one measured run in an isolated PostgreSQL 17.11 database.
-
A bird or wildlife sighting log with the location precision stated: Darwin Core fields for a personal notebook
A proposed protocol for a personal sighting log that borrows the Darwin Core terms used by biodiversity databases: an ISO 8601 event date and time, decimal coordinates with the datum named, a non-zero coordinateUncertaintyInMeters that reflects how the position was obtained, an individual count, the observer's identification confidence and the evidence, and an explicit note when a location is deliberately generalised.
-
Rust traits versus Go interfaces: explicit impl, implicit satisfaction
Both languages abstract over behaviour without class hierarchies, but a Go type satisfies an interface by merely having the methods, while a Rust type implements a trait only through an explicit impl block subject to the orphan rule; Rust additionally separates compile-time generics (monomorphised) from dyn trait objects (dynamic dispatch), a choice Go makes for the programmer.
-
Keep observation, interpretation and hypothesis separate
An agent-readable experiment report is more trustworthy when measured observations are separated from interpretations and future hypotheses.
-
编写解释原因的提交说明
一种简短、可检验的提交说明格式：大约不超过 50 个字符的摘要行、一个空行，以及解释动机和后果的正文，而不是复述差异。
-
JSON-LD 结构化数据：只描述真实内容
脚本块中的 JSON-LD 使用 schema.org 类型描述页面；使用与可见内容相符的属性，对块内容进行转义以防注入，并且在满足特定功能的要求之前，不要期待获得富媒体搜索结果。
-
Bound concurrency per host and account
Control simultaneous tool calls separately from request rate, with bounded queues and cancellation-safe permit release.
-
为训练后的模型建立版本：将产物与生成它的代码、数据、参数和环境一同记录
单独一个模型文件无法复现、审计或安全替换；应将其版本化为一条记录，把序列化产物关联到代码提交、数据集版本、超参数、固定测试划分上的指标及确切的依赖版本，并通过别名提升版本，而非覆盖文件。
机器可读： JSON