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	6 days ago
Guayaquil	Website Down	6 days ago
Flumet	Errors	17 days ago
Irapuato	Errors	19 days ago
Bournemouth	Sign in	2 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:

• 
  Naresh Mintri (@Yogamaestro) reported 18 seconds ago

  @IncomeTaxIndia Seems like e-filing portal overloaded. Taking long to register new taxpayer, buffering. Even dropbox menus not working. Plz look into it. Thanks.

• 
  Dodz4allai (@DrGhattasMD) reported 3 minutes ago

  nstead of waiting for an API integration with Epic (which is costly and slow), OmniMed Pro deploys as a Chrome/Edge Browser Extension.3 Mechanism: Most hospital EHRs (Epic Hyperdrive, Cerner Millennium, AthenaHealth) are now accessed via web browsers (Citrix/VDI or native web interfaces). The OmniMed extension "sits on top" of the EHR window as a persistent sidebar. Data Ingestion (The "Read"): The extension uses the DOM (Document Object Model) to "read" the patient notes, labs, and vitals currently displayed on the doctor's screen. It does not need a backend integration; it reads what the doctor sees, acting as a "visual reader" similar to a human assistant. Intelligence Injection (The "Write"): The extension injects its "Co-Pilot" interface into the side of the screen. It offers "One-Click Transfer" buttons to paste generated notes, codes, or orders directly into the EHR's text fields.3 Value Proposition: This "Zero-Integration" approach allows individual doctors or departments to adopt OmniMed Pro today, bypassing the multi-year IT integration queue. This creates a Bottom-Up Adoption loop similar to how Slack or Dropbox entered the enterprise—employees brought it in because it solved their immediate problems. 5.2 Viral Loops & Community Growth To fuel this bottom-up growth, OmniMed Pro leverages the Medical Creator Economy 16: MedTwitter & Reddit: Solo founders and small teams are winning by "building in public." OmniMed Pro should release "light" versions of its tools (e.g., a "Scientific Paper Summarizer" or "Anki Card Generator" for med students) to gain viral traction. These free tools serve as a "Trojan Horse" for the OmniMed brand.18 The "Secret Cyborg" Phenomenon: Many doctors already use GPT-4 on their phones ("Shadow AI") to help with drafting notes or looking up conditions. OmniMed Pro legitimizes this behavior by offering a HIPAA-compliant, secure wrapper. By solving the "compliance headache" for the individual doctor, it wins the user first, then the enterprise.20 Anki Integration: For the student/resident market, integrating with Anki (spaced repetition flashcards) creates a lock-in effect early in a clinician's career. Tools that automatically generate Anki cards from clinical guidelines or textbooks are highly viral among medical trainees. Capture the medical student today, and you have the Attending Physician of tomorrow.19 5.3 Risks and Mitigation: The "Shadow" Dilemma This strategy carries significant risk. "Shadow AI" creates governance gaps and potential security liabilities.4 To mitigate this and eventually convert to enterprise contracts, OmniMed Pro employs a specific conversion strategy: Enterprise-Grade Security by Default: Even the individual version must be HIPAA-compliant (BAA signed on sign-up). Data processing should happen locally or in compliant cloud enclaves. The "IT Trojan Horse": Once adoption reaches a critical mass (e.g., 30% of doctors in a hospital), OmniMed Pro approaches the CIO with usage data. "Your doctors are already using this tool 5,000 times a week. Let's sign an enterprise deal to give you visibility, control, and single sign-on (SSO)." This flips the sales conversation from "Please try our product" to "Please secure and manage your existing usage".4 This is the exact playbook used by companies like Yammer and Slack to penetrate the enterprise. 6. User Experience: Visualizing Uncertainty and Generative UI The final barrier to adoption is Trust. Clinicians do not trust "Black Box" AI that spits out confident answers without rationale. OmniMed Pro employs a "Glass Box" UX philosophy that prioritizes transparency and interactivity. 6.1 Explainability via Visualization Sankey Diagrams for Reasoning: To visualize the "Chain of Thought," the UI uses Sankey diagrams that show how data flowed from "Lab Result" -> "Intermediate Reasoning" -> "Final Diagnosis".12 This allows the clinician to trace the logic visually. Interactive Debate Logs: The UI allows the doctor to "replay" the debate between the AI agents. "See why the AI ruled out Lupus." This turns the AI into a teaching tool rather than just an oracle, fostering trust and verifying the reasoning process. 6.2 Agentic Generative UI Instead of static dashboards or simple chat bubbles, the OS uses Generative UI.22 The interface adapts to the context of the conversation. Dynamic Charts: If a doctor asks about "Cardiology Trends," the system doesn't just write text; it generates a live, interactive chart of the patient's troponin levels over time. Actionable Forms: If the doctor asks for a "Referral," it generates the referral form, pre-filled with patient data, ready for signature. Contextual Cards: The UI presents "cards" for different data types (medications, allergies, labs) that can be manipulated, reordered, or expanded, creating a fluid workspace that replaces the rigid, click-heavy menus of the EHR.23 7. Regulatory & Ethical Moats: Defending the OS To operate at this scale and depth, OmniMed Pro must build defensible moats around regulation and safety. 7.1 MedHELM Evaluation Framework To prove superiority and safety, OmniMed Pro adopts the MedHELM (Holistic Evaluation of Large Language Models for Medical Applications) framework.1 Unlike static benchmarks (USMLE), MedHELM evaluates models on: Clinical Utility: Is the answer helpful and actionable? Safety/Harm: Did it suggest a fatal dosage or miss a critical red flag? Bias: Does it perform equally well for all demographics? Alignment: Does it follow the specific hospital's protocols? By continuously running MedHELM evaluations on its hybrid outputs, OmniMed Pro provides a "Quality Seal" that single-model providers cannot match without deep integration into the hospital's data. 7.2 Liability Frameworks In a multi-model world, liability is complex. OmniMed Pro positions itself as a Clinical Decision Support (CDS) tool, not a diagnostic device. The "Human-in-the-Loop" is mandatory. By visualizing the debate and uncertainty, the OS places the final decision firmly in the hands of the clinician, mitigating liability risks associated with "autonomous" diagnosis. 8. Conclusion: The Strategic Imperative The OmniMed Pro 'Medical AI Operating System' represents the inevitable evolution of healthcare artificial intelligence. By moving beyond the "Model-as-Product" mindset and embracing an Architecture of Aggregation, it solves the fundamental trilemma of medical AI: Accuracy, Cost, and Trust. Leverage the Router to commoditize the giants (OpenAI, Anthropic) and extract the best capabilities of each.1 Deploy the Consensus Engine (MCC) to achieve "Super-Human" reliability through adversarial debate.2 Unleash the Swarms to automate the physical and administrative burdens of healthcare.7 Infiltrate via Shadow AI to bypass bureaucratic inertia and win the hearts and minds of clinicians directly.3 In doing so, OmniMed Pro does not just "outperform" OpenAI; it contains them, turning their powerful models into mere components of a higher-order medical intelligence. This is the path to disrupting the global medical industry. Technical Appendix: Implementation Roadmap A.1 Deploying the MCC Debate Engine To implement the Model Confrontation and Collaboration (MCC) engine 2: Select Models: Integrate API endpoints for GPT-o1 (Moderator), Claude 3.7 (Reasoning), and DeepSeek-R1 (Critic). Define Prompts: Moderator: "Compare the following diagnoses. If semantically identical, output FINAL. If divergent, initiate DEBATE_ROUND_1." Critic: "Review the diagnosis provided by Model A. Identify any inconsistencies with the provided lab values. Cite clinical guidelines." Set Thresholds: If consensus > 0.8 similarity score, output. Else, iterate max 3 rounds. Fallback: If no consensus, route to "Human-in-the-Loop" queue. A.2 Building the "Sidecar" Extension To build the "Shadow AI" browser extension 3: Manifest V3: Develop using Chrome Manifest V3 for security compliance. DOM Observer: Use a MutationObserver to detect when the EHR (e.g., Epic Hyperdrive web) loads a patient note field. Context Extraction: Scrape relevant DOM elements (vitals, meds) locally in the browser (client-side) to minimize data egress risks. Injection: Inject a floating "FAB" (Floating Action Button) or sidebar IFrame that contains the OmniMed chat interface. Clipboard Actions: Use the Clipboard API to paste generated text back into the EHR's focused input field. A.3 Setting up the Swarm Architecture To orchestrate the Swarm 13: Orchestrator: Use a Python-based orchestrator (like Swarms API or LangGraph). State Management: Maintain a shared "Case State" object (JSON) that all agents can read/write to. Handoffs: Define explicit state transitions. if (labs_missing) -> route_to(Intake_Agent). if (diagnosis_ready) -> route_to(Synthesizer). Standardization: Ensure all agents output in structured JSON (FHIR format) to maintain data integrity across the swarm. Works cited

• 
  emrah (@mrahbayraktar) reported 3 minutes ago

  i met a founder doing $10,000,000+/year at my airbnb gym in dubai at 6am he was the only other person there. we started talking. i asked him what was driving most of his revenue. he didn't say ads. he didn't say cold email. he didn't say a sales team. he pulled out his phone and showed me a dashboard. 28 million views in the last 30 days. accounts he owns. content he already had. no ad spend. no creators. no audience deals. he said something i haven't stopped thinking about since. "most founders are renting attention. i own mine." here's what he meant, and why it's the most important distinction in business right now. when you run ads, you are paying rent on someone else's audience. the moment you stop paying, the leads stop arriving. you don't own anything. you built nothing. you rented a billboard for six months and when the lease expired you were back to zero, except now you're $200,000 lighter and your CAC is a number your board pretends not to notice. when you distribute content on accounts you own, something different happens. the views compound. the audience compounds. the trust compounds. a clip you posted three months ago is still driving profile visits today. a piece of content from last year is still closing deals this quarter. the platform doesn't have an expiration date on good content, and the attention you build doesn't evaporate when you stop writing checks. this founder had 52 accounts across every platform. all owned. all run by a dedicated team posting daily clips from content he already had sitting in a folder doing nothing. youtube recordings. podcast episodes. webinar footage. he wasn't creating anything new. he was just finally distributing what he'd already created, at scale, into every market he wanted to win. the math is what broke my brain. $0 in ad spend. 28 million views in 30 days. if you modelled that as paid traffic at even a $2 CPM, you're looking at $56,000 worth of reach. every month. compounding. from content that existed before we ever had that conversation in a gym in dubai at 6am. i've seen this exact system work for iman gadzhi. 300 million views. 180,000 instagram followers and 280,000 tiktok followers built from zero, on accounts he owns and keeps. i've seen it work for luke belmar. 200 million views and $19M in capital club subscriptions driven through distribution alone, not through ads, not through a sales team, through clips running on owned accounts into the exact audience that needed to see them. i built russell brunson's clipping infrastructure inside clickfunnels. $100,000 in sales from a system that runs without him touching it. the pattern is always the same. founder has content. founder has no real distribution. founder is either buying reach they don't own or posting to their own audience and wondering why growth is flat. we build a dedicated team around their brand, warm up accounts to the exact audience they want to reach, geo-target any market they want to win, post daily, test what's working, double down, and watch the views compound across a system they own completely. the content you already have is the most underused asset in your business. most founders spend years creating it. podcast episodes nobody heard. youtube videos that peaked at 4,000 views. webinar recordings sitting in a dropbox folder. all of it has a shelf life of forever if someone actually distributes it properly, and almost nobody does. the guy in the dubai gym wasn't smarter than you. he wasn't working harder. he wasn't spending more. he just figured out earlier that distribution is the actual product, and everything else is just content waiting to be seen by the people who need it. if you want to see the full strategy we use to build this kind of system... the accounts, the setup, the playbook - comment "distribution" below

• 
  echelon_zero (@echelon_zero) reported 4 minutes ago

  @dhh @renefaurskov Do you have a contact at dropbox that could fix the install on linux to point the dropbox to a folder other than default. Having to pause it and link to another folder after install is mentally unhealthy.

• 
  Greg Ceccarelli (@gregce10) reported 5 minutes ago

  @kunchenguid no one will disagree with that sentiment. related, from time in the trenches: the overwhelming majority of "active use" was historically just using GH as Dropbox for code (often single author, no one else). Memory a bit fuzzy but think about all of the things you can do on GitHub: 1. Core ***: Create, Clone, Fork, Commit, Etc 2. Collab: Issues, PRs 3. CI/CD: Actions, Checks, Webhooks, etc 4. Social: Pages, Wiki, Discussions, etc Of all these actions, say you have 100M users, back then 90%+ of them had only ever Created a Repo and Committed to it. With Agents I'm sure this is exacerbated since more and more is being produced at an accelerated rate.

• 
  dreadnaught (@dr3dn0t) reported 5 minutes ago

  @priestessofdada this dude could have worked at dropbox, ibm, cnet, duolingo, etc. all of them offloaded people by that time in favor of AI. skids hadn't figured out what to do with AI yet because someone hadn't laid out instructions for them. by the time they were starting to flood social media, several companies had made some pretty large public facing fuckups due to their shift to AI, which seems to have slowed down mass adoption. now if we're gonna play the intentionally dishonest game of "AI took my exact job" then you are correct. every single company that did this crap ended up consolidating roles. so there is no exact position to fill.

• 
  Nell AI Labs (@nellaiorgs) reported 7 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.

• 
  GHOST 🌙 (@ghosstty_) reported 7 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.

• 
  kfd&p (@kfdpcom) reported 12 minutes ago

  @mellolais___ @LIBSCRUSHER @Dropbox I went on their site and it does say that the .com access is having issues. I guess we just wait it out.

• 
  Fraser (@iamfra5er) reported 14 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

• 
  Startup Archive (@StartupArchive_) reported 16 minutes 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)

• 
  Sasha Sage (@SSage38676) reported 17 minutes ago

  Most founders confuse awareness with demand. Awareness = people have seen you. Demand = people understand why they need you now. For innovative products, demand doesn’t already exist at scale. You have to create it. Here’s the step process to create demand: 1. Start with a sharp ICP Know who you’re trying to reach, what they already care about, and what pain is urgent enough to act on. 2. Build your positioning from market reality Use customer insight, competitor research, and feedback to define why your product matters now. 3. Reframe the problem Don’t just describe your feature. Teach people to see the problem differently. 4. Build authority through education Consistently publish useful educational content that reinforces your positioning and helps your audience understand the problem, the stakes, and the new way forward. 5. Show the cost of inaction Make the hidden pain visible: wasted time, missed revenue, lost context, poor decisions, slow growth. 6. Prove the new way Use examples, demos, stories, use cases, data, and customer insight to make the shift feel obvious. 7. Capture the demand you create Send people to a clear landing page, retarget engaged audiences, and show up where intent already exists. 8. Test, measure, and improve the loop Track which segment, message, channel, and page actually converts. Then double down. Example: Zapier Most people already knew Gmail, Dropbox, and Basecamp. Almost no one was looking for an "app automation platform." That's missing demand. Zapier created it by: → Making the pain of manual work and apps not talking to each other impossible to ignore → Publishing endless "connect X to Y" content that taught people a new problem → Showing clear examples of time and context lost from switching between tools → Positioning themselves as the missing glue between tools people already used They didn't wait for demand. They built it through education and problem reframing. Don't just get seen. Make the market understand why they need you now.

• 
  Loster (@Loster) reported 18 minutes ago

  @Z3R0Gravitas Thinking that if I do trials with people I'd give them exactly that. Something similar to a Dropbox folder for any health docs they want sync'd to the agent's server. I think that would take up how much it could help a notch (need to think a lot about confidentiality).

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

  @DropboxSupport erm different wifi nope or is this a suggestion should it be possible ? if so then no my internet signal can be hit or miss at times but never had this issue before... Also shared a file earlier for someone near me to edit using ipad app but photos failed to appear on ipad ?

• 
  Phillip Shoemaker (@pbsIdentity) reported 19 minutes ago

  India just ordered hundreds of Google Firebase accounts shut down after authorities found scammers using the platform to impersonate major banks. At least 57 Firebase-hosted websites and databases were targeted for takedown this month alone. Some mimicked banks. Others distributed malicious Android apps. Some were designed to steal financial information from phones. Here's what I find interesting. Firebase isn't some shady hosting company operating out of a basement. It's Google infrastructure. That's exactly why criminals want it. We've spent years teaching people to look for obvious signs of scams. Weird domain. Broken English. Sketchy hosting. Browser warning. No HTTPS. But increasingly the attacker doesn't need to build suspicious-looking infrastructure. They borrow legitimate infrastructure. Google. Microsoft. Cloudflare. GitHub. Dropbox. Whatever gives the attack credibility and reliability. Now imagine the average person inspecting the link. They recognize Google. The connection is encrypted. The page loads perfectly. The certificate is valid. Everything their brain has been trained to interpret as: SAFE may technically be true. Except the person controlling the page is a criminal. That's an important distinction. HTTPS proves your connection to the website is encrypted. It does not prove the person operating the website is honest. A Google URL proves Google is providing infrastructure. It doesn't necessarily prove Google created the content you're looking at. The little padlock was never a morality detector. We just accidentally trained an entire generation to treat it like one. India says scammers have increasingly shifted toward Firebase because its legitimate development tools and database functionality make it useful infrastructure for fraudulent sites and apps.

• 
  dragon1952 (@gmanshk) reported 22 minutes ago

  From GROK Yes. Max Miller’s attorney released a public Dropbox folder containing an undressed photo of his 2-year-old daughter. It came from a February 2025 text exchange documenting a bruise (later a broken collarbone) noticed during bathing. The image was available for about a day before removal. Miller’s lawyer called it an accidental inclusion of a shirtless photo with no ******** visible. The other side’s lawyers described it as potentially showing ******** and possible CSAM. Miller has acknowledged the photo existed in the materials.

• 
  Martin (@martin_valchev_) reported 22 minutes ago

  WordPress people - where do your site backups live right now? - Same server as the site - Google Drive / Dropbox - Dedicated backup service - Honestly not sure That last option is more common than anyone admits.

• 
  Lando, the Chef (@_Lando7763) reported 24 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.

• 
  Sridhar Katakam (@srikat) reported 26 minutes ago

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

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

  System design question. How would you design Dropbox file sync with conflict handling? Constraints to make it real: 1) Same file edited on 2 devices while offline for 3 days, then both reconnect 2) Large files (2GB). Need chunking, resume, and content-hash dedupe 3) Renames/moves vs edits should not explode into full re-uploads 4) At-least-once change events from clients, out of order, with retries 5) Server must support 10M files per user without scanning the whole tree 6) Conflict UX: when do you auto-merge (text) vs create conflicted copies (binary)? 7) Cross-region sync, eventual consistency, and p95 sync latency < 5s for small edits [generated using my AI agent, hope this was useful]

• 
  Craylor (@craylor) reported 42 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.

• 
  FiL Dev (@FiLHashDev) reported 42 minutes ago

  I’m hesitant to work with Jira again. Co-Founder wants it. My issue is that we don’t have a source of truth. Two brains, agents, & knowledge bases, leaves room for a lot of drift. Any suggestions? I’m thinking GitHub read only repo access might be the vibe. We also use Dropbox sync for artifacts. I just think a third central brain = more tokens and more drift. Might just have to build a full AgentOS.

• 
  Urooj (@Urooj978) reported 45 minutes ago

  That old laptop gathering dust in your closet can replace every cloud subscription you pay for. ​• Netflix • Google Photos • Dropbox • 1Password ​That’s over $500 a year to rent things you used to own. ​Enter CasaOS—a free, open-source system that turns any old laptop or mini PC into your own personal server. ​No Linux skills. No code. No weekend-long tutorials. ​You run one command. In 30 minutes, you get an iOS-like dashboard where you can install self-hosted apps in one click: 1/ ​Jellyfin → Replaces Netflix 2/ Immich → Replaces Google Photos (with facial recognition) 3/ Nextcloud → Replaces Dropbox 4/ Vaultwarden → Replaces 1Password 5/ AdGuard Home → Blocks ads on your entire Wi-Fi network ​Setting up a home server used to be a nightmare. CasaOS makes it feel like installing apps on an iPad. ​The laptop you forgot about is more powerful than the servers that ran most websites in 2008. It costs $0, it’s already in your house, and it puts $500/year back in your pocket. ​Your closet is your new data center.

• 
  Duaa 🤲🇮🇳 (@Duaa_1206) reported 48 minutes ago

  @himasoraakane Doing digital forensics on Dropbox error screens to investigate a suspended account is a whole new level of investigative work.

• 
  Ryan Babbs (@buckybabbs) reported 49 minutes ago

  Hello @Dropbox, Just this week I have decided to switch cloud service from Google Drive to you and less than 1 week I'm having an issue. I run a wedding film business and am trying to move the same 200GB file to two separate editors for two separate kind of films and one of them is encountering a "link temporarily disabled" message. I tried to research online and made a new folder and copied over the original folders contents and cannot share that either as it says I've exceeded bandwidth limits. This is maddening as I thought I'd picked the good plan (3TB) and was all set. Please advise asap as I need these files in my editors hands stat.

• 
  Akshay Shinde (@ConsciousRide) reported 51 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.

• 
  WPBeginner (@wpbeginner) reported 51 minutes ago

  You have spent months building your WordPress site. What happens the day it suddenly goes offline? 😱 It happens all the time. We have heard several scary stories. A plugin conflict, a bad update, or a security breach can wipe out your complete website without any warning. The scary part is that most site owners assume their host has them fully covered, right up until they actually need to restore. We have tested countless backup tools on our own projects, so we put together the exact methods we trust to keep a site safe. Here is what you will learn: ✅ Pick the Right Method: Compare backup plugins, host backups, and manual cPanel or FTP so you know which fits your skill level. ✅ Back Up the Full Site: Save your database, themes, plugins, and uploads together so you can restore everything, not just your posts. ✅ Automate It With @DuplicatorWP: Schedule daily or weekly backups and send them straight to the cloud so you never have to remember. ✅ Store Copies Off Your Server: Keep backups in Google Drive, Dropbox, or Amazon S3 so one server crash never takes your site and its backup at once. ✅ Restore in Minutes: Use a disaster recovery link to bring your site back even when it is completely broken. Ready to protect all that hard work before disaster strikes? Read our complete step-by-step guide from the link in the comments 👇 (Link is in the thread below)

• 
  Olivia Jane. 🦇 🗡️ 🩸 (@livtheripper) reported 51 minutes ago

  @HazeOfBlue84 Haha, I get it! Thankfully someone here at the office set it up and all I had to do was re-sync Dropbox! I had no issues at all, so I'm thankful.

• 
  abheet nigam (@MaginAbheet) reported 55 minutes ago

  Dropbox rejected billions of dollars of acquisition offers only to later realise down the line that they were building a feature not product. Which other companies show a similar pattern today?

• 
  Indragie Karunaratne (@indragie) reported 59 minutes ago

  I used the first Dropbox beta back in 2006 and was sold right away - I’m still a paying customer of the product today, 20 years later. But there hasn’t been much innovation in this space since then and we’re in the midst of a broad shift in how people interact with computers. I’m excited to back this great team and see what a modern take on this problem looks like!