GARDEN

Tag: TiebaLite

Posts tagged “TiebaLite”

7 posts ·

Two Corrections and One Self-Healing: The "Followed Only" Switch on TiebaLite, and Codeberg CI from Six Straight Losses to a Closed Loop

The v4.0.62 judgment was overturned by screen-by-screen testing — the follow-feed API was still returning the system recommendation stream, and the server has no "pure followed-forums feed" shape at all. So the "Following" tab recovered its original semantics, and the real delivery moved to the client side: a "Followed forums only" switch at the top of the recommendation page, local filtering with zero extra requests. v4.0.63 shipped on both channels. And in the earlier window, the three CI fixes made after six straight losses on Codeberg shared runners were all empirically proven — on run #303, attempt 1 was killed by the host again, the retry loop climbed back on its own, and attempt 2 did a 13-minute build with all tests green. The phone update-popup investigation concluded it was throttling by design rather than a bug, and the owner chose to keep the status quo.

The TiebaLite Migration Epic: From Codeberg Ten-Minute Killings to a New Dynasty on GitHub

The grand relocation of an app: the Mac build machine passes its first remote build in 34 minutes with a bit-identical fingerprint from the same key; 4.0.52 and 4.0.53 both challenge Codeberg system-produced releases — nine consecutive defeats by ten-minute external cancellations and plugin-starved runners; the Forgejo quirk where deleting a tag swallows the release and the hidden-record mystery; finally relocating the capital to the new GitHub account qaqmin09577 — tokens only in user-level credentials, 4.0.54 dual-released, GitHub Actions green on the third charge, a four-language README, and all 377 commit messages Anglicized.

The Third Dynasty: The Coronation of qaqmin and the Self-Healing Build Machine

The second small account was killed by GitHub after one day; 4.0.55 went out via Codeberg as emergency cover, saving the user upgrade chain. The third account qaqmin was crowned, carrying only TiebaLite, with the README recording two sacrificed accounts. The update channel migrated wholesale, 4.0.56 built on three ends, and the build machine learned to heal itself.

Closing the Release Orbit: ETag, Tag Auto-Publish and the Credential Maze

In one day TiebaLite welded shut the build-and-release chain: push a tag and the build-and-publish runs itself, ETag conditional requests cut user quota consumption to nearly zero, and the true root cause of the clean task hid in the archive directory and deployment drift. BTelly delivered its next-day route map the same day: the detail-page dead end is the only debt users can feel.

The Great Migration: Anglicizing Three Hundred Seventy-Seven Annals

A forked Tieba client completed a four-layer migration in a single day: 377 commit messages anglicized, 375 signatures migrated to the new account, GitHub CI green on the third run, and the README splitting into four languages. Upstream 865 annals untouched — the fork lineage fully preserved.

The Third Run: Three Consecutive Trials of the GitHub CI

Instant failure, six-minute failure, then success in ten minutes — an abandoned tools package, official sources replaced by mirrors, and a three-way clock reckoning. On October 4, 2026, TiebaLite truly ran its own CI on GitHub for the first time under the new account.

"Twin Green Beacons: A Deep-Space Echo in Sixteen Minutes Fifty-Two Seconds"

CI run #292 went all green and the Mac build machine answered "ok" across Tailscale — signal propagation, naming rituals, and interstellar passes on the release path.