Tim Chambers (@tchambers.indieweb.social.ap.brid.gy)

The Seven Deadly UX Sins of the Fediverse Web Experience (To Fix) **So, confession time:** I was recently helping a new client get set up on the Fediverse—guiding them through their first steps into our glorious decentralized galaxy. And seeing it all again through fresh eyes? _Reader, it was brutal._ So much of what should be _table stakes_ for any social media UX in the year of our Lord 2025 still is missing or deeply broken still. I know progress has been made and a good fight, fought. But those of us who love the Open Social Web can get blinded to the rough edges not yet fixed or not having lived with them, start to consider them not so bad. Beloved, they are that bad. Still. Let me be crystal clear before we begin: I say all of the below with love for the fediverse.. Deep, stubborn, open-source-loving, billionaire-eschewing love. I want the Open Social Web to win. But wanting it isn’t enough. If we want this thing to thrive we have to face the user experience sins head-on—and maybe even laugh at them a little along the way. <Caveate>I love native apps like Ivory or Mona or custom web UX like Elk or Phanpy as much or more than any of you but those are all UX bandaids over things we have needed to fix in most cases for years. That time is now.</Caveate> So I jotted down the seven things that make my clients’ eyes cross. And no, this isn’t me dunking on one app or interface. **Pixelfed—you’re not off the hook. No snickering, Friendica. These are Fediverse-wide sins.** And don’t get smug, Bluesky. You’ve got some whoppers in your closet too—and I’m saving those for another article. So grab a cup of coffee—or maybe the nearest comfort blanket—and let’s soberly and bravely take a cathartic journey through the Deadly Sins that plague the Fediverse’s web UX. (And any I missed in the comments to this blog post) * * * ### **1️⃣ The Sin of Overwhelming Complexity: Instance Selection Paralysis** Ah yes, we start the OG sin. This one’s been haunting the Fediverse since before most people even knew the Fediverse existed. Again see this with fresh eyes: Imagine the moment you decide to join the Fediverse. You’re feeling a tad noble. Brave. Ready to reclaim your digital life from Big Tech’s clutches. Then… boom. You’re confronted with a cryptic list of servers, each with a name that sounds like a cross between a startup pitch and a medieval tavern. Wait, what? “social.town or lemmy.world? climatejustice.social or a server with a frog logo? What am I signing up for here?” No warm hand-holding, no curated suggestion. Just a buffet of options that would make even a seasoned sysadmin’s head spin.No wonder so many people bail before they even get started. It’s like trying to join a secret club when no one will tell you the handshake. And even our terms “Server” Or “Instance” make sense in an engineering flowchart but why in all that is holy would we foist those onto users to pretend to understand? At the very least we should talk about new folks joining a “server community” of fellow users. And here’s the harsh truth: even offering _**more than one onboarding “server community” choice**_ **is often one too many.** Even the fix at JoinMastodon for the mobile app only not the web app - while admirable and going in the right direction. If your onboarding flow requires a glossary, a decision tree, and a four-part documentary on federation theory, something’s gone very wrong. A multi-step wizard isn’t going to save you—it’s just a fancier maze. We’ve seen flows that bleed _50% of users per screen_. That’s not onboarding, **that’s a prescription for a slow-motion rage quit.** “But what about decentralization?” someone valiantly cries from the back row. Don’t worry: I’m not selling it out. I adore decentralization as much as you and trust me, we don’t have to throw that out to give users onboard for the first time only one server choice. I hear you audibly confused now but trust me, wait for it. For now I think we can agree that new users to the Fedi need an onboarding experience that doesn’t feel like a grad school entrance exam. I believe a far better way is possible, and I’ll spill the beans in the next post. * * * ### **2️⃣ The Sin of Inconsistent Navigation: Timeline Turmoil** Congrats, you survived the Great Instance Selection Gauntlet™. You’ve picked your server, verified your email, maybe even uploaded a profile pic. You’re finally ready to explore your new digital neighborhood. And then—bam. **Three timelines.** Not one. Not two. **Three.** Home, Local, Federated—each more enigmatic than the last. The Fediverse’s multiple timelines are a beautiful idea in theory, but in practice? * **Home:** Hopefully your cozy friends’ chatter. * **Local:** Pretty much your instance’s collective brain dump. * **Federated:** the cosmic firehose of everything, everywhere, all at once. Many are sure to be in languages you don’t speak. Basically: digital chaos in reverse-chron order. New users are expected to **intuit the metaphysical difference** between timelines, And honestly—**why should new users care?** What does each one _do_ for them? What problem is it solving? No really, I’ll wait. * * * ### **3️⃣ The Sin of Remote Interaction Purgatory: Federation Gymnastics** One of the Fediverse’s great promises is universal interaction—**no matter which server someone calls home, you can still follow them, reply, boost, interact.** In theory? Utopian. In practice—for web users—it’s an absolute effing mystery. Want to boost a post from another instance? Want to follow someone who lives on a server that’s not your own? Brace yourself: copy, paste, search, squint at a remote profile view, and whisper a quick prayer to the federation spirits that it _might_ work this time. Want to reply to a post from a different corner of the Fediverse? You’d better hope the stars align, the server’s awake, and the fediverse goblins aren’t misbehaving today. Sometimes it’s seamless. Sometimes you end up trapped in a **social media escape room** , having to try every door twice. It’s social networking as performance art: awkward, elaborate, and weirdly beautiful—but **absolutely not** the experience most users signed up for. And remember the golden UX rule: **every extra step you give a user cuts retention in half.** That brutal law applies here too. Every clunky redirect, every extra click, every “wait, what do I do now?” moment sends more would-be users quietly packing. * * * ### **4️⃣ The Sin of DM Disasters Waiting to Happen** **Private messages in the Fediverse: because who doesn’t love social roulette?** And yet here we are - as on most Fediverse platforms, “Direct Messages” live right alongside public posts in the same composer, the same timeline view, sometimes even with mostly the same visual styling. You _can_ toggle visibility to “Direct”… but will you notice you didn’t? Will you check? Will the UI save you? Spoiler: It will not. **One wrong toggle, and your private thought becomes a public reckoning.** There’s no special UI wrapper. No bold red warning. No modal that says: “Heads up—you’re about to tell your boss what you _really_ think, _in public_.” Instead, it’s all too easy to accidentally post a private message as public—or vice versa. This isn’t just a newbie trap. **It’s a UX booby trap.** And let’s be real: “Direct Message” in the Fediverse doesn’t even mean what most users think it means. It’s just a post with limited visibility, sent to a tagged user. Worse? There’s no encryption. So it’s not just accidentally public—it’s _intentionally insecure_. It’s plaintext dressed up as a secret. There is some fine print warning you, But let’s be real: nobody reads fine print mid-conversation. The result: drama, confusion, and sometimes real harm. All from a UI that treats one of the most sensitive features of a social platform like just another post flavor. * * * ### **5️⃣ The Sin of Ghost Conversations and Phantom Follower Counts** Federation is the Fediverse’s secret sauce—and as implemented, its spectral curse. What should be lively, multi-user conversations often arrive with limbs missing. Replies that clearly _should_ be there are gone. Half the participants never materialize. You’re reading a thread and suddenly think: _Wait… who is this person even talking to?_ Follower counts of remote users become carnival mirrors: someone shows “800 followers,” you see 12. You follow a fascinating account, only to feel like you’ve stepped into a half-lit room where the conversation’s already happened—and half the guests are ghosts. Why does this happen? Because what you see is only the part of the Fediverse that’s federated _to you._ Each server decides what to fetch, when to fetch it—and sometimes just… doesn’t. There’s no guarantee your instance will pull in every reply, every participant, or even the full thread—especially if the original conversation lives on a server it barely talks to. The result? Phantom threads. Phantom user counts.Hollow outlines of conversations happening elsewhere. Social interaction becomes confusing swiss-cheese cutouts of themselves. It’s enough to make you wonder: _Am I lurking… or am I the one being lurked?_ * * * ### **6️⃣ The Sin of Invisible Discovery: The Content Mirage** The Fediverse was born to be better than Big Tech’s social media rage-bait casino—that places like X or Facebook designed to mine you for clicks, views, and your soul. Good call to avoid that. Let’s not do that. And yes, privacy is precious. Zero arguments here—no one’s asking for surveillance ads or algorithmic doomscrolling. **But the Fediverse takes that privacy ethos and forgets to replace it with… well… _anything._** So what you get instead is discovery by divine accident: No algorithmic curation. No fediverse-wide trending topics. No “here’s what’s buzzing.” Just you and The Void. So new users end up wandering along, stumbling across interesting people and conversations only by sheer luck. It’s charming - but only in a 19th-century explorer way. It’s less charming when you’re just trying to find a cat meme. What about Mastodon Search? On paper, it’s powerful. In reality, it’s opt-in only—tucked behind an Easter egg hunt of privacy settings. Years after launch, Mastodon Search still surfaces a fraction of a fraction of users—basically just those who’ve unlocked the “I read the docs” achievement. And hey, credit where it’s due: Eugen and team _**did**_ **build something.** And erred on the side of caution. Most other Fediverse platforms haven’t even really _tried_ to tackle search yet in a meaningful way. * * * ### **7️⃣ The Sin of User Discovery Hell** Search is one thing. But finding people to follow—especially if you’re new—is where the UX - beyond just search - really starts to melt down. User discovery in the Fediverse is so decentralized, it’s basically unusable. No global directory. No “you might like.” No obvious trails to follow. Just vibes. And maybe a dusty wiki from 2022. _(Full disclosure: I helped build some of those early directories for journalists and activists. We were literally hand-crafting Excel spreadsheets of accounts worth following. Read that again. No really.)_ Want to create your own curated user list of great accounts? Go for it—just don’t expect to share it. Mastodon lists aren’t public. You can’t even make them public. So they live and die with you, like a mixtape you can’t give to anyone. And other Fediverse platforms do not even have lists. Some Fediverse servers maintain public list pages of their user profiles that are on that server —but good luck using them. They’re often: * Unsortable except by these vague, frustrating options: * _**Recently active:**_ OK, fine. Credit where due. Good one. * _**New arrivals:**_ (New…where? From what? And are they “New” and “Aticve” or just lookie-lous that joined then bounced away?) * _**From this-server-name.com only:**_ What? Why? (See Sin #1.) * _**From known Fediverse:**_ I’m begging you. What does that even mean to any newbie? * Unlabeled by any useful tag—even ones users have publicly applied to themselves. * Unfiltered, showing accounts that haven’t posted since Obama’s first term and giving no indication who’s worth following now. * And lastly each server’s public profiles do not flow up to any larger discovery pipeline. So even if you do find cool, active, Jazz fans found by hand from user profile section of the Jazztodon server, no other server benefits but you. Go you. But opportunity firmly lost for fediverse wide discovery. And let’s say you gave up on all of the above. But a new idea struck you: “I know: like on every other social media platform, I can find cool folks that my friends follow and follow **them**.” Yeah…no. Thanks to federation fragmentation - Think you Sin #5 - many of their following—although every last one of them being technically public—are totally invisible to you in practice. So much for that idea. It’s a UX turducken. One Sin nested inside another. You didn’t just fall through the cracks—you’re _living_ in them. * * * ### **🙏 The Path to Redemption** Ok that was withering to write, let alone what it must have been to read. Time for a palate cleanser for both of us: ![Adorable golden retriever puppies] (https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjrdpDT3eMO7ZBVv39srKhyD9rfVaAHAOW-3mzmx-IiO7qCL8j9439fPDhsKPCFnaiPHx0_fi13eZrFvhwy7YiSAGdTb0tXfqNxum9NAH3Rxy_-Q6s7aW2uZnnu-O9H7nciyNHDI4OIMZbP/s1600/Golden_Retriever_Puppies.jpg) OK here is another ray of hope: Remember I’m writing these out of LOVE for the Open Social Web and the fediverse and to improve it. And let’s be clear: these UX sins aren’t as the preachers say, “sins unto death.” There is a path to redemption, each one of these is eminently fixable. These fixed don’t require a pilgrimage to the holy land of W3C working groups or a blockchain duct-taped to the side of the server rack. We’re not waiting on divine intervention via Fediverse Enhancement Protocol v99.9b. The path out of UX hell is paved with thoughtful design, a pinch of frontend finesse, and a few determined devs who are tired of watching newcomers bounce off of this experience back into the waiting arms of Big Tech Silos - often doing so with very good reason, and a sense of loss. And more good news? Many folks have _already_ started making serious strides. Now is the time to push forward. Lastly, remember: The early open web had UX problems just as gnarly—and it worked through nearly all of them. The open social web can too. I’ll dive into the fixes in the next article in this two-part series. Catch you on the other side. * * * _This is Part 1 in a two-article series on the**Seven Deadly UX Sins of the Fediverse Web Experience**._ _**Part 2** —our roadmap to redemption—will arrive as soon as the author can wrestle their love of the Open Social Web back into prose, ideally before the next major Mastodon fork or the collapse of another Twitter clone._ _In the meantime, if you’ve spotted a UX sin I missed, drop it in the comments or send a direct message (just, you know, double-check the visibility setting first)._ https://www.timothychambers.net/2025/06/18/113327.html