... made me realize how easily these recurring expenses slip through the cracks when you're focused on building. I d love to hear from the community: What s the worst "SaaS leak" or ghost subscription you ve uncovered in your own stack? What rules, processes, or cadence do you use to keep subscription creep under control ...

... best combo imo is when you know how to merge those two into one :) Comment from Nika(@busmark_w_nika): @justinlee020617  that is build in public but I have seen how many people stopped doing it because competitors copied 1 : 1. Comment from Nika(@busmark_w_nika): @tijogaucher  Whent the problem is urgent and strong, and you have a good solution, product brand can overrule even your personal brand (in a good way), of course, it will help ... ... sometimes delay learning. Sharing earlier, even in small ways, can shape how people perceive and use what you re building. Maybe it s less about waiting vs

... Anthropic said it uncovered industrial-scale efforts by Chinese Labs ( @DeepSeek , Moonshot and @MiniMax-M2.5 ) to extract capabilities from its Claude models via distillation. According to Anthropic, the campaigns involved: 16M+ exchanges ~24,000 fraudulent accounts Proxy networks to bypass regional restrictions Targeted extraction of reasoning, coding and tool-use abilities Distillation is a common technique for training smaller models from larger ones. The controversy here is using a competitor

... better way. Most products don t start with a grand vision; they start with irritation, curiosity, or firsthand pain. I d love to learn more about how others here have navigated that journey: How did you uncover the problem you decided to work on? What signals told you this problem was worth solving? How did you validate (if at all) whether people would actually pay for a solution? Has your product stayed true to the original problem ... ... product. They asked "can you just keep doing this?" That's when I knew. So I encoded 25 years of pattern recognition into an AI forensic engine. 4-layer check credential integrity, timeline consistency, location signals, resume vs

... Reliability is still not where we need it, it's been our single product focus alongside introducing more feedback loops (first booking for both guest + host, and 3rd booking for host etc.). But along the way, we ve also uncovered some weird and wonderful truths about meetings + AI, that I've been dying to write up for fun: Time zones are fluid in natural language. Nobody says 14:00 GMT. They say after lunch or when I land ... ... just technical: they re social signals (sometimes even power moves) and identity. And finally, the big one: Meetings aren t about minutes. They re about momentum, connection, and energy. Who knew?! Building Ting is so challenging - every day we uncover