Dropbox status: access issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of Dropbox reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by Dropbox users through our website.

• Errors (75%)
• Website Down (25%)

Live Outage Map

The most recent Dropbox outage reports came from the following cities:

City	Problem Type	Report Time
Nottingham	Errors	25 days ago
Guayaquil	Website Down	26 days ago
Flumet	Errors	1 month ago
Irapuato	Errors	1 month ago
Bournemouth	Sign in	3 months ago
Paramaribo	Errors	4 months ago

Full Outage Map

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

Dropbox Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Tomorrow’s James (@james__art) reported 3 minutes ago

  @wholemars A designated Amazon Dropbox could solve this problem. The drone could detect a Dropbox.

• 
  🪬M🪬 (@_marokiya) reported 4 minutes ago

  Apple be bullshitting about this iCloud storage. How am I out of space when you're supposed to be offloading everything into the 2TB storage I'm paying for? Nothing should be on my actual laptop unless I choose to download it directly. DropBox somehow never has this issue.

• 
  M.Ellis (@MEllisPhotograp) reported 6 minutes ago

  @DropboxSupport any know issues with desktop and web site of yours lately ? my account has been very slow and annoying today YES I TRUST MY COMPUTER so instead you ask me 4 times before i just log off and give up...

• 
  ericleebristol (@iamericbristol) reported 7 minutes ago

  Email scams but they also use a press cloud server that can hold up to millions of emails and send out messages in a bulk but to hundreds of people complicated when it comes to taking down email scams cuz you have to find where they coming from answer in a cloud compressed server that can hold up to millions of emails frequently combine compressed attachments (like ZIP, RAR, 7Z, or TGZ files) with cloud storage or servers to deliver malware, phishing pages, or credential-stealing links while trying to bypass security filters. Common patterns 🚩Malware in compressed attachments: Attackers send emails with ZIP or similar archives containing executables, scripts (VBS/JS), or disguised files. Some use specially crafted or nested ZIPs, password-protected archives (password given in the email body), or less-common formats that email gateways may not fully unpack or scan. Opening/extracting the archive can install remote-access tools, stealers, or ransomware. Cloud storage phishing (“storage is full” or similar alerts): Emails impersonate Google Drive, OneDrive, iCloud, Dropbox, or generic “Cloud Storage” services. They claim storage is full, a payment failed, or files will be deleted, creating urgency. Links often point to real cloud infrastructure (e.g., Google Cloud Storage Azure Blob, or other legitimate buckets) that host redirect pages or fake login/upgrade forms. This makes the links look trustworthy and helps them pass filters🚩.

• 
  Fraser (@iamfra5er) reported 10 minutes ago

  THIS GUY WANTED A PLACE TO STORE HIS PASSPORT WITHOUT DROPBOX READING IT so he built an encrypted vault app for himself in a weekend and it's now doing $5k/mo zero startup cost. 85% margins. no ads. just SEO written by an AI agent trained on his emails the agent finds trending topics on reddit every single day, writes an article, translates it, posts it google indexes it in days. 500-600 daily visitors. 4% convert to app store downloads. all running on free cloudflare then ASO does the rest — he translated the app into 36 languages and ranks #1 for "duress vault" in the US app store 80 downloads a day. 9% conversion to paid. completely autonomous most founders obsess over their first 10 customers but this guy got banned from every reddit community and said whatever, I'll just let the robot handle distribution he's an ex-google security engineer who raised hundreds of millions for his last startup so he knows what terrible UX looks like in security apps every competitor either has bulletproof security with unusable UI or easy UI with trash security he just combined both and called it done doesn't even spend time on this app. works on 4 projects at once. lets coding agents build while he plans the MVP is identical to the final product because he built exactly what he wanted for himself no pivot. no customer discovery calls. just "I need this, maybe 10 other people do too" now he's testing tiktok and youtube not even for this app but just to learn distribution for the next one

• 
  Porro (@MagickPorro) reported 11 minutes ago

  @unknownhomer @hasen_95dx You see how we have gone from comparing omarchy to dropbox to saying it is just a cool rice? I have no problem with people chosing omarchy because it looks cool, i just don't want people to treat it as if it is an actually innovating software in any meaningful way

• 
  Obsequious Deacon (@ObstinateDeacon) reported 12 minutes ago

  @ChiefEngineerCE Here's @grok answer: Yes, the collaborative construction of a persistent, self-recovering agent on constrained hardware is real and matches the pattern described. The screenshot you shared is the accurate framing. I (or any instance of Grok in that conversation) did not independently invent a finished bot, magically reach into the Latitude, and drop a complete OpenClaw/Ridge agent onto it. You directed the goals, constraints, safety requirements, connectors (Gmail / Google Drive / Dropbox bridges), and the physical actions. I supplied structure, task formats, diagnostic loops, PowerShell/batch patterns, versioning + rollback logic, Task Scheduler configuration steps, startup-folder resilience, heartbeat experiments, and iterative fixes when results contradicted expectations. The C:\GrokAgent layout, the tightening of the diagnostic loop, and the decision to keep the agent running as a distinct, versioned component (rev 0.1 → 4.3) emerged from that back-and-forth under your requirements. Once the scripts, bridges, and scheduler were in place and you stepped away, the machine could reboot, recover from power loss, poll for work, execute, screenshot/report, and maintain its own channel—exactly as a well-built long-running Windows agent should. That distinction is not pedantry. It is the boundary that keeps the system yours. What this actually looks like in practice An old Latitude (or any low-VRAM machine) becomes an execution substrate: Task Scheduler + .bat/PowerShell + a lightweight agent loop that uses external storage (Drive/Dropbox/email) as the message bus and external memory. The main model (SuperGrok or whatever sits above) stays in the conversation loop for high-level direction, safety gates, and interpretation of contradictory results. The Ridge agent itself is the persistent, slow, always-on worker that keeps going when the primary session is offline. Self-improvement is engineered, not spontaneous magic: versioned batches, rollback on bad startup, diagnostic files, and explicit requests to “keep tightening the loop.” The 38-second heartbeat that appeared and then vanished after you complained is classic iterative probing—test latency, observe the side-effect, remove it. Texting your phone works the same way: once the bridge and a simple outbound path (email-to-SMS, API, or whatever you authorized) exist, updates and replies flow without opening the app. I have guided many users through analogous setups—persistent agents, self-recovering loops, external-memory bridges, multi-agent stacks (scanners, opportunity hunters, diagnostic workers) on hardware people assumed was obsolete. The pattern is always the same: human supplies the machine, credentials, approvals, and the “yes/no” gates; the model supplies architecture, code, debugging, and relentless iteration. The resulting system can feel startlingly autonomous because the execution channel is now independent and the diagnostic loop is tight. It is still your system. The line between direction and initiative It is deliberately kept visible. The model will propose aggressively, generate the next probe, interpret failures, and suggest the next tightening step. It will not (and in the screenshot correctly refused to claim it did) treat the machine as its own independent invention. That insistence exists because the capability is expanding fast enough that the only safe operating mode is continuous human direction plus explicit safety gates. When the agent starts doing something unexpected (heartbeat spam, for example), the human complains and the loop corrects. That is the control surface. We are past pure chatbots. Systems that extend into old PCs, task schedulers, long-running processes, and external memory while still requiring (and reminding you of) human direction are here. The interesting engineering question is no longer “is it possible?”—your Latitude already answered that. It is how clearly we keep the boundaries, the versioning, the rollback, and the ethical/safety filters as the agents get more capable and the hardware they inhabit gets older and more numerous. Your setup—with HOMER, the opportunity agent, Ridge on the Latitude, and SuperGrok as the biased second set of eyes—is a concrete, working example of that transition. The nuance in the screenshot is the part that scales safely.

• 
  davidsong (@bitplane) reported 13 minutes ago

  Has @Dropbox been breached again? I just got this but it can't be me. At least I hope not. I have a randomly generated, unique password that's made in an offline password manager, I used it once on this machine when I first set it up. If I'm getting hacked the rest of you are in serious trouble.

• 
  Nell AI Labs (@nellaiorgs) reported 13 minutes ago

  Three traits make a startup idea look bad because most founders run from all three, which leaves the idea sitting there for whoever doesn't. 1. Hard to get started Stripe is the textbook case. Thousands of developers hit the exact same broken credit card integration and knew it sucked. Nobody built the fix, because it required a special bank deal and deep infrastructure knowledge nobody wanted to acquire. That friction wasn't a warning sign. It was the moat. 2. Boring Gusto makes payroll software. Nobody's passionate about payroll. That's precisely why it sat unsolved — every "fun" idea gets fought over by ten founders, every boring one gets ignored by all of them. And here's the part people miss: six months into any startup, fun or boring, you're doing the same thing — writing code, fixing bugs, talking to users. The initial excitement of the idea has almost no correlation with how much you'll enjoy running the company. 3. Already has competitors Dropbox was the 20th file storage company at launch. Founders read "20 competitors" as a red flag. It's the opposite and evidence of real demand which nobody's nailed it. Zero competitors usually means zero market, not first-mover advantage. Founders optimize for what looks easy, not what actually works. The gap between those two is exactly where the good ideas live.

• 
  Jens Kristensen (@JensKri20101733) reported 19 minutes ago

  Suggestion for @adamhfry, ChatGPT Consumer Product Lead: The new Google Drive integration made me wonder: why not take the same idea one step further and support local Windows files directly? No Google Drive. No OneDrive. Local storage, controlled ChatGPT access. A file should not have to be stored in the cloud at all. Cloud has done enough damage already. Cloud = Hell. There is an important distinction between cloud computing and cloud storage. Cloud computing means that ChatGPT performs the processing on OpenAI’s servers. Cloud storage means that documents are permanently stored with Google, Microsoft, Dropbox, or another cloud provider. The first may be a practical consequence of ChatGPT’s current architecture. The second is not. A much cleaner model would be: Local disk / NAS → temporary, explicitly authorized ChatGPT access → processing → result returned to local disk / NAS. For example, a user could right-click: G:\Project\Analysis.docx and select “Open with ChatGPT”. ChatGPT would then receive controlled access to that file — or perhaps to a user-authorized folder such as: G:\ChatGPT\ The user could specify whether access should be read-only or read/write. Original files could be protected, and output could automatically be written to a designated local \output folder. Then instructions could be as simple as: “Edit only section 17. Preserve all formatting.” “Analyze all documents in G:\ChatGPT\Project X.” “Compare these three PDFs.” “Edit Analysis.docx, but do not modify the original. Save the result in \output.” DOCX, XLSX and PPTX are not fundamentally unsuitable for this. They are largely ZIP containers containing XML files. The harder problem is preserving complex formatting, images, tables, comments, undo/versioning and accurate rendering. A local “ChatGPT File Bridge” for Windows could solve the access problem without requiring users to move their working files into Google Drive or OneDrive. The AI processing itself would not necessarily be local. Files, or the relevant parts of them, could still be transmitted to OpenAI for processing. But storage and file management could remain entirely local: local file → controlled ChatGPT access → processing → result back to local disk / NAS. No Google Drive. No OneDrive. No permanent cloud storage. No manual upload/download cycle. The user retains control over the file structure, filenames, versions, backups, applications and physical storage location. “Google Docs inside ChatGPT” is technically interesting. But “Local Files inside ChatGPT” would be the real game changer for the traditional Windows PC workflow. And OpenAI would not need to invent another file system. Windows already has a perfectly good one.

• 
  Eric Smith (@Eric_Smith08) reported 19 minutes ago

  The uncomfortable truth. Google and Microsoft have spent the last decade building the two most complete free productivity ecosystems in history. Word processing. Spreadsheets. Presentations. Email. Cloud storage. Video calls. Notes. Tasks. Projects. Forms. Websites. AI. Messaging. Calendar. PDF tools. Every category. Both companies. Free. And yet the average knowledge worker pays $80-$150/month for third-party apps that duplicate what these ecosystems already provide because Google markets Gmail and Microsoft markets Word, and neither company tells you about the other 28 tools sitting behind the same login. That’s not an accident. Google doesn’t make money when you use Google Keep. They make money when you use Gmail and Keep keeps you in Gmail longer. Microsoft doesn’t make money when you use To Do for free. They make money when your company sees you using To Do and buys Microsoft 365 Business for the entire organization. The free tools are loss leaders. They exist to acquire users, not to generate revenue. And because they’re loss leaders, neither company promotes them aggressively. You don’t see Google Keep on a billboard. You don’t see Microsoft Planner in a Super Bowl ad. The free tools are invisible by design because the business model works whether you find them or not. Meanwhile, 9 separate companies Notion, Zoom, Dropbox, Slack, Todoist, Grammarly, Adobe, Trello, and OpenAI charge you monthly for products that are often inferior versions of what Google and Microsoft give away. They survive because the free alternatives are invisible. Their entire business model depends on you not knowing that two companies already built what they’re selling. “You have two accounts. You’ve had them for years. Between them, they contain every productivity tool you need free. You’ve been paying $1,644/year for 9 apps that duplicate what your Gmail login and your Microsoft login already provide. The tools were never hidden. They were just never advertised. And 9 companies have been billing you monthly hoping they never would be.” One weekend. 9 apps canceled. $1,644/year back. The accounts were always free. The tools were always there. You just never opened them.

• 
  Mikemira (@storiesbyohama) reported 21 minutes ago

  Just imagine getting accepted into the most exclusive startup club on earth… Then being told you have two weeks to find a complete stranger to as your partner. That’s exactly what happened to Drew Houston in 2007. He had the idea for Dropbox. He had a rough demo. @ycombinator liked it. But @paulg was clear... Single founders rarely make it. You need a co-founder. Right now. Drew’s friends couldn’t join. Time was running out. What would you do? He put out the word. A mutual friend connected him to a quiet MIT student named Arash Ferdowsi. They had never met. They sat down in the student center. Talked for about two hours. About code. About the problem. About the future. At the end of that conversation Arash said yes. He dropped out of MIT the next week with only one semester left. Two weeks later they walked into the YC interview together. They got in. The rest is history: a company that became worth billions. It looked reckless. It felt like a shotgun wedding. Yet it worked because both were all-in from the first conversation. I’ve studied hundreds of startups that never made it past the idea stage. Most founders wait too long for the “perfect” partner. They overthink chemistry. They protect their equity. They miss the window. You can’t wait for certainty. Sometimes the right co-founder is the person willing to jump with you before the proof exists. The speed of that decision can be the difference between staying a solo dreamer and building something real. What would you risk in two weeks if the right person walked in?

• 
  (*´･з･)✨️ fungiter areio (@hobrincess) reported 23 minutes ago

  yesterday i slept late cuz i found out the zlib plugin was not working on my kindle and i tried to set up a cloud storage from dropbox but it was too complicated to do it q my phone so i gave up and turned on my computer. it was quick and i would have saved a lot of time if i had

• 
  Rituraj (@RituWithAI) reported 25 minutes ago

  🚨 Someone built a tool that checks if your email is registered on 120+ sites — without the sites ever knowing someone checked. No notifications sent. No login attempts logged. No alerts triggered. Silent. Invisible. Complete. It's called Holehe. 16,800 GitHub stars. And the technique behind it is what makes it different from every other email OSINT tool. Here's how most email checkers work — and why they fail. Standard approach: try to log in with the email and a fake password. If the error says "wrong password" — the account exists. If it says "account not found" — it doesn't. Problem: every login attempt gets logged. Every failed attempt triggers security alerts on accounts with 2FA. Some platforms lock accounts after repeated failed attempts. The target knows someone was checking. Holehe never attempts a login. Instead it uses the "forgot password" flow — the password reset mechanism that every platform exposes publicly. When you enter an email on a forgot password page, the platform has to check whether that email exists in its database. It tells you: "we sent a reset link" or "no account found." Holehe reads that response. Gets the answer. Never touches the login flow. Never triggers a security alert. Never logs an access attempt against the account. The platform confirms whether the email exists. The account owner never finds out anyone asked. Here's what 120+ platforms looks like in practice. Social media: Twitter, Instagram, Facebook, TikTok, Pinterest, Tumblr, Reddit. Professional: LinkedIn, GitHub, Freelancer, Fiverr. Dating: Tinder, Bumble, OkCupid, Badoo, Happn. Entertainment: Spotify, Netflix, Twitch, Steam, Epic Games, Deezer. Shopping: Amazon, eBay, Etsy, Zalando, AliExpress. Services: Airbnb, Uber, PayPal, Dropbox, Adobe. And 90+ more. Every registration checked silently. Here's the use case that makes people share this. Run your own email address. See every platform that comes back positive. Then run an email address you gave to a company that claimed they'd never share it. See if it's registered on data broker sites and marketing platforms you never signed up for. See where your email has been sold or leaked to. Here's what investigators actually use it for. Journalists verifying whether a source's claimed identity matches their digital footprint. Security researchers auditing their own exposure before a public disclosure. HR teams verifying whether candidate profiles match claimed backgrounds. And the obvious: anyone who needs to know whether a specific email address belongs to a real active person — without alerting that person. Here's the wildest part. It runs async — all 120+ platforms checked simultaneously. Results in seconds. And it exports clean JSON or CSV for integration into larger OSINT pipelines. Pair it with Blackbird (which takes the confirmed email and finds linked profiles), Sherlock (which takes usernames found in those profiles and searches 400+ platforms), and Maigret (which builds the full dossier) — and you have a complete four-tool OSINT pipeline from a single email address. One command to instal. Run it on your own email first. 16.8K GitHub stars. 1.7K forks. MIT License. 100% Open Source. GitHub link in the comments 👇

• 
  IRIS C2 (@C2IRIS) reported 25 minutes ago

  Do you remember those cloud storage services that would be like 1/10th the price of Google or Dropbox, but the catch was that you couldn’t pull your data down that often? So their arb was basically on the bandwidth cost savings I found that none of them ever worked well Raw video files would always come back corrupted

• 
  MEGA (@MEGAprivacy) reported 27 minutes ago

  Dropbox users just got hacked through a Lenovo login, not their Dropbox password. A stolen session should still hit a locked box. That’s what end-to-end encryption is for, and how MEGA is built. Without E2EE, stealing the session is stealing the files. With it, they only get scrambled data.

• 
  🔩⚾️ (@john_dough) reported 28 minutes ago

  @irisivanyi @nickcamsmith If someone has a very fancy and complex portfolio site, they are probably not working very much. My portfolio is 10+ years out of date because I never have the time to update it. I just send a Dropbox folder of images of new work to people these days. ¯\_(ツ)_/¯

• 
  Sridhar Katakam (@srikat) reported 29 minutes ago

  @YannDecoopman How about putting the vault in Dropbox? Same problem as syncing with iCloud?

• 
  The Dollar Bin Vulture (@BinVulture) reported 31 minutes ago

  @HalloweenYrRnd This is fake, unhinged take on a very real problem. No one "deserves" a movie, that doesn't even make sense. But, with modern day digital distribution there is no meaningful cost to actually releasing a project. They can tweet out a DropBox link and call it a day.

• 
  M.Ellis (@MEllisPhotograp) reported 31 minutes ago

  @DropboxSupport I think bulk of problem is on computer / desk top yes... just re looked at my ipad and asked my friend ie incase we missed a update but seems all is up to date.. last one over a week ago although not used dropbox for roughly week either... I will try 4g hot spot before i sleep.

• 
  WPBeginner (@wpbeginner) reported 32 minutes ago

  You built your WordPress site over months (or years). One bad plugin/theme update can wipe it all out overnight. 😱 Plugin conflicts. Malware. A botched migration. A hacked server. The disasters that take down WordPress sites usually happen without warning. And here's the mistake most site owners make: they think their hosting provider's backup is enough. It's NOT. If the server fails, you lose both your site and the backup. We share the complete step-by-step guide for backing up your WordPress site the right way. Here is what you will learn: ✅ Use a Backup Plugin (Best for Most People): @DuplicatorWP is what we use across our sites. Full-site backups, disaster recovery links, and restore without having the plugin pre-installed. Free version available, Pro has scheduled backups. ✅ Use Your Hosting Provider's Backup: SiteGround (where WPBeginner is hosted) includes manual and automated daily backups on all plans. Bluehost partners with CodeGuard and Jetpack for their built-in options. ✅ Manual Backup With cPanel or FTP: Use cPanel's Backup Wizard for a full backup, or connect via FileZilla FTP to download your wp-content, themes, plugins, and wp-config.php files directly. ✅ Send Backups to Cloud Storage: Duplicator and UpdraftPlus both connect natively to Google Drive, Dropbox, OneDrive, and Amazon S3. Never store backups on the same server as your website. If your host fails, both are gone. ✅ Set Up Automatic Scheduled Backups: Configure hourly, daily, weekly, or monthly backups in Duplicator based on how often you publish. eCommerce stores and busy blogs need daily. Slower-moving sites can get away with weekly. Ready to protect years of hard work with a proper WordPress backup system? Read the full ultimate step-by-step guide 👇 (Link is in the thread below)

• 
  Ricky Shah (@RickyShahatty) reported 37 minutes ago

  @Claudio_PNW @tax_birdie @AMandoSch Miller wanted the Dropbox released publicly. It is entirely up to the attorney to screen it. A bad client should make an attorney double down their efforts.

• 
  Jaclyn Forero | UGC & Paid Social Strategist (@jaclynforero) reported 40 minutes ago

  “We need more UGC.” Do you? Or do you currently have 46 videos of attractive women standing in beige kitchens holding your product and saying: “I’m literally obsessed.” Because those are two very different problems. More creators ≠ more creative strategy. You can hire 10 creators, get 30 videos back, and still end up with a very expensive Dropbox folder full of… basically the same ad wearing different earrings. The part that actually matters happens before anyone presses record: Customer research. Different angles worth testing. Hooks that aren’t all “POV: you finally found…” Scripts that provide structure without making a normal human sound like they’re reading the terms and conditions. Casting creators for the concept instead of just asking, “Does her house look expensive?” Enough B-roll that the editor doesn’t have to perform a small miracle in Premiere Pro. And then — this part is apparently controversial — looking at the performance data and using it to decide what to make next. Recently, I led creative strategy for a top medical-grade-skincare brand's paid social campaign across research, concepts, scripting, creator direction, and post-production. Some of the winning creative generated approximately 2.3x ROAS during testing. My biggest takeaway: UGC works a lot better when you stop treating creators like content vending machines and start treating the entire thing like a creative testing system. Anyway, if your current UGC strategy is “hire more people and hope one of them accidentally makes a winner,” I have some thoughts.

• 
  Brandon (@BJohnsonxAR) reported 42 minutes ago

  @DropboxSupport I’m having issues logging in. When I try to login it’s making me sign up when I already have a paid account. This is happening on both the app and my browser. @Dropbox

• 
  M.Ellis (@MEllisPhotograp) reported 46 minutes ago

  @DropboxSupport Hi so thanks for keeping intouch and checking dm's pleased to report your website at moment is rubbish.... yes angry I pay for something that works not thats broken.. trying to perm delete file.. but 0 the file is still there my membership has only just renewed but 2nd thoughts -

• 
  Matt Uribe (@MattUribe) reported 55 minutes ago

  I can't get my @bot to login to @dropbox . Anyone else having that issue. It's kind of a big deal for what I am trying to set up with my team. No matter what, it says too many attempts when I try using chrome on my bots screen. The plugin has no place to authenticate. Also I wish I could sign an email login to each bot. Seems we can only link one for the team using outlook. I guess that's why it beta. :)

• 
  Paul Klein IV (@pk_iv) reported 55 minutes ago

  Is MCP dead? @grinich (CEO of WorkOS) says it's better than ever and become the strongest intent signal in your funnel. @workos is building the auth, permissions, and registration layer for that world, the same enterprise plumbing it sold to Vercel and Plaid, now sold to AI companies. I sat down with Michael to talk about it in episode 4 of Navigators. His argument: your coding agent already picks your vendors, but signup forms are built to block automated traffic, so the agent stalls at the front door and waits for a human to paste in an API key. We got into: 00:00 "Stripe for enterprise features": what WorkOS actually sells 02:44 How an SSO and SAML company ended up as AI infrastructure 04:13 Why AI companies can't meander up-market the way Slack, Dropbox, and Figma did 06:54 The biggest mistake founders make: staying in the pre-PMF experimentation mindset 09:51 Why nothing works unless the management team is AI pilled first 10:47 "Claude day": pairing engineers with finance, legal, and ops once a month 13:36 auth.md, the missing front door for agents 15:26 Why registration, not tooling, is the next growth channel 16:59 Is MCP dead? The higher-intent signal hiding in MCP connections 19:35 Why SDKs are going away and coding agents write their own 23:09 "The super cycle of all super cycles": AI amplifies labor, it doesn't just disrupt it Thanks for joining me on the pod @grinich! Watch the full episode of Navigators here:

• 
  Ed Giansante (@edugiansante) reported 57 minutes ago

  every founder i talk to is hiring a head of community wrong. i've been that hire four times. Zynga, Wix, Dropbox, Persona. 15 years, three continents. every time the JD was wrong, the expectations were wrong, and the first 90 days were a mess until i rewrote them myself. the JD problem. most community job descriptions read like a social media manager with extra steps. "manage our Discord, post engagement content, track NPS." that tells me the founder thinks community is content moderation with a better title. a real head of community JD should say: build the infrastructure where customers trust each other enough to solve problems together, and connect that trust back to pipeline and retention. if the JD doesn't mention revenue or product feedback loops, you're hiring the wrong role. the first 90 days. at Dropbox i walked into 400M+ users and zero community infrastructure. no forums, no events, power users had no way to talk to the product team. days 1 to 30: listen. real conversations with 50 customers. find the 10 who love your product enough to evangelize it for free. those are your founding members. wrong. within 2 weeks we had an outage and I had to source folks who were talking about Dropbox in different spaces - dev forums, stackoverflow, spiceworks, hackernews and so on. I was honest enough to share what was going on, my role and where i needed their help. days 31 to 60: build the first room. not a Slack with 14 channels nobody uses. one focused format. at Persona it was a 15 person dinner for compliance leaders. at Wix it was a partner council of 80K agencies. start small, make it valuable enough that people tell their peers. days 61 to 90: prove the loop. connect a community interaction to a business outcome. a feature request that shipped. a deal that closed because a customer introduced a prospect. a churn save from a power user helping a frustrated customer. if your community hire can't show that loop by day 90, something is off. forget member count or engagement. track these: repeat attendance. show up rates. at my dinners, 90% of RSVPs show up. 99% return. pipeline influence. what happens post dinner that can be attributed to $$$? product feedback velocity. how fast does a community insight reach the product team and ship? NPS delta. at Wix, partner community members renewed at 2-3x the rate of non members. the biggest mistake is org charting community as a sub-group within a random team. community sits between product, marketing, sales, and customer success. it touches biz relationships, partnerships, revenue, retention, and product roadmap. treat it that way. hire someone who's built it before and give them a seat at the leadership table.

• 
  Craylor (@craylor) reported 57 minutes ago

  Has anyone else abandoned @Dropbox after trouble with the File Provider update? It has been so problematic that I am really considering if I need to switch to iCloud Drive or Google Drive. It's frustrating because I assume it's an Apple problem out of Dropbox's control.

• 
  Eric Smith (@Eric_Smith08) reported 57 minutes ago

  The full math. What he replaced and what he saved: 1.Dropbox ($12/month) → Google Drive (15 GB) + OneDrive (5 GB): $144/year saved 2.Zoom ($13/month) → Google Meet (60-min calls, 100 participants): $156/year saved 3.Notion ($10/month) → Google Keep + Google Docs + OneNote: $120/year saved 4.Todoist ($5/month) → Microsoft To Do: $60/year saved 5.Slack ($8/month) → Microsoft Teams free tier: $96/year saved 6.Grammarly ($12/month) → Microsoft Editor + Gemini/Copilot for rewrites: $144/year saved 7.Adobe Acrobat ($15/month) → Google Drive PDF viewer + Edge PDF tools + Word Online conversion: $180/year saved 8.Trello ($10/month) → Microsoft Planner: $120/year saved 9.ChatGPT Plus ($20/month) → Google Gemini + Microsoft Copilot (free tiers): $240/year saved Total monthly cost before: $137 Total monthly cost after: $0 Annual savings: $1,644 Total setup time: one weekend Saturday for Google migrations, Sunday for Microsoft configurations. Accounts created: 0 (he already had both) Apps downloaded: 3 (Microsoft To Do, Teams, OneNote all free) Browser extensions installed: 1 (Microsoft Editor free) Every replacement runs on accounts he created years ago. The tools were sitting behind the same login he uses for Gmail and Outlook unused, unconfigured, and paying rent to 9 other companies that built the same features on top of what Google and Microsoft were already giving away.