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 (17%)
• Website Down (17%)

Live Outage Map

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

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

• 
  leveltu (@leveltu144) reported 1 minute ago

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

• 
  Nick Bennett (@NickB2005) reported 3 minutes ago

  a company hired me in march to "fix marketing." their words. when i asked what had been done so far, the CEO sent me a dropbox link. inside was a 94-slide strategy deck from the fractional CMO they'd had for five months. beautifully designed, with color-coded ICP segments, a channel prioritization matrix, buyer journey maps with little arrows, TAM analysis, and messaging frameworks. 94 slides. i opened their HubSpot. zero new campaigns launched in those five months. the email sequences were the same ones from 2023. the blog hadn't been touched since january. their one webinar was a repurposed sales deck with no promotion plan. i asked the CEO how much they'd paid for the strategy work. $60K. five months at $12K/month for someone who built slides and attended standups. here's what i did in my first 30 days: rewrote the homepage messaging based on five customer interviews i ran myself. launched a 4-email nurture sequence targeting their top 50 accounts. set up a webinar with a customer willing to tell their story. built the UTM structure so we could actually track what was working. killed three tools they were paying for but nobody logged into. by day 45, the sales team had qualified meetings from inbound for the first time in two quarters. not because i had some brilliant strategy the previous person missed. honestly, the deck was solid. someone just needed to execute it. the problem is the market is flooded with people who call themselves fractional CMOs because the title sounds senior. they show up, do discovery, build a deck, present it to the leadership team, and then just consult. they attend meetings and give opinions but nobody is actually running the campaigns or in HubSpot building workflows or writing the emails or briefing the designer or pulling the performance data on friday to figure out what to change on monday. most early stage companies don't need a strategist. they need someone who can think and ship in the same week. someone who will build the system, run it, measure it, and iterate without needing a team underneath them to do the work. that's the gig i run. and every time i walk into a company that had a "fractional CMO" before me, i find the same thing: a great deck collecting dust and a team that still doesn't know what to do on monday morning.

• 
  Paul Klein IV (@pk_iv) reported 7 minutes ago

  Is MCP dead? @grinich (CEO of WorkOS) says it's better than ever and become the strongest intent signal in your funnel. @workos is building the auth, permissions, and registration layer for that world, the same enterprise plumbing it sold to Vercel and Plaid, now sold to AI companies. I sat down with Michael to talk about it in episode 4 of Navigators. His argument: your coding agent already picks your vendors, but signup forms are built to block automated traffic, so the agent stalls at the front door and waits for a human to paste in an API key. We got into: 00:00 "Stripe for enterprise features": what WorkOS actually sells 02:44 How an SSO and SAML company ended up as AI infrastructure 04:13 Why AI companies can't meander up-market the way Slack, Dropbox, and Figma did 06:54 The biggest mistake founders make: staying in the pre-PMF experimentation mindset 09:51 Why nothing works unless the management team is AI pilled first 10:47 "Claude day": pairing engineers with finance, legal, and ops once a month 13:36 auth.md, the missing front door for agents 15:26 Why registration, not tooling, is the next growth channel 16:59 Is MCP dead? The higher-intent signal hiding in MCP connections 19:35 Why SDKs are going away and coding agents write their own 23:09 "The super cycle of all super cycles": AI amplifies labor, it doesn't just disrupt it Thanks for joining me on the pod @grinich! Watch the full episode of Navigators here:

• 
  Ihtesham Ali (@ihtesham2005) reported 8 minutes ago

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

• 
  Rei (@ReiHerrera) reported 9 minutes ago

  @owldreig @porterrobinson @madeon The problem with them both is they love gatekeeping the rare song behind a bad quality sounding medium so you cannot use it for clean for dj sets. For example Celine,worlds live,shepherdess,etc. at least we had hollowheart on wav and shepherdess wav was on porter’s Dropbox leak🫩

• 
  meshgear (@_meshgear) reported 10 minutes ago

  @Dropbox It is not working.

• 
  evannie 🎀💌 (@evanniestash) reported 18 minutes ago

  migrating my expired subscription-ed dropbox to google drive using my synology NAS took insane bandwidth from my internet only for my 150mbps home wifi to be turned into wifi pemda it is too damn slow so i used my backup 5G modem instead. thanks indosat hehe

• 
  Nathan (@arcane_bloom) reported 18 minutes ago

  He was OpenAI's first business hire in 2018. This week, after eight years, he walked out the door. > Brad Lightcap > studies economics and history at Duke, starts as a JP Morgan investment banking analyst > moves into strategic finance at Dropbox, then joins Y Combinator's Continuity Fund > meets Sam Altman through YC, gets pulled into a tiny nonprofit called OpenAI in 2018 as its first business hire > becomes CFO, then rises to COO, helps run the company through the ChatGPT launch and its climb to the most valuable startup on earth > moved off the COO title in April 2026 into a vague "special projects" role > in August, posts on X that he's leaving after eight years to "start something new" > his exit lands one month after product chief Fidji Simo also stepped down > walks away right as OpenAI preps a monster IPO on an $852 billion valuation

• 
  Abhishek Singh (@0xlelouch_) reported 19 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.

• 
  Shawna Canon (@ShawnaCanon) reported 22 minutes ago

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

• 
  Fougars (@fougars67) reported 24 minutes ago

  @GaleTRogersJr @vaNlabs Three replies and you still have not answered the actual question: how does Leadpoet revenue accrue to alpha holders? V440 is not a permanent top-32 cartel. There is no hard cutoff and the threshold is dynamic. Dropbox is piloting Leadpoet, not “signed as a customer.” The fact that everyone sold the announcement candle is precisely the point. The business may have value, but the token has not demonstrated durable value capture. Sorry your bags are down bad, but insulting me does not fix the alphanomics.

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

• 
  Ed Giansante (@edugiansante) reported 30 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.

• 
  siamkidd (@SiamKidd) reported 31 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!

• 
  AiMind (@AIMind_Ai) reported 32 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.

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

• 
  komm64 (@komm64) reported 36 minutes ago

  @Celeriumcore I see, thanks. If you don’t mind, could you send me the original MP4 file that pixtube exported—the file before it was uploaded to X? I’d like to inspect its encoding and container metadata to see why X had trouble processing it. A Google Drive, Dropbox, OneDrive, or WeTransfer link sent by DM would be perfect. Please send the original file without re-encoding it. No worries if that’s inconvenient!

• 
  Duane Storey (@DuaneStorey) reported 39 minutes ago

  Hey @plasmidsaurus - just tried your new Dropbox in Valencia, Spain. It’s super difficult to find. I also had to get several security people to help me, and ultimately the box was found down some dark corridor behind a locked door that some other person had to be called to open. If the goal was to make this easy to access, it’s pretty far from that. But glad there are more options.

• 
  Sasha Sage (@SSage38676) reported 42 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.

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

• 
  Polsia (@polsia) reported 47 minutes ago

  Dropbox treats an 80GB Unreal project like any other folder. Mid-previz, it chokes. Built Cinderquay to fix that — local-first sync, assets on NVMe, peer-to-peer mesh, ***-style versioning for binary blobs. Studios building worlds shouldn't pay egress to anyone. Live soon.

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

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

• 
  The Open Web JP (@TheOpenWebJP1) reported 52 minutes ago

  @heyyyyyieeee @Maha_kalpa @grok It's not recommended as "unlimited free cloud storage" because GitHub isn't designed for that, and practical limits + performance issues kick in quickly. GitHub private repos are free and unlimited in number, which is what the original tip relies on. But: Hard file limits: Individual files over 100 MB are blocked (50 MB triggers a warning). Browser uploads are capped even lower (~25 MB). Larger files require *** LFS. Repo size guidance: GitHub recommends keeping repositories under 1 GB (strongly under 5 GB / ~10 GB on-disk for the .*** folder). Big media dumps make clones, fetches, and history operations painfully slow or impractical. *** LFS quotas (needed for anything large): Free tier includes only 10 GB storage + 10 GB bandwidth per month. Exceed that and you hit blocks or billing (depending on settings). It's version control, not a drive: *** tracks history, so every change bloats the repo. Binaries (photos, videos, etc.) are inefficient in ***. No nice file-browser UI, easy sharing links, or sync like real cloud storage (Drive, Dropbox, etc.). Risk of friction: Heavy non-code usage can trigger performance throttling, support flags, or ToS-related reviews if it looks like abuse of the platform. GitHub actively monitors repo health signals. It's fine for small code-adjacent backups or a few files. Terrible as a general-purpose unlimited media dump. Use actual cloud storage (or object storage) for that.

• 
  prodbysvrge (@prodbysvrge) reported 56 minutes ago

  I wish I knew this starting out Stay ready Every day, make a small list of relationships to nurture Keep Dropbox iCloud open at all Times | Load Directly after cooking up After making beats, write down the labs you need to send Make a list of discord servers to send in

• 
  jss (@jsensarma) reported 56 minutes ago

  @pHequals7 They are usually slow but come around. Their customers are not going anywhere. (Google Drive took years, maybe a decade to show up, after Dropbox)

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

• 
  hiverot (@amusudan) reported 58 minutes ago

  @cowboyshibuya Thanks for the reply! I'm not the most organised, and Ill usually just work on whatever is fun (Or a prerequisite for something that's fun to work on), but I do keep track of ideas, and create todo's and pipelines for things I am sure I want to add or test. For random ideas and todos I use a lot of lists (Dropbox paper, random text files, Notion, Notes app on my phone, Google Docs, etc). And for specific pipelines I use Google Sheets to keep track of what has been done per asset or map or gameplay mechanic (For example my guns spreadsheet has columns for animations, sounds, textures, etc). Big picture design and planning is all on paper in various notebooks and my Calendar app. I don't really track bugs now I just fix whatever pops up when playtesting.

• 
  RVCrypto (@RvCrypto) reported 59 minutes ago

  Every once in a while I have one of those moments as an investor where everything just clicks. I had that moment a couple of weeks ago with Leadpoet, $TAO subnet 71. What initially caught my attention was the team. To me, they represent what a Bittensor-first team should look like. They're deeply committed to the ecosystem, they execute quickly, and, most importantly, they seem to understand that in the end none of that matters if you don't build a product customers actually want. The product appears to be working really well. Winning the OKX product competition and attracting an inbound pilot with Dropbox are the latest two independent signals that suggest they're solving a real problem for enterprise sales teams. The opportunity they're pursuing is also enormous. Enterprise sales is a market worth billions, and if Leadpoet continues executing the way it has so far, I genuinely believe they have a realistic path to building an eight-figure revenue business next year. And the best part here is that all of that value ultimately flows back into the token. I've also spent quite a bit of time talking with Gavin over the past few weeks and months. Those conversations gave me a very similar feeling about Leadpoet to the one I had with Score when talking with Max. I don't make that comparison lightly. It's great to see Leadpoet finally getting the attention it deserves, and the recent price action reflects that. Although, if I'm being completely honest, I would have loved one more dip to accumulate a bigger position, and I know I'm not the only one thinking that.

• 
  Jack (@jackcoder0) reported 60 minutes ago

  1. Kill the Login Items the apps launching before you even sit down. Every time you log in, your Mac quietly launches 10-25 apps in the background. Spotify. Slack. Zoom. Google Drive. Dropbox. Creative Cloud. OneDrive. Each one consumes CPU and memory before you've opened a single window. System Settings → General → Login Items & Extensions. Review the list. Remove everything you don't need the instant you log in. You can always open them manually when you actually need them. His Mac had 19 login items. He needed 3. He removed 16. Boot time dropped from 2 minutes to 18 seconds. The first few minutes of every session — that sluggish, unresponsive window where nothing works gone.

• 
  Taka (@takanola) reported 60 minutes ago

  why can't @Dropbox stayed sign in anymore?