Urgent.News

One page, thousands of outlets. See who else covered it.

Editions

Tech

Hot or Not Built the Internet We’re Still Swiping Through

The early website Hot or Not taught its users to rank people at scale. Twenty-six years later, dating apps are trying to escape the culture the site helped create.

Hot or Not Built the Internet We’re Still Swiping Through

In 2000, Hot or Not launched, inviting people to upload photographs and be rated by strangers on a scale from 1 to 10. This crude and addictive site quickly became one of the most visited on the web. More importantly, it transformed subjective judgments about attractiveness into structured data that could be ranked, compared, and used to organize human behavior.

Professor Brooke Erin Duffy, from Cornell University, notes that this innovative design gamified physical attractiveness and normalized ranking, rating, and scoring concepts now pervasive in social media. By allowing ordinary people to willingly participate in public scrutiny, Hot or Not set a precedent that subsequent platforms have capitalized on.

Initially, Hot or Not's "Meet Me" feature introduced the concept of mutual opt-in messaging, which later became the basis for Tinder's matching system. However, Tinder eventually expanded beyond swiping, introducing more in-person events by the end of the year. The company aims to reduce the number of swipes and promote "fewer, better, more considered signals" to combat user dissatisfaction and declining engagement.

This shift reflects a broader cultural fatigue with the constant need to judge and be judged, leading to potential declines in user satisfaction and engagement within the online dating industry.

Written by urgent.news from Wired's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at wired.com →

More in Tech

The Login Loop of Doom.

This is a submission for DEV's Summer Bug Smash: Smash Stories powered by Sentry . Code snippets are recreated and anonymized for illustrative purposes.

  • Developer encountered endless login loop with Auth0 Universal Login page
  • Custom JWT validation middleware compared exp claim to local server time, not UTC
  • Fix involved comparing expiration time against UTC and handling 401 errors differently

More from Wednesday 19 August →