Indie Web on F L O T I S S E R I E

Feminist blog cohorts: a (semi-) authoritative remapping using AI

Sat, 26 Sep 2026 14:33:12 -0500

I’ve spent the last few months annoyed with the incomplete retrospectives around writers and writing online and how we all got here. At work, I use a portfolio perspective to understand working groups, and used a couple of AI approaches to build out a highly contextual, and likely contested, interactive map charting some of the major players and influences around the feminist blog years, the major platforms, their cultural impacts and major publications. These are case studies and cohorts based on my personal angles mixed with authoritative resources, including a highly annotated bibliography.

Does this feel slimy? I concede it may. But it demonstrates the value of personal writing and thoughtful design in digital spaces despite its many gaps and flaws.

Enjoy and tinker. Feedback is welcome. I’ll have some notes on my approach and why many of these findings remain heavily qualified in the coming weeks.

Old playbook, new eyes

Mon, 21 Sep 2026 08:35:59 -0500

🎵: Veteran of the Psychic Wars - Blue Oyster Cult

When tech enthusiasts discuss federation today, they usually mean open protocols like ActivityPub or Mastodon. But in the 2000s, the feminist blogosphere was one of the earliest, most powerful examples of practical Web 2.0 federation, a decentralized, cross-site architectural network where open web standards powered a global ideas lab.

Instead of sitting inside a single corporate platform (like today’s X, Meta, or Substack), early blogs like Feministe, Reappropriate and Jezebel functioned as individual nodes in a federated ecosystem. Open protocols linked them, letting theory, critique and discussion travel seamlessly across independent servers, seeding some of the political conditions we face today.

Here is how the federated architecture of the 2000s web directly built the “ideas lab” for fourth-wave feminism:

1. Federated communication engine: CMS and protocol Before quote-tweeting or tagging existed, the open web used Trackbacks and Pingbacks. If a post on Feministe analyzed an article about reproductive rights, a writer on Racialicious or Shakesville could respond on their own site. The underlying blogging software (Movable Type, WordPress) would automatically send an XML RPC “ping” back to Feministe.

Socially, this created architecture for ideas: a ping automatically listed the response essay in Feministe’s comment section or sidebar. Readers didn’t just consume one blogger’s singular and authoritative opinion; they could immediately follow the thread across five different independently hosted platforms. This created an inter-site conversation tree, allowing complex ideas to be cross-examined, refined, or challenged without any single person controlling the narrative.

2. Blogroll as federated curation and mutual discovery Before algorithmic feeds dictated what readers saw, blogs relied on the Blogroll, a curated list of links in the site’s sidebar. Blogrolls formed a human-curated, decentralized routing layer. When a high-traffic node like Feministe added a smaller, independent blog (such as a disability rights blog like FWD or a smaller blog like Crunk Feminist Collective) to its blogroll, it directed server traffic directly to that independent domain.

Socially: This was a non-algorithmic way to expand the collective’s political consciousness. It allowed marginalized perspectives to build their own audiences and force mainstream feminist sites to engage with race, class, disability and queer theory. The blogroll mapped an intellectual community in real time – with strong caveats.

3. Open syndication protocols The Architecture: Feeds ran on RSS (Really Simple Syndication), an open XML standard. Readers used independent RSS aggregators (like Google Reader or Bloglines) to subscribe directly to a site’s feed.

Socially: RSS meant no algorithm stood between the writer and the reader—no engagement bait, no rage-farming optimization, and no platform throttling links. Writers could publish 5,000-word, dense theoretical essays knowing their subscribers would receive the complete text in chronological order as designed. This structural stability gave writers the freedom to experiment with complex, “thick” personal narratives and political theory.

4. Real-time stress testing and spillover moderation Because the blogosphere was a network of independent domains, each site maintained its own “house rules” and moderation policies. If a topic proved too controversial or toxic for one comment section, the conversation naturally federated outward. A reader who felt silenced or misunderstood in one blog’s comments could launch their own blog, write their response, and ping back into the original discussion.

Socially, this prevented any single author from monopolizing the narrative. It created a system of checks and balances where academic concepts (like intersectionality, rape culture, or microaggressions) were stress-tested across dozens of distinct, interconnected communities simultaneously.

Thinking about this architecture today The feminist blogosphere proved that decentralized web protocols can generate deep, movement-building intellectual work. When platforms like Facebook, Twitter, and corporate media conglomerates centralized the internet in the 2010s, they broke those open connections. Conversations were locked behind platform walls, trackbacks were abandoned and RSS was marginalized, breaking, fencing and otherwise moderating independent community connections.

Rebuilding a modern “ideas lab” with modern federated protocols (like Webmentions, ActivityPub, RSS, and static site architecture) is simply picking up the technical blueprint OG feminist bloggers used to transform digital culture two decades ago.

Mon, 07 Sep 2026 14:24:27 -0500

Return to markdown?

Mon, 24 Aug 2026 09:41:02 -0500

Micro.bloggers: I’m interested in turning the link log into a micro.blog plug-in, but I don’t have the skill or the will to make it happen. Where should I begin?

Wed, 19 Aug 2026 09:52:52 -0500

Question for micro.bloggers: Can you separate keywords by comma in this category filter field, or is it one word per filter?

Some thoughts on linklogs and link libraries

Tue, 18 Aug 2026 19:03:19 -0500

A linklog is a dated list of outbound links, maybe a tag, and a note about why it’s worthwhile. But that little note does two things at once, and together they make for a better web.

First, it’s a way of organizing the web. The web doesn’t sort itself, so finding good information depends on someone curating and tracking interesting content, preferably on the open, free internet. It acts as a customizable bookmark library: newest at the top, tags to group items, and a line explaining why the link was worthwhile. This is similar to what del.icio.us did, where people grouped and tagged links, creating a rough filing system.

Second, it’s a social act. An outbound link points to someone else’s work, so a linklog is essentially a renewable engine for sending traffic to other people and places. It stays renewable because the content is easy to sort and remix: a URL’s relevance no longer depends on where an algorithm or activity feed happens to place it, so older links can keep resurfacing instead of scrolling out of reach. That’s the precise opposite of what big platforms design for audiences; platforms such as Twitter, Instagram and Facebook quietly bury posts with outbound links to keep your attention (and dollars) on their site and with their advertising customers, losing relevance after one interaction. A linklog explores the opposing dynamic: it willingly hands your audience and attention away while crediting your forebears, comrades, mentors and co-conspirators. It turns the rough digital filing system into a “folksonomy,” if you will.

Compare these dynamics to an algorithmic feed on a platform. An algo also sorts the flood of content, but computer magic does the sorting, and someone else monetizes your attention and relationships and hoards your data. “Engagement” for these companies is primarily a measure of how long you stay on their platform with their content. The goal is to keep you scrolling and the ad revenue rolling. But over here on the indie internet, our goal is to build human communities online and connect people to quality information, tools, ideas and processes.

Back in the day, we had blogrolls, and blogrolls came with a lot of politics around representation and belonging, and some of those choices had real-world impacts. Who you listed in your sidebar was a public statement about your community and your allegiances; however, though smaller blogs linked to bigger ones, the big blogs rarely returned the attention. That contentious dynamic faded as social platforms became the main sites for online interaction, and the follow list, or the Twitter list, took over the blogroll’s old job of reinforcing networked hierarchies of writers and audiences. Because a blogroll is a static list of people, it hardens into a status game and is kind of stale the moment someone stops babysitting it; meanwhile, a linklog points at individual pieces of writing one at a time, so it stays current and rewards the work rather than the social and professional standing of the writer.

In this sense, a linklog is an easy way to be an opinionated curator and a decent neighbor at once, by hosting and sharing with thoughtfulness and deliberation. Out here, my data is also likely being scraped, but I have far more control over what data is findable, shared, and shareable, and over what is investigable and degradable over time.

Tue, 18 Aug 2026 12:02:15 -0500

Posting a lot while I get through the inbox today. Among other stories, WordPress is offering free hosting to students, marketing WP as a way to change how people relate to their own writing. Does a self-hosted public blog make students think differently about audience than a school LMS post does?

Computah: Make it a link

Thu, 13 Aug 2026 15:40:59 -0500

I spent a little time with the blog last night and pulled together two new site features using Claude Cowork. The last time I experimented significantly with Claude like this was to use Claude chat to build the link log from scratch, walking it through my thinking in plain language, then copying and pasting its suggestions into the backend of the site and hitting publish. This time I used Cowork, the tool that runs in the browser, and it clicked through the screens itself, fully taking on the execution of tasks. I have some coding skills, but not the kind these changes required. If I were taking this on, I would need YouTube, Hugo for Dummies, and my own personal IT guy, and still probably couldn’t pull it together.

Last night I asked a few things of Claude: I asked Claude Cowork to get into the backend of the micro.blog site and change my theme to link each line in the linklog back to my original post. The date field in the right column now links back to the original post for each link logged. No problem, easy request with easy execution. I made the request, confirmed the plan, and went about my business while Claude made the edits.

I also asked it to analyze my post content and suggest category tags for groups of content, then to label that content correctly in the backend. Claude reviewed about 500 posts and suggested I add a few new categories to my blog: AI in Practice, Books & Reading and Writing & Language. Then I set up some auto-filters to run at publish time to automatically categorize posts based on keywords moving forward.

Finally, I manually added the archive page, which lets you sort posts by category or year. This means I now have a functional archive here. Enjoy my anodyne thoughts, dear reader.

Adjacent to my day job, I’ve been toying with Claude Pro now for about a year; in my experience, it has improved significantly within the last six months. It’s not perfect: my requested edits were completed, but it also changed the CSS on the linklog so some of the text is too light to read, which I didn’t ask for and don’t want. But it has arguably extended my ability to execute on work that requires skills I don’t otherwise have (such as design and coding). What I do bring to the table is an expansive practical background in publishing and production, and all the language to describe it.

Tue, 04 Aug 2026 17:34:45 -0500

Winer on the purpose of web standards: “I find that most standards that come out of the standards bodies aren’t developed by implementors or with them in mind. They avoid trying to solve any specific problem, rather focusing on the elegance and flexibility of the format. This makes interop much less likely. I saw the differences several times as the web standards were growing up.”

Fri, 10 Jul 2026 15:00:55 -0500

rss.chat is a new, free social network service that uses RSS to create a federated social feed that looks and feels a lot like OG Twitter. See also: the launch of HyperTexting, another RSS-based app that centralizes the open web in a way that feels a little like Google Reader (complimentary).

Mon, 15 Jun 2026 17:10:18 -0500

A deeply nerdy (complimentary) look at the history of Markdown. And more on Markdown, its function and legacy from Anil Dash.

Thu, 14 May 2026 10:36:43 -0500

More on personal websites as digital gardens.

Wed, 13 May 2026 16:13:10 -0500

Garbage Day on whether Bluesky was a net negative for left politics. I’d argue the most important thing Bluesky did/does is technical, by producing the AT protocol that underlies it, thereby building out the federated web. Distribution channels come and go, so consider posting at your own domain.

Mon, 11 May 2026 16:46:00 -0500

Added a Wayback link preserver plugin to the site. This lightweight code detects broken external links on the blog and shows clickable Wayback Machine fallbacks so readers can still access the content. Handy when we’re working on the indie web where the web is fragile.

Wed, 29 Apr 2026 12:38:06 -0500

It looks like Wordpress has produced a short-form blogging app that duplicates the model we are trying over here on the even-more-indie web. I might give it a spin.

Tue, 07 Apr 2026 17:20:16 -0500

Pulling from some old communication theory while I am thinking about blogging and the indie web, and especially thinking about Dallas Smythe, who argues that mass media doesn’t produce content but audiences, packaged and sold to advertisers. On social media, users aren’t just the audience being sold, they’re also a labor force co-producing the content that attracts more audience.

Looking back at the feminist blogging era with the benefit of my current experience, I’d argue that what made Feministe different from our peer blogs was the commitment to convening the audience and sharing the platform without packaging it up for or selling to advertisers. That was largely my boundary – with as much market space as it commanded for the time, it was never monetized at scale, though individual contributors were free to use it as they wanted to build their audiences. We eventually committed to a small advertising carousel to cover hosting costs.

I recall someone balking at me for refusing to broadly monetize when I spoke at Blogher in 2005, but it was a hard line, for better or worse.

Sat, 04 Apr 2026 17:11:43 -0500

I heard a good talk on “slow brain” activities this week and have been thinking about that alongside indie web practices. I’m not alone: how to leave your feed and go exploring again.

Sat, 04 Apr 2026 15:59:04 -0500

A collection of articles that answer the question, “Why have a personal website?”

Sat, 04 Apr 2026 10:36:44 -0500

Testing a new feature I created using a mix of open source code and Claude, hoping I didn’t break my own site. I pulled together a dynamic link library using a Hugo partial and some shortcode that automatically catalogs all of my outbound links into sortable lists.

Sat, 04 Apr 2026 09:58:05 -0500

Just ran across Paul Robert Lloyd’s talk on using tools and approaches from the indie web to build the Internet we want. Talking points and slides at the link.

Fri, 03 Apr 2026 12:59:17 -0500

Playing with a link archive that produces a sortable list of each of my outbound links. An okay start.

Sun, 15 Mar 2026 13:11:33 -0500

I misused PESOS below, c’est la vie, I’m doing a POSSE model. Here’s someone smarter than me on POSSE v PESOS.

Sun, 15 Mar 2026 12:47:56 -0500

Turned on a couple of micro.blog site features: if you’re reading this feed on a social site (Mastodon, Bsky, Threads), I’m posting from micro.blog and syndicating out from there. Replies from federated social sites (Bsky, Mastodon) are now syndicated on my site as comments under my blog posts.

Thu, 12 Mar 2026 23:39:49 -0500

Pulling everything she’s ever posted back to her own website: Lisa Charlotte Muth flips POSSE to PESOS, “Publish Elsewhere, Syndicate (to your) Own Site.”

Tue, 10 Mar 2026 14:43:27 -0500

Excited about Inkwell, a contemporary treatment of the classic RSS reader.

Sun, 08 Mar 2026 16:28:04 -0500

Telling the gods: I would love a micro.blog plugin that provides an easy way to bulk-manage post categories. If there is one, lmk.

Sat, 07 Mar 2026 22:51:10 -0500

Winer on Doctorow on RSS.

Fri, 06 Mar 2026 00:07:38 -0500

Some content notes: while I haven’t quite figured out how much I want to broadcast this space, I have put a couple of feedback mechanisms into place, including an email loop as well as turning on comments for those logged into micro.blog, Bluesky and Mastodon. If you’re reading along, say hello.

Mon, 02 Mar 2026 14:48:10 -0500

Reading about a new “slow” RSS app called Current.

Wed, 25 Feb 2026 12:46:47 -0500

I’ve been spending more time in tech spaces online and getting good information from folks like @manton, creator of Micro.blog. Like this reflection on how to think about AI now that vibe coding works. Something I’m thinking about: there’s an emerging tension between those who see value in being able to immediately prototype an idea and the people downstream who have to manage the outputs/code over time. The ability to proof every idea sounds like a superpower until you’re the one driving and maintaining the results.

Wed, 18 Feb 2026 10:42:02 -0500

“Because RSS is an open protocol, and because there are so many different possible ways to follow and read the news, RSS readers ought to be a UI playground in the way Twitter clients once were, where innovation and experimentation are normal and celebrated.”

Fri, 13 Feb 2026 13:38:00 -0500

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.

Great storytelling helps people understand themselves and their world. We let some of that depth go on the Internet with the onslaught of digital marketing and all of its implications, and today the internet feels less useful and less trustworthy than it once did.

It feels like there’s something to take forward from the experience.

Fri, 23 Jan 2026 13:44:58 -0500

Connected Places uses ICE as a case study to explore trust, safety, and community dynamics on decentralized social networks, examining how federation changes community moderation expectations we’ve developed from centralized platforms.

Sun, 18 Jan 2026 15:25:45 -0500

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.

Sat, 10 Jan 2026 15:51:33 -0500

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.

Fri, 02 Jan 2026 16:21:17 -0500

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.

Wed, 10 Dec 2025 08:50:42 -0500

Our friend, the RSS feed.

A meta lesson about AI assistance

Sun, 07 Dec 2025 17:01:00 -0500

I just completed my first attempt at coding using AI, in this case having Claude assist me with putting together a simple client-side OPML parser using Dave Winer’s Feedland service.

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.

You can check it out here: Feeds

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.

Tue, 02 Dec 2025 16:40:18 -0500

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.

Mon, 01 Dec 2025 13:40:06 -0500

An interesting update by Dave Winer on how blog comments might work in and around federation.

Mon, 10 Nov 2025 21:44:29 -0500

Why Tim Berners-Lee still believes in the web | The Verge

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.

What is this site and why am I doing it?

Sun, 09 Nov 2025 14:12:00 -0500

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.

As I add to this page, I’ll be thinking out loud about digital rhetoric and communication alongside emerging technology, and linking back to foundational ideas I see reflected online today. Occasionally I’ll say something longer.

Ephemera

Wed, 25 Sep 2024 20:22:08 -0500

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.

In other news, I got a new bike.

Mon, 03 Jun 2024 14:04:26 -0500

From the Garbage Day newsletter, my fav newsletter on internet trends and marketing, this blog post on looking for federated blog alternatives to Wordpress which links out to this handy dashboard measuring total users on federated platforms.

⚡ Bookshelves

Fri, 31 May 2024 14:17:37 -0500

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.

Wed, 29 May 2024 14:12:39 -0500

My posts from micro.blog are pushing to Mastodon but not Bluesky. Why?

Wed, 29 May 2024 14:10:36 -0500

Two new media publishers are looking to build out their presence in the Fediverse: digiday.com/media/why…

Wed, 14 Feb 2024 13:25:38 -0500

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.

Wed, 03 Jan 2024 09:51:29 -0500

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.

Thu, 26 Oct 2023 12:09:52 -0500

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.

More human and humane

Wed, 25 Oct 2023 23:44:00 -0500

Hilariously (sadly? regretfully?), since I’ve been writing online for public audiences since about 1997, I’ve been thinking about the art of posting, community building, and who benefits and how, for a very long time. All of this (https://blog.ayjay.org/the-three-paths-of-micro-blog/) sounds about right, specifically:

“…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.”

Wed, 25 Oct 2023 13:12:52 -0500

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?

Wed, 25 Oct 2023 11:20:37 -0500

Microblogging on the open web - and why care? book.micro.blog

Wed, 25 Oct 2023 08:24:47 -0500

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.

See the whole year on one sheet of paper. Any sheet of paper: neatnik.net/calendar/