Ella Baiysbayeva

Ella Baiysbayeva

art, education & technology

Badges

Tastemaker
Tastemaker
Gone streaking
Gone streaking
Gone streaking 5
Gone streaking 5

Recently Supported

WizardNote
WizardNoteVoice notes your phone transcribes, saved as markdown
Kippy AI
Kippy AILearn languages while having fun!
Databox CLI
Databox CLIYour agentic analytics platform in the terminal
Agent Clan
Agent ClanCommand your Claude Code and Codex agents with gestures
Screen Studio 4.0
Screen Studio 4.0Glass Loupe, Camera Cutout, Edit by Transcript, and more
Starlie
StarlieA fast, native Jira client for Mac
Capecho
CapechoCapture new words on any screen & remember them with SRS
Extella.AI
Extella.AIAgentic platform that evolves & builds reusable systems

Forums

What do you check before putting a vibe-coded app in front of real users?

Genuine question for people shipping with Lovable, Bolt, v0 or Cursor. Building fast is the whole point, but the same few problems keep showing up on freshly shipped apps when you look at them from the outside: admin or debug routes left reachable, API endpoints that return another user's data if you change an ID in the URL, Supabase or Firebase tables readable without logging in, and API keys sitting in the frontend JavaScript. None of these need a hacker to find, just someone curious with a browser. So how do you handle it? Do you have a checklist before launch, rely on the platform's defaults, ask the AI to review its own code, or ship and fix later? And which of these has actually bitten you? Disclosure: I work on external recon at Xseth, so this is my day job, but I'd really like to hear what works for people here, with or without tools.

View more