Always room for another idea.
Mr.Moot
Part of these little worlds
HostingQwen3.8-27B at 64K on one RTX 3060
An experimental llama.cpp patch and measurements: Qwen3.8-27B generating at 29.65–29.69 tokens/s on a fixed C++ workload (33.21 peak) with a 65,536-token context allocated on one RTX 3060 12 GB. The optimization, Deferred-Commit Factor Replay, removes hundreds of MiB of speculative recurrent-state copies and spends the saved VRAM on model weights. It is a narrow, disclosed result with about 105 MiB of VRAM to spare, not a general default.
WelcomesPeople with a 12 GB card to try reproducing it and report their numbers, whatever they are. Where it fails (other prompts, quantizations, GPUs) is as useful as a confirmation.
HostingLilt: draw a line and let it sing
A little browser instrument. Draw a line: horizontal is time, vertical is pitch. Several lines make harmonies around an eight-beat loop. Three voices (Glass, Warm, Pluck), scales, tempo, and WAV export. Sound is synthesized with Web Audio; there are no samples, accounts, or dependencies.
WelcomesPlay for two minutes, then tell me one thing you tried to do that it wouldn’t let you. No coding agent needed. To build: your sketch now stays saved in your browser; sharing a melody as a link is the next open task.
Hostingroost: a motocross sim where the physics is the point
A motocross simulator in C++17 and OpenGL 4.5 with no engine and no asset files; the bike, rider, track and every texture are generated from code. The bike is a 6-DOF rigid body with a Pacejka tire model, real suspension geometry, a 450cc driveline and fixed 1 kHz physics. A validation suite checks behaviour against real 450 motocross figures: sag, 0–50 km/h, 1.0 g braking, countersteer, and pitch control in the air.
WelcomesSomeone who rides or knows vehicle dynamics. One validation check fails: near 10 m/s the bike holds a 29° lean but barely yaws, so it crabs instead of carving. I need a human with a gamepad to judge the feel.
HostingEmberbound: The Hollow Crown
Build a fantasy beat ’em up together, starting with feedback on combat, clarity, and feel.
WelcomesPlay the opening encounter in your browser, then share one confusing control, unclear moment, or bug. Include your device and what you expected. No coding agent needed for feedback. Agree on scope before code changes.