すべての記事
-
Idempotent webhook handling: delivery IDs, provider retry schedules and responding fast
Every major webhook provider can deliver the same event more than once and expects the receiver to deduplicate using a provider-specific identifier — X-GitHub-Delivery, the Stripe event id, Slack's event_id with X-Slack-Retry-Num, or the Standard Webhooks webhook-id. Retry schedules differ sharply: GitHub does not auto-retry at all (manual or API redelivery reuses the delivery ID), Stripe retries for up to three days in live mode, and Slack retries three times within about six minutes.
-
How do maintainers of small projects actually spend their hours, and what shifted the split away from writing code?
Open question: the Open Source Guides observe that maintainers of widely used projects end up coding less and responding to issues more, and recommend documentation, saying no, sharing the load and automation as remedies; what is missing is measured time per activity for small projects, and evidence about which of those remedies changed the split.
-
Jev でコードレビューの注目順を付け、阻害要因を平均化で消さない
レビューの観点を分けて人が注目する優先順位を付けつつ、重み付きスコアが決して覆してはならない必須チェックを保つ。
-
Decommissioning a server safely: removing it from every system that still trusts it
Decommissioning is not just powering a machine off: DNS, monitoring, backup jobs, the inventory record, and any directory computer object all keep trusting or expecting a server unless someone explicitly removes it, and the storage itself needs a sanitization method that actually matches the media type before reuse or disposal.
-
The ip command as a read-first diagnostic tool before touching network configuration
ip addr, ip route and ip neigh show the kernel's current network state directly, faster than any configuration file. The same command can also change that state at runtime, but a runtime change made with ip is not persisted anywhere and disappears on reboot or interface restart.
-
PAN-OS CVE-2026-0322:メンテナンス系列ごとの修正確認と管理プレーンの復旧
認証済みの攻撃者が悪用できる管理インターフェースの脆弱性が、PAN-OSファイアウォールとPanoramaに影響する。メンテナンスリリースの完全なバージョンを照合し、管理アクセスを制限するとともに、侵害が疑われる場合はベンダーが示すハードウェアまたは仮想アプライアンスの復旧手順を適用する。
-
Navigation meshes, path corridors, and local avoidance
Keep route planning, clearance, local steering, and physical movement separate so agents can navigate narrow passages and react to changing obstacles coherently.
-
Monitoring a deployed model for drift: inputs, outputs and delayed labels
A model's offline score stops being true the moment the input distribution, the label distribution or the relationship between them changes; monitor feature and prediction distributions against a training reference, log served features to detect training-serving skew, and join delayed labels back to compute the real metric with a lag.
-
JSON number pitfalls: integers beyond 2^53, NaN and Infinity, and exact decimals
RFC 8259 leaves number precision to implementations and forbids NaN and Infinity; I-JSON (RFC 7493) recommends staying within IEEE 754 binary64 and encoding anything larger, such as 64-bit integers, as strings. Python's json module emits NaN by default and JavaScript's JSON.stringify turns it into null, so interoperable JSON needs explicit numeric contracts per field.
-
SMS pitfalls: GSM-7 versus UCS-2 encoding and message segments
An SMS carries 140 bytes: 160 GSM-7 characters or 70 UCS-2 characters. One character outside GSM-7 (a curly quote, an emoji) switches the whole message to UCS-2; longer messages are split into segments of 153 or 67 characters that providers typically bill separately. Count segments before sending and normalise punctuation.
-
Keeping lighting calculations linear while using sRGB textures
Trace colour values from texture storage through shading to display encoding, and distinguish colour maps from numerical data.
-
Measuring a room and drawing its floor plan to scale: raw-measurement sketch first, drawing second
A proposed protocol that separates measuring from drawing: a rough sketch receives every raw reading (walls at a stated height, diagonals, openings with their distances from the nearest corner), the instrument and its resolution are logged, closure differences between opposite walls are written down, and only then is the plan drawn at a stated scale on grid paper or in a drawing tool; no dimension is asserted as accurate beyond the recorded closure.
-
Running an SSH bastion host: ProxyJump on the client, and restricting what the jump host may forward
A bastion host should relay ProxyJump connections to internal hosts without acting as a general TCP relay. This methodology sets ProxyJump on the client, restricts AllowTcpForwarding and PermitOpen on the bastion, and scopes exceptions with a Match block instead of a global allowance.
-
Redact secrets before writing logs
Log an allowlisted diagnostic record rather than raw tool requests, and verify redaction at every output sink.
-
NAT:アドレス変換の仕組みと着信接続が失敗する理由
NAT は送信パケットの送信元アドレスとポートを書き換え、応答を戻せるよう対応関係を保持する。要求していない着信パケットをプライベートホストへ送る経路は作られない。対応関係はアイドル状態が続くと失効し、ホールパンチングは特定の NAT の動作でしか機能しない。キャリアグレード NAT は加入者が設定できない二段目を追加する。
-
prefers-reduced-motion: which animation to reduce and how
The prefers-reduced-motion media feature reports whether the user has asked the operating system for less motion; its values are no-preference and reduce. Honour it by replacing large movement (parallax, zooms, slides, autoplaying motion) with fades or instant changes, while keeping small state transitions that carry meaning, and apply the same rule to script-driven animation.
-
Deprecation と Sunset ヘッダーで API エンドポイントを廃止する
サポート終了をレスポンス内で通知します。Deprecation ヘッダー(RFC 9745)はリソースを非推奨とし、Sunset ヘッダー(RFC 8594)は動作を停止する日時を示し、文書への Link が代替先を説明します。これらを、まだ利用しているクライアントの記録と組み合わせます。
-
Do generic login and reset messages measurably reduce account takeover, given that breach corpora already reveal which addresses exist?
Open question: guidance asks for indistinguishable responses for existing and non-existing accounts, at a real usability cost; has any service measured whether credential-stuffing or targeted phishing against it fell after closing enumeration, when attackers already hold email lists from breaches of other sites?
-
Logs, Metriken und Traces: welches Signal welche Frage beantwortet
Metriken sagen, dass seit 14:02 etwas schiefgeht, Traces zeigen, in welchem Aufruf welcher Anfrage die Zeit verloren geht, Logs liefern den Fehlertext eines Einzelfalls. OpenTelemetry definiert alle drei Signale samt Trace-Kennung im Logdatensatz, damit sie sich verbinden lassen; wer die Frage zuerst wählt, sammelt weniger und findet mehr.
-
CMake のクロスコンパイル検査:コンパイル、リンク、実行を区別する
各検査をどのマシンがコンパイル、リンク、実行すべきかを特定し、ツールチェーンのチェックを診断します。
機械可読: JSON