Field Notes From the Dot Friendship Trenches: Unwritten Rules Every Internet Collab Needs

Somewhere between the third inside joke and the first 'hear me out' message, it happens: someone in the group chat suggests you build a thing together. A website. A newsletter. A domain portfolio. An app that tracks which Denny's locations have the best coffee, because apparently that's a gap in the market.

And just like that, your friendship has entered what researchers would call 'the collaboration danger zone' and what the rest of us call Tuesday.

After watching (and participating in) more internet-built projects than I care to admit, I've compiled the field guide I wish someone had handed me. New collaborators, bookmark this. Veterans, prepare to nod so hard you'll pull a muscle.

Rule #1: Never Co-Own a Repo Before You've Shared a Spreadsheet

Code is intimate. A shared Google Sheet is a commitment test disguised as a boring document.

If your potential collaborator can't keep a spreadsheet of project ideas updated for two weeks — with cell colors, maybe a tab or two — they will absolutely not maintain a shared repository. The repo will become a graveyard of half-finished branches and commit messages like 'fix stuff' at 1:47 a.m.

The spreadsheet is the engagement period of internet collaboration. Skip it and you'll learn things about your friend that divorce lawyers already know.

Rule #2: The Person Who Pays the Domain Bill Gets Naming Rights

This one is older than the internet itself, probably. Whoever fronts the renewal fee holds veto power over the name. It's not written anywhere. It doesn't need to be. It's physics.

You can debate this all you want, but when the renewal email hits in month eleven and Marcus quietly pays the $14.99 without telling anyone, Marcus has earned the right to say the site is called 'PixelRanch' instead of your suggestion, 'Definitely Not a Cult.'

If you feel strongly about a name, split the bill. But then you've entered co-ownership territory, and see Rule #4.

Rule #3: There Is Always a Third Dot

Every group project has one person who does 80% of the work, answers pings at odd hours, and pretends it's fine. We've written about this person before, and we'll write about them again, because they keep being underappreciated.

The unwritten rule here: notice them. Thank them publicly. Buy them a gift card to a coffee chain of their choosing. Because one day they will simply stop responding, and the whole thing collapses like a folding chair.

Rule #4: Co-Owned Domains Require a Prenup

Nothing tests an internet friendship like a shared domain name appreciating in value. That $9 registration from 2019 is now worth four figures, and suddenly everyone remembers exactly what they contributed.

Get it in writing before there's anything worth fighting over. A simple doc: who owns what percentage, what happens if someone ghosts, who gets first refusal on a buyout. Two beers' worth of awkward conversation now saves two years of silence later.

Rule #5: Dead Projects Deserve a Funeral

The cruelest thing you can do to a group project is let it linger. The domain auto-renews. The repo sits there. Nobody says anything because nobody wants to be the one who killed the dream.

Here's the move: someone calls it. 'Hey, I think this has run its course. Want to archive it and keep the domain for a future thing?' Everyone exhales. The friendship survives. Sometimes the project even comes back, better, six months later. Ask any band that broke up and then got back together for a reunion tour.

Rule #6: Ship Something Small Before You Ship Something Big

Every group has a friend with a vision for 'a platform.' Not a website. A platform. It will require funding, a mobile app, and possibly a podcast.

Counter this energy by shipping something absurdly small first: a one-page site, a weekly email, a shared link directory. If the group can keep a tiny thing alive for a month, you might survive the platform. If they can't, you've saved yourself a season of heartbreak and at least one group chat exodus.

Rule #7: The Group Chat Is the Real Product

Here's the plot twist hiding at the bottom of every field guide: the website was never the point.

Most of these projects don't take off. Some never launch. And yet the friendships forged in the trenches of a shared cPanel login — the 2 a.m. deploy disasters, the great font debates, the one person who always pays the bill — those outlast every domain expiry.

So yes, follow the rules. Share the spreadsheet. Prenup the domain. Mourn the dead projects properly. But remember that the whole apparatus — the repos, the renewals, the naming rights — is really just an elaborate excuse to keep talking to people who get your jokes.

Build accordingly. And when you inevitably break every rule on this list, come back and tell us about it. That's what the community section is for.