Discover gists

Gist

3 min read Original article ↗
Log uploaded on Wednesday, November 4, 2026, 2:48:18 AM
Loaded mods:
Harmony(brrainz.harmony)[mv:3.0.1.0]: 0Harmony(2.4.3), HarmonyMod(2.4.2)
Core(Ludeon.RimWorld): (no assemblies)
Royalty(Ludeon.RimWorld.Royalty): (no assemblies)
Ideology(Ludeon.RimWorld.Ideology): (no assemblies)
Biotech(Ludeon.RimWorld.Biotech): (no assemblies)
Anomaly(Ludeon.RimWorld.Anomaly): (no assemblies)
Odyssey(Ludeon.RimWorld.Odyssey): (no assemblies)
Big and Small - Framework(RedMattis.BetterPrerequisites): 0MultiplayerAPI(av:0.5.0,fv:0.5.0), 0PrepatcherAPI(1.2.0), BigAndSmall(1.0.0), BSXeno(1.0.0), RedHealth(1.0.0)

Public release package, 2026-11-01

All files other than this README are byte-identical copies of the repository files of the same name in prereg/.

Manifests (SHA-256 lists; each version keeps the earlier ones unchanged):

  • manifest_v1.txt: pre-registration v1.0 (specification, feature configuration, theta_0 profile files).
  • manifest_v2.txt: v1 entries + v2 additions (2026-10-22): code training domain Python -> Haskell.
  • manifest_v3.txt: v1 + v2 entries + v3 additions (2026-10-23): Haskell-domain profile, added (v1 files unchanged).
  • manifest_v4.txt: Phase 3 input freeze of 2026-10-30 (formal-run evaluation outputs, profile files, staging view, analysis code).
  • manifest_v5.txt: second Phase 3 input freeze of 2026-10-31 (Python seed-42 run used only for the cross-model pairing, low-diversity robustness run, 10000-step continuation; code).
openapi: 3.1.0
info:
title: Makeswift API
description: Documentation for the Makeswift public REST API.
version: '1.0'
servers:
- url: https://api.makeswift.com
description: Production server
paths:
/v1/auth/user-info:
# A temporary Bootstrap machine will be created using this method and can be deleted after the cluster is up. `Bootstrap VM: 4 vCPU, 16 GB RAM, 100 GB disk`
# You will need to provide NTP through MachineConfigs as IPI has no equivalent for additionalNTPSources.
apiVersion: v1
baseDomain: example.com
compute:
- name: worker
#platform: {} # Defaults to 2vCPU, 8GB RAM, 100GB disk
platform:
{"kty": "RSA", "alg": "RS256", "use": "sig", "kid": "skills-oidc-1", "n": "14J1ojSfCV_4bXAOaz5OvhhMiB1sMB1BxiYwj3EmFfv0Afwi0KI4Ep6MB-a8BfIjVbC8yssn5th-Dv1XBiWZDDCpYcPufUMnBg_LCT4GusWVVHtlgAwkzX5Le49KOMaMeZNcF6yCHOjmFjNfnt2GAPBjI2Hj-Cq03EXin__uxtNBz3f185RTvynFGUXniSKkg46eXDNU9ZFWV5yb-LIJdtivMfHTcQS7waIQt0hNGzM1c17me73YSj2WQztABfs7tvsTRLa6it6oQoHkLwy92FYFkGs1-zszA2M_8W7Rhj7Ov7RhRjyzTqv7wHXF5VFz37H7y3Jc4Jzn3QOPJYKctQ", "e": "AQAB"}

Assign Cookies (LeetCode 455): Why Greedy Works and How to Prove It in an Interview

Assign Cookies is a short problem, but it is one of the cleanest ways to show an interviewer that you can justify a greedy choice instead of just guessing one.

Problem

Each c

I read https://helgesver.re/articles/macos-vulgar-word-flags about ~/Library/Keyboard/VulgarWordUsage.db, the per-app, per-recipient SQLite store macOS autocorrect uses to learn which swear words I am willing to type. The file does not exist on my Mac and I want to understand why and make macOS create it, without faking it: the OS must write the file, not you.

What is already known, so you do not have to rediscover it:

  • AppleSpell (the autocorrect XPC service at /System/Library/Services/AppleSpell.service) hosts the iOS keyboard engine for inline predictive text. The database is created by TextInputCore's TI::VulgarWordUsageDatabaseWrapper the moment AppleSpell lazily initializes a TIKeyboardInputManager for a language. That happens once per AppleSpell process per language, and only when a real text view asks for inline predictions. Calling NSSpellChecker from a command-line tool does not reach that path.
  • The usual reason the file is missing is that ~/Library/Keyboard itself does not exist. SQLite create
#!/usr/bin/env bash
# PUBLIC STUB — publish this file's contents as a public Gist; see
# bootstrap/README.md for the current published URL and how to re-publish.
# It holds no secrets and needs no privacy: its only job is bootstrapping
# just enough (Homebrew, a token) to clone the PRIVATE f4usto/setup repo and
# hand off to its own setup.sh.
#
# This copy lives in the private repo purely for version history and
# review — editing it here does nothing on its own until you re-publish it.
<?xml version="1.0" encoding="utf-8"?>
<fileSnapshot xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<files>
<file path="C:\ProgramData\chocolatey\lib\googlechromecanary\googlechromecanary.nupkg" checksum="3C7FADC65470181E2D7EEF517DB7C9AB" />
<file path="C:\ProgramData\chocolatey\lib\googlechromecanary\googlechromecanary.nuspec" checksum="CCF9914DB0CEF2A50967E43666AABF94" />
<file path="C:\ProgramData\chocolatey\lib\googlechromecanary\tools\chocolateyInstall.ps1" checksum="8445357C81F0A3B620B1323A3731E9A4" />
<file path="C:\ProgramData\chocolatey\lib\googlechromecanary\tools\chocolateyuninstall.ps1" checksum="B74F0547FF3C0417FD61CA1F81F29D16" />
<file path="C:\ProgramData\chocolatey\lib\googlechromecanary\tools\helpers.ps1" checksum="D4DE2647DAEE3B74ECFB1E9F9457C3EB" />
</files>
</fileSnapshot>

WATR22D_1793741928_GISTFILE q2

q2img

d2

d2img