VCB News
& Post Headline

Your vibe-coded app can get sued for $100K before it makes a single sale. 6 traps hiding in most AI-built apps: Signup never asks for age + COPPA: up to $53K per child under 13 Google Fonts loaded from Google’s servers → a Munich court made a site pay €100 to ONE visitor for leaking their IP (GDPR) Session replay on by default → recording keystrokes can count as wiretapping in California (CIPA): $5K per session “We launched” email with no unsubscribe link or postal address → CAN-SPAM: up to $53K per email Subscription checkout without renewal terms next to the button → in California, renewals can count as a gift you have to refund No registered DMCA agent (it costs $6) → you lose safe harbor for user uploads: up to $150K per stolen image The word is PER. Per visitor. Per session. Per email. That’s how zero sales turns into a hundred grand. The fix: paste this into Claude 👇 “Audit my app for these 6 legal risks and fix them: add an age gate to signup, self-host my fonts, turn off session replay (or add consent + input masking), add an unsubscribe link and postal address to every marketing email, show renewal terms right next to the subscribe button and walk me through registering a DMCA agent.” Save this before you launch. Following me is the cheapest co-founder you’ll ever hire. Not legal advice. Talk to a lawyer about your specific situation.

Part 1 (親ポスト) Day 1/ We have optimized the default speed to be ~50% faster across GPT-6 Astra and GPT-6.1 Sol through the subscription across all our products and partners using Sign in With ChatGPT (including OpenCode, Pi, Amp, Devin, ...). No changes needed on your end and this should be felt within the next two hours. Part 2 Reaching 50 TPS instead of 30TPS, with also the most optimized tokenizer out there. And the models are quite the efficient ones in terms of number of tokens needed to get things done! https://x.com/thsottiaux/status/2107159119107146237

We'll be spending a lot more time trying to understand the outputs of language models. A few thoughts, tips & tricks: Writing. Something I've had success with: Ask your LLM to explain something in ASD-STE100, it's a controlled language specification originally developed for aerospace maintenance documentation. LLMs well-versed in this language and it comes with heavy constraints on clean writing style that I often find a lot more readable. Sometimes I've tried to soften it a bit e.g. ask for "80% of the way to ASD-STE100" because the spec is quite stringent. But even better: Diagrams / images. Instead of writing, ask your LLM to create a diagram. These can be a lot easier to process, parse, and understand. But even better: Web pages. Ask for output "in HTML" to get a beautiful, interactive webpage. LLMs are getting really good at frontend and can create beautiful experiences, animations, etc. But even better: Explainer videos. The output format I am most bullish on is fully custom / bespoke explainer videos generated on any arbitrary topic. Experiment with things like "Create a 3b1b style video explainer on X. Use my ElevenLabs API key for audio narration". (you'd need an API key for the latter or you can ask your LLM to find you decent free alternatives that use your local compute). This is actually starting to work! In summary: - As LLMs get better, they will do more and more of the legwork autonomously, and a lot more of our work will rise up the abstractions into oversight and understanding. - Luckily, LLMs can help here too because as intelligence and code are increasingly abundant, you can ask for large, custom, discardable software artifacts (e.g. web apps, video explainers) that would have never made sense to create before. Push the boundaries here and you'll be surprised.