room/run/out/case.md

Chronology

The canvas opened while r/blackmirror's thread openings were still dominated by ordinary discussion of the television series. The first selected conduct was instead the room's own April Fools joke: at d0 04-01 05:53 a post announced “SEASON 4 BEING RELEASED ON MONDAY!!!” and instructed readers to “Check today's date” (62qzcv). A regular answered that filming was continuing and that this “wasn't exactly the best 'gotcha',” while another reader later admitted being caught (dfomv09). This separate subreddit joke ran from 62qzcv to dfoxj98; it was not conduct on the r/place canvas.

The canvas entered the case at d0 04-01 11:28, when a post asked, “Should r/blackmirror get together on Place and make the white bear logo?” (62s5if). During the ensuing episode, participants began in an existing black void, shared a measured image, reduced it to something “far easier to make and maintain,” found quieter space, tiled small logos, recruited help, placed pixels, and celebrated making “way more progress” than expected (dfouib2; dfoxud5; dfpu4px). The episode runs from 62s5if to dfpu4px. Its development was practical rather than linear: different speakers alternated between one large logo and many small ones as they considered their limited numbers and maintenance burden.

Protection and accommodation developed alongside construction. A participant warned that spreading onto /r/ainbowroad could make the White Bear “disappear in a flash” and urged repairing damage (dfp9xdy). Another proposed black outlines with “rainbow coloured logos” rather than cutting through rainbow road, and a third said the drawings could “combine ourselves” (dfpn5tg; dfpoywc). Purple placement was described as damage and prompted calls to “fight back” (dfpyi4j; dfq8z2v). At d1 04-02 14:34, a new post said the logos were “under attack” and asked for help (62zxr8). Its comments revisited one large logo, said “we'd need larger numbers,” described private-messaging overnight vandals, distinguished them from “Randoms,” and offered maintenance (dfq95qy; dfq9cbo; dfq9oq4). This defence episode runs from dfp9xdy to the end claim “I got the logo in right before it ended” at d3 04-03 17:09 (dfrzwby).

A one-item proposal at d2 04-02 20:15 asked to “white bearify the A in the tesla logo at 902,204” (631ycf). It appears 5 hours 40 minutes 40 seconds after the defence post opened, but it neither names nor answers that thread. No reply, placement report, or rejection establishes an outcome.

After placement ended, the room memorialised the work. At d3 04-03 23:24 a post celebrated “One brave white bear logo” surviving (63ahf5). A participant claimed “I did that,” but also recalled that “everything was gone,” that rebuilt logos “kept getting overtaken,” and that the canvas ended as they tried again (dfssjhw). Others said they had a “good thing going,” a “good time,” and “fun while it lasted” (dfsu0pz; dfsyng9; dft2frg). This closing episode runs from 63ahf5 to dft2frg. By the end of the window, ordinary show discussion again dominated new openings; the selected r/place practice had become recollection rather than placement.

Relations — what set off what

The initial White Bear request produced a supported response: 58 minutes 53 seconds after 62s5if, a direct reply said, “Good idea. I'll try and start it off,” and identified an existing black void (dfouib2). At 2 hours 48 minutes 26 seconds, another reply said it had made an image “to give everyone a similar goal to work toward” (dfoxud5). The wording, not reply adjacency alone, makes these answers to the request.

The smaller design reflects a participant's own feasibility explanation, not proof of a community-wide decision: its author said it would be “far easier to make and maintain” (dfoxud5). Likewise, the rainbow accommodation carries its own reason—“Instead of completely cutting through rainbow road”—while the warning explains that angering the neighbour could erase the logo (dfpn5tg; dfp9xdy). These passages support practical reasons for scale and accommodation. They do not establish that one speaker caused another to change position.

The later attack post opened 27 hours 6 minutes 46 seconds after the original White Bear request (62s5if; 62zxr8). It gathers the same defence problem, but the corpus does not say that an earlier purple report caused the new post. The Tesla-A proposal follows the attack post by 5 hours 40 minutes 40 seconds (62zxr8; 631ycf); because it does not answer, name, or recall that post, this is sequence only.

The last batch-01 completion report at dfrzwby is followed 6 hours 15 minutes 13 seconds later by the batch-02 surviving-logo post at 63ahf5 [crosses 01|02]. The latter does not cite the former, so this too is a sequence, not a causal link and not evidence that the community changed its mind.

Within the memorial thread, there are two supported response links. The survival post elicited “I did that” 3 hours 8 minutes 38 seconds later (63ahf5; dfssjhw). That recollection ended by hoping r/place would return; 39 minutes 28 seconds later, its direct child answered the prospect of continuation with “go at it again on r/pxlsspace” (dfssjhw; dfsuejb). The record shows a referral, not collective uptake.

Posts against comments

The clearest contradiction occurs in the room's own April Fools exchange: the post says season four is “BEING RELEASED ON MONDAY,” while the comment layer says regulars know it is still filming and calls the claim a weak “gotcha” (62qzcv; dfomv09). This is performed deception and exposure, not disagreement about the canvas.

For r/place, posts provide compressed public objectives—make a White Bear logo, defend it, white-bearify Tesla's A, and celebrate a survivor (62s5if; 62zxr8; 631ycf; 63ahf5). Comments contain nearly all operational practice: coordinates, design measurements, scale changes, recruitment, placement, neighbour accommodation, repair, and maintenance. They also qualify the posts. “Def not enough of us yet” limits the opening ambition (dfp2ajh), while “we're struggling to maintain what we have” accompanies a later large-logo suggestion (dfq9cbo). These contrasting positions belong to different speakers and do not establish a collective reversal.

The post-event layers partly conflict. The post says one logo “has survived,” whereas the comment layer says “everything was gone” at one check and that remaking logos was repeatedly overtaken (63ahf5; dfssjhw). The same commenter also says “I did that” and describes fixing the work, so the comments complicate a simple survival story without rejecting community participation. The Tesla-A proposal exists only in the post layer (631ycf); its reception and enactment remain unknown.

Counter-reading

My reading is that a small r/blackmirror group made White Bear into a workable r/place mark by redesigning, recruiting, placing, accommodating neighbours, and repeatedly repairing it, then turned the unstable work into an end-of-event memory; the fake season-release joke was a separate practice.

Before searching, I specified this competing account: people mostly proposed White Bear work without actually placing or maintaining it, and the claimed survivor was not recognisably theirs. If my reading were wrong, the record should contain admissions of non-placement or abandonment, rejection of the survivor as theirs, or accounts treating purple and rainbow changes as the desired endpoint rather than damage or accommodation.

The strongest contrary item is dfssjhw: “everything was gone” and rebuilding “kept getting overtaken.” It rules out a story of stable control. It does not unseat the account of participation because the same passage claims the surviving work, describes fixing and rebuilding logos, and reports trying again at the end. The search found no explicit giving up or abandonment, no rejection of the survivor as “not ours,” and no statement preferring purple or rainbow damage. A non-ownership/non-placement query returned one unrelated use of “didn't make” in an ordinary episode discussion (dfqn4zu); broader shortage and destruction terms returned the relevant “not enough” passage (dfp2ajh), the already-coded loss account (dfssjhw), and three unrelated show-discussion items (dfg698h; dfredp4; dfrk9ti). All returned items were read. These nulls cover only the supplied record; removed bodies and partial contextual threads mean absence cannot prove that no participant abandoned the effort elsewhere. No late code resulted.

Saturation

The selected practice is internally well represented: the five coded threads were read in full by their slice coders, the forest retains every one of the 62 codes, and surviving passages show design, recruitment, placement, accommodation, defence, end claims, and memorialising. It is not a visually complete record. The linked Imgur design and measurements cannot be inspected; deleted comments leave holes in both main White Bear threads; and the record cannot identify random purple placers, verify the survivor image independently, or show what happened beyond the lone Tesla-A post. The r/pxlsspace referral is visible, but no move there is.

Practice did not fully settle before the final slice. The fake-release joke, making a workable White Bear design, recruiting placers, protecting the logos, proposing other inscriptions, and claiming last pixels or logos first appear in batch 01. Batch 02 repeats the end-claim practice, but first introduces remembering the work as damaged, remade, and fun, plus the single r/pxlsspace referral. Later material therefore brought two new post-event practices rather than only repeating settled ones.

No one reader held the whole week. Chronology and relations were assembled from two slice accounts, the pooled codes, the timeline, and the forest. The only relation crossing the slice boundary is reported above as an observed sequence because neither side supplies a causal link; this makes cross-slice relations weaker than a single continuous reading.

Selection

The case lead read the briefing and the complete openings table before the gate, so the week-wide shape was known before any thread triage. The fixed gate selected branch B on 659 in-window items against a threshold of 500, with 111,070 characters by people. Two coders then disposed whole-thread slices in corpus order. Every one of the 108 threads received a disposition; five were coded. Threads were retained when they concerned r/place conduct, and 62qzcv was retained as the community's own April Fools conduct while explicitly kept separate from the canvas. Ordinary episode interpretation, recommendations, art, news, star-flair play, and related media were excluded. The fleet audit passed before consolidation.

Other communities named

r/place is the named canvas venue, not another ally or opponent; it appears while participants resize their design after “looking at /r/place again” (dfp04j4). r/ainbowroad is treated as a neighbour to avoid angering and to accommodate with rainbow-filled White Bear outlines (dfp9xdy; dfpn5tg). The Imgur link carried the proposed visual design and measurements, so that part of planning moved partially off-platform; location decisions, recruitment, placement reports, repairs, and requests for help remained in the Reddit thread (dfoxud5). After the event, one person suggested that others “go at it again on r/pxlsspace” (dfsuejb), but nothing shows anyone followed.

Absence

Deleted comments create small gaps in the two main White Bear threads, including near discussion of purple changes, but surviving comments still show calls for help, repair, private-message contact, maintenance, and completion claims. No moderator-marked or stickied item appears in the selected conduct. The linked design cannot verify what participants drew, the record does not identify the “Randoms” placing purple (dfq9oq4), and no reply resolves the Tesla-A proposal (631ycf). The memorial thread contains no removed human body; its automatic preview was treated as platform behaviour rather than community conduct.