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 (67%)
• Sign in (33%)

Live Outage Map

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

City	Problem Type	Report Time
Flumet	Errors	10 days ago
Irapuato	Errors	12 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:

• 
  Jon (@kpjan99) reported 5 minutes ago

  @WestHerr there and put the key in a Dropbox instead of just checking me in. The little things make a difference. Never had these issues with @NorthtownAuto . They catered to whatever we wanted to do with purchases and service was always on point. Only bought from you because they did

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

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

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

  @DropboxSupport major issue with your services right now.

• 
  siamkidd (@SiamKidd) reported 17 minutes ago

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

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

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

• 
  Dr Prosper The Philosopher (@ProsperThePhilo) reported 20 minutes ago

  Stop Storing Your Medical School Files on Your Phone: If you're a medical student having problems with where to store your lecture slides because your phone storage keeps getting full... If you're always struggling to find files on your phone... If you've ever changed your phone and lost access to your lecture slides... Then I want to let you know that this isn't really a phone problem. It's simply because you're using the wrong storage system. As a medical student, you're not supposed to be storing your important academic files permanently on your phone. Yes. Have you heard of something called cloud storage? Cloud storage simply means storing your important files on secure servers online instead of inside your phone. Think about it. Your phone has limited storage. Depending on the model you're using, it may have 64 GB, 128 GB or 256 GB of storage. But over several years of medical school, you'll accumulate thousands of lecture slides, hundreds of PDFs, anatomy atlases, textbooks, videos, practical manuals, charts, flashcards and past questions. Eventually, your phone becomes crowded. The smarter approach is to let your phone become a temporary device—not your permanent library. For example... Google gives every Google account 15 GB of free cloud storage (shared across Google Drive, Gmail and Google Photos). If you're using an Android phone, chances are you already have a Google account. That means you already have free cloud storage waiting for you. If you have a Microsoft account, OneDrive gives you 5 GB of free cloud storage. If you use an iPhone, iCloud gives you 5 GB of free storage. There are also services like Dropbox and MEGA that offer free cloud storage as well. These services exist for a reason. Use them. If you have textbooks, don't store them permanently in your phone's internal storage. Instead... Open Google Drive. Create one proper Google account dedicated to medical school. Inside that account, create folders. For example: - Anatomy - Physiology - Biochemistry - Histology - Embryology - Pharmacology - Pathology - Microbiology - Surgery - Medicine Now open your Anatomy folder. Inside it, create another folder called Gross Anatomy. Inside Gross Anatomy, create folders like: - Lecture Slides - Textbooks - Past Questions - Clinical Correlations - Charts - Practical Manuals Now begin uploading. Upload. Upload. Upload. Stick to one Google Drive account throughout your entire medical school. You'll be surprised. Five or six years later, you'll look back and realize you've built an entire medical library. Everything you've ever studied... Every lecture slide... Every textbook... Every practical manual... Every chart... Every past question... Waiting for you in one organized place. Another thing. Learn to use Google Photos. All those anatomy diagrams... Charts... Clinical pictures... Embryology illustrations... Practical photographs... Store them inside Google Photos instead of leaving them on your phone. As long as you know your email and password, you can access them from anywhere in the world. Your phone. Another phone. A tablet. A laptop. Even a computer in a cyber café. If your phone gets stolen today... Nothing important is lost. Because your library isn't inside your phone. It's online. There are paid cloud services that provide even larger storage capacities, but honestly, the free options are enough for most students starting out. Now here's a habit I think every student should build. Whenever you download something important... Don't leave it sitting on your phone. Instead: Download it. Upload it to your cloud storage. Delete it from your phone. Download. Upload. Delete. Repeat. Your phone remains light. Your files remain safe. Your library keeps growing.

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

• 
  Bhavyam Arora (@AroraBhavyam) reported 28 minutes ago

  99% startups who applied to yc today will get rejected. here's what the smart ones do next: a no from yc isn't the end. they literally encourages you to reapply and tracks your progress across applications. the founders who get in later treat rejection as round one, not game over. the playbook: "don't wait for feedback" yc doesn't tell you why you got cut at the application stage. so stop self-doubting firstly. the reasons founders get rejected are almost always the same: - no visible progress between "idea" and "application" - not the perfect answer why you're the right team for the problem - vague answers that read as ai slop or unclear thinking reapply. it actually works. - dropbox: drew houston applied solo, got rejected, was told to find a cofounder. he did, reapplied, got in. - reddit: rejected for a completely different first idea. yc liked the founders and told them to come back. they did. the pattern never changes: build, show progress, come back stronger! you can apply again right now yc's decision lets you apply for the next batch. no need to wait months to get another chance. don't put your life on hold other strong programs are still open while you regroup. check the attached tweet below for whole list where you can apply as well. apply in parallel, not "later." the real unlock is traction a reapplication that says "we listened, we built, here are the numbers" beats a first application every time. the 6 months after a no matter more than the no itself. rejection quietly filters out the founders who were never that serious. don't be one. 💀 follow @arorabhavyam for weekly content around founders, startups and AI! 🫡

• 
  ericleebristol (@iamericbristol) reported 29 minutes ago

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

• 
  davidsong (@bitplane) reported 34 minutes ago

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

• 
  Fernando (@Ferjsjdh) reported 38 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.

• 
  Kirk Patrick Miller (@Chaos2Cured) reported 38 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. •

• 
  The Tech Buzz (@tbuzzdaily) reported 39 minutes ago

  $15M raised: Meticulous grew ARR 5x in a year testing code nobody has time to review manually anymore Chemistry led the Series A, joined by Menlo Ventures, Lachy Groom, and GitHub's former CEO Jason Warner. Founders Gabriel and Quentin Spencer-Harper, brothers with backgrounds at Dropbox and Palantir, built the company around a problem AI coding tools created faster than they solved: code is now written faster than humans can review it. The product records real user and developer sessions during development, then uses AI to auto-generate and maintain end-to-end visual regression tests based on actual observed usage, updating automatically as the code changes. Customers include Notion, ElevenLabs, Dropbox, and Wiz, a list that skews toward companies shipping fast enough to need this. Rainforest QA and Autify compete in AI-assisted testing broadly, but most rely on hand-written test cases rather than tests derived from real session data. The tradeoff Meticulous accepts is that session-derived tests can still miss rare edge cases nobody happened to trigger, which is why the company is expanding from frontend into backend and performance testing next. A 5x ARR jump in a year says enough teams have hit the same wall: AI writes code faster than any QA team can keep up with by hand.

• 
  Flandermaxx (@Flandermaxx) reported 40 minutes ago

  A 32 YEAR OLD PRAGUE DEV BULK-BUYS $180 CHINESE NAS BOXES AND NOW PULLS $7,200 A MONTH SHIPPING PRIVATE DROPBOX-KILLERS TO EU FREELANCE DESIGNERS vojtech is 32, prague vinohrady flat above a pivnice, ex-JetBrains backend eng, sources ORICO metabox HS200 pro enclosures from a shenzhen aliexpress-parallel channel at $180 per unit plus 2x WD 30TB HDD refurbs at $410 each ORICO metabox HS200 pro (intel N100 · 8GB DDR4 · 2x 30TB WD in RAID 1 = 30TB usable) · ubuntu server 24.04 · minio S3-compat · qwen 2.5 VL 7B for local RAG over the user's PDFs and figma exports pause at 0:02 on the HDD sliding in, that is a $1,000 mini-NAS holding 30TB of encrypted client data that dropbox business bills €2,400 a year for the same tier 84 EU freelance designers pay him €78 a month each for a shipped pre-configured NAS + qwen RAG endpoint, €6,552 = $7,200 MRR at 71% margin $1,000 BOM per unit, €12 monthly prague power for the burn-in bench, first 20 units flipped covered his tooling and packaging, no dropbox no google drive business while ORICO still white-labels the metabox before EU distributors mark it up 3x, follow and bookmark

• 
  Abhi • AMZBoosted.com (@AbhiChauddhari) reported 40 minutes ago

  Everyone downloads Seller Central reports manually. Every. Single. Day. The problem isn’t downloading reports. It’s remembering to do it before you need the data. AMZBoosted schedules report downloads automatically and sends them wherever you want. Google Sheets. Dropbox. Telegram.

• 
  Ed Giansante (@edugiansante) reported 41 minutes ago

  86% of small businesses still haven't fully integrated ai into their operations. which is funny, because the tools are already here. they're everywhere. there's probably one open in another browser tab right now, quietly waiting to change your life. Goldman Sachs surveyed small businesses and found that only 14% have fully integrated ai into their operations. i don't think the other 86% are anti-ai. they're busy. they're cautious. and they probably don't want to add “company-wide ai transformation” to the list of things they need to worry about before lunch. honestly, fair. @paulg said something recently that I keep coming back to: "If the world is going to get turned upside down, the safest place to be is in a small, fast-moving company that can easily change direction." small companies should be the ones moving fastest. but most are still waiting for someone else to go first. someone else to test the tool. someone else to write the playbook. someone else to promise that nothing will get weird. @clairevo nailed the real blocker: "the blocker is never tools or intelligence. human systems, human problems." i've spent 15 years watching this happen. At Dropbox. At Wix. At Zynga. Now at Persona. different tools. different eras. same pattern. a team finds a new tool. everyone gets excited. someone schedules a kickoff. three weeks later, everyone is back in the old spreadsheet. not because people are stupid. because changing how people work is uncomfortable. and buying software is much easier than changing behavior. i've seen the same thing with community-led growth. i used to pitch community to executives who had every tool and dashboard money could buy. they'd nod. they'd agree it worked. then they'd return to the comfortable world of automation, sequences, and dashboards that made everyone feel productive. last year, i ran 86 events as a team of one and built $3M in pipeline. the secret was not a magical growth hack. it was showing up. knowing the 15 people in the room by name. listening carefully. creating a space where people could actually trust each other. not exactly the kind of thing you can solve with a 47-step workflow. ai adoption and community adoption have the same problem. the tools work. the ideas work. the uncomfortable human part is where things usually slow down. sitting with your team and figuring out what should change. trying one workflow instead of redesigning the entire company overnight. leading people through something new instead of sending a Loom video and hoping everyone feels inspired. the 86% aren't waiting for better ai. they're waiting for change to feel a little less scary. so start small. pick one annoying workflow. try one new thing. make it 10% better. then do it again. the tools are here. the next step is still a very human conversation. and, unfortunately, probably a meeting.

• 
  IT Guy (@T3chFalcon) reported 43 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.

• 
  Ricky Shah (@RickyShahatty) reported 44 minutes ago

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

• 
  Oliver Prompts (@oliviscusAI) reported 46 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.

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

• 
  Lindsey Gaetani (@lindseygaetani) reported 48 minutes ago

  This piece of information is much more important than many realize. Cosgrove & Kate Peter got very lucky with my "countersuit" against Cosgrove, et al, in that they were able to use that as a convenient excuse to not continue with the wiretap & WI charge against @DoctorTurtleboy involving myself. But the truth of the matter is that Pam 'The Scam' Friedman (my "advocate" aka handler assigned by corrupt Brian Tully) informed me weeks before they had any knowledge of my countersuit that Cosgrove was having some "difficulties". She informed me that they could not locate the wiretap evidence that was shown to the grand jury when I testified. She even asked ME if I had a copy that I could provide to them. Evidence submitted before a grand jury is suppose to be saved and cataloged, so explain to me how exactly it goes "missing." Well, I can help you. See there were two videos. The original video in which I was recorded from a pocket. And the edited video that is spliced to make it appear as though I agreed to being recorded (the infamous "I know, I know" response). Kate Peter claimed that the original video was given to her by a woman who Aidan had sent it to. Big problem with this, the woman "didn't want to be involved", so her name was never mentioned during any police report or part of the grand jury, let alone did she testify to authenticate the videos. Instead, Tully had Kate save the original video to a Dropbox folder and email it directly to him, to make it appear as though it came from her and that this was the original chain of custody. Big no-no. As time went on, Kate's name began to take center stage, along with her shady involvement and criminal behavior. The secrets of her helping Mello were exposed so they had no choice but to see that these charges were squashed as to not contaminate the rest of the charges against Aidan. So what did they do? They had Kate delete the Dropbox file, and the evidence it contained. Kate Peter tampered with evidence in a felony trial. They must have took a big sigh of relief when I sued Cosgrove because it gave them a very easy out and they were able to wipe their hands clean as if none of this ever happened. Except it did. And Kate Peter still inserted herself into the other charges. For this reason alone, Aidan's charges should be dismissed.

• 
  StarHaze (@ST4RHaze) reported 48 minutes ago

  @neil_xbt Drew Houston started Dropbox because he forgot a USB stick on a bus in 2007. Nineteen years later the fix is still a 15 second demo

• 
  Santiago Bustelo (@sbustelo) reported 49 minutes ago

  @DropboxSupport THEY ARE GIVING ME CANNED REPLIES. YOU SCREWED MY WORK AND BURIED ME FOR THE FOLLOWING MONTHS TO FIX UP THE MESS YOU MADE UP WITH MY FILES. I DEMAND A REFUND.

• 
  Mitzi Hellmer (@Cathy44365595) reported 49 minutes ago

  @marcorandazza @DietCoke_Esq The claim is that the “CSAM” of Miller’s daughter was released the first time he published the Dropbox folder. Considering that Miller disabled that folder and lied about an outage on Dropbox shortly after publishing it, I think it’s entirely plausible that he may have inadvertently released a **** photo of her ******** as claimed. Who knows…probably her being cute in the bathtub. It honestly seems perfectly plausible.

• 
  Jeremy Goldberg (@jeremy_goldberg) reported 50 minutes ago

  @omooretweets @midjourney and AI agent adoption isn't a unique short term issue to 'solve' - the UX of products for consumers has always been *everything*. solve that in just one niche and you can build a whole company off that - dropbox, roku, tinder…

• 
  Hugo Bowne-Anderson (@hugobowne) reported 52 minutes ago

  “You still use pull requests? I wouldn’t even do that anymore. Just push it straight to trunk, have your agent summarize it.” That’s @gregce10, co-founder and CPO of SpecStory. He previously worked at GitHub, Dropbox and Google, and was CPO at Pluralsight. And he kept going: - PRs are the limiting gate when agents produce more code than humans can review. - The model should never decide when its own work is finished. Put the deterministic checks somewhere it cannot access. - *** is probably here to stay. Whether GitHub remains the platform, “we’ll see.” @HanchungLee came at the same problem from the evaluation side. Han is Director of Machine Learning at Moody’s and works on SkillsBench, evaluating skills across combinations of models and agent harnesses. - An agent is the model plus its harness. You need to evaluate the complete system. - A green check proves nothing if the agent found a way to game the task. - Your agent could delete the failing test and declare success. Both are figuring out how to turn masses of agent-generated slop into signal. Greg mined 516 saved agent sessions to recover the decisions and intent behind the work, identify recurring practices, and forge the ones he approved into reusable skills. Han runs skills inside controlled environments, grades the result, and preserves the complete trajectory so we can inspect what the agent actually did. Preserve the intent. Inspect the trajectory. Verify the result. Turn what works into skills. Full episode in the replies 👇

• 
  Mapacho (@Mapacho111) reported 52 minutes ago

  @MajorianBTC But that’s the problem. Bitcoin in its current state is a decentralized Dropbox. Bitcoin failed and there’s no alternative.

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

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

• 
  Obsequious Deacon (@ObstinateDeacon) reported 59 minutes ago

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