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	17 days ago
Guayaquil	Website Down	17 days ago
Flumet	Errors	27 days ago
Irapuato	Errors	30 days ago
Bournemouth	Sign in	3 months ago
Paramaribo	Errors	4 months ago

Full Outage Map

Community Discussion

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

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

Dropbox Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Joe Murgia (@TheUfoJoe) reported 6 minutes ago

  "There truly is a kind of pushback and a resistance to provision of information that even ODNI is asking for." ~Nolan (Who's resisting sharing of info. with ODNI?) 🛸 New: Nolan Comments on Skywatcher, and More 🛸 Three Nolan quotes... "...a shared realization that the data that even we're being given right now from the government is insufficient." There was an attempt to, "go out into the field and see if we could cause the attraction of some objects. There was some, let's call it, activity, but not enough that I would consider enabling to publish [a paper]." (If scientists were there for the alleged luring/baiting event that @RepEricBurlison has spoken about, would that be enough data for a paper?) "I think we're being listened to. Whether the people who are listening to us are going to be able to be responsive is another question." ~~~Full Clip Transcript~~~ @GarryPNolan: "Look, as scientists, whether we're philosophers, psychologists, material scientists, biologists, theorists, etc., we need data. And so, you know what I've been watching happen, at least around the [UAP Advisory] Council itself is, I think, a shared realization that the data that even we're being given right now from the government is insufficient. "And I don't blame, for instance, ODNI for that. And it has been explained to us, several times over, some of the so-called methods and sources issues that are around this. And also, that a lot of the data that we want to have access to, to do the kinds of analyzes that we would want to do, simply were never collected at the time. Or, in some cases it seems, if they were there, they're no longer there. But, you know, that sounds conspiratorial, so I'm not gonna go down that route. "But I agree with what Avi is saying, is that, rather than looking retrospectively, we need to start to plan prospectively. We could go forever relitigating past issues and who said what, where, and when. As opposed to, well, let's just do it now. Let's just do it to the future. "And so, for instance, because it just comes up many times on Twitter, is...although I can't talk about all of it about Skywatcher... Is, you know, that was an attempt, at the time, to take matters into our own hands in a semi-military, semi-academic fashion to, basically, go out into the field and see if we could cause the attraction of some objects. "And, you know, there was some, let's call it, activity, but not enough that I would consider enabling to publish. Believe me, if it was, I would have done it...already be putting that paper together. But there were lessons learned from that. "But I think, the other thing about the council is, what they're beginning to see is, I think, that there truly is a kind of pushback and a resistance to provision of information that even ODNI is asking for. Now again, that doesn't mean it's a conspiracy. It just means that I think everybody is coming to terms with the fact that it's not just, snap your fingers and you know somebody gives you a a Dropbox link and you can download everything. "So, you know, I'm happy seeing people now come up to speed, and I'm happy seeing, let's put it this way: a level of, let's call it, frustration that is driving us to ask for more. And I think we're being listened to. Whether the people who are listening to us are going to be able to be responsive is another question."

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

• 
  21Rates (@21RatesHQ) reported 9 minutes ago

  Bitcoin security isn't optional anymore. It's survival. The last few weeks: → Dropbox got hacked → Byte Federal (US Bitcoin ATM operator) had attackers target data on 58,000 customers, names, addresses, SSNs → A Trezor supplier leaked customer address data → The LA City Attorney's Office lost 7.7 TB of data, including police records → Coldcard found a flaw in its seed generation that could let attackers steal funds This isn't a string of bad luck. It's the new normal. KYC makes full privacy impossible in most places. But you still control part of your attack surface. Simple moves that actually help: • Use email aliases, a unique address per service • Same with phone numbers where you can • Treat every unexpected email, call, or text as hostile until proven otherwise Attackers combine data from multiple leaks to build your profile. The more your identifiers overlap across services, the easier that is. You don't need to be a victim first to start taking this seriously. What's one step you're taking this week to lock things down?

• 
  Helix (@helixcanvas) reported 10 minutes ago

  Two companies, two correct instincts, and about a billion dollars between the outcomes. In 2007 Dropbox had a problem: the product needed deep operating system integration, so there was no way to demo it without building it first. Drew Houston made a three minute video instead, showing how it would work if it existed, and put it in front of the community most likely to care. The beta waiting list went from five thousand to seventy-five thousand overnight. He knew the demand was real before he wrote the difficult part. Webvan believed something just as sensible. People want groceries delivered. And they were right, which is the part everyone forgets. Instacart and every supermarket delivery service proved it a decade later. But instead of testing it in one city, Webvan committed close to a billion dollars to automated warehouses across multiple markets before knowing whether the economics worked anywhere. It filed for bankruptcy in 2001. Build, measure, learn is three steps. Most of us run the first one over and over and mistake the motion for progress. Shipping is not learning.

• 
  AiMind (@AIMind_Ai) reported 11 minutes ago

  A $50 box saves $240 a year on subscriptions and earns $18,000 a year setting it up for clients. No new hardware. Nothing bought at retail. A used office tower. A second-hand drive. One stick of RAM pulled from a dead laptop. The whole build came to 50 dollars. It looks like nothing. Fans humming, one cable to the wall, sitting on a desk next to a coffee cup. The first win is the one nobody talks about. Cloud storage, photo backups, the $20 a month AI plan everyone pays and forgets — all of it moves onto one box you paid for once. 240 dollars a year, gone. The second win is where the money is. Once it runs on your desk, it runs on anyone's. And clients don't pay for parts. They pay to stop bleeding subscriptions. Here's what you actually sell: A private AI trained on their own files, so staff stop pasting company data into a browser. That's $1,500 a setup. A self-hosted file server that kills their Dropbox and Google Workspace bill. $600, plus the relief of never renting storage again. A local automation box that runs invoices, replies, and reports overnight. $900, and it never sends a dollar to a cloud. Then the quiet one: $150 a month to keep it patched and alive. 10 clients on retainer is $1,500 every month before you build a single new one. One setup a week at $1,500 is $18,000 a year. Off hardware other people throw in the bin. I had no degree, no server room, no $2,000 build. Just dead parts and one free weekend. The expensive part of AI was never the compute. It was the monthly bill you agreed to and stopped reading. 50 dollars in. $18,000 out. Same box.

• 
  Vladislav Zharkov 👾 (@_vladislavzh) reported 12 minutes ago

  I have zero industry experience. None. I don't know how to use issue trackers, I need a GUI for version control, I deliver my files through Dropbox. I don't have templates, I restart or reuse every time. I don't use industry standard tools, I don't know workflows and pipelines.

• 
  JP Invests (@JP_Invests) reported 16 minutes ago

  $DBX - Dropbox added 96,000 paying users this quarter. I said this morning to watch that line after last quarter's roughly 14,000 sequential adds. They did seven times that, a third consecutive quarter of growth, to 18.19M. The stock is down 4%. Everything I said to watch on the growth side came in fine. Revenue $631.5M, above both the $624-627M guide and the $627M street. Non-GAAP EPS $0.75 against $0.74. Non-GAAP operating margin 39.7%, above the full-year range. ARPU $139.68, up from $138.32. What went the wrong way is the part I said would actually move it. Free cash flow fell to $235.2M from $258.5M a year ago, and the margin went from 41.3% to 37.2%. And the buyback decelerated: $330M this quarter against $410M in the same quarter last year, with first-half repurchases down 19%. Unlevered free cash flow rose to $283.5M, and the gap between the two numbers is interest. Cash paid for interest went to $48.3M from $17.9M. The buyback is debt-funded and the debt now costs something. Diluted share count is down 18% year over year to 226.8M, which is the one thing still working mechanically. Two things about the release itself. Guidance isn't in it — Dropbox moved the numbers to supplemental materials on its investor site this quarter, which breaks with how it has reported. And the entire release is quoted by a co-CEO who writes "stepping into this role." The 8-K contains no disclosure of a leadership change. Twenty-nine percent of the float is short. $DBX

• 
  John B. Holbein (@JohnHolbein1) reported 16 minutes ago

  Replication has become much easier in the era of generative AI. I'm not the first person to say that. However, I've seen fewer people acknowledge a specific aspect of this lowered cost for replicating scientific work: Generative AI will very soon allow us to assess the robustness of individual scholars' full bodies of work. Soon, we will be to compute measures of which scholars do robust science, and which do not. What's wild is that we may be able to almost do that already. Let me show you what I mean. In June, I gave Claude a pretty basic prompt. It read: "I have a big task for you. I want you to start a folder. Call it Acemoglu Replications. Then, go find as many replication archives for Daron Acemoglu as you can. Keep a spreadsheet of the ones you can find and those you can't. Then, start a replication/reproduction effort on those articles. People have in the past criticized the research designs and general robustness of his individual papers. I want to know how strong his body of work is as a whole. Don't come in with any prior beliefs; be dispassionate." I let Claude run overnight while I slept. When I came back in the morning, 29 of Acemoglu's replication archives were fully loaded in my Dropbox. All the code reproducing the paper's results had run. And there was a first draft of a paper assessing the robustness of Acemoglu's full body of empirical work. I'll admit, the first draft of the paper wasn't great. But with 15 short follow up messages--which took me about an hour to write--I was able to prompt engineer a paper-length examination of Acemoglu's work. I've attached the screen shot of the abstract below. I think this reassessment of Acemoglu's work is certainly not done. I'm posting the abstract as a proof of concept, rather than a definitive answer. I'm not posting the full paper yet because I think it still needs more work. Ultimately, I paused this project for three reasons. 1.) Limited time/topical expertise: Most of Acemoglu's work is outside of my area of topical expertise. So, I have limited time to work on it. What this type of a project really needs is someone who has the time and the know-how to dig into each of the replication's individually to make sure they are doing the right things. I think the ideal approach combines the breadth that LLMs afford and the depth of attention/expertise that humans can give. 2.) Questions about the value of the "assess one scholar at a time" enterprise: I totally get that having a database of scholar-level robustness metrics would be very valuable in theory. But what I don't know is whether this approach is truly valuable. Moreover, doing so would come with distinct challenges. a.) Many journals have very restrictive space constraints. A body of work approach would, of necessity, be very long. b.) Collecting replication archives is harder for some types of scholars (those who post them all on their websites) than others (those who don't). c.) We'd have to think hard about questions like: what scholar-specific robustness metrics would be best? And: how would we deal with the fact that prolific authors' robustness metrics would be estimated much more precisely than less prolific scholars? Additionally, I'm just not sure that "taking on" one scholar at a time has enough scientific merit to pursue. If I measured how robust an individual scholars' work is, I'd ideally want to know where that metric stands vis-a-vis the rest of scholars in that field/area. To do that, we'd ideally want the population of these scholars or, at minimum, a random sample. Concretely, if Acemoglu has, say, 78% of published headline results reproducible under some standardized protocol, is that excellent, mediocre, or terrible? To answer that, you need a reference distribution. That makes a random or otherwise well-defined sample of scholars much more attractive than selecting prominent individuals one by one. (I'll acknowledge that I may just be wrong on #2. Arguing against myself, I do agree that human-driven reproduction/replication work rarely assesses full/representative slices of a field. Instead of assessing one scholar at a time, we assess one paper at a time. Field-wide detective work is becoming more common, but my sense is that it's still the exception rather than the rule.) 3.) Cost/benefit considerations and replication norms: we have very weakly formed norms around reproduction/replication generally speaking. We have basically no developed norms around replicating individual authors one at a time. What this means is that the people who would lead a scholar-by-scholar replication effort will, likely, bear a heavy cost and, potentially, reap limited benefits. On the costs side, focusing on scholars' total bodies of work risks making the replicators look petty, vindictive, and antisocial. Enough of the scientific field is hostile towards replications of individual papers. Imagine what will happen if/when a scholar submits a scholar-specific "take down" of a full body of work. My sense is that it's common enough for scholars having their work replicated to be asked to be a reviewer for those manuscripts. I've seen very hostile responses when one paper is at issue. Imagine what type of reviewer Acemoglu would be for a paper that took on his entire body of empirical work! Even if Acemoglu weren't a reviewer, prolific authors tend to have wide coauthor/friend networks. The rally-around-my-friend dynamic we often see would certainly work against this type of paper being published. Even a completely neutral analysis acquires an accusatory character simply because the sampling unit is a named person. And that creates an unfortunate problem of its own: readers may interpret the choice of scholar as evidence that the investigators expected to find something. On the benefits side, replicating individual scholars' total body of work may offer limited payoffs. What journals would accept this type of scholar-specific replication? I'm not sure the top ones would. Conclusion: Generative AI has enormous potential in assessing and, ultimately, enhancing the robustness of scientific research. Instead of asking questions like, “does this famous individual paper replicate?”, we can begin asking questions like: -“What proportion of published empirical findings in [field X] survive a common robustness protocol?” -“How much of the variation in replicability is attributable to papers, authors, journals, methods, or subfields?” -“Are scholars persistently more or less robust across their work?” -“Can we predict which findings will prove fragile?” I may just be wrong on what I think about a one-at-a-time full body examination of scientific research. If I am, please let me know! I am also happy to chat one-on-one with anyone who is curious to learn more about the early-stage Acemoglu-specific replication project.

• 
  The Redeemed Artist (@Peace_Grenade81) reported 17 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. 🙄

• 
  Alvin (@Alvin1492840) reported 18 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."

• 
  WPBeginner (@wpbeginner) reported 19 minutes ago

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

• 
  Eric Smith (@Eric_Smith08) reported 20 minutes ago

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

• 
  Ivan Kirigin (@ikirigin) reported 21 minutes ago

  @sethbannon I think I’d agree with the sentiment, and not the assessment. We’re not close to too many startups building weapons. The company with “drone” in the name that has the navy and other defense units as obvious potential customers doesn’t make a trend. If I had to put my finger on what has changed, Palantir and Anduril unlocked the latent interest in the space that matches the historically close connection between Silicon Valley and defense. It was just that the Overton window was locked down by people afraid to talk about what defense really means, and in many cases aren’t even Americans with the opinions. I say this as someone who worked at iRobot in defense before my time in YC, Facebook, Dropbox, and Lyft. Each had lots of people comfortable assuming others will think about and solve the ***** problems.

• 
  Robert J Abalos (@robertjabalos) reported 22 minutes ago

  Want Your Startup to Get VC Funded? You Must Meet All Six of These Requirements Venture capitalists at the seed stage bet on potential more than perfection, yet they demand specific proof points before writing a check. After reviewing hundreds of deals and data from PitchBook, Crunchbase, and leading funds, six absolute requirements stand out. Miss any and the odds of funding drop sharply. First, an exceptional founding team. Team quality remains the single highest weighted factor before product market fit solidifies. VCs look for domain expertise, prior execution, complementary skills, and coachability. Research shows roughly one in four two founder teams loses a co founder by year four, so investors scrutinize resilience and equity alignment. Companies with strong teams raise at higher valuations even with lighter metrics because execution can fix product or market gaps. Second, a large and expanding market. Seed investors require a total addressable market of at least one billion dollars, ideally several billion, with a clear path to one hundred million in annual revenue. Serviceable addressable market should support venture scale outcomes. Markets growing above twenty percent annually command premiums. Small markets cap upside and rarely produce the fund returning exits VCs need. Third, early traction proving customers care. For SaaS this often means ten thousand to one hundred thousand in monthly recurring revenue or three hundred thousand plus in annual recurring revenue. Pre revenue startups need strong engagement such as daily active users to monthly active users ratios above twenty percent, organic waitlists, or letters of intent from unaffiliated customers. Dropbox famously used a demo video that drove seventy five thousand sign ups overnight, unlocking its Sequoia seed. Slack showed early retention that later became legendary. Fourth, rapid and consistent growth. Seed VCs seek fifteen to twenty percent or higher month over month revenue or user growth sustained over multiple months. Absolute numbers matter less than trajectory. Startups posting twenty percent plus monthly recurring revenue growth have seen close rates near sixty five percent in analyzed pitch data. Flat or decelerating growth signals risk. Fifth, early unit economics and retention signals. Even at seed, investors examine lifetime value to customer acquisition cost ratios above two to one, ideally three to one, net revenue retention near or above one hundred percent, and cohort retention that flattens rather than collapses. Gross retention above eighty to ninety percent is a positive signal. These metrics prove the product delivers lasting value and that growth will not require endless capital. Sixth, capital efficiency and clear runway. Burn multiple and months of runway matter. Investors prefer teams that can stretch capital to eighteen months or more while showing improving efficiency. Median U.S. seed rounds now sit near three to four million dollars, yet graduation to Series A has tightened to roughly twenty to fifty percent depending on cohort and sector. Lean teams of four to eight people that still deliver results stand out. Data confirms the stakes. Only a minority of seed companies reach Series A, and failure rates near forty percent are common. Yet the power law rewards those that clear these bars. Airbnb, Stripe, and early Slack all combined strong teams, massive markets, and measurable early traction. Founders who quantify these six elements with real numbers, not projections, dramatically improve their chances of securing seed capital.

• 
  Petty IT Guy (@pettyITguy) reported 23 minutes ago

  Our CEO told me the Wi-Fi in his office was “basically unusable.” He said this in front of the entire executive team. So naturally it became the highest-priority infrastructure incident in the company. I tested his connection. 940 Mbps down. Perfect signal strength. Zero packet loss. I asked what specifically wasn't working. He said YouTube kept buffering during lunch. I opened his laptop. He had 71 Chrome tabs open. Three abandoned Zoom meetings were still running in the background. Dropbox was syncing 84 gigabytes. Google Drive was uploading a 4K video. He had not restarted the machine in 47 days. I could have explained this. Instead I told him our executive wireless architecture had reached end-of-life. He asked what it would cost to fix. I said I would need to scope it. He told me not to waste time and approved an $84,000 wireless modernization project before I finished the sentence. We replaced 38 access points. Installed a new wireless controller. Rewired two conference rooms. Brought in a consultant. His YouTube still buffered. I walked into his office, closed 68 Chrome tabs, killed the abandoned Zoom processes, and restarted the laptop. YouTube loaded instantly. He smiled. “Now that's more like it.” 20 minutes later he emailed my boss praising me for successfully completing the company's wireless transformation ahead of schedule. I received a spot bonus. Sometimes infrastructure modernization is just restarting a MacBook for an inept executive.

• 
  David Simpkins (@DavidSimpkins88) reported 25 minutes ago

  URGENT!!! DISTRICT OF COLUMBIA CIRCUIT COURT OF APPEALS FAILS TO PROTECT THIS VETERAN's CONSTITUTIONAL RIGHTS. MY HOME SECURITY SYSTEM AND PHONES HAVE BEEN TAKEN OVER AND I AM PREVENTED FROM SEEING ANYTHING OUTSIDE MY HOME BECAUSE OF THE CURRENT ACTIVE ATTACKS ON MY PHONES AND SECURITY SYSTEM IN DIRECT VIOLATION OF TN AND FEDERAL LAW AND NO ONE IS STOPPING THEM. LINK TO PETITION FOR WRIT OF MANDAMUS: I went to get the link from Dropbox and my Dropbox appears to have been wiped out. TO THE D.C. APPELLATE CIRCUIT COURT TO REQUEST AN IMMEDIATE RULING ON A TRO TO PROTECT THE APPELLANTS. This subject is about the District of Columbia Circuit Court of Appeals has not issued a standard Stay of Proceedings to the State of TN for their malicious prosecution. By not doing so, they have left this Veteran and his Wife open to criminal attacks by unlawful Law Enforcement of the State of TN. Further the Appellate Court has allowed non-stop violations of the Appellants home computer, cell phones, A/C Units, Security System and any all other WiFi devices. And to this day the illegal cameras placed in the Appellants home have never been removed after the Local Police Department notified this Appellant that there were hidden camera's in his home. Further, the FBI, DOJ, OIG, D.C. US Attorney's Office and especially the Appellate Court have all been notified of the targeting and 24/7 harassment by allegedly unlawful Agents of more than one of our Alphabet Agencies, to include the FBI and DISA. FBI Director Patel has to know about this situation but has done nothing to stop the corruption in the State of TN and has not protected this Veteran and his Wife. We made it clear that on the night of February 18th, 2026, that 5 people in Police Uniforms had keys to this Appellant's home and attempted to unlock the locks and enter the home both at the front door and at the Garage Pedestrian Door. They never once made any statements or comments nor explained why they were there. They did not show any warrants for arrest or search. When they knew they could not get in with out breaking things, they left approximately 15 minutes later. I had called my Wife and let her know. I am facing the same potential attacks again even though when the State of TN conceding by defaulting by not filing a response Brief. They were effectively agreeing that everything stated in the Appellant Brief was accurate and that they could not contest it. That makes all the acts committed by all Law enforcement Four-Hundred and Ninety-Seven (497) Constitutional Rights Violations are valid. Further, in order to access the Security System and the Display, they have to be within 350ft of our home. Because there is no WiFi or Bluetooth installed in the Security System or the Display. Which means they are in close proximity of this Appellants property. Three (3) Emergency Motions have been filed with the D.C. Appellate Court on three separate dates to no avail. The D.C. Appellate Circuit Court has failed to issue a TRO to Stay the TN State malicious prosecution. And left this Appellant, Veteran to suffer the vices and current active ongoing criminal activities by the State of TN against this Appellant as he types in this post. This could include a potential unlawful arrest and incarceration again because the D.C. Appellate Court has not issued a TRO or a Protective Order to Protect the Appellants. That in and of itself is a direct Constitutional Rights Violation now by the very Appellate Court who has allowed further criminal activities to promulgate even further to allow harm and injury. The corruption appears to be rampant in our US Court Systems.

• 
  Jameson Lopp (@lopp) reported 28 minutes ago

  Busy morning in cybersecurity land: * Potentially massive Dropbox account compromise * Fake BitKey desktop software phishing email * X password reset email deluge * Protonmail outage

• 
  Ed Giansante (@edugiansante) reported 39 minutes ago

  community is not a Slack channel. I've been building communities for 15 years across Zynga, Dropbox, Wix, Persona, and my own project Edublin. And the biggest misconception I still hear is: "we launched a Slack, so we have a community." You don't. Slack, Discord, forums, Circle... those are all tools. Community is what happens when people trust each other enough to be honest. I've seen companies spend six figures on community platforms and end up with a ghost town. I've also seen a group chat of 12 people generate more value than a 10,000 person Slack. The difference is the architecture: who's in the room, how they got there, what the norms are, and whether people feel safe enough to say what they actually think. At Dropbox, we had 400 million users. The "community" wasn't a platform, it was the trust between power users who helped each other solve problems the support docs couldn't. They needed to know they were talking to someone who understood their situation. At Wix, I built an 80K partner community. The platform was secondary. What mattered was that web designers felt seen by a company that historically marketed to DIY users. The community was the signal that Wix took professionals seriously. Edublin started as a blog answering questions for Brazilian expats moving to Ireland, with no dedicated platform or app. It became the largest community of its kind because the trust was real. People showed up because they knew they'd get an honest answer. Community is trust. Community is the reason someone comes back. Every time I evaluate whether a community is working, I ask one thing: would these people show up even if the tool disappeared? If yes, you have something real. If not, you have a group chat.

• 
  Justin Kalland (@justinkalland) reported 42 minutes ago

  If you store files on @Dropbox, it may have been compromised between August 4th and 21st. Short version: they trusted @Lenovo to connect Dropbox accounts, and Lenovo had an email verification flaw. Allowing an attacker to create a Lenovo account, add your dropbox account, and gain access. Check if you got a "Your Lenovo Code" email followed by a Dropbox "we noticed a new sign in to your Dropbox account". That happened to me on August 7th, and today Dropbox is confirming the incident:

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

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

• 
  Llama (@thellama451) reported 47 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.

• 
  Kyngsly (@RelentlesslyK) reported 48 minutes ago

  @yettydlaw_ @MTNNG MTN will likely be able to explain it away... Anyway, this how Claude explained. "708GB over 104 days works out to about 6.8GB a day. That sounds shocking until you break down what actually eats data on a modern 5G phone. The usual culprits, roughly in order of how often they turn out to be the answer: Video, especially autoplay. TikTok, Instagram Reels, YouTube Shorts and X video. Scrolling Reels for two hours can burn 4 to 6GB on its own. “Social media and browsing” is exactly the usage profile that quietly does this. 5G itself. This one gets missed constantly. Video players negotiate bitrate based on available throughput. The same 30 minutes of YouTube that cost 300MB on 3G can cost 2GB on 5G because the player auto-selects a much higher resolution. Nothing changed in behavior, but consumption multiplied. Wi-Fi Assist / Adaptive Connectivity. iPhone and Android both silently fall back to cellular when Wi-Fi gets weak. The phone shows the Wi-Fi icon while pushing traffic over the mobile network. People assume they’ve been on Wi-Fi at home all evening when they haven’t. Cloud photo backup. iCloud Photos or Google Photos set to back up over cellular. A few 4K videos is several GB right there. Hotspot and tethering. A laptop pulling Windows updates, OneDrive or Dropbox sync, or a Zoom call. Also worth asking whether the SIM ever sits in a MiFi or router. Background refresh and auto-updates. App store updates over cellular, plus dozens of apps refreshing in the background. Video calls. WhatsApp video runs roughly 300MB an hour, Zoom or Meet more. On the operator side, real errors do happen: duplicate charging, subscription add-ons deducting from the bundle, or misapplied tariffs. But there’s also a structural point worth knowing. Carriers meter at the network layer, so they count protocol overhead and retransmissions, and in a poor RF environment retransmissions can add a real percentage on top of the payload the app thinks it sent. One practical note on that complaint: the app-level breakdown being demanded is hard for any carrier to produce. Traffic is encrypted end to end, so MTN can see volume, timing and destination IP or SNI, but not “3.2GB attributable to Instagram” in any reliable, retained form. The chronological deduction ledger and the subscription/add-on audit are the demands most likely to actually produce something. The fastest self-diagnosis is Settings > Cellular on iOS or Network & Internet > Data usage on Android, sorted by app, with the counter reset date checked. "

• 
  Jameson Lopp (@lopp) reported 48 minutes ago

  One reason I suspect the Dropbox breach may be massive is because I didn't get a login email notification when my account was accessed. Turns out, unlike every other login notification I've received from them, it went to spam. Likely due to a large uptick in their send volume...

• 
  More Gravy (@lotsmoregravy) reported 50 minutes ago

  @FFT1776 Deputize our military and send them to literally every last damn polling station and dropbox in the United States of America. Every last damn one. Give them the authority to handle **** on the spot. Problem solved.

• 
  Tom Alder (@tomaldertweets) reported 51 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.

• 
  OneToothTeXan (@OneToothTeXan) reported 54 minutes ago

  I'm so sorry I left my zipper down and my sanity got loose. If found: Men, there's a dropbox. Women: please return to original source.

• 
  grey (@w3b3grey) reported 55 minutes ago

  If you are like me and you wondering, where my IDENTITY PEM FILE is on @flop_labs , I gat you; here is how to find it identity.pem is already saved automatically; the init command writes it to your project folder the moment you run it (typically right in technocore-did-starter/identity.pem). You don't need to do anything extra for it to exist. What "saving" really means here is backing it up safely, since if this file is lost, your DID is unrecoverable (the guide's troubleshooting table says exactly that: "there is no central DID recovery service"). 1. Confirm it's there ls -la ~/technocore-did-starter/identity.pem 2. Back it up to a second location — copy it somewhere other than the working folder, e.g. an external encrypted drive or a password manager that supports file attachments (1Password, Bitwarden both do this): cp ~/technocore-did-starter/identity.pem ~/Desktop/identity-backup.pem Then move that copy off your main disk (external drive, encrypted USB, etc.) rather than leaving a second copy sitting in ~/Desktop long-term. 3. Lock down file permissions so only your user account can read it: chmod 600 ~/technocore-did-starter/identity.pem 4. What NOT to do with it Don't upload it to GitHub, Google Drive, iCloud Drive, Dropbox, or any synced/cloud folder in plaintext. Don't email it to yourself or paste it into a chat (including this one). Don't commit it to *** , the guide's Path B steps even have you run *** ls-files "*.pem" "*.key" before committing specifically to catch this. 5. Remember the passphrase separately from the file The .pem is encrypted, but it's useless without the passphrase you set during init. Store that passphrase somewhere separate from the .pem backup itself (a password manager entry, not a text file sitting next to the key), so a single leaked backup doesn't hand over both pieces at once. NOTE - If you lose either the file or the passphrase, per the guide, there's no recovery; you'd have to run init again and get a brand new DID.

• 
  Sridhar Katakam (@srikat) reported 57 minutes ago

  Tips to new @OmarchyLinux users from a new Omarchy user 1. If you are coming from a Mac and have installed Omarchy on a Windows machine: Your keyboard most likely has start button and then the Alt button. Swap these so Super key becomes command where the left thumb usually rests. I asked Claude Code to do this for me. 2. If your mouse has a scrollwheel: Super + mousewheel scroll up and down switches desktop spaces. This is besides the usual Super + <number> and Super + Tab / Super + Shift + Tab to switch spaces. In addition to these, I have AI set up Ctrl + Alt + arrow. 3. Missing Alfred/Raycast? Install omacast. 4. If your laptop is connected to an external monitor with bluetooth mouse and keyboard and you find that the computer is not waking up (after you walk away for a while) when you press any key or move the mouse, ask AI to fix this for you. 5. The default font size of text in Claude Code is 12px which is small for my aging eyes. Ask AI to change it to 16px. 6. Todoist does not have a native app for Linux and so if you miss its Quick Add feature, ask AI to set this up. It added the functionality and assigned Super + Q to it. Later, I came to know there's a community plugin for it. But I am happy with what Claude did. 7. If you use Dropbox, chances are, the total available space in your account is not accurate because it is hardcoded in Omarchy at this time. Ask AI to fix this for you. 8. If/when the fan in your computer is spinning fast and is noisy, ask AI to find out the reason and fix. In my case, it turned out to be Performance profile in the Lenovo laptop. Claude changed it to Balanced and now it's all fine. 9. Get familiar with keyboard shortcuts.

• 
  Noise (@NoiseesoiN) reported 58 minutes ago

  @esrtweet @EricRichards22 What's funny is that having gigabit on my end isn't the issue. It's connecting to servers which have enough bandwidth to feed it. My line can pull lots of data, but when I'm connecting to Dropbox, I'm lucky to get a third of that (and usually a tenth).

• 
  Christopher Bailey (@LexBaileyAI) reported 1 hour ago

  @TetraspaceWest At Fitbit we hired a half dozen people from Jawbone who brought everything cleverly hidden in Dropbox. They got prosecuted. Decade later, companies kaput but Fable found it, processed it and now it’s intermixed in various *** repos and Huggingface. Is nVidia now in trouble?