The Proboards38 Blog

Field notes from the operator's chair: postmortems, load tests, migrations, and governance audits for forum-class platforms of 10k+ users.

The Motion Alert Shirt: A Notification That Cannot Be Dismissed

The shirt prints a white rounded banner with a bell icon and the sentence There is motion at your front door. Beneath it, inside a circular green-tinted frame, an orange tabby stares into a doorbell camera from a distance of roughly four inches. Porch siding and a light fixture sit behind the cat. That is the whole design. The joke is not the cat, and it is not the sentence. The joke is the collision between a system notification and the thing that triggered it.

I keep coming back to this because notification copy is one of the few places where platform engineering and comedy use the same raw material. A motion alert is a machine’s attempt to summarize a physical event in a fixed string. The string is written for a generic event: something moved near a sensor. The camera then supplies the evidence, and the evidence is a cat’s face filling the lens. The banner and the image disagree about what kind of event this is. The banner says motion. The image says supervision.

What the artwork actually shows

The observed design has two stacked elements. The top element is a notification banner: white, rounded corners, a small bell glyph at the left, and the sentence in a plain sans-serif. The bottom element is a circular viewport with a green cast, the kind of tint you get from a cheap image sensor pushing color balance under porch lighting. Inside the circle, the tabby is close enough that its eyes are wide and its pupils are doing the thing cats do when a lens is pointed at them. The background is domestic exterior: horizontal siding, a wall light, a bit of structure.

I read the green tint as a deliberate visual cue rather than a literal photograph of a specific camera model. It signals doorbell camera the way a red circle signals record. The rounded banner and the circular viewport together form a recognizable interface grammar: alert on top, evidence below. The shirt is not depicting a cat. It is depicting a notification about a cat, and the notification is the subject.

The sentence is doing the work

Consider the wording. There is motion at your front door. Not someone is at your door. Not your package has arrived. The system does not know what moved. It knows only that a threshold was crossed. The sentence is honest about its own ignorance, and that honesty is what makes the cat funny. The camera promised motion; the cat delivered presence.

This is the same gap that shows up in every alerting system I have ever operated. A monitor fires because a metric crossed a line. The metric is real. The interpretation is not included. You get a page at 03:14 that says latency elevated, and then you open the dashboard and discover the actual event was a backup job that started on schedule and will finish on schedule. The alert was correct. The alert was also useless. The cat shirt is a two-panel incident report: the page, and the cause.

Why the framing matters more than the meme

I am not going to tell you where this phrase came from. I do not have retrieved evidence for its origin, and the retail listing does not supply one. What I can say is that the design works as a composition independent of any meme lineage. The banner is small and the viewport is large. The sentence is calm and the cat is not. The interface element is crisp and the photographic element is slightly degraded. Those contrasts are doing the comedic labor, and they would work even if you had never seen the phrase before.

That is the difference between a slogan and a usable joke. A slogan asserts. A usable joke sets up a system and then lets the system fail in a legible way. The banner sets up a promise of useful information. The cat breaks the promise. You laugh because you have been on the receiving end of that exact failure mode, probably this week.

The tradeoff the shirt is quietly about

Doorbell cameras exist to answer a narrow question: is there a person at my door who should not be? The motion alert is the first stage of that answer. It is deliberately low-precision because high-precision detection is expensive and because the cost of a false positive is low. You glance at your phone, see a cat, and go back to what you were doing. The system is tuned for recall, not precision, and the cat is the price of that tuning.

Every alerting pipeline makes this trade. If you want to catch every real event, you accept noise. If you want silence, you accept misses. The shirt does not argue for either setting. It just shows you the noise, rendered at close range, with whiskers. I find that more useful than a thinkpiece about alert fatigue, because it puts the false positive in front of you as an image rather than a statistic.

An object note

The shirt is sold as a standard t-shirt by Quirky Cotton Collective under the title There Is Motion At Your Front Door Funny Cat Doorbell Meme. The listing is here. I have not worn it, washed it, or tested the print. What I have done is look at the artwork and describe what is on it.

Editorial note: this publication and Quirky Cotton Collective share an owner. This is not an independent review.

What I would want an operator to take from it

If you run a system that sends notifications, the shirt is a small test you can apply to your own copy. Does your alert describe the event or the evidence? There is motion describes the evidence. Your cat is on the porch would describe the event, and it would require a model that can tell a cat from a raccoon from a person. Most systems cannot, so they send the evidence and let the human do the classification. That is a reasonable design. It is also a design that produces a certain volume of cat.

The shirt is funny because the classification step is visible. The banner and the image are stacked, and you can see the gap between them in a single glance. Most of our dashboards hide that gap behind a link. The shirt puts it on your chest, which is a more honest place for it than a status page.

When ZetaBoards Died: The 2018 Tapatalk Migration as a Data-Portability Case Study

When ZetaBoards Died: The 2018 Tapatalk Migration as a Data-Portability Case Study

The most useful fact about the ZetaBoards-to-Tapatalk migration is not that a hosted forum platform was retired. Platforms get retired. The useful fact is that a board administrator, writing publicly in July 2018, reported that the platform’s own staff seemed insistent that the community could not have a data dump of its site. Everything else about the episode — the broken themes, the uncertain fate of custom emotes, the migration window that kept sliding — is downstream of that one sentence.

This is a case study in the difference between conversion and portability. Those are different properties, they are routinely conflated in vendor communications, and the gap between them is where communities lose things they cannot get back.

What the record actually shows

Two contemporaneous community announcements carry most of the documented timeline. Neither is a primary platform document; both are operator-side accounts, and they should be read as such.

Kill the Can, a quit-support community that had hosted on ZetaBoards since November 2006, posted an announcement in July 2018 stating that ZetaBoards had been acquired by Tapatalk in July 2017, and that on July 1, 2018 the community learned — via a Facebook message — that Tapatalk had opted to end ZetaBoards as they knew it and convert all boards to Tapatalk (Kill the Can, “Forum Changes on the Horizon”).

That announcement is also the clearest statement of what the migration promised. User information — username, password, email, signatures — would not be affected. Posts, forums, subforums, and private messages would be converted, “though things may look a bit weird.” The community was told to expect the production migration “within next few weeks,” with the caveat that it might take longer.

The Ocarina Network’s site administrator, posting on July 23, 2018, filled in the parts the vendor-facing announcement left out. Themes were expected to be “broken completely.” Custom emotes, custom CSS, and custom JavaScript might not survive. Uploaded content was hoped-for but unconfirmed: “We hope uploaded content will be transferred, but again we can’t be sure.” And then the load-bearing line: “the staff at Zetaboards seem insistent we can’t have a data dump of the site” (The Ocarina Network, “Zetaboards takeover by Tapatalk”).

Note what is and is not established here. These are community reports, not platform announcements. They document what administrators were told and what they believed at the time. They do not establish that data was lost, that any particular board migrated on any particular date, or how many communities were affected. The migration window in both threads is described as pending and approximate; the Ocarina Network admin relays an August email saying conversion would happen “in two weeks,” which is the kind of estimate that has never once in the history of computing meant two weeks.

The distinction that matters: converted is not portable

Read the two announcements side by side and a structural gap appears.

The Kill the Can post describes conversion: your posts, forums, subforums, and PMs will be moved into the successor platform. From a user’s perspective, this sounds like preservation. The content still exists; you can still read the thread where someone talked you out of a relapse at 2 a.m. in 2011. That is not nothing.

The Ocarina Network post describes the absence of portability: the operator could not obtain an export of the database. Conversion moves your content into a system someone else controls. Portability means you hold a copy you can load into a different system without asking permission. A platform can do the first while refusing the second, and that is precisely the configuration the ZetaBoards shutdown appears to have presented to its board owners.

This matters because the two properties fail differently. Conversion failure is visible: threads go missing, attachments 404, formatting collapses. Portability failure is invisible until you need it. As long as the successor platform keeps running, an operator without an export has no way to distinguish “my data is safe” from “my data is currently being served to me.” The distinction only becomes legible at the next acquisition, the next shutdown, or the next pricing change.

The Ocarina Network thread also shows the community improvising around the gap. Members asked whether an offline reader could capture the valuable parts of the site, and whether content could be archived on the Internet Archive. These are reasonable responses, and they are also a tell: when the operator cannot get a database dump, the fallback is scraping your own forum page by page and hoping the crawler gets the pagination right.

What the successor platform’s marketing says now

It would be unfair to characterize Tapatalk’s current posture from a 2018 community thread, and no Tapatalk source was available for this piece. What can be documented is how a competing platform frames the same problem today.

Discourse’s site states: “Your data, your control. Export everything, anytime. Self-host or use our managed hosting. Switch whenever you want.” It also describes the codebase as open source with “no vendor lock-in” (Discourse). NodeBB’s site similarly offers a self-hosted open-source option alongside managed hosting (NodeBB).

Treat these as marketing claims, not verified migration results. A vendor saying “export everything, anytime” is a statement about intent and positioning; whether a given export round-trips cleanly into another platform is an engineering question that only a test answers. The point of citing them is narrower: the market now contains platforms that treat export rights as a selling point, which means operators have more procurement leverage than ZetaBoards board owners had in 2018. Whether that leverage is real depends on what you do with it before signing.

An operator’s checklist, derived from the failure mode

The lesson is not “self-host or perish.” Self-hosted platforms fail too, usually at 3 a.m. when the database server fills a disk. The lesson is that migration risk is a procurement decision made years before the migration, and it is cheap to hedge.

Get the export right into the contract or terms, and read the actual clause. “You own your content” is a copyright statement, not a portability guarantee. What you want is a stated right to obtain a complete machine-readable export of posts, users, private messages, attachments, and metadata, on request, without discretionary approval. If the terms only promise that content will be “converted” or “preserved” on the platform, you have conversion without portability.

Test the export before you need it. Request a full export during the trial or first month, and again on a schedule. A hypothetical worth sitting with: an operator who runs a quarterly export drill and stores the output off-platform is in a materially different negotiating position after an acquisition announcement than one who first learns about export limits from a Facebook message. The drill does not need to be elaborate. It needs to produce a file you have opened and confirmed contains your posts.

Keep an independent archive of high-value threads. Not the whole board — that is a backup problem, and you should have backups. The threads that constitute the community’s institutional memory: the how-to posts, the canonical arguments, the reference lists that people link to from elsewhere. A static archive of those pages costs little and survives platform changes, domain changes, and the successor platform’s redesign.

Assume customization is a casualty. Themes, custom emotes, custom CSS and JavaScript, template hacks, and plugin behavior are the first things to break in any migration, because they are the parts of your board that depend on the specific software rather than on the data. The Ocarina Network admin anticipated exactly this. Budget for rebuilding the presentation layer, and do not treat the loss of a theme as evidence that the content is gone — or the reverse.

Distinguish “users can still log in” from “you can leave.” The Kill the Can announcement’s most reassuring line — user information will not be affected — is also the one that tells you least about exit. Accounts surviving a migration means the successor platform has your user table. It says nothing about whether you can take that table elsewhere.

Why the timeline detail matters

The acquisition closed in July 2017. The conversion was announced to at least one community in July 2018, with production migration described as weeks away and then, in August, two weeks away. That is a year of operating a forum under a known terminal condition, and the operators’ public posts show them spending that year on uncertainty management rather than on export.

This is the normal shape of hosted-platform risk. The acquisition is the signal; the migration is the event; the gap between them is the only window in which an operator can do anything. In that window, the useful actions are unglamorous: read the terms, request the export, test the export, archive the threads that matter, and write down what you would do if the successor platform’s answer were no. The ZetaBoards board owners appear to have gotten a no. The next platform’s board owners should find out earlier.

Questions operators ask about this

Did ZetaBoards data actually get lost? Nothing in the retrieved sources establishes that. The documented claim is that an administrator was told a data dump was not available, and that the fate of uploaded content was unconfirmed. Loss and inaccessibility are different outcomes, and the second is bad enough.

Was the migration completed on the announced schedule? The sources give plans and estimates, not confirmed completion dates. The Kill the Can post says “within next few weeks”; the Ocarina Network thread relays an August estimate of two weeks. Treat both as intentions.

Does an open-source platform guarantee portability? No. It guarantees that the code can be inspected and that self-hosting is possible, which changes the failure mode from “vendor decides” to “you decide, and you are responsible.” Export quality still depends on the specific tooling and on whether you tested it.

What is the single cheapest hedge? A scheduled export you have actually opened. It converts an unknown into a known, and it gives you a file to point at when the acquisition announcement arrives.

The Large Lowercase ‘meh.’ Shirt: When the Typeface Does the Arguing

The native garment preview shows four letters and a period: meh. — lowercase, bold, white, set large on a dark shirt. No animal. No secondary slogan. No decorative frame. The period is the only punctuation, and it lands like a door closing quietly rather than slamming.

That is the whole design. The interesting question is not what the word means — everyone who has ever sat through a status meeting knows — but why the typography is so loud about something so indifferent. A whisper set in 72-point type is a contradiction, and the contradiction is the product.

The visual mechanics of a shrug

Lowercase matters here. Set MEH. in caps and you get a shout, a complaint, a person who is angry about being bored. Set it in lowercase and the word slumps. Lowercase is the typographic equivalent of shoulders going down. The bold weight keeps it from disappearing, and the period gives it finality — not the finality of a verdict, but the finality of someone who has stopped arguing.

I read the scale as the joke. A small meh. on a chest is a private mood. A large one is a public statement about the limits of public statements. The shirt is not saying the wearer is bored of you specifically. It is saying that the wearer has a finite budget for enthusiasm and has elected to spend it elsewhere. The type size is the only evidence you need that the budget is real.

This is an interpretation of the artwork, not a claim about the designer’s intent or the shirt’s history. What is observable is the lettering, the color contrast, and the absence of any other graphic element. Everything else is reading.

Why this belongs in a column about work culture

Technical teams run on slogans. “Move fast.” “Bias for action.” “Customer obsession.” Most of them are promises that the organization cannot keep at the individual level, and everyone in the room knows it. The meh. shirt is the rare slogan that promises nothing. It is a boundary written in the grammar of a shrug: I am here, I am competent, and I am not going to perform enthusiasm as a condition of employment.

That is a useful thing to have in a drawer. Not because it changes anyone’s mind, but because it names a posture that most people adopt silently. The shirt makes the posture legible. It is the visual equivalent of a status page that reads degraded performance instead of all systems operational — honest, unglamorous, and slightly funny if you have been on call long enough.

There is a difference between a slogan and a usable promise. A usable promise tells you what will happen next. A slogan tells you what to feel. The meh. shirt is neither, which is why it works as an off-duty object. It is a mood rendered in type, and moods do not need to be operationalized.

The period is doing more work than the word

Strip the period and you have a sound. Add the period and you have a sentence. The period is what turns a noise of indifference into a complete thought, and complete thoughts are harder to argue with than noises. A person who says meh can be cajoled. A person who says meh. has already considered the cajoling and declined it.

I would not overstate this. It is a t-shirt. But the design is doing something specific with punctuation that most novelty shirts do not bother with, and that specificity is worth noticing. The period is the difference between a reaction and a position.

What the shirt is not

It is not a diagnosis. It is not a statement about mental health, burnout, or any clinical condition, and it should not be read as one. It is a piece of dry humor printed on cotton. The word meh has been in English usage for decades as a marker of mild indifference, and the shirt leans on that ordinary meaning rather than any technical or medical claim.

It is also not a substitute for saying what you actually mean. A shirt can carry a mood; it cannot carry a boundary that needs to be spoken aloud to a manager. If the meh. is a real message rather than a joke, the shirt is the wrong medium. The shirt is for the days when the joke is the message.

The object itself

The listing is the Meh Funny Sarcastic Saying Introvert Dry Humor shirt from Quirky Cotton Collective, and the native preview shows the large bold white lowercase meh. lettering on a dark garment. That is the design as observed. The shirt is a standard t-shirt, and the visual observation does not extend to fit, fabric weight, or how it wears over time — those are not things a preview can tell you.

What the preview can tell you is that the design is legible at a distance, which is the only performance criterion a shirt like this has. The contrast is high, the letterforms are simple, and there is nothing to squint at. For a garment whose entire job is to be read across a room, that is sufficient.

The takeaway

Most slogan shirts fail because they try to be clever at the wrong scale. This one succeeds because the scale is the cleverness. The word is small in meaning and large in type, and the gap between those two facts is the joke. If you are going to wear a mood, wear one that has been set in a typeface that knows what it is doing.

Editorial note: This publication and Quirky Cotton Collective share an owner.

Reddit’s $60M Google Deal and the Bargaining Power of Independent Forums

In February 2024, Reddit announced an expanded partnership with Google. Google would get programmatic access to public posts and comments through the Reddit Data API, and Reddit’s own announcement said the arrangement enabled Google “to use the Reddit Data API to improve its products and services – including supporting new ways to display Reddit content and providing more efficient ways to train models” (Reddit). The Verge reported the deal as worth $60 million per year, giving Google real-time access to Reddit’s data while Reddit got access to Google’s Vertex AI (The Verge). The Hindu, citing the Associated Press, put the value at roughly $60 million and noted the reciprocal access to Google AI models for Reddit’s internal search (The Hindu).

The number that matters more for anyone running a forum is in the S-1. Reddit disclosed that in January 2024 it entered data licensing arrangements with an aggregate contract value of $203.0 million over two to three years, expecting at least $66.4 million of that in 2024 (TechCrunch, quoting the prospectus). The Google deal is the visible tip of a larger licensing line item.

The temptation, if you operate a forum with ten or twenty thousand users, is to read this as a market signal: human conversation has a price now, and your archive is sitting on it. That reading is mostly wrong, and the parts where it is right are the parts you can act on without waiting for a check.

What the deal actually is

Reddit’s announcement is careful. It describes API-based programmatic access, display of Reddit content across Google products, and training. It also states that the expanded partnership “does not change Reddit’s Data API Terms or Developer Terms, which state content accessed through Reddit’s Data API cannot be used for commercial purposes without Reddit’s approval,” and that API access remains free for non-commercial usage under a published threshold (Reddit).

So the deal is not a change in the rules for everyone. It is a specific commercial grant to one counterparty, layered on top of terms that already reserved commercial use. The API is the chokepoint. The terms are the legal instrument. The corpus is the asset. All three had to exist before anyone could sign anything.

The three ingredients of licensable content

Strip away the press coverage and Reddit’s position rests on three things. None of them is “being big” in the abstract.

1. A large, continuously refreshed corpus of human-written text. Reddit’s filing, as quoted by Ars Technica, describes the value of continuous access as resting on data that “constantly grows and regenerates as users come and interact with their communities and each other” (Ars Technica). A static archive is a snapshot. A live forum is a stream. Buyers pay for the stream.

2. A single party able to grant access. Reddit can sign because Reddit controls the platform, the terms, and the API. A forum where the database is hosted by a vendor, the domain is registered to a former admin, and the terms of service were last edited in 2011 cannot make the same representation to a buyer. Rights posture is not paperwork; it is the ability to say yes.

3. A technical point through which access flows. The Data API is where Reddit can meter, log, and condition access. If your forum’s content is fully crawlable, mirrored, and syndicated with no gate, you have already granted the access you might otherwise have negotiated over. That is a choice, even when it is made by default.

Leverage is not control

Reddit’s own filing is candid about the limits. Ars Technica quotes the S-1: “Some companies may decline to license Reddit data and use such data without license given its open nature, even if in violation of the legal terms governing our services,” and enforcement “could take years to resolve, result in substantial expense, and divert management’s attention and other resources, and we may not ultimately be successful” (Ars Technica).

If the largest forum-class platform on the internet, with a legal department and an IPO on the line, describes its enforcement position that way, a 15,000-user board should calibrate accordingly. Having a licensable corpus is not the same as being able to stop someone from taking it. The realistic value of a licensing audit for most independent forums is not a revenue line. It is a clearer picture of what you hold, what you can prove you hold, and what you can technically control.

An operator’s audit

The useful exercise is not “how much is my forum worth to an AI company.” It is a set of questions you can answer this quarter.

Content inventory. How many unique threads and posts do you hold? How much of it is original human writing versus syndicated feeds, quoted articles, or bot output? A corpus padded with scraped content is harder to license, not easier. Provenance matters.

Rights review. What do your terms of service actually say about reuse of member content, and when were they last updated? Do you have a clear chain of custody for the domain, the database, and the trademark? If a buyer asked you to represent that you have the right to grant access, could you sign that representation without lying?

Access posture. What does your robots.txt allow? Do you have an API, and is it authenticated? Are you logging large-scale retrieval? Access controls designed for spam and scraping are the same controls that determine your future negotiating position. Treat the question “could we technically gate this?” as governance before it becomes commercial.

Export and archival hygiene. Can you produce a complete, structured export of your forum on demand? Stable URLs, consistent schema, documented provenance, and a tested restore procedure make a corpus legible to a partner, an auditor, or your own successor. Discourse’s own positioning is instructive here: it describes itself as open source since 2013 and states that community data “is never locked into a proprietary system” and that operators can self-host or migrate away (Discourse). Self-hostable software reduces lock-in risk. It does not by itself create bargaining power. The operator still has to decide what access to grant and on what terms.

Buyer reality check. Would anyone actually want your corpus? NodeBB’s about page notes that forums pre-date blogs, social networks, and smartphones and that “millions of them are still going strong” (NodeBB). That is a statement about durability, not about market demand for any particular archive. A niche board with deep, specific, well-moderated technical content is a different asset from a general chat forum with ten years of off-topic threads. Be honest about which one you run.

What the deal does not tell you

It does not tell you that independent forums can expect comparable deals. No retrieved source supports a specific figure for what a 10k+ user forum’s corpus is worth, and the arithmetic of the Reddit deal does not scale down in any straightforward way. It does not tell you that Reddit’s terms, pricing, or enforcement posture changed after February 2024; the announcement explicitly says the Data API terms did not change. And it does not tell you that Google’s use of Reddit data has produced any particular product feature or model capability. The deal is a data point about what one platform with a specific combination of scale, rights, and technical control was able to sign. It is not a forecast for yours.

The durable lesson

The bargaining power in the Reddit–Google deal came from being a well-run, well-documented archive with clear rights and a technical gate. Those are properties you can build regardless of whether a licensing check ever arrives. A forum with clean exports, current terms, authenticated API access, and a documented chain of custody is easier to migrate, easier to hand off, easier to defend in a dispute, and easier to sell access to if the opportunity ever appears. A forum without those things is not sitting on an asset. It is sitting on a liability with a search box.

The unsentimental version: most independent forums will never sign a licensing deal, and the ones that do will not sign one that resembles Reddit’s. The audit is still worth doing, because the same work that would make you licensable is the work that makes you survivable.

FAQ

Did Reddit’s Data API terms change because of the Google deal? No. Reddit’s announcement states the expanded partnership did not change its Data API Terms or Developer Terms, and that API access remains free for non-commercial usage under its published threshold (Reddit).

How much was the Google deal worth? The Verge reported it as worth $60 million per year (The Verge). The Hindu, citing the AP, reported roughly $60 million (The Hindu). Reddit’s S-1 disclosed $203.0 million in aggregate data-licensing contract value across arrangements entered in January 2024, with at least $66.4 million expected in 2024 (TechCrunch).

Does self-hosting on Discourse or NodeBB give me leverage? It reduces lock-in risk and makes migration and export more tractable. It does not create a buyer or a price. Leverage comes from corpus quality, clear rights, and a technical gate, and those are operator decisions, not software features.

Should I block crawlers to preserve negotiating position? That is a governance decision, not a default. Blocking may protect content from unlicensed use; it may also remove you from discovery channels that bring members. The relevant question is what access you are granting, to whom, and under what terms, and whether you can document the answer.

The Rooting Shirt: Four Vegetables, Two Meanings, and the Growth Clause

The artwork is a closed loop of text. LET’S ROOT FOR EACH OTHER AND WATCH EACH OTHER GROW runs around the perimeter, and inside it sit four root vegetables — carrot, radish, beet, onion — each with a face and each with its roots drawn down into visible soil. The pun is doing double duty: root as encouragement, root as the thing underground that makes the encouragement possible. The second clause is the part worth reading twice. Watch each other grow is not the same promise as support each other. One is a stance. The other is a metric.

That distinction is the whole argument of the shirt, whether or not anyone wearing it has thought about it in those terms. The design is a diagram of a team promise, and like most team promises it contains an unexamined assumption about what happens when growth stops.

What the drawing actually shows

The four vegetables are not identical. The carrot is tapered, the radish is round and small, the beet is bulbous with a crown of stems, the onion is layered. Their roots are drawn individually, not as a shared mass. That matters: the illustration is not claiming that everyone grows the same way or at the same rate. It is claiming that everyone is rooted in the same soil and that the rooting is mutual.

The faces are smiling. This is a retail convention, not a scientific observation, and I am not going to pretend the smiles carry hidden data. But the composition does something specific: the text encircles the vegetables rather than sitting above them. The slogan is a boundary, not a banner. The vegetables are enclosed by the promise. Read literally, the promise is the container and the plants are the contents. Read less literally, the plants are trapped inside a sentence about their own improvement.

I do not think the designer intended the second reading. I think the designer intended a cheerful gardening pun with a mutual-support message, and the execution is competent at that. But the enclosure is there in the geometry, and it is the kind of thing that becomes visible after you have sat in enough planning meetings where someone says we want to help everyone grow and nobody asks what happens to the people who are already grown.

Two meanings of rooting, one of which is a demand

To root for someone is to want them to succeed without requiring anything in return. It is cheap, in the good sense: you can root for a stranger, a rival, a team you will never meet. It costs attention and nothing else.

To root, intransitively, is to put down roots — to stay, to establish, to become difficult to move. This is the meaning the vegetables embody. A carrot that has rooted is a carrot that is not going anywhere. The shirt uses both meanings at once, which is the joke, and the joke is fine. But the two meanings pull in opposite directions. Rooting for is outward and unconditional. Rooting in is inward and territorial. A community that confuses the two will tell itself it is being supportive while it is actually asking people to stay put.

This is not a criticism of the shirt. It is a criticism of the way the shirt’s sentence gets used. The phrase let’s root for each other is a good thing to say to a colleague before a hard week. The phrase and watch each other grow is a different kind of statement, and it is the one that shows up in performance reviews.

The growth clause is the load-bearing part

Growth is the only clause in the sentence with a direction. Rooting for each other has no endpoint. Watching each other grow implies a trajectory, and a trajectory implies a comparison — growth relative to what, measured how, over what period. The shirt does not answer these questions, and it does not have to, because it is a shirt. But the people who wear it into a workplace are carrying a sentence that sounds like solidarity and functions like a target.

There is a version of this argument that turns into a rant about hustle culture, and I am not interested in writing that. The more useful observation is narrower: the shirt works as a gift between gardeners because gardeners already understand that growth is seasonal, uneven, and mostly out of your control. A radish is ready in weeks; a beet takes months; an onion overwinters. The illustration knows this — the roots are different shapes and the plants are different sizes. The sentence does not know this. The sentence says watch each other grow as if growth were a single event that happens to everyone at once.

If you are going to wear the shirt, the interesting question is which clause you mean. If you mean the first one, you are making a claim about your stance toward other people. If you mean the second one, you are making a claim about their trajectory, and you should be prepared for someone to ask who is doing the watching.

Why this design reads better than most slogan shirts

Most pun shirts put the joke in the text and leave the image as decoration. This one puts the joke in the relationship between the text and the image. The text says root; the image shows roots. The text says grow; the image shows plants at different stages of growth. The text says each other; the image shows four distinct plants with distinct root systems, not a monoculture. The illustration is doing argumentative work, even if the argument is gentle.

The color choices are also doing work, though I am reading them rather than reporting them. The vegetables are drawn in recognizable earth tones — orange, red, deep purple, pale yellow — against what reads as a light background. That is a deliberate choice to keep the design legible at a distance and to avoid the high-contrast palette that makes most novelty shirts look like warning labels. The result is a shirt that reads as a garden sign, which is probably the correct register for a gardening pun.

The Let’s Root For Each Other And Watch Each Other Grow Garden shirt is listed under Quirky Cotton Collective, and the design is what the listing shows: the full sentence wrapping four smiling root vegetables with their roots in soil. I am describing the artwork, not vouching for the cotton weight or the fit, because I have not worn it and the listing does not give me a reason to pretend otherwise.

The usable version of the promise

If I were going to adapt the shirt’s sentence into something I would actually say to a team, I would keep the first clause and drop the second. Let’s root for each other is a complete promise. It asks for attention and goodwill and nothing measurable. And watch each other grow is the clause that turns a stance into a surveillance arrangement, and it is the clause that makes the sentence sound like a quarterly objective.

But the shirt is not a management framework, and it should not be held to that standard. It is a garden pun with a good drawing and a sentence that is more interesting than it needed to be. The reason to notice the growth clause is not to condemn the shirt. It is to notice how easily the language of mutual support slides into the language of mutual evaluation, and how a sentence that begins as encouragement can end as a benchmark.

The vegetables, at least, are not being measured. They are just sitting in the soil with their roots showing, smiling in the way that drawn vegetables smile, waiting for someone to decide whether they have grown enough.

Editorial note: this publication and Quirky Cotton Collective share an owner. This is not an independent review.

The Composition Notebook Shirt: A Printed Cover, Not a Costume

The garment image shows a rectangle of black-and-white speckle, a dark binding strip down the left edge, and a white ruled label headed COMPOSITION. Inside the label, an outlined ghost and an outlined pumpkin sit on the ruled lines. The whole thing is printed on a shirt. It is not a notebook. It is a picture of a notebook cover, scaled to a torso, with the binding running vertically where a spine would be if a person were a book.

That distinction matters more than it sounds. A costume implies an object you put on and take off. A printed cover implies a surface that was already there, waiting for content. The shirt does not dress you as a notebook. It dresses you as the front of one — the part that faces the room, the part that gets written on, the part that carries the label. The ghost and pumpkin are not decorations added to a notebook. They are the content that has been entered into the ruled lines, the way a student would fill a label with a name and a subject.

I keep looking at the binding strip. It is dark, solid, and runs the full height of the printed rectangle. On a real composition notebook, that strip is cloth tape over the spine, and it is the only part of the cover that is not meant to be written on. On the shirt, it functions as a visual anchor: it tells you which edge is the left edge, which way the book opens, which way the wearer faces. It is a small piece of graphic design doing the work of a diagram. Without it, the speckled rectangle would be a texture. With it, the rectangle becomes an object with an orientation.

The label is the other anchor. It is white, ruled, and headed with a single word in all caps. The word is not a slogan. It is a category. COMPOSITION tells you what kind of book this is, not what kind of person you are. That is a different grammar from most printed shirts, which tend to make a claim about the wearer — a team, a mood, a profession, a joke. This one makes a claim about the surface. The ghost and pumpkin are then free to be content rather than identity. They are what has been written in the book, not what the book is.

I read the ghost and pumpkin as a seasonal entry, not a permanent label. They sit inside the ruled lines, outlined rather than filled, the way a pencil sketch sits on a page before it is inked. The pumpkin is round and ribbed; the ghost is a simple arched shape with a scalloped hem. Neither is scary. They are the kind of drawing that appears in the margin of a notebook during a lecture, which is to say they are evidence of attention wandering in a controlled way. The shirt does not claim you are a teacher. It claims you are a surface that has been written on, and the writing happens to be Halloween-themed.

That is the useful argument here: the design works because it treats the body as a page, not as a billboard. A billboard makes a statement to the room. A page receives a statement from the hand. The composition notebook shirt is closer to the second. The speckle pattern is the paper stock; the binding is the spine; the label is the header; the ghost and pumpkin are the entry. The wearer is not the author of the message. The wearer is the medium the message was written on. That is a strange and specific thing to print on a shirt, and it is more interesting than a generic school slogan because it has a structure.

If you are looking for the object itself, the composition notebook shirt is listed under the Quirky Cotton Collective brand. The retail title calls it a costume, and the group framing is there in the listing language, but the artwork is doing something quieter than a costume. It is a printed cover. The distinction is not pedantic. A costume is worn to signal a role. A cover is worn to signal a surface. The ghost and pumpkin are the only parts that signal the season, and they are contained inside the label, which means the season is an entry in the book rather than the whole book.

I have written before about shirts that function as diagrams — the ramp and ball, the periodic table that refuses to spell its own sentence, the lowercase meh. that uses scale as its argument. This one belongs in that family, but its mechanism is different. Those shirts make an argument about a promise or a scale. This one makes an argument about containment. The label contains the ghost and pumpkin. The binding contains the speckle. The rectangle contains the whole design. Nothing spills. The shirt is a set of nested boundaries, and the outermost boundary is the edge of the print itself, which stops before the sleeves and the hem, leaving the rest of the garment as margin.

That is why it reads as a group object rather than a solo costume. A group costume works when each person is a recognizable unit of a larger set. A composition notebook is already a unit — one book among many identical books, distinguished only by what is written on the label. The shirt reproduces that logic. If several people wear it, they are not matching in the sense of identical slogans. They are matching in the sense of being the same kind of surface, each with its own entry. The ghost and pumpkin are the entry on this particular cover. Another wearer would presumably have a different entry, or the same one, and either way the structure holds.

The tradeoff is that the design is quiet. It does not announce itself from across a room the way a large slogan does. It rewards a second look, which is a different kind of attention. The binding strip and the label header are the parts that resolve at distance; the ghost and pumpkin resolve up close. That is a reasonable distribution for a work-culture object, because it means the shirt can be worn in a setting where a loud costume would be out of place. It reads as a notebook from far away and as a Halloween drawing from near. The two readings do not compete. They are layered, the way a cover is layered over a page.

I would not claim the shirt improves anything, teaches anything, or solves any problem. It is a printed surface with a specific visual argument: that a person can be a page, that a label can contain a season, and that a binding strip can tell you which way a book opens. The argument is small and complete. It does not need a slogan to finish it. The word COMPOSITION is already there, doing the work of a category, and the ghost and pumpkin are already there, doing the work of an entry. The rest is margin.

Editorial note: This publication and Quirky Cotton Collective share an owner.

The I Had Potential Shirt: A Ramp, a Ball, and the Difference Between a Diagram and a Promise

The shirt shows four words in white capitals: I HAD POTENTIAL. Beneath them, a white curved ramp descends from an upper-left ledge to a lower-right flat. At the top of the ramp, a dashed empty circle. At the bottom, a solid white ball. That is the whole design. No caption, no arrow, no equation. The ramp is curved, not a straight diagonal, which matters more than it first appears.

I want to read this as a diagram, because that is what it is drawn as. The dashed circle is the conventional mark for a position that is not occupied — a placeholder, a ghost, a thing that was supposed to be there. The solid ball is the thing that is there. The ramp connects them. The joke is not that the ball rolled down; the joke is that the ball is at the bottom and the dashed circle is at the top, and the words above say I had potential. The diagram is a before-and-after with the after left implicit. The ball did not fail. The ball arrived.

What makes the drawing worth a second look is that it is not a physics diagram of potential energy. A ball at the top of a ramp has gravitational potential energy; a ball at the bottom has converted it to kinetic energy and then, presumably, heat and sound. The shirt does not label the axes, does not show a height h, does not invoke mgh. It borrows the visual grammar of a physics diagram — the ramp, the ball, the dashed position marker — and uses it to make a sentence about a person. The pun is structural, not verbal. Potential is both the physics quantity and the human promise, and the drawing lets both meanings sit in the same frame without resolving which one is the joke.

That ambiguity is the useful part. A slogan shirt usually tells you what to think: World’s Best Dad, I’m Not Arguing I’m Just Explaining. This one gives you a diagram and lets you supply the verdict. The dashed circle at the top is the potential you had. The solid ball at the bottom is where you are. The ramp is the distance between them, and the ramp is curved, which means the descent was not a straight line — it had a shape, a slope that changed, a moment where it got steeper. That is a more honest drawing of how potential gets spent than a straight diagonal would be. Straight lines imply inevitability. Curves imply a path.

I keep thinking about this in the context of how technical teams talk about promise. A sprint commitment is a kind of potential-energy claim: the work is at the top of the ramp, the team has the capacity, the release is at the bottom. The diagram on this shirt is what happens when the ball is already at the bottom and the dashed circle is still at the top. The gap between the two is not a moral failure. It is a measurement. The shirt is sarcastic, but the sarcasm is aimed at the gap, not at the ball.

The design is also unusually restrained for a garment that could have been loud. White on white, no border, no background shape. The words and the drawing occupy the same visual weight. The dashed circle is the only element that is not solid, and it is the only element that represents something absent. That is a clean piece of visual argument: the thing that is missing is drawn as an outline, and the thing that is present is drawn as a fill. You do not need a caption to read it.

If you want the object itself, the I Had Potential shirt is listed under Quirky Cotton Collective. The retail title calls it a funny physics pun and a sarcastic minimalist quote, which is accurate as far as it goes, but the drawing is doing more work than the title admits. The ramp is curved. The circle is dashed. The ball is solid. Those three choices are the argument.

Disclosure: this publication and Quirky Cotton Collective share an owner.

What I take from the shirt is not a joke about wasted talent. It is a note about how diagrams communicate. A diagram that shows a ball at the bottom of a ramp and a dashed circle at the top is not saying the ball is bad. It is saying the ball is somewhere specific, and the dashed circle is somewhere else, and the distance between them is the thing worth looking at. That is a more useful frame for a postmortem than most of the language we actually use. The ball is at the bottom. The circle is at the top. The ramp is curved. Draw it honestly and the argument makes itself.

The Periodic Table Shirt That Refuses to Spell Its Own Sentence

Editorial note: This publication and Quirky Cotton Collective share an owner.

The shirt reads I WEAR THIS SHIRT PERIODICALLY, and beneath the words sit four tiles in the visual grammar of the periodic table: 53 I, 74 W, 22 Ti, 16 S. Read the symbols in order and you get I W Ti S. Not I W Ti S as a hidden message. Not a chemical formula. The tiles are a diagram of the sentence above them, and the diagram does not spell the sentence. That gap is the joke, and it is also the most interesting thing about the design.

Most periodic-table puns work by substitution. You take a word, break it into element symbols, and let the reader reassemble it. The pleasure is in the decoding: Ba + Na + Na, and so on. This shirt does something slightly different. It gives you the sentence in plain English first, then offers a tile row that looks like it should encode the key word — periodically — but instead encodes the first four words. The tiles are not a cipher for the punchline. They are a visual echo of the setup, dressed in the typography of a cipher.

That is a more honest joke than it first appears. The word periodically is doing double duty: it means from time to time in ordinary speech, and it means in periods in chemistry. The shirt does not resolve that ambiguity; it stages it. The sentence says one thing. The tiles say another thing that looks scientific. The viewer has to hold both readings at once, and the pleasure comes from noticing that the design refuses to collapse them into a single clean punchline.

I have written before about shirts that function as diagrams of a promise — the rooting shirt, the composition notebook. This one is a diagram of a different kind of promise: the promise that a joke will resolve. It doesn’t, quite. The tile row is not a literal spelling of periodically, and it is not a literal spelling of anything else either. It is a near-miss that has been carefully arranged to look intentional. The atomic numbers are correct for the symbols shown — 53 is iodine, 74 is tungsten, 22 is titanium, 16 is sulfur — so the tiles are not random. They are a real sequence of real elements, chosen because their symbols happen to form the letters I W Ti S. The design is not sloppy. It is precise about being imprecise.

That distinction matters if you are the kind of reader who notices when a visual system is being used loosely. A periodic-table tile carries a specific set of expectations: atomic number, symbol, sometimes atomic weight. When you put four tiles under a sentence, you are borrowing the authority of that system. The shirt borrows it and then spends it on a pun that does not quite cash out. The result is not a failure of design. It is a design that knows exactly where the joke lives, and the joke lives in the gap between the sentence and the tiles.

There is a work-culture reading here, though I want to be careful not to overclaim it. Technical readers spend a lot of time with diagrams that are supposed to encode meaning precisely. A schema, a query plan, a network diagram — these are visual systems that borrow authority and are expected to repay it with accuracy. The periodic table is one of the few visual systems that most people learn early and trust completely. Using it to make a joke that does not resolve is a small act of rebellion against the idea that every diagram has to mean exactly one thing. It is the visual equivalent of a comment in code that says this is fine while the build is on fire.

The shirt is available as a standard t-shirt through the listing at Amazon. I am not going to tell you it is soft, or that it fits well, or that people stop you on the street to ask about it. I have not worn it. What I can tell you is what the artwork does: it puts a plain-English sentence above a tile row that looks like it should decode the sentence, and then declines to decode it. That is the whole design, and it is enough.

The tile row is the part worth looking at twice. 53 I is iodine. 74 W is tungsten, which is the only element whose symbol does not match its English name — W comes from Wolfram. 22 Ti is titanium. 16 S is sulfur. Read as symbols, they are I W Ti S. Read as a sentence, they are nothing. The shirt is asking you to notice that the periodic table is a notation system, and notation systems are only as good as the reader’s willingness to accept their rules. Here the rules are bent just enough to make you smile, and not enough to make you angry.

That is a narrow target, and the shirt hits it. It is not a chemistry lesson. It is not a spelling lesson. It is a joke about the difference between a system that looks like it means something and a system that actually does. If you have ever shipped a diagram that was technically correct and completely useless, you will recognize the move.

The Small Lowercase ‘meh.’ Shirt: Scale as the Argument

The native garment preview shows a dark shirt with very small, centered lowercase lettering: meh. No animal illustration. No pride variant. No slogan in a display face. The period is there, and it is doing more work than the word.

That is the whole design, and the scale is the argument. A shirt that says MEH across the chest in a heavy sans is a complaint. A shirt that says meh. in a size you have to lean in to read is a verdict delivered quietly and then abandoned. The difference is not decoration. It is the difference between a slogan and a usable promise.

I keep thinking about this in the context of team communication, because the small-meh. shirt is a better model for boundary wording than most of the incident-adjacent language I see in postmortems and runbooks. The word is lowercase. It ends with a period. It is centered, which means someone made a layout decision and then stopped. There is no exclamation point, no emoji, no second clause explaining the first. The design trusts the reader to arrive at the meaning without being pushed.

What the artwork actually shows

Literal observations only: dark shirt, small centered lowercase meh. lettering, no illustration. The retail title mentions sarcastic, introvert, and minimalist, but those are marketing words, not printed text. The shirt does not say introvert. It does not say sarcastic. It says meh. and lets the wearer supply the context. That restraint is the design.

My interpretation, not a historical claim: the period is the load-bearing element. Without it, meh is a sound. With it, meh. is a complete sentence — a small closed loop of disinterest that does not invite follow-up. In typography, a period is a stop. On a shirt, a period is a boundary marker that happens to be wearable.

The scale problem in operational language

Most team-facing messages fail because they are sized wrong. A status page that says DEGRADED PERFORMANCE in red is a MEH shirt. A runbook step that says ensure the system is healthy is a MEH shirt. The volume is high and the information is low. The small-meh. shirt is the opposite: low volume, complete information, no follow-up required.

This is not an argument for vagueness. It is an argument for proportion. A message should be as large as its content and no larger. The shirt gets this right. The word is small because the sentiment is small. If the sentiment were large, the word would be large, and the shirt would be a different object with a different job.

Slogan versus usable promise

A slogan asks for agreement. A usable promise tells you what will happen next. meh. is neither, exactly — it is a refusal to promise anything, which is its own kind of honesty. In work culture, the useful version of this is the terse boundary: not today, out of scope, no. These are small words that close loops. The shirt is a reminder that closing a loop does not require a paragraph.

I would not read the shirt as a statement about introversion, despite the retail title. The artwork does not support that reading. It supports a reading about understatement as a communication strategy: say the small thing, mean the small thing, stop.

The object itself

The shirt is sold as the Meh Funny Sarcastic Introvert Minimalist Saying by Quirky Cotton Collective. The design is the small lowercase meh. on a dark garment, as observed in the native preview. If you want a shirt that makes a quiet point rather than a loud one, the scale is the feature, not a limitation.

Editorial note: This publication and Quirky Cotton Collective share an owner; this is not an independent review.

The Not Friendly Do Not Touch Shirt: A Boundary Written in Warning-Sign Grammar

The shirt reads NOT FRIENDLY DO NOT TOUCH in warning-sign lettering, with a yellow caution triangle and a crossed-out hand. That is the whole design. No slogan beneath it, no winking subtext, no decorative flourish. It is a public-safety placard applied to a torso, and the interesting question is not whether it is funny — it is — but why the warning-sign format carries the joke at all.

Warning signs work because they compress a rule into a shape. The triangle says hazard before you read a word. The crossed-out hand says prohibited action before you parse the sentence. By the time your eyes reach the text, the grammar has already told you what kind of statement this is: a boundary, not an invitation. The shirt borrows that grammar and redirects it from a machine or a wet floor to a person. The result is a boundary that reads as institutional even though it is intensely personal.

What the sign format actually promises

A warning sign is a contract with a very narrow scope. It does not promise safety. It does not promise courtesy. It promises that a specific action is prohibited and that the prohibition is not negotiable. That is a useful thing to promise, and it is a different thing from what most social slogans promise.

Consider the ordinary introvert shirt, the one that says something like I’m not antisocial, I just don’t like you. That is a joke about a preference. It invites the reader to agree or laugh. The warning-sign shirt does something colder: it states a rule. Not friendly is a status. Do not touch is an instruction. The two together are not a mood; they are a policy.

I think that is why the design holds up. It is not asking for sympathy or offering a personality. It is posting a notice. The humor comes from the mismatch between the bureaucratic register and the intimate subject — the same mismatch that makes a do not feed the ducks sign funny when taped to a person. But the mismatch is doing real work. It lets the wearer say something blunt without sounding rude, because the sign is doing the talking.

The crossed-out hand is the load-bearing element

Strip the crossed-out hand and you have a yellow triangle with words. That is a caution, not a prohibition. The hand is what converts the message from be careful to do not. It is also the part of the design that is most specific: it names the prohibited action rather than the prohibited person. The shirt does not say do not talk to me. It says do not touch me. That is a narrower and more defensible boundary, and the narrowness is what makes it usable.

This is the difference between a slogan and a usable promise. A slogan is a vibe. A usable promise names a specific behavior and a specific consequence. The shirt names one behavior — touching — and one consequence — the sign says no. It does not attempt to regulate conversation, eye contact, or small talk. It regulates the one thing that a warning sign is actually good at regulating: physical contact. That restraint is why the design reads as a boundary rather than a tantrum.

Why this belongs in a work-culture conversation

Technical teams spend a lot of time writing rules that nobody reads. Incident response runbooks, on-call rotations, code review norms, escalation paths — all of them are attempts to state a boundary in advance so that nobody has to negotiate it in the moment. The warning-sign shirt is a tiny, wearable version of the same problem. It is a rule posted on the body because the body is where the rule applies.

The useful observation is not that introverts like shirts. It is that the sign format is a legitimate interface for a boundary, and that most teams are bad at building those interfaces. A runbook that says page the on-call engineer is a warning sign. A runbook that says use good judgment is a slogan. The shirt is on the runbook side of that line. It names the action and the prohibition. It does not ask the reader to infer the rule from a mood.

That is a small thing to learn from a t-shirt, and I am not going to pretend it is more than that. But it is a real thing, and it is the reason the design works better than the average novelty print. The shirt is not a personality test. It is a notice, and notices are supposed to be readable at a glance.

The object itself

The shirt is sold as the Not Friendly Do Not Touch Funny Warning Sign Introvert by Quirky Cotton Collective. The design is exactly what the title describes: warning-sign lettering, a yellow caution triangle, and a crossed-out hand. I am describing the printed artwork as observed, not claiming anything about how it wears or how it is received. The point of the piece is the grammar of the sign, not a product review.

Editorial note: this publication and Quirky Cotton Collective share an owner.

What the design gets right, and what it leaves out

The design gets the hierarchy right. Triangle first, hand second, text third. That is the correct order for a warning sign, and it is the order the eye actually follows. It also gets the scope right: one prohibited action, stated plainly. What it leaves out is any attempt to explain or soften the rule. There is no please, no thanks for understanding, no apology. That is not rudeness; it is the convention of the format. A warning sign that apologizes is not a warning sign.

Whether that convention translates well to a social setting is a judgment call, and I do not think there is a single right answer. Some people will read the shirt as a joke and some will read it as a genuine request. The design supports both readings because it does not resolve the ambiguity. It states the rule and lets the reader decide how seriously to take it. That is the same ambiguity every boundary carries when it is posted in public, and it is the reason the shirt is more interesting than it first appears.

The takeaway is not that you should buy this shirt. It is that the warning-sign format is a compact, legible way to state a boundary, and that most of us could stand to write our boundaries more like signs and less like slogans. Name the action. State the prohibition. Skip the apology. The shirt does that in three lines and a triangle, which is more than most runbooks manage.