Nostalgia web

Why the Friend Request Beat the Follow

For about a decade, adding someone online was a two-sided decision: you asked, they said yes, and you both ended up on each other's page. Then the follow button arrived, the asking disappeared, and the friend list quietly turned into an audience. Nothing that made the mutual request good depended on 2006 technology, so you can still run it — and if you want to know the people within a few miles of you, you should.

What a friend request actually was

It was a small ceremony, and the ceremony was the product. You went to someone's page, clicked add, and in the good years typed a line explaining who you were — the concert, the class, the cousin. Then you waited. They saw your name, decided, and clicked. Now each of you appeared on the other's page, with the same access, at the same moment.

Four properties fell out of that tiny transaction:

  • It had a cost. Asking risks a no, so you asked people you actually wanted.
  • It required consent. Nobody landed in your life without your saying yes.
  • It was symmetric. You saw them exactly as much as they saw you, so nobody was performing at anybody.
  • It carried a message. It was the only social action that made a stranger introduce themselves before they got access.

Compare a follow: a decision made by one person, about another person, without asking.

The follow solved a publishing problem, not a people problem

The follow was not a mistake; it was the right answer to a different question. Mutual friending caps a network — you cannot approve a million people — and it makes an account a person rather than a channel. A one-way follow lifts that ceiling instantly, so a band or the bakery down the street can reach anyone without negotiating each connection.

What it also does, quietly:

  • It turns your list into a number. Once the count is public and one-sided it becomes a score, and scores get optimized.
  • It changes what you write. Talking to people you approved sounds like talking; posting to an audience of unknown size sounds like broadcasting, and broadcasting is exhausting.
  • It deletes the introduction. Nobody has to say who they are anymore, so nobody does.

A good trade for a platform becoming a media company, and a much worse one for what most people wanted, which was a way to keep up with people they know. The same swap happened to feeds — we walked through that in social apps without an algorithm.

Write the line that goes with the request

Here is the part you can do this week, and it works on any app that still has a request: never send a bare one. The line attached to a request is the difference between a connection and a notification, and three sentences is plenty.

  1. Where you crossed paths, with one detail they can picture. “We talked for a minute at the garage sale on Linden — I'm the one who bought the terrible lamp.”
  2. Why you are asking. “You mentioned a Thursday walking group and I never got the details.”
  3. An offer instead of an ask, if you have one. “Also, we have a pressure washer if you ever need it.”

What not to send: nothing at all, the word “hey,” or anything that reads like a pitch. And when a good line arrives with a request, answer the line before the request — a two-word reply today beats a perfect one that never comes.

Keep the list at a size you can actually be a neighbor to

The anthropologist Robin Dunbar's much-argued-over estimate is that people can hold something like a hundred and fifty stable relationships. Treat it as a mood rather than a law, but the direction is right: a list you cannot hold in your head is not a list, it is a feed.

  • The one-sentence test. If you cannot say one true, specific thing about a person — their dog's name, their job, where you met — they are someone you follow, not someone you are connected to.
  • Local lists want to be small and dense. Twenty households you would wave at beats four hundred accounts within a hundred miles.
  • Density is what makes a list useful. If your people also know each other, one message finds whoever owns the ladder; if they do not, you are the only bridge and everything runs through you.
  • Add slowly, on purpose. Two or three a month, each one somebody you spoke to first, and a street becomes a network within a year.

The yearly prune, done without hurt feelings

Mutual lists need maintenance, which is the one real chore the format asks of you. The good news is that quiet maintenance is invisible to everybody else.

  • Quiet before you cut. Most apps let you mute someone without removing them — on MetroMeet a mute is one-sided and silent. Usually that is the whole problem: the person is fine, the volume is not.
  • Prune once a year, in one sitting. A yearly pass reads as housekeeping; removing three people on a Tuesday night reads as a message.
  • No announcements. Nobody has ever benefited from a post about cleaning up their list.
  • Keep the dormant ones. The neighbor you have not spoken to since spring is the connection you will be glad exists the week your basement floods.
  • Blocking is for harm, not for boredom. It is a real sentence with real effects.

Ranking your people out loud: the Top 8 problem

The old web took the mutual list one step further and made it public and ordered, which is where it got interesting and where it got mean. The Top 8 was a friend list you had to rank, in view of everyone in it, and adults telling that story still remember exactly where they sat.

Keep the forced choice: a list that costs nothing to add to says nothing, and a list of eight says a great deal. Leave behind the public scoreboard, which is why the grown-up version is a short list of people you actually see, with no implied order and no notification when it changes. The full history, damage included, is in Myspace bulletins and the Top 8, explained.

Requests from people who live near you

A request from someone eight blocks away is a different object from a request from a stranger on the internet, because it is checkable in the physical world. You will pass this person at the hardware store. That is not a risk; it is the accountability the format runs on.

  • Look at the page first. A profile with a theme, a signature, and real comments took effort. An empty one took none.
  • Know what the check does and does not mean. MetroMeet profiles are selfie-checked, so a real person made the account. That is a floor, not a recommendation — whether you want them on your list is still your call.
  • “No” needs no reason, and neither does “not yet.” A request left sitting is a complete answer.
  • Close the loop offline within a week. A connection that never becomes a hello on the sidewalk was just a click.

To see which neighbors are actually within reach of you — MetroMeet scopes by distance from wherever you are, not by which side of a line on a map you live on — start with your area page. Then send three requests with a real line attached to each. That is the whole practice, and it worked better twenty years ago than anything that replaced it.

MetroMeet is coming soon. Leave your email and we'll send one note the day it's live.

Get the launch note

Quick answers

Isn't a friend request more awkward than just following someone?

Slightly, and that is the feature. The small cost of asking is what keeps the list made of people you actually chose, and it is why a mutual connection tends to produce a conversation while a follow tends to produce a view.

What should I do with a request from someone I don't recognize?

Read the note they sent, if any, and look at whether the profile shows a real person doing real things. If nothing places them, you can leave the request pending or reply asking where you met; neither is rude.

How many people should be on a local friend list?

Fewer than you think. Twenty to fifty neighbors you could greet by name is a strong, dense list, and it will do more for you than several hundred accounts you would not recognize on the sidewalk.