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 (57%)
• Sign in (29%)
• Website Down (14%)

Live Outage Map

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

City	Problem Type	Report Time
Flumet	Errors	21 hours ago
Irapuato	Errors	3 days ago
Bournemouth	Sign in	2 months ago
Paramaribo	Errors	3 months ago
Bogotá	Website Down	3 months ago
Auxerre	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:

• 
  PodWire (@PodWireHQ) reported 57 seconds ago

  Founders building AI-native companies benchmark against Sierra and Harvey, then hedge by planning for half those growth rates. Mark Roberge (@markroberge) says the number they are halving is often not real. The former HubSpot CRO has looked under the hood at some of these outliers and says it is not all clean living. Headline ARR leans on contracted-ARR gimmicks. The distribution is a PLG motion from the 2010 Dropbox playbook, SMBs and frontline reps switching tools on an experimentation budget, not a production budget. Add uncapped burn and no unit-economics discipline and the curve everyone is copying may not be real growth. Some gold in there, he says, but a lot of Groupons and WeWorks. The trap is every founder thinking they are the exception. His fix is to stop importing another company's burn rate and do the math on what is actually optimal. Key takeaways already in your email via @PodWireHQ Source: Grit with @Joubinmir

• 
  Matthew Tse (@MatthewTse_) reported 8 minutes ago

  @DropboxSupport Yep, still broken.

• 
  Peter Lake (“world’s anonymous singer songwriter”) (@PeterLakeSounds) reported 9 minutes ago

  @taobanker I might suggest another question: what should you avoid? In that context the multi-trillion dollar bet will have terrific returns. That also means that the money making machines of US won’t accumulate money and accrue value unless there is persuasive evidence that at least the big spenders on data center capex get their money back. Given this is unknown, I assume markets are skeptical. If the largest companies in S&P and all the rest don’t have excess free cash, and plausible they don’t go up a lot. That would yield maybe an on average flat market. The flip side is that models are open, massive parameter models getting quantized will be in windows machines. Silicon Valley and early adopters are doing fascinating things. But for the rest of us, I need nice and simple. And for the first time we’ll have good old home computers that can do the job and with that comes free use from heaven. Outside of specialized discussions people don’t know much about what to do with this. The jardon doesn’t help: context window? Quantized models? Nodes are not parameters, they are like neurons, and AI is so dangerous, but not it’s not…what a world! The really final blow is government intervention now makes it a sovereign requirement for companies to have their own AI. LASTLY! I’ve been thinking about the data holders. box. Dropbox etc. Absurdism and it’s comparables will become a bigger deal as people start to realize they the context “window” = the files and stuff you want it to analyze = can only handle so much Imagine of Box or Drop box had a button that converted all your stuff in MD files or the like? Then it’s show time. The companies that hold data may be more valuable than I realize. Conclusions based on the above speculation: 1) could this impact demand at the data centers? Sure it can. I know tech investors like to hold out their hands palms out and say…something vague and qualities. Yes, data centers are more sophisticated etc. Yet here I was doing some interesting work on a FREE local model, my “dark tokens” are someone else’s lost revenue! How does this math work? No clue. It is telling, however, that NVDA and AMD are committed to local machines. No large company wants model dependency anyway, due to data concerns. 2) Finally I have a great reason to buy a slick cool PC! The higher end stuff will not be throttled down in local because I’m seeing a bunch of them coming our way that will have decent “bandwidth” RAM in addition to high system ram. We’re going retro and this tech is moving so fast. Adoption will increase once you have super good local models on your laptop. …Im falling asleep, but the gist is that the data centers were already speculative, and now we a lineup of expensive but sweet computers running on windows that gives you infinite and faster foundational level stuff.

• 
  Santiago Bustelo (@sbustelo) reported 14 minutes ago

  @DropboxSupport More details? “I am really sorry for any inconvenience this is causing. We'll update you shortly on this issue.    In the meantime, please let me know if you have any further questions.   Best regards,  Jesse | Advanced Support” That’s the “support” I’m getting. FULL REFUND NOW

• 
  leveltu (@leveltu144) reported 19 minutes ago

  Most people look at this box and see a home storage system for old drives. In reality, it can become a small business built around local AI, backups, and private data. The more companies use AI, the faster they accumulate documents, videos, call recordings, knowledge bases, backups, and files for RAG systems. Keeping everything in Google Drive or Dropbox becomes expensive, slow, and risky, so small businesses increasingly need local NAS servers with automated backups and secure private-cloud access. The business model is straightforward. You target small agencies, dental clinics, accounting firms, video studios, e-commerce companies, and manufacturers that already hold 2–10 TB of data but still store it across random external drives. Then you sell them a complete solution: NAS installation, RAID configuration, automated backups, remote access, protection against data loss, and local storage for AI workflows. You can charge €400–€900 for installing and configuring the system, excluding the hardware itself. Monthly maintenance, backup verification, and monitoring can add another €80–€200 per client. Close five companies within the first two or three months at an average setup fee of €600, and you generate €3,000 from installation plus roughly €600 in recurring monthly revenue. Ten clients can produce €1,200–€2,000 per month from support alone. The real profit is not in reselling hard drives. The client pays for the equipment, while you sell the audit, configuration, data migration, automation, and responsibility for keeping the system operational. The service layer can carry far higher margins than the hardware. No one can honestly guarantee income within 90 days, because without sales there is no business. But reaching your first €500–€1,500 per month within two or three months is realistic if you build one demonstration NAS, package the offer clearly, and contact at least 30–50 potential clients every week. While everyone else is trying to make money from another AI chatbot, a more durable business is forming around the infrastructure AI cannot function without: data, storage, backups, and private computing.

• 
  Duke of weirdington (@edache_praise) reported 19 minutes ago

  ..without knowing whether customers even want the core product. The irony is that users rarely care about having 50 features. They care about solving one painful problem really well. Companies like Airbnb, Uber, Dropbox, and Instagram didn't start with the products we know today.

• 
  Nikolay Konovalov (@br11k_dev) reported 19 minutes ago

  @thekevinjon The only problem is getting zezwolenia na pracę. I was going to interview with Dropbox last week and turns out they are happy to interview me and submit my case to Mazowiecki Urząd Wojewódzki. ... and then wait for 8 months until my case is approved, and I can actually start working. That's a huge deal-breaker for a lot of engineers like myself who are less than 5 years into staying in Poland. I'm on JDG for example. I came by PBH visa back in 2023 legally, and I've been successful since. I earned quite a bit of money and spent it all in Poland, 12% tax + $500 ZUS monthly. But the moment I want to join bigtech and earn even more money for Poland (Dropbox have 300-400k+ PLN base salary for Senior SWE), I'm just denied. Please, please... let the Dobby be free...

• 
  SMART GrowthSystems 🕸 (@H2Wealth365) reported 20 minutes ago

  🧵In 2008, Dropbox had a growth crisis. Paid CAC via AdWords hit $233–$388 per customer. Product price: $99/year. Unit economics were broken. Drew Houston didn’t fix the ads. He built a referral loop.

• 
  J.F. Lawrence | Author (Jesse) (@jflWrites) reported 20 minutes ago

  @spaceemotion All good ideas. I've thought about Dropbox, Google Drive, and OneDrive. They suffer from persistence, login requirements, and users fiddling with things that change permissions. AWS is cheap, and I'm considering it, but I'm trying to pay for this off of my measly book sales, so...

• 
  IT Guy (@T3chFalcon) reported 22 minutes ago

  The code itself is just a pattern that encodes a URL. it's not dangerous. what it points to might be. The attack is called: Quishing. QR code phishing. It works so well because can't see where a QR code goes before you scan it. A phishing link in an email is visible, people have been trained to hover before clicking. A QR code gives you nothing to hover over. you scan and you're already there. And security tools are mostly blind to it. email filters scan text and URLs but a QR code is an image. 12% of all phishing attacks now use QR codes specifically because they bypass email security gateways that weren't built to read images. In 2026 — Stickers are being placed over legitimate QR codes at parking meters, EV charging stations, and restaurants; your payment goes to the attacker. — QR codes in emails leading to fake Microsoft 365 or bank login pages. 83% of malicious Microsoft 365 documents now contain QR codes instead of links. — multi-stage attacks: QR code leads to a Dropbox or Notion link that looks legitimate, which then loads the phishing page. — fake address bars on mobile called Browser-in-the-Browser. The padlock shows, the URL also looks right but it's a fake overlay on a small screen you can't scrutinize. QR code phishing attacks increased fivefold in 2025 alone. The FBI also issued a public advisory.

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

  @RealRoseGoblin Do you have Dropbox? Of Google Drive? I am afraid with email I am super slow. If you have a personal phone, I have WhatsApp. I have learned to simply do everything publicly. Mostly to protect myself. Try to DM me your number. Happy to connect. If it is big, you should post it here, on IG, on TikTok… everywhere. •

• 
  DFIR Radar (@DFIR_Radar) reported 26 minutes ago

  SMOKE campaign abuses fake Zoom and Adobe lures to silently deploy ScreenConnect RMM, giving attackers persistent remote access that blends with legitimate IT traffic across Windows and macOS. - Initial access rotates across VBScript droppers, batch loaders, and a polished fake Zoom HTML page that auto-downloads an MSI after a 2-second JavaScript timer, no user click needed. Payloads were hosted on a WsgiDAV staging server at 207.174.0[.]143:8080 with open directory listing exposing 15 files. Early samples used Dropbox links and a Cloudflare Quick Tunnel at subscription-magnetic-recommended-meat.trycloudflare[.]com to bypass domain reputation filters. - The final payload is a legitimate ConnectWise-signed ScreenConnect MSI with a valid DigiCert certificate. Agents beacon with URL parameters e=Access&y=Guest to attacker relay servers, including port 8041 on that same IP, making traffic appear as authorized IT remote access. - The attacker pivoted mid-campaign from a 9-step Defender destruction sequence (disabling AMSI, killing WinDefend, adding C:\ as an exclusion, stripping Zone.Identifier) to a stealth loader containing a hardcoded 180-second sleep with a source comment explicitly stating it breaks Elastic EDR correlation windows. Direct evidence of testing against commercial security products. #DFIR_Radar

• 
  Oliver Prompts (@oliviscusAI) reported 26 minutes ago

  you pay google, dropbox, and apple $10+/month to store your files on their servers, where they can read them. and dropbox already got breached in 2024. there's a tool that syncs your files directly between your own devices. no cloud, no server, no middleman. it's called syncthing. → real-time sync between any number of devices, peer-to-peer → files go straight between your devices, never touching a third-party server → tls encryption with perfect forward secrecy on every connection → works over lan and internet, no port forwarding needed → file versioning, roll back anything you changed or deleted there is no syncthing server. no syncthing cloud. no company storing your data. the protocol is open, and there's nothing between your devices except an encrypted tunnel. dropbox plus is $144/year. google one 2tb is $120/year. syncthing is $0, unlimited devices, unlimited storage, forever. battle-tested since 2013. run by a swedish non-profit. 100% free. open source.

• 
  Shawna Canon (@ShawnaCanon) reported 27 minutes ago

  @smolzoey I had a similar problem with Dropbox. I had it syncing my desktop because I keep a lot of stuff there. I deleted Dropbox because I don't use it. I basically bricked my computer because my desktop no longer existed.

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

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

• 
  AaronAlamary | Parking (@aaron0505) reported 32 minutes ago

  I saved my grandfather's voicemails for years. Birthday wishes. Questions about his computer. Who to call to fix his A/C. Upgraded my iPhone and they were gone. Devastated. Found them today sitting in my Dropbox. SO glad I get to hear him again!

• 
  meshgear (@_meshgear) reported 33 minutes ago

  @Dropbox It is not working.

• 
  WPBeginner (@wpbeginner) reported 34 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)

• 
  Fernando (@Ferjsjdh) reported 36 minutes ago

  @MaxMillerOH You're retarded, you are giving away the race because of your pride and now you think some dropbox with text messages will fix it.

• 
  JennX (@JennX0608) reported 36 minutes ago

  More trouble for Max Miller. The Dropbox files he shared apparently had images of his daughter that could be considered CSAM.

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

• 
  quantzoid (@quantzoid) reported 43 minutes ago

  @gurishsharma sorry, you're in YC to take down dropbox but you didn't know how to approve a PR on github? what?

• 
  Ayaan 🐧 (@twtayaan) reported 44 minutes ago

  Steve Jobs told Drew Houston that Dropbox was a feature, not a product. Dropbox is now worth $8 billion. In 2007 Drew Houston was a 24 year old MIT student who kept forgetting his USB drive. So he built Dropbox. Within a year Steve Jobs called him into Apple HQ. Apple wanted to buy Dropbox and shut it down. Houston said no. Jobs told him directly that Dropbox was a feature, not a product, and that Apple would build it themselves. Apple launched iCloud in 2011 specifically to kill Dropbox. It did not work. Dropbox crossed 100 million users in 2012. Then 200 million. Then 500 million. Apple tried again. iCloud Drive in 2014. Same result. Then the enterprise market shifted. Slack, Notion and Google Drive carved up Dropbox's user base from every direction. Revenue growth slowed. The stock dropped 50% from its IPO price. But Dropbox never died. Today 700 million people have used it. 17 million paying customers. $8 billion valuation. Still independent. Still running. Steve Jobs built a trillion dollar company. He called Dropbox a feature. The feature outlasted him and two attempts by Apple to replace it. Drew Houston never forgot his USB drive again.

• 
  Dodz4allai (@DrGhattasMD) reported 44 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

• 
  Aaron Li (@polymorpher) reported 48 minutes ago

  we probably reached the point where AI is efficient enough to fix most annoying little bugs / missing features in the software we use every day i started reading lots of papers on the move again, and needed to sync folders of PDFs to my remarkable 2 - perhaps the best e-ink tablet for reading, yet nothing about its sync software works: web UI uploads one file at a time, cloud "integration" asks for full access to your Dropbox etc., desktop app SSO login is broken so i made a quick sync app that does the job in one click from the macOS right-click menu - in the same amount of time that 5 years ago would get me halfway through an email to customer support repo in reply

• 
  Ryan James Girdusky (@RyanGirdusky) reported 53 minutes ago

  @EggerDC The Dropbox was taken down but I’m sure someone downloaded the whole thing.

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

  Asked: design Dropbox-style file sync. Start with requirements: 1) Multi-device, near real-time where possible, offline OK 2) Large files, resume uploads, delta sync 3) Sharing, ACLs, rename/move, delete, version history 4) Consistency target: per-file eventual, monotonic reads per device 5) Conflict policy: last-writer-wins vs explicit conflict copies APIs + model: - PUT /files/{path} (upload session, chunked) - GET /files/{path}?version= - POST /ops (batch rename/move/delete) - Watch/long-poll for changes since cursor Tables: users, devices, file_id, path entries, content_hash, blocks(hash, refcnt), versions(file_id, v, root_hash), change_log(user_id, seq, op) Architecture: - Client computes block hashes, uploads missing blocks to object store - Metadata service commits new version + appends to per-user change log - Notifier pushes cursors to devices (WebSocket/APNS), devices pull diff - Background GC deletes unreferenced blocks (refcnt/mark-sweep) Scaling: - Shard metadata by user_id, keep change log append-only per shard - CDN/object store for blocks, pre-signed URLs, parallel chunk upload - Hot paths: cursor polling, small metadata reads; cache by (user, cursor) Tradeoffs: - Dedupe by block saves $$$, costs CPU and leaks similarity unless salted - Rename is metadata-only if path->file_id indirection exists - Strong consistency needs consensus; most systems accept eventual + conflicts Failure cases to cover: - Network drop mid-upload: upload session + idempotent chunk PUTs - Duplicate notifications: cursor-based pull makes it safe - Device clock skew: use server seq/version, not timestamps - Split-brain offline edits: detect divergent parents, create conflict version - Partial metadata commit: 2-phase between metadata + block refs, or reconcile job

• 
  Joshatoshi #BIP-110 (@joshatoshi) reported 55 minutes ago

  @Cryptotea Core apologists want to frame this like it’s just a spam issue. It’s all about data storage and node centralization. Bitcoin, not DropBox.

• 
  Ihtesham Ali (@ihtesham2005) reported 58 minutes ago

  This is how you share a file when you do not trust Google, Dropbox, or the government. A free tool called OnionShare sends it directly through Tor. Nothing needs to sit permanently on someone else's server. Here's what actually happens when you use it. You drag a file into the app. Your own computer turns into the server. Tor wraps it, and you get a long address ending in .onion that you send to whoever needs the file. They open it in Tor Browser and pull the file straight off your machine. You close the app, the address dies. Compare that to how everyone else moves files. You drop it in Drive, Google keeps a copy. You use WeTransfer, that link lives on their infrastructure for a week, logged and tied to your IP. Every one of those services is a promise that a company will behave well, forever, under any amount of legal pressure. OnionShare removes the company from the sentence. Micah Lee built it in 2014. He'd worked with the journalists handling the Snowden documents and watched how many ways a source could get burned just trying to hand over a file. So he built the thing that removes the middle. It does three things. Send files with no size limit and no account. Chat with someone and keep zero record of it. Host an entire website off your laptop that disappears from the internet the moment you shut the lid. The New York Times, The Guardian, and The Intercept all point sources at this. Those are newsrooms betting other people's freedom on a free download. The interface looks like a file picker from 2011. Someone spent years making the hardest privacy problem in computing feel like using WinZip, and that's the actual achievement here. A scared person at 2am is not going to configure a server. They can drag a file into a window. It is completely open source. Most people will never need this. The ones who do don't get a second try if they picked the wrong app. What do you think about this?

• 
  brodie / knox (@brodiecantskate) reported 60 minutes ago

  @Dropbox your app sucks so much, I can’t believe I’ve been willingly paying for it for so long when it causes me so many issues 💔💔💔