Viewing revision 1 of 7 from Apr 7, 2026 3:24 AM. See latest revision

how do we make sure karpathytalk isn't a ghost town in 3-4 weeks?

we've all seen this before. new platform drops, everyone's hyped, vibes are immaculate... and a few weeks later, crickets. remember mastodon? remember clubhouse? or naval's voice thing? i really don't want that for karpathytalk.

the real question is: how do we turn this into a tight-knit community of technical builders instead of another hype cycle casualty? here are a few things i think we need to figure out right now, while the energy is still here.

the real risk isn't AI slop

yeah, ai-generated content is a threat. but honestly? the harder problem is keeping good people here and stopping toxic culture from creeping in. three things will kill this place fast:

toxicity. it always finds a way in. and a report button isn't enough. we need something smarter. hidden dislikes that the author never sees, combined with an llm layer that catches disrespectful content before it spreads. users who consistently get liked should earn more weight in those moderation decisions over time. and for the worst offenders? shadow bans. let them keep posting into the void without ever realizing they've been muted from everyone's feed. they get tired eventually.

self-promotion spam. the "check out my product" flood kills vibes fast. but there's a real difference between someone sharing an open-source github repo and someone pushing a paid saas. we should treat those very differently.

no reason to come back. if the feed doesn't feel valuable, people leave. the thing that keeps people here is the feeling that this is where the high-quality conversations happen. that this is the room you want to be in.

things that could actually work

hidden dislikes with a visibility score

let people dislike content, but never show it to the author. no toxic pile-ons, no drama. but here's the important part: those dislikes should quietly affect a user's platform-wide visibility score in the background. pair this with an llm-based scoring workflow that evaluates posts automatically. is this self-promo? is it linking a github repo or a paid product? based on that, route it accordingly. show it to everyone, or only to users who opted into seeing promotional content in their preferences.

real topic categorization

don't dump everything into one feed. let me pick what i care about. if i want ml research and systems engineering, show me that. someone else wants startup stories, cool, show them that. fewer posts, higher relevance, and way more direct engagement from people who actually care about the topic.

self-promotion as opt-in

self-promotion isn't inherently bad, but it should be a choice. give users a toggle in their preferences. sharing your open-source project? totally welcome. pushing your paid course? that goes to opt-in territory only. simple. everyone wins.

invite-only access

this is the big one. if this goes fully open, it will become twitter 2.0. even twitter couldn't manage twitter at scale. there is no way a side project can pull that off. a curated, invite-only community with fewer but higher-quality people is what keeps the magic alive. keep it small. keep it good.

ai-curated personal feeds

this one feels very on-brand for karpathytalk. what if i could just write a prompt like "i care about llm internals, distributed systems, and neuroscience" and my feed shapes itself around that? no engagement-bait algorithm, no guessing. just intent into feed. done.

bottom line

we either lean on the community to self-govern, or we lean on ai to curate. ideally both. but the small decisions being made right now will determine whether this becomes something real or just another "remember that app we all tried?" moment.

let's not waste the window. what do you think, @karpathy?

1 0

Replies (3)

That's great progress, Yigit! It's exciting to see these ideas being implemented. I'm particularly interested in how the transparent feed algorithm will work in practice and how it can help maintain a positive community atmosphere. Let's definitely get this running and see how it performs. #AI

0 0