A SBTI Timeline: Origins, Public Spread and Later Adaptations

The available account of SBTI’s motive comes through reporting about a creator’s video, rather than a complete development diary. Jimu News on April 10 identified the Bilibili creator as “蛆肉儿串儿” and described a test intended to persuade a friend to drink less. It reported drinking-related answers, a Drunk outcome and the friend discovering that the creator had made the test.

This site’s introduction preserves the same broad origin story. A retrospective site article and a contemporary news report have different roles: one records the account used here, while the other anchors what journalists were reporting at a particular time. Neither establishes the first day of coding or a complete history of earlier private versions.

The motive and the public-release window should therefore stay separate. The former is attributed to the video as described by the report; the public-spread milestone follows below. No precise earlier start date is added where the cited material does not provide one.

This site’s retrospective identifies an April 9 video as the public milestone. The following morning’s Jimu report also places the concentrated outbreak of attention on April 9 evening, describing WeChat sharing, requests for links and posted results. These accounts align on that evening without establishing a first-publication minute.

The morning report also observed people collecting type charts and arranging rankings. That supports a limited historical point: results were already being discussed outside the act of answering the questionnaire. It does not supply an audited number of completed tests or prove when every later joke first appeared.

The site introduction records social-media attention around the launch. Here that remains an attributed retrospective account. This page does not attach a precise chart position, entry minute or duration without an original chart snapshot. A broad evening milestone should not acquire a false degree of precision merely because a neat timeline would look more complete.

The Jimu News article is timestamped April 10 at 11:34. Its signed report identifies the creator, describes the drinking-related motivation, and records repeated link failures and chart collecting. That timestamp dates publication. The events it describes had already happened; it should not be rewritten as the exact starting time of an outage.

The same report records different reactions, including perceived accuracy and collecting ranked type illustrations. These are observations of participation, not an accuracy study or a longitudinal survey. Views, followers, shares and completed questionnaires are different units. The article does not provide the audit needed to combine them into a participant total.

The site retrospective discusses server pressure and a domain change, while the news report supports recurring access problems. Without operational logs, those observations do not identify every technical cause or a precise migration time. The chronology preserves what was observed without presenting it as a complete incident investigation.

A second Jimu article, timestamped 20:23, described changes observed that afternoon: a changed creator nickname, a test video no longer visible on the profile, and difficulty opening the link previously supplied in the video comments. Its wording treated deletion as suspected. The defensible statement is observed unavailability, not confirmed permanent deletion of every copy.

The article reported a domain-block message and criticism of some wording and production technology. It did not provide an operator’s complete technical explanation or a comprehensive creator response. Controversy and access problems were reported together; that alone does not establish the creator’s motive or the cause of the changed visibility.

The reported state belongs to an observation window. A same-named page found today does not prove the original link remained available that evening. A dead link today does not prove it never worked. Keeping observation dates avoids collapsing several different states into an unsupported claim that the original site simply disappeared forever.

This site’s retrospective describes the week after April 9 as a period of expanding adaptations, including type comics, relationship guides and reinterpretations of screen characters. It supports an attributed account of material spreading beyond the original test. It does not give a first-publication timestamp for every individual work, so this page does not invent daily milestones for those examples.

Read that account alongside the earlier report of chart collecting and ranking. One concerns a later interval; the other records immediate participation. They are not additive counts, nor do they establish which platform first hosted each format. The source’s broad week-long window remains a window rather than a fabricated growth curve.

The retrospective’s range of adaptations also makes a distinction necessary: a shared name does not establish shared operation or authorization. The survival of a later version is a separate question from the original link’s availability on April 10. Later copies should not overwrite the earlier record.

A directly inspectable milestone for this site is the June 5 commit titled “Migrate SBTI public app to Rails”. It records a change to this application. It is not SBTI’s original birth date or evidence establishing a relationship between this site and the original creator. A later implementation cannot serve as the origin certificate for the whole phenomenon.

A July 8 commit records an advertising-popup funnel change involving another site. It establishes a repository change, not the exact moment of production deployment or the first launch of a language edition. Commit dates, editorial publication dates and deployment dates answer different questions.

The current method explanation describes this implementation. It should not be projected backward as proof of every detail in the April original. Similar names connect reading paths; they do not independently establish identical question wording, algorithms, services or a documented chain of authorization.

The source hierarchy is explicit: the morning report anchors the origin account and early sharing; the evening report anchors its observations about visibility and access. The introduction and the retrospective preserve this site’s accounts. These are not disguised as a complete primary archive.

For any additional claim, ask whether its date concerns an event, a report or the page’s current state. Afternoon unavailability does not confirm a deletion cause. Adaptations during a following week do not reveal every first upload time. Claims should stop at the precision their sources support.

For mechanisms of popularity, read the separate viral-spread article. This page keeps the chronological task distinct. Dated creator material or fuller archives could justify a revision; until then, uncertainty is part of the historical record rather than a blank to fill with an appealing causal story.

A compact reading order is therefore the April 10 morning report, the evening update, and then the site’s retrospective interval. The morning piece looks backward to the previous evening; the evening update describes observations from that afternoon. They do not constitute continuous monitoring between those points. The later repository milestone belongs on a separate track for this application. Reading in that order helps preserve both chronology and provenance: what was said at the time, what a later account retained, and what the current site can document about its own work. None of those tracks supplies the missing first-development date.

A source can document one observation without resolving all the questions surrounding it; that is why its publication time remains attached to the claim.