... percentage says what's gone. A Lancetta suggestion says what to do about it, and shows the numbers it rests on so you can weigh it. No model is asked: it's plain arithmetic on your Mac. Slow down: "At this pace Claude stops in 51m, then waits 1h18m for its reset." Both moments, because the gap between them is the time you'd lose. Push on: a window about to reset mostly unused is quota gone

... excited about everything. Reading them was strange. The enthusiasm was real. Mine and theirs. They were actually rooting for me. They gave detailed feedback. They said "can't wait to see where this goes." Almost all of them are gone now. Not angry. Just gone

... Android rollout actually changed: Staying signed in. On some devices the system was dropping the saved session between launches: fully close the app, reopen it, and you'd land back on the sign-in screen with your subscriptions apparently gone. They weren't gone

... broken, and a couple of times it confidently rewrote logic I hadn't asked it to touch. Being a dev already, I could catch it and course-correct, but I kept thinking about how differently this would've gone for someone non-technical. Curious what this community's experience has been: Has AI ever confidently gone

... 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

... five of the six show two or more different last crawl dates across the reports before they disappeared. /blog/custom-software-development-usa-enterprise-and-startup-solutions was recrawled on 17 July, 1 August, 3 August, 5 August, 10 August and 12 August, then it was gone from the list. /blog/building-a-successful-saas-product-in-2026-from-idea-to-launch moved from a 21 July crawl to 21, 22 and 24 August and 1 September, then it was gone

... counts. Change your Gmail interface language and every [Gmail]/* gets renamed at once congratulations, everything is now twice. Skim now reconciles against what the server actually lists, follows renames (cache and all), and drops what's genuinely gone. Carefully: it won't prune on a suspicious listing with no INBOX, or while your offline ops are still in flight. Mid-sentence mailbox switches no longer eat your words. Swapping the From account rewrote the body from the database which, thanks ... ... debounced save, was a slightly stale version of your draft. Everything typed since the last save: gone

... companies that don't want to host and maintain it themselves. The technical side of the project is well underway. What we're struggling with is choosing the right distribution and business model before launching. For founders who have gone through this decision: Did open-sourcing your product actually help with adoption and distribution? Did you get meaningful community contributions, or did it mostly create more maintenance? How did you decide what to keep open source and what to monetize ...

... front of an audience. So everyone reports the ticket they had open, because that's the retrievable answer. The actual texture of the day, the part where you'd learn something about how the sprint is really going, is gone. The thing that's worked better for us: declaring intent in the morning instead of reporting history. "Here's what I'm picking up today" takes ten seconds, is answerable without memory, and produces something you can compare against reality ... ... Plan versus

... kept running into the same problem when using AI to think through startup ideas. I'd ask: "Is this a good startup?" And I'd get a very convincing answer. Market opportunity. Customer segments. Competitors. Pricing. Growth ideas. The problem wasn't that the answer was necessarily wrong. It was that the AI was answering a question that was too easy to agree with . So I started building FounderMind AI at Evolvix AI around a different workflow. Instead of asking ... ... overall verdict, FounderMind breaks the idea down and looks at it from multiple perspectives: Business Strategy does the business model make sense? Market Analysis what alternatives

... while, and I kept running into the same problem. Whenever I had a startup idea, I could ask an AI: "Is this a good business?" And it would give me a surprisingly convincing answer. Market opportunity. Potential customers. Competitors. Business model. Pricing. Growth ideas. The problem was that I wasn't really getting challenged. I was getting a very sophisticated way of making my original idea sound reasonable. That became the starting point for FounderMind AI , something we're building ... ... Evolvix AI. Instead of treating startup validation as one question with one answer, FounderMind looks at an idea through different perspectives: Business Strategy Does the business model actually make sense? Market Analysis Who already solves this problem, and what alternatives

... cell where it belongs. Example 2: Buy back the most expensive hour of your day (GitHub + Slack + Calendar Notion) Every morning starts the same: check GitHub for what happened overnight, climb through Slack, glance at the calendar an hour gone before any real work starts. Hand the whole routine over. Connectors team up on a single task, and with a schedule attached, you don't even have to ask: "Every weekday at 8:55 check overnight GitHub activity and #product ... ... digest to my Notion." Example 2: Buy back the most expensive hour of your day (GitHub + Slack + Calendar Notion) Every morning starts the same: check GitHub for what happened overnight, climb through Slack, glance at the calendar an hour gone

... cards. shipped the landing page. told everyone. a month in, a company in a different sector had already filed the trademark on that exact word. their .com. their case. i had to kill it. two weeks of brand work gone. all the copy, the deck, the emails to allies, all renamed overnight. the trademark search that would have caught this took 5 minutes. i just never did it. just ship is great advice for the product. it is terrible advice ...

... side. Drop on AirDrop and the picker opens the moment you let go. Drop on Shelf and the files wait there until you send or save them. Displays became a straight multi-select The three placement presets are gone. The Displays pane now lists every connected screen and you tick the ones that should carry an island. Clamshell users asked for exactly this: a closed MacBook driving external monitors keeps them island-free unless you say otherwise. Icons instead ... ... whole interface. Reduce Motion is honoured everywhere, with a Pulse-only switch if you want just the island calm. The battery card names your charger: charging on 68W charger, 41 minutes to full. Phantom Bluetooth toasts are gone

... Product Hunt! I m Jinny, the solo founder and developer of Crazy Sajangnim. The name comes from the Korean sale phrase , or The boss has gone crazy. It is commonly used when a store offers discounts so dramatic that the owner must be crazy to sell at those prices. That idea became the inspiration for Crazy Sajangnim: one place to discover genuinely discounted designer fashion across Korean and U.S. retailers. But I did not want to build another ...

... just me and the OP going back and forth, that is engagement, not compounding. The one thread that kept going had someone unconnected join inside 48 hours, and that window is also roughly when the other three had already gone flat. Curious if anyone else tracks this specifically, or if there is an earlier signal worth watching for before the third person even shows up. Comment from Abdullah Javaid(@abdullah_javaid3): @jernej_jan_kocica  Honest gap: I've only ... ... properly, including the boring ones, and one of those replies gave something up. that told me an argument would not be wasted here. then i wrote about the thing i actually had, which had nothing to do with position versus

... instead. That became 204 sources reviewed one at a time. Terms, robots, whether caching a snapshot counts as redistribution. Some yes, some silence, a few no, which left holes in my data I still haven't filled. Four months gone. Two competitors

... every AI coding community: an agent gets told not to touch something, then touches it anyway. it just never had a wall there, only a request in its instructions it decided didn't apply this time. Prod env vars gone, a repo gone

... pane. We were capping the message at 840px wide, which meant a big monitor bought you one skinny column of text, a lot of empty pane, and a scrollbar floating somewhere in the middle of the screen. Cap's gone. The mail gets the room. Wide emails are no longer quietly guillotined. Some senders lay their newsletters out wider than that old column allowed, and the overflow just didn't exist. No scrollbar, no hint, no right-hand edge ... ... small ouroboros of blank canvas piling up under your email, one resize at a time. 788 812 836 860, same mail. It now measures the actual content, lands flush, and stays put. Bonus side effect: with that 8px gone

... escalate" gate flag something as broken weeks ago, and every scheduled run after that just re-confirmed the same escalation without re-checking whether the original check was still true. Turned out it wasn't. The gate itself had gone stale and nobody, including me, thought to question it since it kept "agreeing" with itself. Curious if OpenClaw gives you any way to force a fresh look at a standing escalation instead of just re-reading the last verdict. Comment ...

... flopping between two setups that both feel wrong. Setup 1, babysit: I watch every command and approve everything myself. Nothing slips past me, but I'm stuck at the terminal and the whole point of running an agent is gone. I might as well be typing it myself. Setup 2, let it rip: auto-approve, skip permissions, go do other work. Faster in theory. Except I come back to one of three things. It finished 30 minutes ... ... deploys, rm, db writes?) - What is the worst thing you came back to that an agent did while you weren't looking? - And honestly, how do you tell "it's blocked" from "it's done" from "it's gone

... sharing! Comment from Anna Ludwinowski(@anna_ludwinowski): @austinbuhl  Interesting that you land on problem-first for Salestrics but demo-first as a viewer. Do you think there's a difference between what convinces you to look closer versus what you'd actually put in your own launch copy? And on "most startups" - is there a specific kind of team you picture hitting that per-seat pricing wall, or is it genuinely everyone past a certain size? Comment from Anna ... ... exactly the right swap! It's the same trap in enterprise IT and in most launches here, just dressed differently (feature list vs

... probably saw the VS Code 1.117 story: "Co-authored-by: Copilot" silently added to commits by default, including for code that Copilot never wrote. Microsoft reverted it in 1.119. Good. But the revert is the wrong ending to the right story. The developer anger was about consent and accuracy both valid. What did not get picked up in the discourse was the architectural question underneath: even when Copilot does write code, a git trailer tells you almost nothing useful ... ... capture provenance at insertion time before the diff ever hits git. Each insertion generates a structured record with roughly 40 fields: four timestamps, the full prompt body, the raw model response, 10 named capability slots indicating what was captured versus

... both content and   product work.   2. Google Search Console I basically live in it. For anything SEO, it's the only honest source of truth   about what's actually happening vs. what I assume is happening.   3. Ahrefs keyword and competitor

... code provenance does not work this way. The prompt a developer submits to Claude Code exists for a few hundred milliseconds in transit. After the model returns its response and the editor applies the change, that prompt is gone. Git records the diff. Nothing else records the origin by default. There is no reconstruct operation. I built LineageLens partly because I ran into this problem in my own workflow traced a bug to a block I had accepted from Cursor ... ... weeks earlier and had no way to recover what I had asked for. The architecture reflects this constraint directly: the Base extension (free, zero config, VS