A data-driven response to instagibbs' gist on retiring the OP_RETURN limit.

The original gist presents a reasonable-sounding engineering case. This response does not question the author's intent. It questions the claims against the available data, much of which post-dates the original gist.

Cryptographic identity for AI agents in one command.

git init
npm init agent

Minimal RDF library optimized for JSON/Linked Objects only

Code golf version of rdflib.js with 97% smaller bundle size and zero dependencies.

Date: 2026-01-18 Objective: Create minimal RDF library for JSON/LION only, removing all bloat

What if seeding torrents paid real Bitcoin?

Private trackers solved the free-rider problem with reputation. 500 million people torrent. Most content dies because no one seeds.

Use git to clone and push to a JavaScript Solid Server (JSS) pod with Nostr NIP-98 authentication.

• Node.js 18+
• JSS server running with --git flag (or "git": true in config)
• Git installed

This guide explains how to add Git HTTP backend support to a Solid server, enabling git clone and git push operations on pod containers.

The Git HTTP protocol allows clients to clone and push to repositories over HTTP. This is implemented using Git's built-in git http-backend CGI program - the same one used by Apache and Nginx.

draft optional

This NIP defines standard guidelines for how clients SHOULD detect and render inline media URLs and other embeddable content within event .content fields. The goal is to provide a consistent user experience across different Nostr clients.

Bitcoin Core v30 and later relay, index, and expose up to 100,000 bytes of arbitrary OP_RETURN data by default. When an attacker embeds a self-rendering Data URI (e.g., data:image/*;base64,…) inside an OP_RETURN output, Bitcoin Core stores the content and makes it accessible through standard JSON-RPC and REST interfaces. Any client retrieving the transaction through these interfaces receives the Data URI in cleartext, which can be immediately rendered by a web browser or other HTTP-capable software without specialized tooling.

This behavior may unintentionally cause node operators to store, retrieve, or serve content that is harmful, illegal, or high-risk, creating operational, security, and legal exposure for downstream systems.

This document provides a detailed analysis of how RGB Non-Inflatable Assets (NIA) are encoded, hashed, and committed to Bitcoin using the RGB protocol. The analysis is based on the issue_nia::case_1 test executi on.