Flip the Switch: Going Public

The composer with the Public checkbox now checked, ready to post a build-in-public update

One checkbox. Everything to the left of it is the same. Everything downstream of it is different.

Part 4 of 7: A Field Guide to Messages

Let me introduce a different version of me for this one. Call her the build-in-public founder. She is shipping a small app, she is doing it in the open, and she has learned the hard way that working entirely in private is a great way to finish something nobody wants. She wants the accountability of an audience and the early signal of people reacting before she has sunk a month into the wrong thing.

She has been using Messages exactly like the last three posts described: private scratchpad, timestamped log, notebook she reads backward. Now she wants some of it to be seen. And the beautiful part is she does not switch tools. She checks a box.

The one switch

Public is a checkbox on every single post. Not an account setting, not a mode you enter, not a separate "public" surface. Per post. She writes shipped the new onboarding flow tonight, cut it from 6 steps to 3, curious if it actually moves activation and, this time, she checks Public before hitting post.

That is the entire ceremony. The post that would have been visible to one person is now visible to everyone: her followers, people browsing her profile, the public feed. Same box, same keystrokes, one different checkbox. And the posts around it, the messy private ones, stay private. She is not flipping her whole history into the open. She is publishing this one thought.

Because the switch is per post, the mental model is clean. Default to private, opt into public deliberately, mix the two on the same timeline without maintaining two accounts. I think this is the right default for a tool that is a notebook first and a social feed second. The loud thing should be the choice, not the accident.

What "public" actually opens up

Once a post is public, three things become possible that a private note never allowed, and all three are free.

Replies. Anyone who can see the post can reply to it, and replies thread underneath. One useful, slightly opinionated rule lives here: a reply inherits the visibility of the post it answers. Reply to a public post and your reply is public. There is no way to sneak a private reply onto a public thread, which keeps a conversation from becoming half-visible and confusing. Threads read oldest-to-newest underneath the parent, the way a conversation actually flows.

A public post with a short thread of replies underneath it, oldest reply first

A public post grows a thread. Replies inherit the parent's visibility, so a public conversation stays fully public.

I Dig! The reaction is a single button. Someone taps "I Dig!" and the post's dig count ticks up by one, and you get a notification the first time it happens. It is one dig per person per post, so the count means what you think it means. It is deliberately one flavor of reaction, not a shelf of emoji. You dig it or you do not.

Pushes. This is the repost. If someone likes your update enough to put it in front of their own followers, they push it. A plain push is a straight reshare with no commentary. A "Push & Comment" is the quote-post version, where they add their own line on top of yours. Both are free, and both are public by nature: you can only push a public post, because pushing a private one would leak it, so the system simply does not allow it.

The accountability loop, closed

Here is why the founder actually cares, past the vanity of a dig count. The public switch turns her private log into a feedback instrument. She posts the onboarding change, three people reply that step two still confused them, one person pushes it to an audience that includes someone in her exact market, and she has learned something real before breakfast. That is the entire reason to build in public: compress the distance between "I made a change" and "here is what people think of it."

And she did it without leaving her notebook. The private posts from last week are still private, still hers, still woven into the same timeline. The public ones went out to the world. Followers, replies, digs, and pushes are all free, so the social layer costs her nothing but the decision to check a box.

There is one thing the public switch does not do, and it is the thing a lot of people actually want: it publishes to InterlinedList, not to the rest of the internet. Her post is public here. It is not on Bluesky, not on Mastodon, not on LinkedIn, not on X. Getting a single post to show up on all four of those at once is a different switch, a paid one, and it is where this series goes next.

Adron