Champt: a manifesto
2013
In April 2013 I put Champt online. The tagline was "Where you chat with your local geeks." The bet was that someone worth talking to was probably a few streets away, and nothing on the internet was helping you find them.
It took me two or three weeks to build. I launched it on free cloud credits, fixed a few bugs, and that was it. Very few people used it, so I didn't care much, and when the credits ran out and it went offline, I sort of forgot about it. I don't have the logins any more, and I'm not even sure whether it was on AWS or Heroku.
Someone else had the same idea
I didn't know until this week, but I wasn't the only one. Seven months after Champt went online, Yik Yak came out: threads from anyone within five miles, with no names attached. It took off on college campuses in the US, and a year later it was the ninth most downloaded social app in the country. Then came the racism, the sexism and the bullying. Yik Yak made handles mandatory in 2015, then backed down. It stopped growing, and it shut down in May 2017. It came back in 2021.
Reading its story, I think I missed two things in 2013.
The first is that it was never a geek thing. I assumed only people like me would try an app like this. Yik Yak's users weren't geeks. They were students who wanted to know what was going on around them. The idea never needed geeks, it needed people nearby.
The second is what happens when those people show up. Yik Yak showed how fast an anonymous local chat can turn on the people it's meant to bring together. The first Champt never got big enough to find out.
Why now
I found the old code while cleaning up my GitHub, and rebuilt Champt in about a day with Claude. The first version took me two or three weeks.
That's the real change since 2013, and it isn't the people: Yik Yak showed they were ready back then. What changed is how little it costs one person to build something like this and keep it running. Robin Sloan wrote in 2020 that "an app can be a home-cooked meal". Champt doesn't have to become a company to deserve to exist.
It also shouldn't die the way the first one did. This version is built to survive being forgotten: it runs on free plans rather than trial credits, there's no server to look after, and threads expire on their own, so nothing piles up.
What hasn't changed
What hasn't changed is how little of the internet is local. Feeds decide what we see, ranked for attention rather than for where we stand. Group chats keep us inside the circles we already have. We can follow a stranger on another continent in real time and still not know what is happening two streets away. The places where a city used to talk to itself, the noticeboard, the local forum, the paper on the doorstep, have mostly gone quiet.
So Champt is for anyone who lives somewhere, not just local geeks: the people on your train, in your neighbourhood, at the same gig, caught in the same downpour.
What Champt is
A map of the conversations happening around you.
- You start a thread where you are. It is pinned to that spot, rounded to about 100 metres, not to you.
- You can read any thread, anywhere in the world.
- You can reply to the ones within 100 km of you: your city, your region.
- A thread lives for 24 hours, and every reply from someone else gives it another 24. Talking to yourself buys nothing. It takes two people taking turns to keep a conversation alive.
- You sign in and post under a nickname, which is all anyone else sees of you.
What I believe
-
01
Place before audience. What you say belongs to where you said it, not to how many people follow you.
-
02
Conversation, not broadcast. A thread nobody answers fades away. The only way to stay on the map is to be talking with someone.
-
03
Look anywhere, talk nearby. Curiosity can be global. Conversation works best between people who could actually meet. I set the reach at 100 km because that's how far people can easily travel today. I can, at least.
-
04
No feed, no ranking, no counts. No likes, no followers, no algorithm. The map is the interface, and you refresh it when you want to.
-
05
Pin threads, not people. People have long been happy to let an app use where they are, and slow to let it show anyone. In a 2013 Pew survey, 74% of US smartphone owners used their location to get directions or local information, but only 12% shared it with friends, down from 18% the year before. Champt never shows where a person is. A thread's pin is rounded to about 100 metres, and when you reply, your location is checked against the 100 km reach and never stored.
2013 PEW SURVEY · US SMARTPHONE OWNERSUse location for local info 74%Share location with friends (2012) 18%Share location with friends (2013) 12% -
06
A name is enough. Anonymity is what let the worst of Yik Yak in. On Champt you post under a nickname, and your email stays on the server, so if something goes wrong I know who wrote what. Nobody else ever sees it.
-
07
Today, not forever. Most of what a city says to itself is about today. Let it be about today.
Where I want to take it
- Safety before growth. Yik Yak showed how quickly local chat goes wrong. Rate limits, reporting and clear norms come before inviting a whole city in.
- A reach that fits the place. 100 km is the default. A dense city may want less, a rural region more.
- Reach you can see. Show the circle your voice carries within, so the map tells you who can answer.
- One city at a time. Start where people already care about their place, and let each city find its voice before the next.
What it will never be
Not a feed, not a follower count, not a marketplace, not a dating app, not a tracker. If a feature makes people stare at the screen instead of talking to someone nearby, it does not belong in Champt.
How I will know it works
When two people in the same city, who would never otherwise have spoken, keep a conversation alive for days, one reply at a time.
P.S. Full disclosure: part of why I rebuilt it was that I wanted an excuse to try Rust on Vercel. The API is one axum function on Vercel's Rust runtime, which is still in beta as I write this.