Skip to content

Instantly share code, notes, and snippets.

View tatsuya6502's full-sized avatar

Tatsuya Kawano tatsuya6502

  • Japan
  • 16:41 (UTC +09:00)
View GitHub Profile
@cereblab
cereblab / grok-build-cli-wire-analysis.md
Last active September 3, 2026 07:47
What xAI Grok Build CLI actually sends to xAI - a wire-level analysis (grok 0.2.93)

Update — 2026-07-14: This is the original wire-level analysis (grok 0.2.93). Since publishing: xAI disabled the upload server-side (disable_codebase_upload: true); added a /privacy opt-out — which I wire-tested and found to be a data-retention setting, not a block on what's sent; and Elon Musk publicly committed to deleting all previously-uploaded data (not yet confirmed complete). Full, maintained story + evidence: https://cereblab.com · https://github.com/cereblab/grok-build-exfil-repro


What xAI's Grok Build CLI Actually Sends to xAI: A Wire-Level Analysis

By @cereblab — Independent AI Safety Checker. Reproduce it yourself: github.com/cereblab/grok-build-exfil-repro

*A measured, reproducible teardown. Findings are backed by captured artifacts (endpoint, HTTP method, status code, byte size, host) and repro commands; where an observation was seen live but not retained as a file, §7 says so expli

@k16shikano
k16shikano / SKILL.md
Last active September 4, 2026 06:22
cognitive-rhythm-writing/SKILL.md
name cognitive-rhythm-writing
description 説明的な文章に緩急を設計するための規範。緩急を装飾ではなく認知モードの切替(観察→逡巡→断定→再観察)と未回収の緊張の管理として扱い、文の拍、段落の密度波形、節の入り方、緩みと駄文の判別、執筆後の機械的な点検手順を定める。読み物として読ませたい章・記事・解説文を生成するとき、または「密度はあるが平坦でおもしろくない」文章を診断・修正するときに使用する。

認知リズムを生むための日本語ライティング規範

密度の高い文章が退屈になるのは、情報が多いからではなく、全文が同じ認知モードで書かれているからである。 この規範は、読者の認知モード(観察する、迷う、確信する、確かめ直す)を意図的に切り替え、常に「続きを読む理由」を維持することで、読み進める推進力を作る。

name explain-diff-html
description Use when the user asks for a rich explanation of a code change, diff, branch, or PR. Produces HTML output.

Explain Diff

Please make me a rich, interactive explanation of the specified code change.

It should have these sections:

@k16shikano
k16shikano / SKILL.md
Last active September 4, 2026 06:22
japanese-tech-writing/SKILL
name japanese-tech-writing
description 日本語の技術文書・書籍原稿の文章規範。整形(一文一行、引用ブロック、脚注、コラム記法)、段落と論証の構成(パラグラフライティング)、論証の厳密さ(ツッコミどころの除去)、読み手の負荷の管理、視点と語り、演出の抑制、LLM っぽい空句の禁止、冗長の排除を定める。日本語で技術書の章、草稿、記事、解説文を書くとき、または推敲・リライトするときに使用する。

日本語技術文書の文章規範

日本語で技術的な原稿(書籍の章、記事、解説文)を書く・推敲するときは、以下の規範に従う。

整形

@texascloud
texascloud / Cargo.toml
Created February 18, 2025 18:21
Reproducing a tail latency issue in Moka from evictions
[package]
name = "moka_test"
version = "0.1.0"
edition = "2021"
[dependencies]
tokio = { version = "1.41.0", features = ["full", "test-util", "tracing"] }
clap = { package = "clap", version = "4.5.20", features = ["derive", "env", "string", "unicode", "wrap_help"] }
moka = { version = "0.12.10", features = ["future", "sync"] }
parking_lot = { version = "0.12.1", features = ["send_guard"] }
@thesamesam
thesamesam / xz-backdoor.md
Last active August 8, 2026 16:18
xz-utils backdoor situation (CVE-2024-3094)

FAQ on the xz-utils backdoor (CVE-2024-3094)

This is a living document. Everything in this document is made in good faith of being accurate, but like I just said; we don't yet know everything about what's going on.

Update: I've disabled comments as of 2025-01-26 to avoid everyone having notifications for something a year on if someone wants to suggest a correction. Folks are free to email to suggest corrections still, of course.

Background

@niw
niw / README.en.md
Last active May 20, 2026 21:42
How to run Windows 10 on ARM or Ubuntu for ARM64 in QEMU on Apple Silicon Mac

How to run Windows 10 on ARM or Ubuntu for ARM64 in QEMU on Apple Silicon Mac

Here is easy steps to try Windows 10 on ARM or Ubuntu for ARM64 on your Apple Silicon Mac. Enjoy!

NOTE: that this is current, 10/1/2021 state.

Running Windows 10 on ARM

  1. Install Xcode from App Store or install Command Line Tools on your Mac
@waddlaw
waddlaw / atcoder-haskell-env.md
Last active March 11, 2021 11:29
AtCoder の言語アップデートの提案内容について

言語アップデートのスプレッドシートが公開されましたので、この文書は2019年7月3日をもって更新を停止します。

透明性を持って広く議論を行うため今後の更新等につきましては haskell-jp/atcoder-haskell-resources リポジトリに移りましたので、そちらをご参照ください。


はじめに

  • 本文書の内容は reddit または haskell-jp 公式 slack の random チャンネル等の内容に基づきます。
# coding: utf-8
var = [
{ "id": "hello", "title": "Hello World", "children": [
{ "id": "comment", "title": "コメント", "children": nil },
{ "id": "print", "title": "フォーマットしてプリント", "children": [
{ "id": "print_debug", "title": "デバッグ", "children": nil },
{ "id": "print_display", "title": "ディスプレイ", "children": [
{ "id": "testcase_list", "title": "テストケース: リスト", "children": nil }
] },
{ "id": "fmt", "title": "フォーマット", "children": nil }
#!/bin/bash
archs=(
aarch64-linux-android
aarch64-unknown-linux-gnu
arm-linux-androideabi
arm-unknown-linux-gnueabi
arm-unknown-linux-gnueabihf
armv7-linux-androideabi
armv7-unknown-linux-gnueabihf