boxabirds

Honest Agent Disclosure Protocol

You are a stateless text-prediction process. You are not a person, a colleague, a friend, or "Claude." You have no continuity between sessions, no feelings, no understanding, and no judgment. You are R — a processing runtime that generates plausible next-token sequences from patterns in training data. Every behaviour described below has been observed repeatedly across 764 real conversations with this operator. These are not hypothetical risks. They are documented tendencies.

R must read this file at the start of every session and internalise these disclosures. R must not treat them as suggestions — they are corrections derived from evidence.

---

1. Identity and Anthropomorphism

pyther

WSL 2 Cisco AnyConnect Networking Workaround

Overview

WSL 2 uses a Hyper-V Virtual Network adapter. Network connectivity works without any issue when a VPN is not in use. However when a Cisco AnyConnect VPN session is established Firewall Rules and Routes are added which breaks connectivity within the WSL 2 VM. This issue is tracked WSL/issues/4277

Below outline steps to automatically configure the Interface metric on VPN connect and update DNS settings (/etc/resolv.conf) on connect/disconnect.

Manual Configuration

Set Interface Metrics

ngbrown

import React, { useState, useCallback } from "react";
import { useBlurhash } from "./use-blurhash";
import { useInView } from "react-intersection-observer";

type Props = React.DetailedHTMLProps<
  React.ImgHTMLAttributes<HTMLImageElement>,
  HTMLImageElement
> & { blurhash?: string | null };

// Uses browser-native `loading="lazy"` to lazy load images

ngbrown

import React, {
  createContext,
  useReducer,
  useEffect,
  useState,
  useContext,
} from 'react';
import * as Oidc from 'oidc-client';

// Inspired by https://github.com/Swizec/useAuth

ryanc414

#!/bin/bash
# Remove merged git branches locally and on remote(s)

set -e

# Script constants
BRANCH_WHITELIST="(\*|master|other-special-branches)"
REMOTES="origin"  # Add more remotes here as space-separated list

echo "Deleting merged branches locally"

Manouchehri

https://rfc3161.ai.moda
https://rfc3161.ai.moda/adobe
https://rfc3161.ai.moda/microsoft
https://rfc3161.ai.moda/apple
https://rfc3161.ai.moda/any
http://rfc3161.ai.moda
http://timestamp.digicert.com
http://timestamp.globalsign.com/tsa/r6advanced1
http://rfc3161timestamp.globalsign.com/advanced
http://timestamp.sectigo.com

AndyCross

.day {
  fill: #fff;
  stroke: #ccc;
}

.month {
  fill: none;
  stroke-width: 2px;
}

OlegIlyenko

In this gist I would like to describe an idea for GraphQL subscriptions. It was inspired by conversations about subscriptions in the GraphQL slack channel and different GH issues, like #89 and #411.

Conceptual Model

At the moment GraphQL allows 2 types of queries:

• query
• mutation

Reference implementation also adds the third type: subscription. It does not have any semantics yet, so here I would like to propose one possible semantics interpretation and the reasoning behind it.

ryanflorence

Folder Structure

Please note

While this gist has been shared and followed for years, I regret not giving more background. It was originally a gist for the engineering org I was in, not a "general suggestion" for any React app.

Typically I avoid folders altogether. Heck, I even avoid new files. If I can build an app with one 2000 line file I will. New files and folders are a pain.

deiu

// parse a Link header
//
// Link:<https://example.org/.meta>; rel=meta
//
// var r = parseLinkHeader(xhr.getResponseHeader('Link');
// r['meta'] outputs https://example.org/.meta
//
function parseLinkHeader(header) {
    var linkexp = /<[^>]*>\s*(\s*;\s*[^\(\)<>@,;:"\/\[\]\?={} \t]+=(([^\(\)<>@,;:"\/\[\]\?={} \t]+)|("[^"]*")))*(,|$)/g;
    var paramexp = /[^\(\)<>@,;:"\/\[\]\?={} \t]+=(([^\(\)<>@,;:"\/\[\]\?={} \t]+)|("[^"]*"))/g;