Wizzle wasn't born in a meeting room, and it didn't come out of a market study. Wizzle was born one evening, over a beer, between two friends talking about MSN Messenger. An ordinary conversation, the kind you have a hundred times without consequence — except this one ended with an idea scribbled on the corner of the table: what if we brought back the Wizz, that button that shook the other person's screen and was impossible to ignore?

The scene: one evening, two friends, a beer

Picture the moment. Two glasses, a table, and that familiar drift of late-night conversation where you slip from the present into the past without noticing. Someone says something like "remember the nicknames with the little crosses?". The other one answers by imitating the sound. And then something opens up.

For a solid hour, they talk about nothing else:

  • the online statuses you watched like a radar, just to know whether she was connected;
  • the mood of the day under your nickname, updated three times an evening depending on how you felt;
  • the animated nudges you sent to say something you didn't dare type;
  • the famous Wizz, the shaking screen, the sharp sound, and the slight awkwardness right after;
  • the social equivalent of "hit F5": signing out and back in so you'd pop to the top of someone's list.

What struck the two friends wasn't the nostalgia itself. It was its precision. Twenty years on, they remembered tiny details with unsettling sharpness. Not the design, not the features: what they felt when they opened the app after school.

We weren't remembering a piece of software. We were remembering being expected by someone.

Why shared nostalgia turns into a product idea

Nostalgia, on its own, is a bad adviser. It flatters, it filters, it leaves out the bad parts — and there were plenty: dropped connections, contact lists that emptied out, conversations lost on restart.

But shared nostalgia is something else. When two people who never compared notes remember exactly the same things, that stops being sentimentality: it's a signal. It means those details were touching something structural in the way we used to talk to each other online.

The next morning — because every good bar idea has to survive the next morning — the idea was still standing. Not in the "let's rebuild MSN Messenger" form, which would be a pointless exercise in taxidermy. In a more useful form: what actually worked in those messengers, and what did we lose along the way?

The morning-after test

The idea passed three questions.

  1. Is the loss real? Yes. Just raise the subject and the conversation starts on its own.
  2. Is there an answer to it today? Not really. Today's messengers are efficient, but they've stripped out almost everything expressive.
  3. Can we build it without betraying the memory? That's the hardest question, and the one the project has been wrestling with ever since.

The Wizz: an honest, unapologetic demand for attention

At the heart of the project, then, sits that one gesture. The Wizz is an explicit request for attention. It doesn't dress itself up as anything else. It doesn't pretend to be useful information. It says one thing, and it says it clearly: I want you to look at me, right now.

Compare that with what lands on us today. A modern notification is polite, discreet, and designed to be ignorable — except it arrives forty times a day, usually sent by a system rather than a person. The result is a paradox: we're interrupted constantly, and yet nobody really has our attention.

The Wizz worked better because it cost something. Not money: social capital. You didn't wizz just anyone. You didn't wizz three times in a row, unless you genuinely wanted to annoy someone. That self-imposed scarcity is what made it a reliable signal.

What makes an interruption acceptable

An interruption is bearable when it meets three conditions:

  • it comes from a human, not an algorithm;
  • it is rare, so it means something;
  • it can be turned down without a fuss.

Today's notifications usually fail on all three. The Wizz met them almost naturally — and it's that "almost" the project sets out to fix.

What we keep, what we change

A nostalgic messenger project only makes sense if it's honest about what it copies and what it refuses to copy. Here are the trade-offs as they were laid down.

What we keep:

  • The Wizz, with the shaking screen and the sharp sound. The gesture, the attack, the feel of it.
  • The moods of the day: that line of text under the nickname, which said more than any profile ever did.
  • Explicit online statuses — available, away, busy — decided by you, not inferred from your activity.
  • Stylish nicknames, symbols included. Full Unicode, because turning down †Léa† would mean turning down a way of existing.
  • Animated nudges, those small expressive interruptions that have never had an equivalent since.

What we change:

  • The Wizz has a technical cost: a minimum delay between two Wizz sent to the same person. The gesture stays strong because it stays rare.
  • The Wizz can be turned off, contact by contact, with no need to explain yourself.
  • No automated Wizz, no advertising Wizz. A Wizz comes from a person who pressed a button. Always.
  • Your status isn't spied on. No "last seen at 11:47 pm" quietly inferred in the background. You show what you decide to show.
  • No news feed. There wasn't one back then, and that's part of why it worked.

What the project is really trying to recover

Wizzle isn't out yet, and it would be dishonest to promise anything beyond what's being built. But the direction has been clear since that evening.

The goal isn't to replay the 2000s note for note. The 56k modems can stay where they are. The goal is to recover a quality of relationship: a small number of people, present at the same time, able to interrupt each other openly because the interruption actually means something.

It came from a beer and a conversation between two friends. It stuck because, the next morning, it was still standing.