My wife and I are fairly boring people. I'm a sysadmin and fill-in sales rep at work, she works for the local government. Our hobbies are run of the mill; she reads and reviews the books she's read, I tinker with embedded computing projects and niche operating systems, and in the past have written (but not published) short fiction.
She maintains a review blog she started a few years ago when she wanted to connect better with the authors and fellow reviewers she was in contact with on Facebook and Twitter. It has taken off as far as such sites can, and while it takes up a ton of her free time after work and on weekends, we balance with time together as well. She makes absolutely no money from it (she hates the idea of ads on her site) and honestly I agree with her; she would feel like it was a second job if she tried to monetize it. Still, she does it because she enjoys the back-and-forth she gets with authors, and she often gets to meet some of her personal heroes in real life at conventions and release parties. I'd say having a personal website has helped her feel fulfilled outside of a boring day job and I'm all for it, even though it means less time spent doing things together. It makes that time together even more precious and fulfilling.
Oh, and as for me...I did start a writing blog several years ago but writing fell to the wayside and I haven't posted anything in a couple of years. I've thought about ditching that altogether and blogging about embedded projects instead, but I have more fun doing the hobby itself than I would writing about it. I'm not a very social person and I don't have any social media accounts (unless this site and my sporadic activity on OSNews counts), and overall I feel I'm a pretty boring guy outside of niche circles. I'm also not job hunting nor am I in a hiring role at work, so I don't feel the need for my info to be out there.
This is a real problem.
I tend to always have at least one hobby project going on that I know would be of interest to a wide group of people (such as the smartphone I'm currently building).
However, I don't like to document the projects as I go along, because it makes the project more difficult and time-consuming to accomplish, and I start to feel pressure to make sure that I'm providing regular updates -- which turns the hobby into a sort of job.
Instead, I prefer to document dump all my notes and sketches, and put the code and schematics up, after I've completed the project entirely. This means that I don't have a great deal of "work in progress" photos and the like, and that my post is not useful for people who want to see the process of development itself, but it's a compromise that works for me.