When I started building websites in the late ’90s, the line between writing and coding didn’t really exist. A person probably learned HTML because she had something to say and needed a place to put it. The internet was free and anonymous and it felt audacious to put your stuff online, like flinging a message in a bottle out to sea. The code was a container for the ideas that rendered them onscreen, and every post and page you published was both a piece of your thinking and a brick in something larger.
People forget that the early web was a writing community. Writers, or bloggers, built their own sites, maintained their own archives, linked to each other deliberately. A blogroll was both a reading list and a show of solidarity, a trackback was a way of saying, “I see you, I’m thinking with you.” The technical architecture - RSS feeds, permalinks, comment threads - existed to organize the writing and the writers’ thoughts, and to push their ideas forward on the open web.
This worked for a time. Communities of writers, most of them without institutional backing or media credentials, built new bodies of knowledge together through interacting as readers and writers, communicating across a foundation of code. The work didn’t stay online. It spilled into conference halls and state houses and newsrooms and policy discussions. As the body of communication built, it created something that accumulated over time. These people influenced mainstream journalism, shaped public conversations, launched careers and movements. In many ways, the national political conditions we face today are a reaction to that movement, and how it allowed regular people to influence the world through the democratization of mass communication.
Midway through the aughts, the brick and mortar publishers and venture capitalists started looking across the landscape, at all the writers creating fantastic content, largely for free, and sucked them into their content and editorial teams. Google Reader lost institutional and financial support as writers moved off the open web and onto publishing platforms, often backed by VC money, that measured the quality of your work by engagement. The addition of algorithmic feeds further broke down this structure – the algorithm doesn’t measure whether your work contributed to shared understanding, but whether it generated a click, a share. The code changed, and the writing changed with it.
The writers changed with it, too. The blogger became the influencer. Bloggers operated in a gift economy of ideas: you wrote to think, to argue, to contribute, and your standing in the wider community came from the quality of your work and contributions over time. Was it a meritocracy? No, but the conditions made it possible for a regular person to talk with experts as peers, which upended traditional power structures around authority and expertise (in both directions, good and bad). Meanwhile, influencers operate in a heavily capitalized attention economy where engagement converts to dollars. The audience is a market to press for money.
The gendered dimension of this shift matters as well. The early blogosphere was full of women writing sharp, rigorous work about politics, culture, parenthood, identity, and technology — work that was explicitly feminist and anti-racist and genuinely moved public conversations. This was the community I helped build (Feministe.us was my project, a community platform of writers and commenters whose coverage and discussion broadly fell under, but was certainly not limited to, the topic of feminism). When the monetized platforms absorbed that energy, the commercial model recast women’s online authority almost entirely in terms of consumer influence. What could we sell? And to whom? The framing around our work went from “this person has important ideas” to “this person can sell things to a niche market.” Meanwhile, men who’d built audiences through tech or political blogging were more likely to be absorbed into mainstream media as columnists and analysts, roles that kept their intellectual authority intact. The influencer label, with all its connotations of superficiality, landed disproportionately on women, and it stuck.
There’s a class piece here, too. The platform model offered something the early blogosphere mostly didn’t — a way to get paid. For women who’d been doing enormous amounts of unpaid intellectual labor building online communities, the question of monetization wasn’t shallow. The implications of information centralization and monetization were as present then as they are now with LLMs and AI. Some people figured out the social platforms and worked their way into viable digital careers. Platforms offered a lot of perks, but all of the perks had a backstop. Corporate interests introduced the problems of advertising, audience and sponsorship, which meant reorienting your individual practice around maximizing your commercial value over and above your intellectual contribution and community management skills. It often meant giving away some or all of your IP rights.
For most people, new system didn’t offer a viable way to get from “respected independent writer” to “respected, protected and compensated writer.” Many of us found ourselves in positions too precarious to take the leap into freelancing and social media, and some, like me, got regular jobs doing regular stuff. Some married money. And in the meantime, some folks figured out how to get into real journalism, which looks much different in 2026.
Wondering whether I want to switch to something more robust like Wordpress if I keep doing this thing, but at the same time I have enjoyed not working within and around the world of WP, which has dominated my CMS experience since the aughts.
I too have been challenged by defining “federation” to non-technical audiences, so it was fun and instructive to see others give it a go.
Blogging from the Ruins is an essay getting a ton of attention in the fediverse this week, making a strong case for intentionally building non-algorithmic intellectual communities on the open web.
Winer’s original script is pretty slick, and includes a list of all my feeds with titles, URLs, and categories; click-to-expand functionality to see the 5 most recent posts from each feed; clickable post titles that open articles in new tabs; sort options (by title or by update); and automatic updates when I change my FeedLand subscriptions.
The official documentation method didn’t initially work because Hugo (the blogging software behind micro.blog) was wrapping client-side templates around the script. The toolkit requires server-side dependencies that don’t exist on static sites like micro.blog, and we hit a cascade of missing JavaScript dependencies (jsonStringify, servercall, etc.). Each fix revealed another dependency, leading to some “sunk cost” frustrations for me. I kept trying because I wanted to see if Claude could pull it together. Through trial and error, I got to a point where the OPML file was rendered correctly without server dependencies or complex external libraries.
Time invested: ~3 hours (including wrong turns)
Time it should take: 10 minutes
AI extended my code reach beyond my practical skillset by quite a lot. I now have a dynamic and dedicated place to read and share news feeds as I wish. Though even when generative AI works and works well, I have significant concerns about the intellectual property implications of AI, and this project brought those tensions into sharp focus. The AI could only help me because it was trained on documentation and intellectual work from the open source community, contributions made freely in the spirit of knowledge sharing, not to train commercial AI systems. I tapped into their expertise by paying Anthropic $15 a month. While I’m grateful for the accessibility this provides to non-developers like me, I recognize there’s an unresolved ethical question about whether this use respects the intent and labor of the original creators. The feat is incredible; the foundation it’s built on deserves careful consideration.
After the exercise was complete, I asked Claude how I could have improved my prompting to make this process easier, and in short, Claude said I could have been a web developer. But since I’m not, here’s what it recommended:
✅ When the process isn’t working, question the process mid-stream. Most people either give up or keep following bad advice deeper into rabbit holes. Stop and question the LLM’s process and ask for alternatives to force a reset.
✅ Push for usability. Keep bringing the conversation back to what you actually need the end result to do, not what’s technically impressive or “correct.” In my case, this meant repeatedly asking “can I click through to the articles?” rather than getting lost in discussions about CORS proxies or JavaScript syntax. Focus on outcomes, not implementation details.
✅ Ask for complete solutions. Instead of trying to mentally patch together incremental changes across multiple responses, ask the LLM to provide fresh, complete code each time. This prevents copy-paste errors and ensures you’re always working with a coherent, tested solution. There’s more than one way to crack an egg, but you want the whole egg regardless.
After all that, I got it to work but can’t figure out how to make it show up in my header menu, with or without Claude. TBD.
Just speaking this into the universe, but it would be exceedingly cool if someone pulled together a micro.blog plugin for Feedland blogrolls and page feeds.
You want to have control of your own destiny. We call it digital sovereignty. In the old days, the early days of the web, anybody used to be able to make a website. So that feeling of sovereignty as an individual being enabled and being a peer with all the other people on the web, that is what we are still fighting for, and in fact, we need to rebuild.
In recent history I stopped posting on most social media and moved to the fediverse. I still browse the social platforms to keep up with trends and friends, but I only post on my private IG and here.
What I share here is separate from but related to my professional life — I’m thinking out loud and making room for rough, unfinished ideas. I write mainly for myself, but if others find it useful, that’s great. The practice of reading and reflecting makes your thinking stick, and I am from a certain time and place, so this is how I approach learning and communicating about what I’m learning. It’s a habit.
While this is my preferred approach, I acknowledge that sharing unfinished ideas publicly is risky and you have to accept accountability for the messiness that comes with that. But I also know that working through your vulnerability through the act of writing lets you tap into your most creative, innovative self and test your ideas against an evolving sense of what’s good. The potential for an audience, however real or implied, keeps you more honest and less self-indulgent. Despite the trade offs, I think it’s worthwhile.
Been playing with micro.blog for a bit now and very much recommend the experience. The interface is friendly and the team behind the app is ultra responsive. My fav features are Bookshelves - and the ability to push new posts to Bluesky and Mastodon.
The Bookshelves feature of Micro.blog is easily my favorite of this platform. It sits right at the intersection of medium and function: as a reader I want to keep track of things, but I don’t need so much infrastructure around it. Just some checkmarks and a place to dash off my immediate thoughts.
I’ve been keeping my virtual bookshelf up to date while pushing myself to take on a bunch of literary fiction, but I’m tired, reader. So instead of laboring on with a pile of good books I didn’t really want to read, I lined up a bunch of rock n’ roll memoirs for the summer while I manifest camping, hammocks and time otherwise spent by a lake.
My posts from micro.blog are pushing to Mastodon but not Bluesky. Why?
Two new media publishers are looking to build out their presence in the Fediverse: digiday.com/media/why…
I don’t need a WYSIWYG editor on micro.blog, but some buttons for linking and styling on new posts would be a no-brainer addition to this app.
I am enjoying the Twitter/Tumblr feel of micro.blog and feel like I could settle in here. But it would be cooler if there was a quick reference for markdown near the input field to better format our posts.
My biggest complaint about the slow, excruciating car crash of Twitter/X is that all of my journalist friends moved to Bsky and all my geek friends moved to Mastodon.
“…it will — by design — never be a place for you to monetize your brand, troll, shitpost, or become an influencer. But hey, there are plenty of other platforms better suited for that kind of thing. Micro.blog is better suited for the more human and humane paths I have identified here.”
I’m a dummy, but I can’t log into mastodon.social since connecting with micro.blog. What am I doing wrong? Or do I need to log in elsewhere?
Microblogging on the open web - and why care? book.micro.blog
While noodling around on other things, I ran across the omg.lol domain (https://home.omg.lol/), clicked around, found Neatnik (https://neatnik.net/), and this fun PHP project where he created a year-long calendar that automatically resizes to fit a single page.