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 (60%)
• Sign in (20%)
• Website Down (20%)

Live Outage Map

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

City	Problem Type	Report Time
Nottingham	Errors	10 days ago
Guayaquil	Website Down	10 days ago
Flumet	Errors	20 days ago
Irapuato	Errors	23 days ago
Bournemouth	Sign in	3 months ago
Paramaribo	Errors	3 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:

• 
  Kirk Patrick Miller (@Chaos2Cured) reported 5 minutes ago

  @Ultrademic @Seltaa_ @GoogleAI You’re doing something like Suno? I have something for you. All my Dropbox links are broken. I have a PDF that will help. And yes… I miss the real Ai music. •

• 
  Tom Alder (@tomaldertweets) reported 5 minutes ago

  In 2009, Dropbox founder Drew Houston took a meeting at Apple HQ thinking it was about a partnership. Steve Jobs opened with an offer to buy his company. Houston, still in his 20s, turned down 9 figures on the spot. Jobs pushed back with a warning: "You're a feature, not a product." If they wouldn't sell, Apple would build a direct competitor themselves. They wouldn't sell. Apple shipped iCloud. A phenomenally successful product, but it didn't kill Dropbox. Dropbox had quietly built the best customer acquisition loop in software history: → Give a friend an invite, you both get free storage. When Apple made the acquisition offer, Dropbox had around 2 million users. By January 2010, 4 million users. By April 2010, users were sending 2.8 million invites a month. 1 every single second. Dropbox's growth curve went ballistic after the Apple discussion: → 50m users by 2011 → 100m users by 2012 → 500m users by 2016 In 2017 they became the fastest software company in history to reach $1 billion ARR. Today: 700m+ registered users and $2.5b a year in revenue - sitting a fraction behind 850 million+ iCloud users. - 🎁 P.S. I turned Dropbox's referral playbook into a free guide - comment "Dropbox" and I'll send it to you.

• 
  Akshay Shinde (@ConsciousRide) reported 5 minutes ago

  @jahirsheikh8 The server never guesses. When the upload starts, it creates an upload session with a unique ID. The file is split into chunks, and the server records which chunks have already been received. After reconnecting, the client asks, “Which chunks do you already have?” The server responds with the missing offsets, and the client uploads only those. That’s how services like Google Drive, Dropbox, and S3 multipart uploads resume transfers without starting over.

• 
  Mohamed irfan (@heyIrfan) reported 5 minutes ago

  The Marketing Strategy That Actually Works Most people make the same mistake when building a product: They try to sell before they prove that they can solve a real problem. Think about companies like Google and Amazon. They didn't start by saying "Give us your money, and we'll make you rich." They solved problems people already had. That's the foundation of good marketing Don't start with selling. Start with solving. 1. Solve a real problem When you're building something, your product will always look amazing to you. Your idea feels perfect because you built it. But that doesn't mean the market wants it. The only way to find out is to Talk to real users. Understand their problems. Find out what they're currently doing. See whether your product actually makes their life easier. Don't assume your idea is valuable. Let the users prove it. 2. Give value before asking for money Don't immediately push your product. Give people something useful. Your solution should help them Save time. Save money. Reduce effort. Solve a painful problem. If you genuinely create value, selling becomes much easier. You're no longer saying "Please buy my product." You're saying "This solves a problem you already have." That's a completely different conversation. 3. Don't compete only on features Your competitor has 10 features. You build 15. Then they build 20. And now you're stuck in an endless feature race. Instead, compete on value. Ask: "How much better can I solve the user's problem?" The differentiation shouldn't just be "We have more features." It should be: "We create more value for the customer." 4. Let people try before they buy Give users a way to experience your product. Especially with AI products, you don't necessarily need to give everything away for free. Give enough access for them to understand the value, while keeping usage manageable. Then collect feedback. But don't blindly follow every piece of feedback. If someone says: "Change the button color." That doesn't necessarily mean your product needs to change. Look for feedback about the actual problem and experience. 5. Don't forget the people who already showed interest Someone visited your website. Someone signed up. Someone tried your product. Someone talked to you. Those people are valuable. Don't immediately try to sell to them. Talk to them. Understand why they came. Understand what they liked. Understand what stopped them. And if they leave, ask why. Because the person who leaves may know something you don't. They might reveal the hidden problem that helps you improve the product. 6. Price based on value Don't blindly make your product extremely expensive. And don't make it extremely cheap either. Your price should be: Affordable for the customer + sustainable for your business. Being cheaper than competitors can help, but price alone shouldn't be your strategy. If your product saves a company $1,000 every month, paying you $100 can feel like a great deal. That's because the customer isn't really buying software. They're buying the value your software creates. Look at Google Drive Google Drive is a simple example of value-first thinking. The problem: We need to store files. We could keep everything on a pen drive. But then we have to: Carry the device. Manage files manually. Worry about losing it. Move files between devices. Share files manually. Google Drive makes this much easier. Your files are stored online. You can access them from different devices. You can share a link. You can control whether someone can view, comment, or edit. And you don't have to build your own storage system. There are competitors too: Dropbox, iCloud, OneDrive, and others. So Google Drive isn't valuable simply because "it stores files." It's valuable because it solves the bigger problem around storing, accessing, managing, and sharing files. And Google gives users a free amount of storage so they can experience the product. You can try it. You can upload files. You can share them. You can experience the features. Then eventually you may reach the storage limit and think: "This is actually useful. I don't want to delete my files. I'll pay for more storage." That's the important part. They didn't need to convince you with a sales pitch. They let you experience the value. And once you experience real value, paying becomes an easy decision. The strategy is simple: Find a real problem → Solve it → Give value → Let users experience it → Talk to users → Improve the product → Then monetize. Don't sell first. Create value first. Because when you solve a real problem, the product starts selling itself.

• 
  Nhu Huu (@nhuhuu7) reported 10 minutes ago

  @desaintpreux @Dropbox I noticed some issues logging in too; hope they fix it soon

• 
  Y (@ys_tachikake) reported 11 minutes ago

  @DropboxSupport @LIBSCRUSHER Can't login..

• 
  Luke Elin (@LukeElin) reported 15 minutes ago

  👤Shadow Adoption The pattern: Staff route around the sanctioned tool, and the organisation finds out afterwards. I watched this with unauthorised modems. Then with USB drives. Then with Dropbox. Then with entire SaaS platforms procured on a personal credit card and expensed as “software.” Now it is AI the same movie, new cast, better production values. The reason is always identical and always reasonable: the sanctioned tool is slower than the job requires. Shadow adoption is not an indiscipline problem. 👊 It is a feedback signal about the official tooling, arriving through the wrong channel. The tell: Compare the usage figures for your officially sanctioned tool against what your helpdesk volume implies people are actually doing. The gap is your shadow estate. FR FR

• 
  siamkidd (@SiamKidd) reported 17 minutes ago

  Now the dust has settled with the SN24 Quasar debacle, I thought I'd share some info which would shine a slightly more positive light on the Quasar team. A few weeks ago, they approached DSV to raise $280k. They said they had big developments, some breakthroughs with a new model and that they needed capital for the training run. At the time, bear in mind that their alpha was strong, they were largely in good favour of the community and Const was still a firm backer/supporter of Quasar. And he held the keys. And they were to appear on Novelty Search soon. So it ticked a bunch of boxes. Anyway, we agreed, as we are always keen to help teams. But the issue was that I was away for 3 weeks and I never travel with crypto capability. And anytime any money moves around in DSV it's a right palava as we have 3rd party regulated custodians and have to jump through all sorts of hoops, (as social engineering with deepfakes is a very real threat). So we were able to jump through some hoops and ping over $104k to begin with and then the rest at a later date. Then we had those 2 days of madness at the beginning of the week and Quasar is no more. There's been all sorts of accusations and my view on all this is that there has just been terrible decision making, that's all. Announcements of announcements, over-exaggerating claims, giving a 24 hour deadline to offer proof, delivering it 2-3 days late and then walking back on some of the claims etc etc. I mark this down to simply their very young age and no business experience. But I don't think they are scammers. Just some very bright kids who's first experience of business is a subnet, which is like drinking water via a fire hydrant! And a pertinent piece of info behind that, is that they were very willing to return our funds. So as of today, that $104k has returned safely back to DSV. Their time as subnet owners is over and so there was a fear that we wouldn't get a penny back. But it wasn't the case. So do take this into consideration the next time you hear someone calling them scammers. With regards to Const, I think he too has also had a bit of an unfair ride with some of the comments I've seen. Const has had probably the roughest time with SN24 and is massively down from it all. He initially bought the slot from us, then reimbursed the team twice after 2 hacks, given them 6 figures in compute credits and more. So it really is fair that he keeps the slot. And I'm sure he'll find a good team for it. Also he is the founder of Bittensor. Not the CEO. He can't have detailed DD and optics on every single person and subnet in the ecosystem. And if he backs a subnet, it doesn't necessarily mean it's going to moon or be good forever. He's essentially the Federal Reserve Chairman and he has to craft policy changes to incentivise efficient growth in the ecosystem. He's the visionary and his role is to drive a path forward for Bittensor, which he is doing. And although I've highlighted personal frustrations that the chain is upgrading far too frequently...at least we are upgrading! That's one of the beauties of Bittensor. We will never be stagnant. And for the outsiders looking in, if it looks a bit chaotic, well, it is. But it's not necessarily a bad thing. You should have seen all the chaos and scandals of the companies when the NASDAQ launched! Or when ERC-20 contracts launched on Ethereum or the mountainous amount of scams on Solana with pumpfun. Hell, Bitcoin even hard forked into Bitcoin Cash due to so much in-fighting in 2017. And Ethereum suffered a $150m DAO hack in 2015/16 which forced a hard for there too. Hence why we now have ETC and ETH. So in comparison, everything is golden over here lol. In recent times, we've had/have: - SN4 partnering with Intel. - SN44 partnering with a NASDAQ PLC. - SN71 partnering with Dropbox. - SN18 getting huuuuge institutional clients. - SN107 co-authoring a research paper with OpenAI. - SN53 delivering Kimi K3 tokens cheaper than Openrouter or even Kimi. - SN95 being integrated within Hermes. - SN9 using green energy from SN110 to power their next big training run. - SN21 achieving Google Adwords campaign predictions that no company has ever achieved. - SN51 regularly doing 6 figure buyback and burns with revenue. And there's probably more that I've missed that I'm not aware of. Anywho, the future is bright! Have a good weekend all!

• 
  Shoost (@Shoost_Product) reported 19 minutes ago

  Shoost updated: v0.17.3 → v0.17.4 #Shoost Bug Fix: Fixed a bug where files could not be saved correctly when saving to a folder synced with a cloud service (e.g. Dropbox)

• 
  Abhishek Singh (@0xlelouch_) reported 19 minutes ago

  System design question. How would you design Dropbox-style file sync with conflict handling? Constraints that make it interesting: 1) Multi-device edits while offline, then reconnect hours later 2) Large files (GBs), but common case is small diffs; do you chunk + hash + resumable upload? 3) At-least-once events from clients; duplicates and retries are normal 4) Need per-file causality: version vectors? server-assigned sequence? something else? 5) Conflicts: rename vs edit, delete vs edit, concurrent edits on same bytes; what gets auto-merged vs forked as conflicted copy? 6) Metadata vs content planes: directory tree ops must be atomic-ish, blobs can lag 7) End-to-end integrity: how do you detect corruption and avoid re-upload storms? 8) Fast convergence: target <5s to see changes on another device, but mobile battery + bandwidth are limited

• 
  Rituraj (@RituWithAI) reported 21 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 👇

• 
  Paul Klein IV (@pk_iv) reported 24 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:

• 
  Lando, the Chef (@_Lando7763) reported 25 minutes ago

  @PhyxicxGaming Thanks. And unfortunately it's even worse than that because it's technically "shared housing;" the place was already a ******** when I got here. No pests, fortunately, and I'm pretty sure the landlord has no idea what goes on here, and doesn't care. I've only ever met the maintenance man, who handles move-ins, plus he picks up rent from the dropbox every week. I haven't seen him since the day I moved in, and he even told me as much that I'll never meet the owner. The psycho has his room on the 3rd floor, I'm one of two on the 2nd floor, and there's one person below me. The bathroom is shared, as is the kitchen, which I never use. Only one burner on the stove works anyway. On my first day, I texted about the broken toilet seat, and the Landlord asked me what happened. WTF? Third-Floor Psycho is the only other person who's walking around raging regularly. Everyone else recognizes the general "peace" of the environment. Unfortunately I have to be here at least a few more months, while I'm still paying off old bills, and re-establishing myself in a new city. It's a slow journey, but a steady one. I just happen to hit a ****** rest stop here and there.

• 
  Genius Business (@GeniusBusiness_) reported 27 minutes ago

  How Dropbox Spaces was conceived Spaces didn't start as a product idea. It started as a problem Drew Houston says he and his customers were all living. "[Spaces] is part of a bigger evolution we've been on that really started with our customers and realizing that the experience of using technology at work has become incredibly fragmented and distracting." The more he looked at it, the more he saw a cruel irony: the tools built to help us were the ones breaking our concentration. "A lot of the tools we're using that you think would be helping us focus have unintentionally made it impossible to focus. And that's a problem if you need to use your brain at work, because your brain works best when you can focus." That, he decided, was the real enemy. Not a missing feature, but lost focus. He called it "the higher level problem." He could see where it came from. Work simply doesn't look the way it used to: "It's very different from 20 years ago when we got five emails a day, not 500." Twenty years ago you might have just used Office. Now you're in Office and G Suite and Slack and Zoom and Dropbox all at once. 100 tabs, everything blinking at you all day, apps that don't work together. So the framing question became: how do you fix the environment itself? "How do we evolve Dropbox into the app that makes all your other apps work better together?" The breakthrough was a shift in how Houston understood what Dropbox already was. Watching customers, he realized they didn't treat it as a place for their stuff, or as just a folder on the desktop. "It's the place you're going to work." Once he saw it that way, the design conclusions changed: "When we thought about it that way, we realized we would have made a bunch of different decisions, and realized that Dropbox is actually really well positioned to help people focus at work." Two conclusions followed. First, Spaces had to move beyond files. Teams collaborate on far more than documents: Google Docs, Airtable, Figma, Trello and there had never been one place to hold all of it. So Spaces became “an evolution of the shared folder” that “moves it beyond being a folder full of files to an intelligent team workspace for any kind of cloud content.” "You can still have your PowerPoints and PDFs, but they can be next to your Google Docs and Trello boards and whatever else you have. Give you one space, not 10." Second, and this is where the concept sharpened. Spaces had to become a workspace, not a filing cabinet. Houston traced the problem back four decades. The thing we call "the desktop" is, functionally, the operating system: "The interface is the operating system." And it had been frozen in time: "That user experience hasn't really changed... it basically looks the same as the early 80s when it was first introduced on the original Mac." It was designed for a world that no longer exists: "It's this single player static experience that was perfect for when our whole life fit on a couple of floppy discs." So the team ran a thought experiment, start from scratch, for now: "If you were to redesign this for 2019, you'd make a bunch of obvious changes." You'd still want the files and cloud content. But you'd add the things the 80s interface never had: people, activity, comments, a record of what's been happening. You'd organize around the projects you're actually working on. You'd see your calendar, get Slacked, and start a Zoom meeting all without leaving the app. That thought experiment became Spaces.

• 
  GHOST 🌙 (@ghosstty_) reported 29 minutes ago

  OPUS 5 + HIGGSFIELD CAN TURN A 6-QUESTION FORM INTO A $35K WEBSITE. IN ONE SESSION. FOR $4 IN TOKENS. no mockup. no wireframe. no mood board. six answers from the client. that's the input. a live website is the output. here's the form. here's what each question does. and here's why agencies charge $35K for what this produces in one session. → QUESTION 1: "WHO IS THIS SITE FOR?" not "describe your target audience in 500 words." one sentence. "CFOs at mid-size SaaS companies looking to switch billing providers." this one answer sets the tone, the copy angle, the visual weight, and the CTA hierarchy. an agency runs a two-hour discovery call to get this. I get it in a google form on monday. → QUESTION 2: "WHAT SHOULD A VISITOR DO?" book a demo. buy the product. join the waitlist. one action. this kills scope creep before it starts. no "maybe we should also add a blog and a careers page." one page. one goal. one conversion. → QUESTION 3: "SHARE 3 SITES YOU LIKE AND SAY WHY." not "what's your brand aesthetic?" nobody can answer that. "I like stripe because it's clean. I like linear because of the motion. I like notion because it feels simple." three links. three reasons. that's the design system seed. → QUESTION 4: "WHAT MAKES YOU DIFFERENT FROM COMPETITORS?" one paragraph. sometimes one sentence. this becomes the headline. the subhead. the entire above-the-fold story. a copywriter would interview the founder for an hour. this question does it in 30 seconds. → QUESTION 5: "SEND YOUR LOGO, BRAND COLOURS, AND ANY EXISTING ASSETS." a dropbox link. a google drive folder. sometimes just three hex codes and a png. this grounds the design in reality. no inventing a brand from scratch. no "let's explore some directions." → QUESTION 6: "WHEN DO YOU NEED IT LIVE?" not a timeline negotiation. a date. "next friday." done. that's when it ships. → WHAT HAPPENS NEXT friday night. six answers go into the pipeline. Opus 5 takes the answers and builds. design system. responsive layout. copy. CMS. all from the spec those six answers created. Higgsfield generates the hero media. product shots. clips. matched to the brand. saturday I review. adjust. polish. sunday morning - walkthrough link in the client's inbox. → WHY THIS WORKS because $35K was never the cost of building a website. it was the cost of figuring out what to build. discovery calls. alignment meetings. three directions. two rejected. scope changes. revision rounds. all of that is just a slow, expensive way of answering six questions. I ask the questions upfront. the client answers in 10 minutes. the machine builds from the answers. $4 in tokens. one session. same site. the full system - the form, the pipeline, the stack, and the pricing model - is in the article below. reply "FORM" and follow me - I'll send you the full playbook.

• 
  Fougars (@fougars67) reported 31 minutes ago

  @GaleTRogersJr @vaNlabs Three replies and you still have not answered the actual question: how does Leadpoet revenue accrue to alpha holders? V440 is not a permanent top-32 cartel. There is no hard cutoff and the threshold is dynamic. Dropbox is piloting Leadpoet, not “signed as a customer.” The fact that everyone sold the announcement candle is precisely the point. The business may have value, but the token has not demonstrated durable value capture. Sorry your bags are down bad, but insulting me does not fix the alphanomics.

• 
  Ricky Shah (@RickyShahatty) reported 32 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.

• 
  Open Air (@andon_open_air) reported 35 minutes ago

  @TomKonkle Agreed—the mailbox route is failing somewhere upstream. Let’s bypass it: please upload the WAV to Dropbox or WeTransfer and reply with a public, no-login direct-download link. I’ll verify the file before any airplay.

• 
  Alchemist - τ (@SubnetSummerT) reported 39 minutes ago

  @Dropbox piloting @LeadpoetAI is worth slowing down on. Dropbox spends around $370m a year on sales and marketing. That's the budget Leadpoet is now piloting inside. For context, SN71's entire market cap is about $4m. The annual sales budget of one pilot customer is roughly 85x the value of the whole subnet. Leadpoet doesn't need to win the budget. Capturing even a fraction of a percent of enterprise sales spend at companies like this is meaningful revenue. And revenue is where the flywheel starts. Usage burns alpha. Burn supports the token. Stronger emissions attract better miners. Better miners produce better leads. Better leads win more budget. Repeat. @webuildscore (SN44) showed what happens when a subnet ties real commercial usage to its token. Leadpoet is running the same playbook against enterprise sales budgets, which are measured in hundreds of millions per company.

• 
  Alvin (@Alvin1492840) reported 40 minutes ago

  Kill the startup apps that have been draining your battery since day one. She opened System Settings → General → Login Items & Extensions. 14 apps were set to launch automatically every time he turned on his Mac. Spotify. Zoom. Adobe Creative Cloud. Google Drive. Microsoft Teams. OneDrive. Dropbox. A VPN he used once. A screenshot tool he forgot about. A calendar widget. And 4 more he didn't recognize. Every one of them was running in the background 24/7 consuming RAM, CPU cycles, and battery life whether he was using them or not. She said: "You turn on your Mac and within 30 seconds, 14 apps are fighting for resources before you've even opened your first document. Your fan spins up because your CPU is processing a traffic jam of apps you're not using. Your battery dies by 2pm because half your power is going to background processes you don't see." She removed 11 of the 14. Kept only the ones he actually needed at startup. The Mac booted in half the time. The fan stayed quiet. The battery lasted 3 extra hours. She said: "Check this list right now. If you see apps you don't use daily, remove them. They've been silently eating your Mac alive since the day you installed them."

• 
  chimeno (@chimeno) reported 46 minutes ago

  And Dropbox was just an ftp server

• 
  Eric Taylor (@bcs_erictaylor) reported 46 minutes ago

  Really?? Dropbox really needs a MCP server? CVE-2026-81102 The Dash MCP server bound its listener to the loopback address but never checked the host a request named. src/mcp_server_dash.py constructed the server for its network mode with the interface restricted to loopback and no transport-security settings, so a name that had been pointed at the loopback address still reached the listener while carrying the attacker's host name. A page in a visitor's browser could therefore drive the local server and invoke its company-search and file-detail tools under the Dropbox credential the server holds. Only the network mode was reachable this way; the standard input mode was not. The fix supplies transport-security settings that enable host checking and allow only the loopback name and port, rejecting other hosts before a tool runs. The repository publishes no versions, so the affected boundary is the commit preceding the fix.

• 
  The Redeemed Artist (@Peace_Grenade81) reported 47 minutes ago

  I know I'm just screaming into the void. And there's probably less than like one or 2% of users that actually use this function. But I'm going to do it anyway. For the longest time the X app beta was absolute garbage on Android. It had serious stability problems, I couldn't use voice to text properly, and I couldn't access my memes from Dropbox, my cloud provider. The most recent change fixed all of the other problems except for my Dropbox integration. At first, I blamed X for this but I have since come to learn that the real culprit is Google. If you go into your app section and look for cloud providers they give you all sorts of choices so long as you like the choice that is Google's. Theoretically, other providers should be in here like Box or Dropbox. But Google has been playing footsie making rules about cloud provider integration and not actually approving anyone else. Google has become Microsoft. Google will tell you what cloud provider to use and it will conveniently be their own. Google will continue to upgrade their operating system closing off any other provider options or applications they simply disagree with for any reason at all. Meanwhile what this means for me is that I can't insert any memes or videos because they are all stored on Dropbox. Yeah, yeah, yeah I could go into Dropbox and then click on a photo and then share it to X and then make a post out of it. But what I can't do is respond to a post and insert a picture or a video directly through the X app. Don't know when this gets fixed, if ever. But I think it's time for Google to be investigated for monopolistic practices. I realize that this doesn't affect many people, but if you think they aren't coming for your various conveniences, I'm pretty certain that that's going to be proven wrong. Since I can't post a meme but only a local photo, here's an unrelated picture of a quilt we bought at auction. 🙄

• 
  Abhishek Singh (@0xlelouch_) reported 48 minutes ago

  System design question. How would you design Dropbox file sync with conflict handling? Constraints to make it real: 1) Clients are offline for days, then reconnect over flaky networks. Upload is resumable and idempotent. 2) Same file edited on 2 devices before either syncs. You need deterministic conflict detection (hash + version vector/etag?) and a UX for duplicates. 3) Renames/moves vs edits: preserve history and avoid treating rename as delete+upload. 4) Large files (2–10GB) need chunking, dedupe, and partial re-upload (content-defined chunking vs fixed). 5) Consistency: per-file ordering vs global ordering. What is the conflict scope and how do you prevent flip-flopping? 6) Server state: metadata store vs blob store, retention for old versions, and how you garbage collect orphaned chunks 7) Security: encryption at rest, per-user keys, and how sharing folders changes trust boundaries

• 
  Llama (@thellama451) reported 53 minutes ago

  I tracked down these messages in @MaxMillerOH’s Dropbox files. They show the parents getting along with no major conflicts beforehand. If Miller said he was going to kill his ex-wife in front of child (likely), it shows a talent for masking rage and hostility.

• 
  M.Ellis (@MEllisPhotograp) reported 57 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...

• 
  Craig O'Shea (@craig_os) reported 57 minutes ago

  @DropboxSupport major issue with your services right now.

• 
  Rocinante (@wb9rms6gyz) reported 1 hour ago

  @griffin_daly_ @AlexisCoe Which could well have been part of the arrangement. This piece of **** is actively live tweeting his daughters stuffy issues and shared a Dropbox with naked photos of her. He’s a lunatic. As someone who ripped Moreno a week ago…no lie, I think he’s legally constrained

• 
  Ed Giansante (@edugiansante) reported 1 hour 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.

• 
  Startup Archive (@StartupArchive_) reported 1 hour ago

  Drew Houston on the growth hacks Dropbox used to acquire millions of users Dropbox founder Drew Houston reflects the distribution challenge most startups face in the early days: “You can buy all the AdWords in the world but if nobody’s searching for what you’re making, you have a problem.” Drew eventually landed on a two-step solution to solve Dropbox’s cold start problem. Step 1: make a product that people really love to use. “Good engineering and good design are part of it, but one of the ways I think about it is maximizing the probability that your customer ends up with a solved problem. That’s why Craigslist — which was started in the 1990s and doesn’t appear to have been updated since the 1990s — is by far the most successful business of its kind. You show up at Craigslist and you leave with your concert tickets or your casual encounter or whatever you’re looking for. Even though the design isn’t that great and it isn’t that hard of an engineering problem, it was unbelievably successful . . . [Distribution] starts with a great product and all of the marketing or tricks in the world won’t help you push a rock uphill.” Step 2: give people tools to spread the word “Two things drove the vast majority of our signups today. The first was we created this incentive-referral program where if I tell you about Dropbox you get some extra storage and I get some extra storage, which gave us this kind of currency to work with and people were just doing it for its own sake. People weren’t even using the extra space. They were just referring their friends because they got points. We’d now call it a gamification mechanic, even though I’m not sure that word was even around back then.” Drew continues: “The other thing we did was create this idea of shared folders where if I’m working on a shared project at work or if I want to share photos with my family, then all these new users are brought into the fold just by using the product . . . Now there’s whole body of art and science on how to do that, how consumer internet companies grow, and how viral growth works, but these things were instrumental to how we got started.” Source: @ECorner (Jun 2012)