On the surface, social networks and communities look like the same thing: places online where people gather, post, and react to each other. In practice, the two are different products with different incentives and different effects on the people who use them. Confusing them is one of the more common framing mistakes in coverage of the platform economy.
The structural difference
Big social networks optimise for engagement at scale. Their business model depends on keeping vast numbers of loosely connected users active enough to see ads. Communities optimise for relationships at depth. Their value comes from the fact that members know each other — by name, by handle, or by reputation — and that conversations carry across visits. The first is a feed; the second is a room.
Why the distinction matters
If you treat a community like a social network, you push for growth, scale, and frictionless onboarding — and you erode the relationships that made the community work. If you treat a social network like a community, you wait for relationships that the format does not actually support. Both mistakes are common and both produce bad experiences.
Where this leaves users
For most use cases the answer is not one or the other but a stack. The social network for broadcast and discovery, the community for the conversations that need context, history, and trust. yippy coverage tracks both, but treats them as distinct categories rather than competing flavours of the same thing.