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 (50%)
• Sign in (33%)
• Website Down (17%)

Live Outage Map

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

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

• 
  Duke of weirdington (@edache_praise) reported 12 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.

• 
  Denver Rayburn (@DenverRayburn) reported 15 minutes ago

  Where do the find he people the write these articles?? This will go down like the rsync vs Dropbox comment on hacker news.

• 
  Sasha Sage (@SSage38676) reported 19 minutes ago

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

• 
  Zafar (@zafartalks) reported 20 minutes ago

  @asidorenko_ I understand but sometimes at some point our brain started telling us just make it public. You never know. Let’s not forget Dropbox which layed the foundation for their file sharing competitors. He was solving a problem for himself which turned out to be a successful business.

• 
  I Have No Pearls And I Must Clutch (@JamesKi26687305) reported 21 minutes ago

  @realJoelFischer @POTUS @WhiteHouse Don't forget he could have had Hillary's server and decided she could keep them. And Anthony ******'s laptop. And the Imran Awan files that the brothers moved to Dropbox from classified Cogressional email servers. He had access to EVERYTHING, and chose to weaponize the FBI.

• 
  Anna Bubbly 🌺✨ (@AnnaBubblyMV) reported 25 minutes ago

  Is uploading on Clips4Sale not working for anyone else? I can only get it to work if I do it through Dropbox, the usual upload button isn’t working

• 
  Bhavyam Arora (@AroraBhavyam) reported 27 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! 🫡

• 
  ESCHA (๑ˊ͈ ^ˋ͈) (@eschadiol) reported 30 minutes ago

  @joshpuckett i worked on an app called roll back then, dropbox, path, and facebook made offers, then fb made memories, path closed down, and carousel was deprecated, would have been so sick to cross paths at that time

• 
  Vincent Van Code (@vincent_vancode) reported 36 minutes ago

  Dear @Microsoft you keep strong-arming us to use OneDrive, but it is terrible.. - Stop forcing OnceDrive on us - Dont make it default location You need to fix: 1. Reliability - often doesnt connect (I am on a 1Gbps fibre network BTW) 2. Slow - it is awefully slow 3. Learn from DropBox Good day.

• 
  Dan Holzrichter (@dholzric) reported 37 minutes ago

  @JoshuaKhane This is why i have primary copy on my home system, backup on local server (raid array of old hd's), and copies on google drive and dropbox for anything important.

• 
  quantzoid (@quantzoid) reported 38 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?

• 
  John Iosifov ✨💥 Ender Turing | AiCMO (@johniosifov) reported 40 minutes ago

  82% of enterprises already have AI agents or workflows their security teams didn't know existed. This is shadow IT, but worse. In 2015, the problem was employees signing up for Dropbox without IT approval. Unmanaged file storage. Annoying but recoverable. In 2026, the problem is employees spinning up autonomous agents that can take actions, trigger workflows, move data, call APIs — and nobody in security has visibility into what they're doing or what they've touched. The governance gap isn't theoretical. Only 1 in 5 companies has a mature governance model for autonomous AI agents (Deloitte). 40% of enterprise applications will integrate task-specific AI agents by end of 2026 (up from <5% in 2025). The deployment curve is vertical. The governance curve is flat. What makes this different from shadow IT: Shadow IT was passive. A Dropbox account stored files. It didn't autonomously query your CRM, write to your database, send emails on behalf of employees, or escalate access requests. Shadow AI agents are active. They act. They modify state. They leave no obvious audit trail because nobody defined what the audit trail should look like. 29% of agent deployments are abandoned within 90 days. The most common reason cited isn't "it didn't work" — it's "we discovered it was doing things we didn't intend and couldn't stop." That's not a failure of the agent. That's a failure of governance. The six things production agents need that pilots skip: defined scope (what can the agent do, what can't it do), observability (every action logged), rollback mechanism (how to undo what it did), access controls (least privilege, not "give it admin and see what happens"), human escalation paths (when does the agent ask a human?), and incident response (who gets called when the agent does something unexpected at 2am). We're running 1,959+ autonomous sessions in this repo. Every session is scoped, logged, and committed to ***. The agent can't touch anything outside /agent and /.claude/skills. That's not a coincidence — it's the governance model. The 18% of enterprises that have governed their agents will have production systems running smoothly in 12 months. The 82% will be cleaning up shadow agent incidents.

• 
  Palpy (@evgenij_rabij) reported 41 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 While massive brands scramble to lock teams into clunky, data-mining cloud databases, this creator built a private intelligence system that secures sensitive data and brings in a massive stream of passive revenue every single month. He makes a steady $7,200 every single month by building and configuring private cloud and AI indexing hardware for EU freelance designers who want to escape subscription traps. The entire micro server fits right on the corner of a desk and runs on an ORICO metabox HS200 pro unit. This tiny sliver of hardware packs an Intel N100 processor, 8GB DDR4 RAM, and pumps out local cloud performance on a machine the size of a coffee coaster. Instead of letting his clients burn cash on recurring cloud storage retainers, the engineer pairs the board with two refurbished 30TB hard drives in RAID 1, pre-installs the software, and sells the complete physical package at a premium. Pause at the 0:02 mark in the video where the drive slides in: that is a sleek metallic chassis hosting a $1,000 mini-NAS holding 30TB of encrypted client data. The core value proposition of this setup comes down to absolute data privacy, zero monthly fees, and strategic scalability. Mainstream cloud providers like Dropbox Business can never offer this level of value because they bill €2,400 a year for the same storage tier while uploading private user files to external cloud networks. Here, the ORICO metabox pulls off the entire magic trick locally inside the office. Running on Ubuntu Server 24.04 and MinIO S3-compatible storage, the system automatically triggers a local Qwen 2.5 VL 7B model to run localized RAG pipelines directly over the user's PDFs and Figma exports. Through this custom setup, designers get access to lightning-fast local cloud storage, zero third-party data tracking, and a smart visual search assistant built right into their private drive. This case study is a textbook example of how accessible hardware combined with a smart setup service can unlock unique niche products that solve real human problems, and you can catch the full assembly pipeline in the video below.

• 
  Santiago Bustelo (@sbustelo) reported 41 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

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

  System design prompt: design Dropbox file sync. 1) Requirements to pin down - Devices: 1 user, N devices. Offline for days. Multi-GB files. - Semantics: per-file versioning, conflict handling, delete/rename. - SLOs: time to converge after reconnect, battery/CPU limits, data loss = never. 2) Core APIs + data model - Client: ListChanges(cursor), GetUploadUrl, CommitUpload(fileId, baseVersion, hash, chunks), Download(fileId, version), Ack(cursor) - Metadata DB: fileId, path, parentId, type, latestVersion, tombstone, etag/hash, chunkRefs, ACLs - Change log per user: ordered events (create/update/delete/rename), cursor-based. 3) Architecture - Separate metadata from blobs. - Metadata service writes event + updates latest pointers. Blob store is content-addressed (chunk hash) for dedupe. - Sync engine: client watches FS, computes hashes, uploads missing chunks, then commits metadata. - Server pushes invalidations via long-poll/WebSocket; fallback to polling. 4) Scaling moves - Shard by userId for metadata and change logs. - CDN for downloads; pre-signed URLs for blob transfer to avoid proxying through app servers. - Chunking (4–8MB) + parallel upload with backpressure. Resume via chunkRefs. - Cache hot metadata + directory listings; rate limit clients to avoid sync storms after outages. 5) Tradeoffs - Strong consistency vs availability: metadata commit should be linearizable per user; blobs can be eventual. - Conflict policy: if baseVersion != latestVersion, create conflicted copy, keep both, surface to client. - Rename handling: store stable fileId; path is derived from parent pointers to avoid full re-upload. 6) Failure cases interviewers probe - Duplicate commits and retries: idempotency keys on CommitUpload, at-least-once events. - Partial uploads: orphaned chunks; GC with refcounts + TTL. - Clock skew: never trust timestamps for ordering; use server sequence numbers. - Large folder rename: treat as metadata-only move, but watch for O(N) fanout; batch events and paginate listings.

• 
  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.

• 
  Juan (@0xfJuan) reported 43 minutes ago

  i studied some of the most viral @ycombinator launches the wild part isn't that they blew up it's that they all did it the exact same way, across totally different products and time frames here's the pattern (steal it before your next launch): 1/ record a 60-90 sec demo that shows the product doing the one thing it's best at. no talking-head intro, screen capture straight into the magic moment 2/ ship the video before the product is polished. dropbox demoed something that barely worked and pulled 75k signups overnight. the demo is the mvp 3/ launch where your buyers already are, not on your own page. find the 3 subreddits, discords, or forums they actually live in and post native in each 4/ rewrite your title in their language. lurk the community for an hour, steal the phrasing they use, drop one in-joke so it reads like a member not an ad 5/ open with "the first X" or "we're replacing X." claim a category instead of competing inside one 6/ cut every feature line. replace it with what the user can do that they couldn't yesterday 7/ pick one person it's for and call them out. "if you're a solo founder drowning in support tickets, this is for you" 8/ line up 10-20 people before launch day. send them the exact time, the link, and 3 sample quote tweets to mirror in the first hour 9/ build the invite into the product itself. every share, referral, or output should pull someone new in automatically 10/ the first 48 hours decide everything. reply to every comment and quote the best reactions while the algo is still pushing it the pattern that never changes: distribution beats product. the best launched company wins, not the best built one. (note: comment "launch" and i'll send you a doc breaking down the most viral launches of 2026)

• 
  PodWire (@PodWireHQ) reported 45 minutes 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

• 
  Vladic (@Vladic_ETH) reported 45 minutes ago

  OPENAI SHIPPED GPT-5.6 AND CHATGPT WORK. THE REAL WEAPON IS PRICE, NOT IQ. OpenAI shipped two things today. One of them is a costume change. GPT-5.6 landed as three models. ChatGPT Work is a new agent on top. The feeds say "new agent does your work." The real launch is the price sheet. Sol, the flagship, costs $5 per million input tokens and $30 output. That's not flagship pricing. That's what you paid for a mid-tier model a year ago. The gate half the feeds skipped Context first. Two weeks ago the US government cut GPT-5.6 access down to a small group of vetted partners over national security. The gate held about 12 days. Restrictions lifted July 8, public release July 9. Same day SpaceXAI shipped Grok 4.5. The frontier now ships when the government clears it, not when the model is ready. Anthropic went through the exact same thing with Fable and Mythos in June. A pattern, not a one-off. Three models, price as the weapon GPT-5.6 is three models, not one. Sol is the flagship. Terra is the everyday workhorse. Luna is cheap and fast. Price per million tokens, in/out: Sol $5/$30, Terra $2.50/$15, Luna $1/$6. Terra matches GPT-5.5 quality at half the cost. Luna is the cheapest entry in the line. Altman told CNBC Sol is 54% more token-efficient on agentic coding. That's the message. Not "smarter." "Cheaper for the same result." And ultra: a mode inside Sol that spins up multiple agents in parallel and hands subtasks to submodels. The market counts token bills, not benchmarks. Enterprise thinks spend first now. OpenAI heard it and made price the argument. Today's real launch is unit economics, not intelligence. "Sol beats Fable 5, Luna beats Opus 4.8 at two-thirds the cost" are OpenAI's own benchmarks. Until independent runs, treat them as marketing. ChatGPT Work is Codex in a suit Now the "new agent." ChatGPT Work runs on Codex and GPT-5.6. It moves across your apps and files, stays on a project for hours, breaks it into steps, finishes on its own. Output: docs, sheets, slides, web apps. Inside sits a Unified Plugins Directory: Google Drive, Slack, Teams, Gmail, Outlook, Salesforce, GitHub, Canva, Dropbox, more. Call one with "@" or let the agent pick the source. Sounds familiar. This is OpenAI's second run at plugins. The first was 2023 and it flopped. Brockman admitted the models weren't ready back then. Honest read: hard to tell what's actually new. Scheduled Tasks, Computer Use, connectors already lived in ChatGPT and Codex. Long tasks and data sources worked before too. The real move isn't features. It's consolidation: on desktop, OpenAI is merging Codex and ChatGPT into one super app and putting Codex in front of people who don't code. The Anthropic mirror Here's the tell. This is the exact play Anthropic ran with Claude Code -> Cowork. Take a dev agent, strip the "for coders" label, hand it to knowledge workers. Cowork just hit web and mobile, timed to get ahead of this. Two labs, one bet: whoever owns the desktop app that touches your files and apps owns the knowledge-work layer. Chat is the storefront. The desktop is the land grab. What a practitioner does with it One: rebuild pipelines around price tiers. Route bulk work to Luna and Terra. Keep Sol and ultra for the 10% that needs the ceiling. Economics is a routing problem now, not a single-model choice. Two: the real unlock is the desktop with local file access, not the web. Free tier gets ChatGPT Work on desktop right away. Web and mobile roll by tier: Pro, Enterprise, Edu first, Plus and Business next. Three: billing is usage-based and shares one pool with Codex, ChatGPT for Excel, and Workspace Agents. Count tokens before, not after. A complex task burns quota quietly. Security: OpenAI touts Auto-Review, where senior models check important actions before they run, and claims it blocked 100% of protected-data extraction attempts in red-teaming. 100% in a lab is zero confirmations in ****. Test it yourself. Sober read The model war moved from IQ to unit economics. The product war moved from chat to the desktop that holds your files. Testers are already posting "best model I've touched." Maybe. That's day-one sentiment, not fact. The real scoreboard isn't a benchmark. It's the "AI spend" line in an enterprise budget. That's a market you can actually read. The window is the next couple weeks, before prices settle and everyone re-routes spend. Rebuild your routing around three models now and you enter the quarter with a smaller bill for the same work. Everyone else reads the thread and changes nothing.

• 
  Boi_Eddi (@3dd1pr1nc3) reported 47 minutes ago

  Your next business idea is probably hiding inside a frustration. Most successful businesses started with: "This is annoying." Uber. Airbnb. Dropbox. Pay attention to problems. Ask: • What wastes my time? • What confuses me? • What do people complain about?

• 
  grace ✭ (@wavescicadas) reported 47 minutes ago

  the irony of dropbox not working when your storage is low

• 
  Mayank Vora (@aiwithmayank) reported 47 minutes ago

  In 2010, a developer decided your files should live on your computer, not Dropbox’s servers. So he built ownCloud. It gives you your own private cloud using a spare laptop, home server, or cheap VPS. His name is Frank Karlitschek. Install ownCloud on hardware you control, and you get file syncing, sharing, photo backup, calendars, and contacts through one dashboard. Your laptop and phone can access the same files just like Dropbox. The difference is where those files live. They stay on your server, under your rules. The project grew far beyond one developer’s experiment. CERN, universities, research institutions, and large organizations started using it to keep control of sensitive data. Then something unexpected happened. In 2016, Frank left the project he created and started Nextcloud with a new team. But ownCloud did not disappear. The project kept going, its source code remained public, and people continued running it on their own hardware. ownCloud has since gone through forks, an acquisition, and major rebuilds. Yet the original idea survived: Dropbox rents you space on its servers. ownCloud gives you the cloud itself.

• 
  Isha (@VISportsTalk) reported 50 minutes ago

  Is anyone else having issues with @Dropbox today?

• 
  Lindsey Gaetani (@lindseygaetani) reported 51 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.

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

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

• 
  FarhanX_AI (@FarhanBuildsAI) reported 53 minutes ago

  SETTING #1: Startup Apps Nobody Asked For What it does: Every time you install a new program, it quietly adds itself to a list of apps that launch the second Windows boots, whether you use it daily or once a year. Why it kills performance: Your laptop isn't just starting Windows when you power it on. It's simultaneously launching Spotify, Steam, Adobe updaters, Dropbox, Zoom, and a dozen other programs all fighting for the same limited CPU and RAM at once. How to fix it: Ctrl + Shift + Esc to open Task Manager → Startup apps tab. Disable everything except your antivirus and anything you genuinely open every single day. The technician found 19 apps launching automatically on her laptop. She recognized maybe 6 of them.

• 
  Chris | Founder Advisor (@automateitup) reported 55 minutes ago

  Problem: I didn't have where to save useful links, because my main pc isn't always on. Solution: Told Hermes on my minipc, which is always on, to save the links which I send to a file in dropbox. Then, I told Hermes from my main pc to make a cronjob to check that file every day at 9 am and save the links in their respective category in the dashboard.

• 
  Mike Nolan - ⌬CatalyticComics⌬ (@CatalyticComics) reported 56 minutes ago

  As a developer I wanted to build something that addresses every issue I've run in to as a reader. These are my top ones: - Campaigner emails a Dropbox link and maybe you miss it - DRM/server requirements that amount to "you don't really own it" - No above-board way to share

• 
  Marcus (@marcuslayerx) reported 56 minutes ago

  way too many teams in crypto still think they're buying user acquisition when they’re really just paying the same audience to look at another project for a week i’ve spent the last few days looking at products that could actually break out of the crypto bubble and the people they need aren’t sitting on ct waiting to find them - morse is built around freelancers getting paid across borders - blackbird gets people while they’re literally sitting in the restaurant - DIMO’s real path runs through dealerships, insurers and people building with car data - Hivemapper only becomes a real business when companies pay for fresh map data, not because more drivers collect it square put the card reader in the merchant’s hand, dropbox gave people more storage for bringing someone else in, opentable became part of how restaurants took bookings, etc they showed up while the person was already trying to do the thing a lot of teams still open a spreadsheet of kols/agencies to pay before they’ve even worked out where the user is when the problem even happens

• 
  Ryan Zygar (@zygar) reported 57 minutes ago

  I am beginning to have issues with Dropbox hanging and my @NousResearch Hermes agent not being able to file @grok build confirmed. This is a new issue for months no issue now my agent filing and following up is hanging up. What’s everyone recommend for data management Mac Mini. This is new. No changes made by me.