... product sense before it was a legal question, and it's nice when the two agree. Which of your products would you have put under the emotion rule, and would you have gotten Article 50(1) right? Comment from Mona Truong(@monatruong_murror): @galdayan  Good catch, and my read did stop at text. I only worked through it for a typed-journaling product, so I haven't done the analysis for voice and wouldn't want to hand ...

... reading from acting point is especially important. Giving agents broad access by default can turn a simple prompt-injection issue into a real-world action. Least privilege + human approval for sensitive actions feels like the right approach. Comment from Mona Truong(@monatruong_murror): @_lakshmi  Thanks Lakshmi. The part that made it click for me is that prompt injection only becomes a real problem when the same agent that reads the untrusted text can also act on it. Once ... ... split those two, a bad email can at worst mislead a summary instead of sending something. Do you run any agents yourself, and where do you draw that line? Comment from Mona

... evolved. It s the kind of IDE-native documentation layer I always wished existed. I m opening early access for engineers who want to try it and shape the direction. If you re curious, here s the waitlist: codetrackerai.com Mona Hidalgo Founder & Software Engineer Mix It Hub, LLC I d love to hear: What s the biggest code understanding pain you deal with in your IDE? Your feedback will directly influence what we build next ...

... absence would stop the product doing one of its functions. If your app is a thin client over your API, that API is not a separate service you can wave at. It's part of the product. This product-versus-service line is the genuinely contested bit, and I'm reading the Commission's guidance and a pile of law firm notes rather than a court ruling. I'm a founder, not a lawyer. If you're near the boundary ... ... from Gal Dayan(@galdayan): this is genuinely useful, thank you for actually reading the ENISA FAQ instead of recycling the 2027 headline. the part I'm chewing on is where a pure telephony/voice API sits relative to your product-vs

... nobody covered, which is worse, because it changes a line of code a lot of us shipped this year without thinking about it. If your product has a "paste a URL" box, a link unfurler, an enrichment step, a competitor-monitoring job, or anything that fetches a page and hands it to a model, this is about you. What was actually measured. The paper is "Indirect Prompt Injection in the Wild" by Khodayari, Zhang, Acharya and Pellegrino, out of CISPA ... ... knew. One last thing. 65% of the pages in that dataset already contained their prompt 12 months before the analysis. This is not a new risk arriving. It's an old one you've been ingesting. Comment from Mona

... right and is more useful than either, and the revised version went up this month, so it's worth twenty minutes before you write your Q4 plan. It's NBER working paper 35275, Demirer, Musolff and Yang - "Writing Code vs. Shipping Code." More than 500,000 GitHub developers, matched against their actual AI usage telemetry rather than a survey, in a matched event study design. The headline numbers are large and I have no interest in arguing with them. Cumulative ... ... them code. However, my own rule is part of the bottleneck. I wrote it after the FAQ spent months recommending a tool for audio we already generate, so it's a brake I installed on purpose Comment from Mona

... Apple's own support pages. Apple In-App Purchase: 26%, or 15% if you're in the Small Business Program, the Mini Apps or Video Partner Programs, or on an auto-renewable subscription after the subscriber's first year. Alternative payment processing inside your app: 20%, or 10% for those same groups. Out-of-app offers with an actionable link: a 15% store services commission, or 10% for those groups, on anything bought within 7 days of the tap. Apps ... ... distributed outside the App Store entirely - an alternative

... Three numbers from it get quoted. Users who saw an AI summary clicked a traditional result in 8% of visits; users who didn't, 15%. Users ended their browsing session 26% of the time with an AI summary present versus 16% without. And the one that should matter most to anyone buying GEO: users clicked a link inside the AI summary itself in 1% of visits. One per cent. That is the click value of the thing the entire optimisation ... ... more often. Just 8% of one- or two-word searches produced one. For searches of ten words or more, 53%. For searches starting with a question word - who, what, when, why - 60%. Sit with that next to the 8%-versus

... times. I'm a founder, not a lawyer, and none of this is legal advice - but the arithmetic of which paragraph applies to you is something you can do yourself in twenty minutes, and it's cheaper than the alternative. Comment from Siarhei Hamanovich(@hamanovich): I think ,the voice note request is carrying two obligations: Your Recital 18 read is about what you infer from, and typed text isn't biometric. If a voice note ever comes back ... ... side only answers for people who come and ask me. Those are different things, and I'd rather say so than let a good record stand in for a mark I can't actually produce Comment from Mona

... could have. And I still don't have a clean answer on the verification-method question, because the honest version is that I don't yet know what I'd do differently with a government-ID-checked 16 versus a self-declared one. I'd rather say that than write a paragraph pretending I've resolved it. The thing I am confident about is narrower. The signal is sparse for a long while yet. Texas only covers accounts created after ... ... never right anywhere refusing is an option. Self declared isn't the case where you behave identically, it's the case where you should be more cautious, and throwing the field away removes your ability to be. Comment from Mona

... shape I keep running into today: the signal was never missing. It was dropped a layer above the question, and by the time anyone asked, the only evidence still in the room was the ambiguous kind. Comment from Mona Truong(@monatruong_murror): @serdarships  The 500-on-dotted-paths detail is the useful part of this and I'd never have guessed it. Discovered, currently not indexed reading identically for "we were refused", "we deprioritised you" and "your own server ... ... built around that, so the failing cases are the ones nobody has a reason to visit. I have no method for generating them rather than stumbling into them. If you have one I would take it. Comment from Mona

... real person uses is enormous, and that gap is where products in spaces like mine quietly disappear. I don't have this solved. I've just stopped assuming the name is the thing that gets found. Comment from Mona Truong(@monatruong_murror): @jernej_jan_kocica  That's a sharper version of the same problem and I hadn't connected them. A directory category is someone else's taxonomy, and if your product doesn't sit cleanly ... ... early, the request is still pending with their catalogue team. worth knowing before you try it: we asked for help desk, got declined, and their rules say a declined category can never be requested again. Comment from Mona

... destination? If the value is a result someone wants and doesn't care how they got an action then being agent-callable is close to free distribution and you should be looking hard at it before your competitor does. If the value is the experience of a person actually being there a destination then racing to become a tool call is optimizing for a future where your product's whole reason for existing has been abstracted away. Worse ... ... server fastest. They'll be the ones who were honest about whether they should and, if they did, treated that borrowed trust like it was hard to get. Because it is. Comment from Gal Dayan(@galdayan): the action vs

... Mona, a marketer turned founder from Germany. I'm building Xolora, a marketing analytics tool dedicated to solopreneurs and small business owners. I noticed that 80% of that niche is overwhelmed with their marketing and just guessing. When it comes to ads, this means that they're wasting money (around $10,000/year). And the sad truth is that there is no tool out there, that helps them. All the other marketing tools are made for marketers or big teams ... ... underserved niche. Xolora's goal is to simplify ad analytics, give back time, money and ultimately confidence. It just launched in beta and I hope that it will be valuable for its users. What is your niche? Comment from Mona

... loud and instant and mostly noise. In 2026, taking care of the builder is not self-help fluff. It's the actual bottleneck. Treat it like one. Comment from Omri Ben-Shoham(@omri_ben_shoham1): the make mode vs judge mode split is the one that actually changed something for me. i used to check analytics mid build and it wrecked the session every time, not because the numbers were bad but because i'd switch from building to defending ... ... pick it back up next day, or is there some catch-up rule? that's usually where these systems fall apart for me, not the routine itself but the recovery after the first missed day. Comment from Mona

... weight by turn 15. feels like the actual skill isn't deciding what to leave out once, it's re-deciding it continuously, which is a much harder engineering problem than just writing a tighter system prompt. Comment from Mona Truong(@monatruong_murror): @omri_ben_shoham1   Yes that's the part I underplayed in the post. Curating once is a prompt; re-deciding every turn is a system. What's helped us is treating context assembly as a step ...

... this: if building is no longer the moat, then the moat is available to anyone willing to do the unglamorous work. Knowing your person. Owning a relationship instead of renting attention. Being early to a workflow before a competitor gets embedded in it. None of that requires funding or a team. It requires you to stop hiding in the part of the work that feels productive and go do the part that actually decides whether the thing lives. Ship ... ... weekend, sure. Just don't confuse the weekend with the work. Comment from Mona

... best day, on a task you made up. Your users meet it on an average day, on the task they actually have. Build for the average day. That's the whole game now. Comment from Mona Truong(@monatruong_murror): @dalemooney   This is a sharper version of my third point than I wrote, and you're right that it has the same shape as the problem a report sensor only fires when the user already caught ... ... transcripts starts accurate and then decays, not because the model changed but because your users did. Which means it has to be refreshed from live traffic on a schedule, or in a year you have rebuilt the exact lab-versus

... inside your app if they can only feel understood while they're talking to your model you haven't solved loneliness. You've made it more comfortable to stay lonely. You've built a very sophisticated waiting room. The alternative is to design for the exit. Concretely, that means three things. Point users back at real people, not deeper into the app. The most valuable thing an emotional AI can do isn't be a better listener than your friends ... ... about: when your user closes the app, are they better off, or just less alone for the next four minutes? Your roadmap already knows the answer. The question is whether your metrics will let you admit it. Comment from Mona

... which one were you actually optimizing for? Comment from Nika(@busmark_w_nika): imo, the whole thing with AI agents is becoming oversaturated the same way as it was with AI in 2024 Comment from Stacy Wycoff(@stacywycof83995): Mona, this is the question I keep circling back to while building FounderFlow. My honest answer is uncomfortable, I want usage to go down over time, not up. If it is doing its job, a founder should need fewer of my alerts ... ... like proof of value to an investor, but for the actual founder using it, quiet is the win. How are you thinking about measuring a product that is supposed to make itself less necessary? Comment from Asad M.(@asadmalik901): Mona

... stickier feature. do you say any of that specific data to users who push back, or does explaining the 'no' stay more philosophical in practice? Comment from Asad M.(@asadmalik901): @monatruong_murror   This made my day, thank you Mona. The fact that you were already testing the gentle prompt before we talked tells me the instinct was there, you just needed the words for it. One thing I would watch as you build it: the risk with a lighter ... ... door is that it quietly becomes the default one, so the real win is if it stays the exception and hands people back to the writing quickly. Rooting for you and the team on this. Comment from Mona

... animation and 8 seconds of silence. Our engineer thought it was a bug when he first saw the spec. "You want me to add... a delay?" Yes. On purpose. Here's why. We ran an experiment: instant AI response vs. an 8-second pause before the same response. The content was identical. The only difference was time. Users who got the pause rated the AI's reflections 40% more helpful. Same words. Same insights. They just felt more considered ... ... user has a second to sit with what they just wrote before getting a response back. the pause does something to the user's own processing regardless of what they believe about the AI side of it. Comment from Mona

... agent that has the same blind spot you do is one thing, but iterating on something you can't reason about at all tends to get slower each round, not faster Comment from Omri Ben-Shoham(@omri_ben_shoham1): @Mona Truong "debug through conversation instead of through code" is a good way to put it. the risk I keep running into with that approach is the agent can answer "walk me through the data flow" confidently and wrong ... ... same time - it'll narrate a plausible-sounding flow that isn't actually what the code does. have you caught it doing that, and if so what tipped you off that the explanation didn't match reality? Comment from Mona

... forgotten isn't a privacy feature. It's a trust feature. People will only be truly honest with technology that promises not to remember everything. Has anyone else experienced this tension between data retention and user trust? Comment from Mona Truong(@monatruong_murror): @galdayan   Really sharp question. Right now each 30-day cycle produces its own summary, and they accumulate as separate entries not re-summarized into each other. We deliberately avoided compounding because of exactly the drift ... ... that itself becomes a record but at a level of abstraction where users have told us it feels more like a "mood journal" than surveillance. We're watching closely to see if that holds at 12+ months. Comment from Mona

... feeling? Comment from Gal Dayan(@galdayan): @monatruong_murror  that opt-in rate over time is the metric I'd watch too - it's basically a leading indicator for the fatigue before it shows up in journaling quality. curiosity vs being watched is a really clean way to put words to the difference. good luck keeping it that way as usage scales up Comment from Mona