Habitual

Seven weeks of posting how DROPVIBE got built — the bugs, the numbers, and one public correction — in one piece, organized by lesson instead of by date.

DROPVIBE BUILD UPDATE Not every creator has artwork. Now you can type it. "Add text" sits in every artwork grid in the DROPVIBE builder: front, back, sleeves. Nine fonts, from Bebas Neue and Archivo Black to Playfair Display and Permanent Marker, with colour, letter spacing, line spacing, alignment, and a preview on light and dark garments. Every font is self-hosted and licensed for printed products. A font that's free to use on a website isn't automatically free to print on something you sell. The builder also reports how big the text will actually print, in points. Under 10 pt is flagged red and 10–12 pt amber, because small text is where prints fail. Two limits, both stated in the dialog: saved text can't be edited, so you make it again. And characters a font doesn't include, emoji among them, fall back to a standard font. DROPVIBE From Vibe to Drop

DROPVIBE Build Update DROPVIBE kept signing me out after the site sat idle. The answer was one error message on a phone. Supabase's logs showed nothing. No rejected renewals. Nothing reaching it at all. I wrote a fix, then ran the old and new code side by side against expired sessions and dropped connections. Neither reproduced the problem. A fix that can't be shown to change anything is a guess, so I removed it and shipped a recorder instead. The answer came the same day: signing back in on my phone failed with "Legacy API keys are disabled." I'd rotated every key on October 22. The public database key is compiled into the site's code, and phones keep tabs alive for days without reloading them. Old tabs were still sending the key I'd switched off, and it was refused at the gateway, before the auth service saw anything. That's why its logs were empty. Now every build publishes an id. A tab coming back into view checks it, and an outdated one reloads itself. In the dashboard, where someone might be mid-edit, it asks first. A key compiled into a web page doesn't change when you rotate it. It changes when every open copy of the page is replaced. And the fix I removed would never have helped: the failing tab wasn't running the code I was debugging. DROPVIBE From Vibe to Drop

GMs DROPVIBE Build Update Background removal rejected a black-and-white illustration on a pure white background. Its edge scored 83.8%. The check looks at the image's outer edge: if 85% of those pixels share a colour, the background is solid and can come off. This one's top, left and right edges were 100% white. The character's shirt ran off the bottom. Every head-and-shoulders portrait cropped at the bottom fails the same way, and that's one of the most common compositions in merch. Each edge is judged on its own now, and two clean edges are enough. Removal also starts only from the clean edges. Starting from the cropped one would have erased the white lettering and seams where they run off the shirt. It works on logos and flat artwork, runs in the browser, and saves a new copy next to the original. Photos aren't supported yet. A threshold tuned on the obvious case, a logo centred on white, fails on the common one nobody tested. DROPVIBE From Vibe to Drop

😂😂😂😉😎