A short post should not have to disappear into someone else’s feed to be worth sharing. I built Bonumark Stream because I wanted the speed of social posting without surrendering the post.
The Problem Was Ownership
I built Bonumark Stream because I wanted a place for short thoughts that belonged to me. Not a social media account. Not a rented feed. Not another profile sitting on someone else’s platform, controlled by rules I do not make and algorithms I do not trust. I wanted a simple place on my own site where quick thoughts, photos, links, project updates, and notes from the day could live under my control.
That sounds simple, but it came from a problem I had been feeling for a while. Social media is fast, and that speed is useful. A thought hits, you post it. A photo happens, you share it. A project changes, you give a quick update. Not every thought needs to become a polished article, and not every small moment needs to be forced into some big content strategy. Sometimes a post is just a post, and that is fine.
The problem is what happens when all of those small pieces of your life live somewhere you do not own. Social platforms train you to post quickly, but they also train you to build your public voice on rented ground. The platform controls the feed. It controls the reach. It controls the format. It decides what gets shown, what gets buried, what gets ignored, and what disappears into the noise. You can call it your content, but if the only place it lives is inside someone else’s system, then your control is limited.
I do not like dependency. That is true in recovery. It is true in fitness. It is true in publishing. It is true in software. It is true in life. I do not want my words, my work, or my public identity depending entirely on platforms that can change direction whenever they want. Social media can be useful, but it should not be the foundation.
That was the original problem behind Bonumark Stream.
I wanted the speed of social posting without surrendering the post.
It Started With a WordPress Theme
Bonumark Stream did not start as a standalone CMS. The first version of the idea was a WordPress theme called Microblog Stream. I built it for JimLunsford.net because I wanted that site to serve a different purpose than JimLunsford.com.
JimLunsford.com is my main home on the internet. It holds finished writing, project pages, bigger ideas, articles, and the more permanent parts of my work. JimLunsford.net is different. That site is my stream. It is where the smaller pieces go: short thoughts, project notes, training notes, photos, cats, quick updates, and whatever else fits the rhythm of a living site instead of a formal article archive.
I wanted JimLunsford.net to feel like a personal timeline, not a traditional blog. That meant the theme needed to behave differently. A normal blog structure expects headlines, excerpts, archives, categories, and the usual post format. A stream needs to move faster than that. It needs to let a thought stand on its own without making it dress up like an article.
So Microblog Stream was built around that idea. It had a dark, single-column layout. It used post cards. It made short posts feel natural. It allowed replies. It supported likes and media. It gave the site the feeling of a live personal stream without trying to become a full social network.
That theme worked. It gave me the first real version of the experience I wanted.
It also showed me why the idea was bigger than a theme.
A Micro Post Should Not Need a Headline
One of the earliest problems I wanted solved was the title problem. WordPress is built around posts with titles, but microblogging is not. If I post a quick thought, I should not have to stop and create a headline for it. That extra step may sound small, but it changes the way posting feels. It turns a quick note into a mini article before it even leaves your head.
That was not what I wanted. I wanted to write the thought and post it. The post itself was the point. If I added a photo of Milo being ridiculous, I did not need to title it like a newspaper article. If I posted a quick project update, I did not need to pretend it was a finished essay. The format needed to respect the way short-form publishing actually works.
So the theme was built around titleless public posts. The backend could still generate a date and time title so the WordPress admin area stayed organized, but the public side did not need to show a title. That small decision mattered because it removed friction and protected the feel of the stream.
A micro post is not always a headline with body text. Sometimes the post is the whole thing.
That idea carried forward into Bonumark Stream.
Short Does Not Mean Disposable
The next issue was replies. I did not want the stream to be a dead wall of updates. I wanted people to be able to click a post, open it, and leave a reply. That meant each post needed its own page, even if the post itself was short.
That matters more than people think. Social media has trained us to treat short posts like disposable content. They live for a few minutes, maybe a few hours, then they get pushed down by the next wave of noise. A post may get reactions, comments, likes, or nothing at all, but the platform’s rhythm is always moving away from it.
I wanted something different. If I posted a short thought, I still wanted it to have a home. I wanted it to have a URL. I wanted someone to be able to open it directly, read it, reply to it, and find it later. That does not mean every short post is important in some dramatic way. It means I do not believe short automatically means worthless.
The small stuff matters too. The quick note during a project. The thought after a run. The picture that captures a normal day. The line that may become a bigger article later. The small update that shows the work was moving even before it became polished enough for the main site.
That is part of what I wanted the stream to hold.
Not just finished work.
The pulse behind the finished work.
The WordPress.com Moment
In April 2026, WordPress.com announced a short-form blogging direction that looked a lot like the kind of thing I had already been building with Microblog Stream. Quick posts, replies, likes, a timeline-style experience, and the idea of using real posts for short-form publishing.
I am not saying they copied my code. Their code was not released, so there was no way for me to compare anything real. I could not compare PHP, CSS, JavaScript, templates, hooks, structure, or implementation. The only thing I could compare was the public idea.
And the public idea overlapped hard.
I am not interested in making a claim I cannot prove. What mattered to me was simpler: the overlap confirmed that the gap was real. People want the speed of social posting without losing ownership of the post. That was the problem I had already been trying to solve for myself.
Seeing WordPress.com move in a similar direction made the bigger question harder to ignore. If the idea was strong enough for them to move toward it, why was I only building a theme that depended on WordPress?
That was the turn.
The Theme Was Not Enough Anymore
Microblog Stream worked, but it was still WordPress underneath. I had built the experience I wanted on top of a system that was not originally built for that exact purpose. WordPress is powerful, and I still respect what it can do. I have used it for years. I have built a lot with it. I am not interested in pretending WordPress is bad just because I started building my own software.
But this project was starting to feel like it wanted to be its own thing.
The more I worked on the theme, the clearer the limitation became. I was bending WordPress into a microblog. That could work, but it meant carrying WordPress assumptions with it. Traditional posts. Theme limitations. Plugin ecosystem complexity. Repository approval friction. Platform decisions outside my control. Hosted WordPress.com limitations and paywalls. A system that could do almost anything, but still had to be shaped into what I actually wanted.
At some point, the better question was not, “Can WordPress be made to feel like a microblog?”
The better question was, “What if the software was built for this from the beginning?”
That is where Bonumark Stream started becoming real.
What Bonumark Stream Is
Bonumark Stream is a self-hosted microblog CMS for publishing short-form posts on a site you control.
That is the mission, and it needs to stay that simple.
It is built for owned short-form publishing. A public stream. A simple posting workflow. A clean timeline. Optional comments. Optional likes. Media support. Import and export paths. Portability. Shared-hosting compatibility. A system someone can install, control, back up, move, and keep.
Bonumark Stream is not trying to clone social media or rebuild WordPress in a different skin. The goal is not to chase algorithms, recreate engagement loops, build discovery feeds, or turn a personal site into another platform treadmill.
The point is speed without surrender.
The point is giving short posts a real home.
That is enough of a mission.
A project gets bloated when it forgets what problem it was born to solve. I do not want that for Bonumark Stream. Every feature has to answer the same question: does this make owned short-form publishing better?
If the answer is no, it probably does not belong.
The Stream Is the Pulse
The best way I know to explain the difference between my sites is this: JimLunsford.com is the home base, and JimLunsford.net is the pulse.
The main site holds the more finished work. Articles, pages, projects, structure, and the work that needs a stronger permanent frame. The stream moves differently. It can be lighter. It can be quicker. It can hold things before they become polished, and it can hold things that should never become polished at all.
Not every thought deserves a full article. Not every update needs a strategy behind it. Not every picture needs to become a lesson. Sometimes life is just life, and I want somewhere to put that without handing it to a social platform first.
That is what the stream is for.
It is not the main site. It is not supposed to be. It is the live edge of the work and the life around it. It lets the smaller things exist without forcing them into the weight of a finished essay.
That matters to me because I spent too much time trying to turn every piece of my life into content. I do not want that anymore. I still write when something is worth saying. I still build. I still share. But I do not want every thought to become a performance. The stream gives me a place for what is real, immediate, useful, funny, rough, or small.
A site can have a pulse without becoming a content treadmill.
Ownership Is the Real Thread
The more I build Bonumark Stream, the more I see that it fits the same pattern as the rest of my life.
Recovery taught me ownership. Fitness taught me proof. Writing taught me clarity. Software is teaching me structure. Bonumark Stream sits in the middle of all of that because it solves a real problem through the same lens I use everywhere else.
I do not like dependency. I do not like rented identity. I do not like systems that make people feel like they have control when they really just have permission. That shows up in my recovery philosophy, and it shows up here too.
That does not mean everyone needs Bonumark Stream. It does not mean every person needs to self-host everything. It does not mean social media has no value. It means I know what I wanted, and I got tired of waiting for someone else to build it in a way that matched my standards.
So I built it.
That is usually how my best work starts.
Find the problem. Live the solution. Build the proof. Share the path.
Bonumark Stream is part of that.
Built for Real Use
I am not building Bonumark Stream as a fake demo or a weekend toy. I am building it because I intend to use it. That matters because real use exposes what planning misses.
A feature can sound great until you have to click through it every day. A setting can look powerful until it clutters the experience. A role system can seem flexible until it bloats the product. A theme can look clever until it starts doing work the core should handle. Real use strips away fantasy.
That is why the project has gone through clean-break decisions. Some things were removed. Some things were simplified. Some things were reset. That is not failure. That is the product getting clearer.
A tool should become more itself over time, not less.
Bonumark Stream has had to move away from some ideas that made it heavier than it needed to be. Multiuser publishing sounded useful, but it pulled the project away from the core. Theme logic needed to be separated from application logic. The stream home needed to be clear. The public release theme needed to be clean. The account model needed to match the actual direction.
That is what building does. It forces decisions.
You can either keep every idea because you are afraid to cut anything, or you can protect the product by removing what does not belong.
I would rather cut.
Why I Built It
Bonumark Stream exists because I wanted ownership over the small stuff too.
Not just books. Not just longform articles. Not just polished pages. The quick thoughts matter. The daily notes matter. The project updates matter. The photos matter. The small observations matter. The stream of a life matters.
Social platforms taught people that short posts are disposable. Bonumark Stream rejects that. A short post can still be yours. A quick note can still live on your domain. A photo can still belong to your archive. A thought does not have to be rented from a platform to be worth publishing.
That was the problem from the beginning.
I wanted a place to post without handing the post away.
Microblog Stream proved the idea inside WordPress. Bonumark Stream became the answer outside of WordPress.
An owned stream.
That is why I built it.
Bonumark Stream started as a tool for my own site, but the principle is bigger than my site. Own the small stuff too. Own the notes, the updates, the photos, the unfinished thoughts, the rough edges, and the proof that life was happening before it became polished enough for an article.
That is what an owned stream is for.
Bonumark Stream is still in active development. The project is public, and the repository is where the work continues: