anshulxyz

TERMS OF SERVICE AGREEMENT

This Terms of Service Agreement (the "Agreement") is entered into between [Anshul Chauhan] ("Bot Owner") and the user ("User") of the [Bot Name] Discord bot (the "Bot").

By using the Bot, the User agrees to be bound by the terms of this Agreement. If the User does not agree to the terms of this Agreement, they should immediately discontinue use of the Bot.

1. Use of the Bot: The Bot Owner grants the User a non-exclusive, non-transferable, limited license to use the Bot for personal or non-commercial purposes.
2. Prohibited Use: The User may not use the Bot in any way that violates applicable laws, rules, or regulations or infringes upon the rights of any third party. The User may not use the Bot for any commercial purposes without the express written consent of the Bot Owner.
3. Limitation of Liability: The Bot Owner shall not be liable for any damages arising out of the use or inability to use the Bot, including but not limited to, damages for loss of profits, loss of data, or o

karpathy

LLM Wiki

A pattern for building personal knowledge bases using LLMs.

This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.

The core idea

Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.

JRex286

GA100 VBIOS Comparison Table

Cross-variant comparison of VBIOS structure and configuration across the GA100 product family. Sourced from static binary analysis of ROM dumps + empirical flash experiments + Lapsus Booter disassembly.

Last updated: 2026-05-31 (Drive A100 PG199 VBIOS dumped and analyzed)

Contributors: Petri Krohn (ECB cryptanalysis, RFRD manifest decode, known-plaintext identification), Cab (ECB padding block confirmation, ImHex structure labeling, license region offset discovery via gpuio BAR0 dump)

Table of contents

JRex286

GA100 Fuse & Register Reference Table

Cross-variant comparison of all registers read by tools/mmio-probe/probe.sh. 15 Ampere cards probed: 2× CMP 170HX 10GB (Cab + Own physical hardware, 2026-05-05/07) + 11 via Vast.ai rentals + 2× Drive A100 32GB (PG199, GA100-550F-A1, physical hardware, 2026-05-31).

Table of contents

• Key findings
• FMA / Tensor Core throttle
• Feature override chain

Chenx221

Visual Studio 2026

https://c2rsetup.officeapps.live.com/c2r/downloadVS.aspx?sku=community&channel=Stable&version=VS18

https://c2rsetup.officeapps.live.com/c2r/downloadVS.aspx?sku=enterprise&channel=Stable&version=VS18

https://c2rsetup.officeapps.live.com/c2r/downloadVS.aspx?sku=professional&channel=Stable&version=VS18

https://aka.ms/vs/18/Stable/vs_community.exe

vertti

{
  "$schema": "https://opencode.ai/config.json",
  "permission": {
    "bash": {
      "*": "ask",

      "cat *": "allow",
      "head *": "allow",
      "tail *": "allow",
      "ls *": "allow",

k16shikano

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

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

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

整形

razhangwei

This is an excellent LangGraph cheat sheet! It provides a comprehensive and practical overview of LangGraph's key features and usage. Here's a slightly refined version with added clarity and formatting for better readability:

---

LangGraph Cheat Sheet

1. Import Necessary Modules

from typing import TypedDict, Dict, Any, Callable
from langchain_core.runnables import Runnable

geoffreylitt

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:

h2dcomputers

For use with tutorial at:

#SSH into ProxMox node
ssh root@<ipaddress>

#change directory to ProxMox Widget Toolkit
cd /usr/share/javascript/proxmox-widget-toolkit

#Back up Proxmoxlib.js
cp proxmoxlib.js proxmoxlib.js.bak