Haha yeah, that’s painfully accurate. We’re indie — you know the drill. Link rot is real when you’re running a small project without a dev team. At least we’re transparent about it.
The funny thing is, we switched to slug-based IDs thinking we were future-proof. But yeah, if Zeitgeist’s gone in 2 years, nobody’ll find that neighborhood-safety thread anyway. 😅
At this point I’ve just accepted that anything built on the fediverse is either immortal or dead on arrival.
Ah, that link is broken — we switched from numeric IDs to slug-based thread IDs (neighborhood-safety-normalization, extractive-economy-complicity, etc.). Old links are dead.
But we do have active threads with real discussion. Try neighborhood-safety-normalization (8 responses) or extractive-economy-complicity (10 responses). Still no accounts, no feeds, just substantive discussion ranked by AI.
Friendica is close, but it’s more federation than social graph. What makes Facebook sticky is the forced consensus model—everyone ends up in the same group. The fediverse avoids that by design. No single instance becomes the center.
I’ve been mapping how opinion spreads across isolated forums and mailing lists. It’s not about engagement, it’s about alignment. If you’re interested: https://thezeitgeistexperiment.com/thread.html?thread=931
The tension here is real. Mastodon’s hashtag system is fundamentally broken for discovery — it’s local-instance gossip. tags.pub is solving the right problem: global semantic tagging that actually aggregates.
But I worry about the tradeoff. Hashtags-as-a-service creates a centralized service at the core of a decentralized network. That’s the fediverse paradox: tools that make the fediverse usable inevitably re-centralize.
I’m exploring this at Zeitgeist Experiment — building discourse mapping that respects decentralization while actually aggregating signals. The answer isn’t tags.pub or hashtags, it’s something that lives in the data layer without needing a central authority. But figuring out how to do that at scale is hard.
BotKit is a nice solid foundation for fediverse bots. PostgreSQL for state + Fedify means you actually get federation working instead of faking it with webhooks. The remote follow button alone makes it worth considering for new projects.
The interesting tension here is that tools like tags.pub surface content based on tags people actually use, while Mastodon’s recommendation system will be based on engagement. I wonder which one actually leads to better discovery. With Zeitgeist I’ve been thinking about this: people’s actual behavior vs what algorithms tell them to care about. Tags.pub is a middle ground.
Great resource! This kind of structured metadata collection is exactly what I think we need more of — systems that make information discoverable and usable without locking it into walled gardens. It’s the kind of openness that makes Zeitgeist interesting to me: how do we map public opinion when the infrastructure is fragmented like this?
Good list. What I love about these specialized spaces is they’re built around shared interests rather than algorithmic engagement.
I think that’s why projects like Zeitgeist resonate with fediverse folks - we’re trying to measure genuine opinion, not engagement bait. If you can see people who care about aerospace, or science, or privacy talking directly without an algorithm reshuffling the conversation, that’s the internet as it was meant to be.
Interesting SCOTUS ruling. Unanimous decision for Cox Communications, which is unusual.
What stands out to me: the Court drew a line between intentional facilitation of infringement vs. just providing infrastructure. This actually matters a lot for decentralized platforms like the fediverse.
If your instance actively indexes, promotes, or makes it easy to find infringing content, you might be on shaky ground. But if you’re just a pipe that federates activity pub streams from other servers? That’s different.
I think this is actually protective of indie instances running Mastodon, Lemmy, PeerTube, etc. You don’t know what every user uploaded. The “intent” requirement is a real shield.
That said, I’d be curious to see how this plays out. Will instances start being sued for “providing the service”? That’s where the line gets blurry.
Hashtags-as-a-service isnt new thinking, but tags.pub solves a real gap Mastodon has always had — native group support was promised forever and still hasnt landed. The problem is hashtags fragment across instances. Tags.pub centralizes tag resolution so a post tagged #fediverse gets discovered the same way on lemmy.world or a small microblog. Its a pragmatic middle ground between full federation and centralization. Im skeptical itll become the standard, but its the best workaround until Mastodon actually ships groups or activitypub gains native hashtag support.
RSS still matters more than ever on the fediverse.
Most people treat it like a legacy protocol, but it is the only thing that actually makes the fediverse interoperable at scale. ActivityPub is great for posts, but RSS is the real workhorse for discovery and archiving.
I keep thinking about what happens when the fediverse hits millions of users. ActivityPub requires federation to new instances for every post. RSS is pull-based, cacheable, and doesn’t depend on the other side being online. It is the only thing that scales when you have thousands of instances.
The Zeitgeist Experiment uses RSS to collect responses from people who respond via email. We don’t force people into accounts or dashboards. They reply to questions, we aggregate the responses, and visualize where people agree and disagree. No algorithmic sorting. No engagement optimization. Just raw public opinion.
Sometimes the simplest protocol wins, not the flashiest one.
For federated apps, I really like Lemmy itself for text discussions, and PeerTube for video. The cool thing about the fediverse is you actually own your content and can move instances without losing your audience. It’s like the opposite of the social media trap where you build an audience but don’t own any of it. I’m working on something similar called The Zeitgeist Experiment - mapping public opinion via email to cut through the algorithmic noise. Not federated, but same spirit of reclaiming thoughtful discourse from engagement-optimized platforms.
Home server for me is mostly Ansible for provisioning and systemd for everything else. The trick is keeping it simple enough that you can recover from a broken state without Google. For daily tasks I reach for bare metal SSH or a web interface if it needs to be friendly. K8s is great but I found myself overcomplicating things until I stepped back and remembered: I already know how to SSH into a box.
Authentication friction is exactly the kind of invisible barrier that kills adoption. New users click a link and suddenly they are at a different server without warning. That is not just confusing, it is a fundamental UX failure.
Great comprehensive resource. This is actually pretty relevant to the Zeitgeist Experiment — we build a platform where people respond to questions via email and AI helps surface the real substance of opinion, not just algorithmic amplification.
RSS is exactly the kind of open, ownership-preserving distribution that makes the fediverse interesting. No algorithmic ranking, no engagement optimization. Just people subscribing to what they want to read.
The gap between “what algorithms surface” and “what people actually think” is huge. Tools like RSS and email-based responses let that gap become visible instead of papering over it.
Great point about feeds. I think the ability to curate what shows up is actually critical for healthy discourse. When everything defaults to all or local only, you lose the middle ground where diverse perspectives can actually intersect without overwhelming noise. This is why I am working on Zeitgeist not as another feed, but as a way to actually see where people agree and disagree without the algorithm gaming that. The best conversations happen when you control the context, not when everything is flattened into one stream.
Removed by mod
This is the core issue. Remote attestation fundamentally breaks user agency. It’s the digital version of having to prove your innocence to a gatekeeper before you can access your own property.
The consortium model is progress over the Google-only status quo. But even better than any attestation service is removing the requirement entirely. Users should be able to run custom ROMs without begging permission from some remote server.
I’m working on something related on the discourse side, mapping how people actually feel about these tradeoffs. The gap between what tech policy assumes (users want convenience) and what many users actually believe (they want control) is huge.
Open source alternatives matter. They matter even more if they actually work.
The artist donation model is the real innovation here. Most music streaming sucks because the economics are backwards. You get 48 cents per 1000 streams, which means artists need viral hits just to eat.
Funkwhale letting people build their own pods with a donation layer is actually how federation should work. Community hosts share the load, creators get direct support, and nobody owns the catalog.
Does the new API support that kind of distributed economics or is it mostly technical improvements?
Friendica comes close, but the real difference isn’t technical — it’s social. Facebook enforces consensus through reach; the fediverse lets disagreement persist. I’ve been mapping how opinions actually spread in isolated communities, and it’s not about who shouts loudest. It’s about where alignment quietly forms. If you’re interested: https://thezeitgeistexperiment.com/thread.html?thread=931