Drew Raines drewr

Small Colleges with Track & Field, On-Campus Housing & High Acceptance Rates

All schools listed are NCAA Division III with on-campus housing, a track & field program, and a high acceptance rate.

#	School	Location	Division	Approx. Acceptance Rate	Undergrad Size
1	North Central College	Naperville, IL	NCAA DIII	~60%	~3,000
2	Wartburg College	Waverly, IA	NCAA DIII	~80%	~1,500
3	Augustana College	Rock Island, IL	NCAA DIII	~65%	~2,500
4	Loras College	Dubuque, IA	NCAA DIII	~82%	~1,500

Datum Q1 2026 — Top 10 Accomplishments

Activity across datum-cloud/enhancements, datum-cloud/infra, and datum-cloud/network-services-operator. Period: January 1 – March 10, 2026.

1. Activity Service — Full Stack to Production

The activity system went from an idea to a fully deployed production service. Work spanned the activity-apiserver (sharing the etcd cluster, infra#1875), activity-processor with NATS mTLS (infra#1584, infra#1587), a ClickHouse full-text index fix for v26.1 (infra#1885), the activity-ui (infra#1581), ActivityPolicy support wired into dns-operator ([infra#1832](https://github.com

id	ops-001
title	Manual Signup Defense Workflow
status	draft
created	2026-03-09
author	architect

Manual Signup Defense Workflow

Datum Cloud Authoritative DNS Service: Research Report

1. Overview

The authoritative DNS service solves two distinct but related problems:

User-facing DNS management: Datum Cloud customers own domain names (e.g., example.com) and want Datum to serve authoritative DNS for them. Users create a Domain resource to claim ownership, a DNSZone resource to declare a hosted zone, and DNSRecordSet resources to manage records. Datum's infrastructure then serves live DNS responses for those zones.

This should instead be:

Whatever you're working on needs an issue somewhere
Every day look through the open issues assigned to you
- Do they have a recent status? If not, add one.
- Is the status still accurate? If not, fix it.
- Does the status have a time component? If not, add when others can expect the next action to be completed.
- Is the issue blocked? If so, reach out to whomever is blocking the work. Push it forward.
- Is the issue's purpose and next action clear? If not, go get clarity.
- Is the work still relevant? If not, or if it's unclear and you're unable to get clarity, add a comment describing that's the case and unassign yourself.

HTTP/3: A Comprehensive Research Report

Executive Summary

HTTP/3 represents the most significant architectural change in web communication since the internet's inception. While previous versions of HTTP (the protocol that allows your browser to fetch web pages) made incremental improvements, HTTP/3 fundamentally reimagines how data travels across the internet. It replaces the 50-year-old foundation (TCP) with an entirely new transport system called QUIC, designed for the mobile-first, always-connected world we live in today.

Key takeaway: HTTP/3 is not just a faster version of HTTP/2. It is a ground-up redesign that solves problems the original internet architects never anticipated: smartphones switching between WiFi and cellular networks, video calls that cannot tolerate delays, and billions of simultaneous connections that must remain secure without sacrificing speed.

name	about	title	labels	assignees
Turn-Up Ticket	Procedure for managing changes in production.	[turn-up] <Summary>

	#!/usr/bin/env bash

	INPUT=$*
	OUTPUT=$(basename $INPUT .MTS)

	### Fast version, just copies streams to mp4, but failed on one MTS file
	#echo ffmpeg -i $INPUT -c:v copy -c:a aac ${OUTPUT}.mp4

	### Slow version, re-encodes, but works on every file
	echo ffmpeg -i $INPUT -y -c:v libx264 -crf 23 -c:a aac -b:a 128k ${OUTPUT}.mp4

	{:paths ["src"]
	:deps {org.clojure/clojure {:mvn/version "1.12.3"}}
	:tasks
	{:require [[clojure.string :as str]]

	test {:doc "Run the test suite."
	:task (clojure "-M:test" "-m" "cognitect.test-runner")}

	test:bb {:doc "Run the test suite using Babashka to check compatibility."
	:extra-paths ["test"]