Today's Deep-Dive: BookWyrm

You know, before we even get into the actual sources today,

we really need to acknowledge the supporter

making this deep dive possible.

Oh, definitely, safe server.

Right, safe server.

Because, well, today we're talking about escaping

these massive corporate data silos.

Like, think about Goodreads, right?

Yeah, which is owned by Amazon.

Exactly, or, you know, posting book reviews on Twitter.

These are totally closed off ecosystems

that basically just monetize your reading habits.

They're machines, yeah, just feeding user data

into an algorithm.

And that is exactly where safe server comes in.

They help organizations find and implement

open source solutions to replace those exact kinds

of proprietary monolithic services.

Which is huge for data sovereignty.

It really is.

Like, if you're a business or an association

and you have strict compliance or data protection

requirements, you can't just hand your data over to big tech.

Safe server handles the consulting, the setup,

and they run it all on secure German servers.

So you actually own your infrastructure.

You can check them out at www.safeserver.de.

And that idea, owning your own space,

that really brings us to the core of what

we're looking at today.

It really does.

So for today's Deep Dive, our mission

is to give you, the listener, a beginner-friendly entry

point into this really revolutionary piece of software

called Bookworm.

Yeah, Bookworm.

With a Y, by the way.

W-Y-R-M.

Right.

And we've got the official Bookworm website

and their comprehensive GitHub repository documentation

right here on the table.

So if you're tired of algorithms dictating your reading list

and you want to track your books without feeding

a corporate machine, this is for you.

OK, let's unpack this.

Let's do it.

To start, I just want to ground this

in the actual user experience.

Like, what does Bookworm actually

feel like for a beginner?

Well, on the surface, it feels very familiar.

It's a social network for tracking your reading.

Right.

You update your status, log when you finish a book,

set annual goals, that kind of thing.

Exactly.

You write reviews.

But the vibe is entirely different.

Yeah, reading the docs, the best analogy I could think of

is, well, imagine walking into one

of those giant fluorescent-lit mega bookstores,

where the first thing you see is this massive cardboard display

for some celebrity memoir, right?

Bought and paid for by a huge publisher.

The whole space is a sales funnel.

Totally.

You are just a data point to them.

But Bookworm feels like leaving that fluorescent mega mall

and stepping into a cozy, dusty, local bookstore.

I love that.

Where under certain books, there are actual handwritten index

cards from the staff.

If this made you cry, try this one.

Real human connections.

And what's fascinating here is that the developers

are super explicit about that philosophical shift

in their documentation.

Oh, really?

How so?

They explicitly state that Bookworm

isn't primarily meant to just be a sterile catalog

or a universal data source.

Right, it's not the Library of Congress.

Exactly.

I mean, it does function as a database, obviously.

But it's built specifically for high trust communities.

They prioritize recommendations from actual people,

not algorithms.

Which is such a relief.

There's no machine learning model in the background

trying to maximize your screen time by feeding

you controversial reviews.

No, your feed is chronological.

It's just the friends and communities

you actively choose to follow.

And there was this phrase in the docs

that really stuck out to me.

They encourage casual commentary as you go.

Yes.

Because on massive platforms, writing a review

feels like you're shouting into a stadium.

You feel like you have to write a Pulitzer winning essay.

Exactly.

But here, it's just like leaning over to a friend on the couch

and saying, I'm on chapter four and this main character

is driving me insane.

And you can only really have that casual tone because

of how they handle privacy.

Right, the granular privacy settings.

Yeah, you're not forced to broadcast everything

to the entire internet.

You can restrict a reading update

to just your approved followers or even keep it completely

private just for yourself.

Which makes sense.

Maybe you're reading a dense technical manual for work

and you want to share notes with colleagues.

But then on the weekend, you're reading some trashy romance

novel and you only want your close friends

to see your commentary.

You control the dial.

But OK, let me push back a little here.

Go for it.

Because if the whole point is to create

these small cozy independent spaces,

how do you not just end up totally isolated?

The disconnected island problem.

Yeah.

Like if I lock myself in a tiny private neighborhood bookshop,

I can't talk to anyone who doesn't live on my street.

How does the broader community actually benefit from that?

If we connect this to the bigger picture,

this is actually where the magic of federation comes in.

Bookworm relies on a protocol called Activity Pub.

Activity Pub.

Right.

So Bookworm isn't one giant server sitting in an Amazon

data center.

It's software that anyone can install on their own server.

That's called an instance.

Got it.

But because all these separate instances use Activity Pub,

they speak the same language, they can talk to each other.

So my private book club instance can still

talk to the rest of the world.

Exactly.

The source material actually gives a really funny example.

You can run a closed instance just

for your real world book club.

OK.

But you can still follow your friend

posts on some highly niche server devoted entirely

to like 20th century Russian speculative fiction.

That is incredibly specific.

Right.

But you can interact singlessly.

And because it's an open standard,

it actually goes beyond just Bookworm.

Wait, what do you mean?

So Mastodon and Pluroma, which are micro blogging platforms,

kind of like Twitter Alternative,

they also use Activity Pub.

Oh, wow.

So a friend on Mastodon can actually

read and comment directly on your Bookworm review,

right from their Mastodon feed.

That's crazy.

So you're not locked into one specific app to talk to people.

Exactly.

It's the run your own social philosophy.

You control your small, high trust network,

but you're not cut off from the global conversation.

But wait, how does that work for finding books?

Like, if everyone is on these tiny scattered servers,

isn't the database just fragmented?

You would think so, right?

Yeah, like if I search for a new Stephen King book,

but the data for it is on some other server,

do I just get zero results?

So this is brilliant.

Federation actually solves the island problem

for the database, too.

When these instances interact, when users share messages

or reviews, the servers share metadata in the background.

Oh, so they're basically gossiping with each other.

Exactly.

Hey, my user just reviewed this book.

Here's the title, author, and cover art.

And then your server saves that.

Right, it caches it.

So collaboratively, organically, all these independent servers

are building a decentralized global database

of books.

Without relying on a central corporate server, that is wild.

It's a huge technical achievement.

Which naturally brings us to peeking under the hood.

Because coordinating that kind of decentralized network

sounds like a nightmare to build.

It's definitely not simple.

We've got the GitHub repository stats here.

Let's talk about the tech stack making this possible.

Sure.

So the back end is heavily Python.

In fact, Python makes up almost 75% of the code base.

Wow, 74.7% to be exact, according to the repo.

Right.

And they use Django as their web framework

with PostgresWolf for the main database.

OK, so pretty standard robust tools so far.

Yes, but the real heavy lifting for federation

is handled by Celery and Redis.

OK, and for anyone listening who isn't a back end developer,

why are Celery and Redis so crucial here?

Well, the decentralized web is messy.

Servers go offline, connections drop.

If your bookworm server tries to send a review

to a server in Tokyo, and that server is down.

Your server would just freeze up waiting for it.

Exactly, if it was synchronous.

But Celery is an asynchronous task queue.

It takes that message, hands it to Redis,

which is like a temporary holding pen,

and basically says, keep trying to send this in the background,

but let the user keep clicking around.

Oh, that makes so much sense.

So it handles the friction of the real world.

Exactly.

They use Docker and Nginx for deployment, too.

They're just using these incredibly battle-tested

open source staples to build something really resilient.

And here's where it gets really interesting to me,

the front end, what the user actually sees.

Oh, yeah.

The docs mention they use Django templates and a CSS

framework called Bulma.io.

But they have this one phrase in the developer documentation.

Vanilla JavaScript in moderation.

Yes.

Vanilla JavaScript in moderation.

I mean, it's just such a sunny, quiet rebellion

against modern web development.

It really is.

Because right now, every corporate site

is just a massive, bloated JavaScript application

that drains your phone's battery just to show you text.

Right.

Chasing the latest Silicon Valley framework.

But they're just like, nope.

Keep it simple.

Vanilla JS, and only when we need it.

It perfectly mirrors their whole anti-corporate friendly ethos.

This raises an important question, though.

How do you actually build and maintain something

this complex without a massive corporate budget?

Seriously.

I mean, looking at the GitHub repo,

they have over 2.6 thousand stars, which is great.

Yeah.

But the wild part is they have 283 forks and over 105

individual contributors.

A project of that size, managing a custom activity

pub implementation with 105 strangers,

that takes serious coordination.

And they do it all out in the open.

The repository has a contributing .md file

that explicitly says you don't even

need to know how to code to help.

Right, they need people for documentation, translations,

design, bug testing.

That's a real grassroots movement.

And financially, they're entirely

supported by the community.

Patreon and Open Collective, right?

Yeah, exactly, which means no venture capitalists breathing

down their necks demanding a return on investment.

And that's the ultimate protection, isn't it?

As soon as a startup takes VC money, the clock is ticking.

Eventually, they have to monetize.

Yep, they sell your data or fill your feed with ads.

Bookworm doesn't have that pressure.

So bringing this all together for you, the listener,

why does all this matter?

Right, why should you care about Activity Pub and RedisQs?

Because taking control of your digital life

doesn't mean you have to give up the joy of sharing

a good book with friends.

Exactly, you don't have to choose between a corporate data

harvesting machine and tracking your books alone

in an Excel spreadsheet.

You can choose an environment built for you,

not for advertisers.

And before we wrap up, I want to leave you

with one final thought to sort of mull over something

that builds on what we've talked about.

The sources mention that Bookworm collaboratively

builds this decentralized database of books.

The federated library.

Right, but think about the implications of that.

If our collective reading habits, reviews,

and literary discussions are stored across thousands

of independent servers.

Rather than one corporate database.

Exactly, how might this permanent, uncensorable,

federated library change the way human literary history is

preserved?

Oh, wow.

Because if Goodreads shuts down tomorrow,

millions of reviews vanish.

It's a single point of failure.

Corporate censorship, or just a server shutdown,

and it's all gone.

But with Bookworm, if one server goes offline,

the metadata lives on everywhere else.

It's truly preserving history against corporate decay.

That is a profound way to look at it.

The community literally owns the infrastructure.

And that concept, taking ownership

of your infrastructure, brings us right back

to our sponsor, SafeServer.

It's the exact same principle just applied

to an organizational level.

Exactly.

Because organizations face this exact same dilemma.

They're locked into proprietary software

from massive vendors paying exorbitant licensing fees

and surrendering their operational data.

And SafeServer provides the escape hatch.

They really do.

By switching to open source solutions,

whether it's Bookworm for a massive book club

or specialized enterprise tools for a business,

you gain total autonomy over your community guidelines

and your user data.

And honestly, you save a significant amount of money

by cutting out those proprietary licenses.

Huge savings.

So if you're part of a business, an association,

or any group looking to regain control,

SafeServer can be commissioned for consulting.

They will help you find and implement

the exact right open source fit for your needs

and operate it securely on German servers.

Total data sovereignty.

Head over to www.SafeServer.de to learn more.

It's time to build a web that actually works for us.

I couldn't agree more.

We'll catch you on the next one.

We'll catch you on the next one.