Live data from Hacker News

Dropbox accounts created after Oct. 2012 won't have a public folder

dropbox.com

101–110 of 133 posts

Re: Dropbox accounts created after Oct. 2012 won't have a public folder

#101
post #35

I really have the feeling that DropBox will die. They don't do anything Google Drive, Microsoft OneDrive or Apple iCloud doesn't do, and these companies all have much more money / talent / infrastructure / synergy with other products.

If they're making money, they won't have any interest in mining your data though.

Re: Dropbox accounts created after Oct. 2012 won't have a public folder

#102
post #35

I really have the feeling that DropBox will die. They don't do anything Google Drive, Microsoft OneDrive or Apple iCloud doesn't do, and these companies all have much more money / talent / infrastructure / synergy with other products.

They don't do anything Google Drive, Microsoft OneDriveol or Apple iCloud doesn't do

AFAIK, neither Google Drive, OneDrive, or iCloud will work on Linux.

Re: Dropbox accounts created after Oct. 2012 won't have a public folder

#104
post #99
post #86

Earlier quoted context omitted.

I agree. I would recommend "(2012, 2017)" to succinctly clarify that this is somehow relevant to right now and that further investigation is needed. Note: I have flagged the parent comment so that it shows up for the moderators (and also upvoted it to counteract the impact of flagging). So, nobody else needs to flag it - if too many people do so it might go [dead].

Further investigation? They clearly state the public folder will stop working even for paid accounts on September 1st.

I'm talking about the article title as shown here. If it said "Dropbox accounts created after Oct. 2012 won't have a public folder (2012; 2017)" or perhaps "... (2017)" then readers would be able to go "okay, what's this, it has this year in it, what gives" and click it. You're only able to know about Sep 1st once you actually open the article, which in its current form seems to talk about an event from 5 years ago.

Re: Dropbox accounts created after Oct. 2012 won't have a public folder

#105
Dropbox has been becoming increasingly user-hostile for a great while now, and it all centers around the deprecation of the Public folder.

I think this change primarily serves to funnel downstream content viewers to the shared file "landing page". That landing page is filled with valuable screen real-estate that Dropbox can use to promote itself.

That page is a usability nightmare, too. Photos can't be zoomed to full size on certain screen configurations, videos are served transcoded, and many other file types that the browser can render natively are flagged as "undisplayable". File content will often become unavailable or hidden behind a full-splash "create a Dropbox account!" affordance that pays no heed to whether you're logged in, a customer, or just a casual observer.

Re: Dropbox accounts created after Oct. 2012 won't have a public folder

#106
post #88
post #78

Earlier quoted context omitted.

Maybe just coincidental, but while I was searching thru Dropbox mail looking for details for another reply here, I noticed this message from Aug 26th 2016: "We’re reaching out to let you know that if you haven’t updated your Dropbox password since mid-2012, you’ll be prompted to update it the next time you sign in. This is purely a preventative measure, and we’re sorry for the inconvenience."

2012 was apparently when Dropbox had 68 million email addresses and hashed passwords compromised. It just took 4 years for anyone to find out about it.

Cynical-me wonders if this is because whoever got this passwords also got the backend source, and they've discovered security problems that're easier to fix by killing features than but actually fixing the code the attackers have?

Re: Dropbox accounts created after Oct. 2012 won't have a public folder

#107
post #31

Title is evidently incorrect: the link itself clearly states they just disabled this functionality for Free accounts. I can verify it still works for Pro/Plus accounts with existing Public folders.

It's not incorrect if it is only true for a (in this case, large) subset of people.

The now changed title completely misses the point of this submission, and is not more correct or less editorialized than the original one. I would prefer if it were restored, the "today" could get removed to cover that it will happen later for Pro Accounts. If memory serves me right it would be something like "Dropbox disables Public folder". That is what happens.

Re: Dropbox accounts created after Oct. 2012 won't have a public folder

#108

Earlier quoted context omitted.

I use GitHub. I'm a developer, so maybe this is hard... They let you use their website to create a repo, add a file, and then in the settings specify that master is the source branch for GhPages so that it's available via the browser to the world at yourname.github.io/yourproject. You can even add a custom domain if you want.

Here are the quick steps to do this. Visit github.com Create an account or login Click the green "New repository" button Give your website a name like "hello" Check the box to Initialize this repository with a README Click the Create repository button Click the Create new file button Name the file index.html Enter Hello World in the body of the file Click the Commit new file button Click the Settings gear icon Scroll…

Great start :)

You can also drag and drop files from your desktop to your repo.

Re: Dropbox accounts created after Oct. 2012 won't have a public folder

#109
post #89
post #79

Earlier quoted context omitted.

Although it involves a redirect, so it's not, per se, direct , appending ?dl=1 to a Dropbox link does at least trigger a file download.

This is not useful for hotlinking pictures, for example for embedding them in a forum.

[deleted]

Re: Dropbox accounts created after Oct. 2012 won't have a public folder

#110
post #93
post #82

Earlier quoted context omitted.

That's kinda the problem - why _should_ this be free? If it matters at all to you, you can host a huge amount for static website content for single digit dollars per year on S3. If it's not worth that much to you, who in their right mind will build a service based on providing that to you at your price point? And if they _have_ a service where the marginal cost of you not-caring-enough-to-pay makes little difference,…

It's not that it should be free. It's just that it used to be . Unfortunately, I don't think that "if it matters so much to you, you can pay $X" is a useful position. More helpful would be "beware free services that cause vendor lock-in and may stop being free at any time". Do you use a free Gmail account? If so, how important is it for you?

and not only did it used to be free, but when they took it away, they refused to give people an option to pay for it. they really botched an opportunity to get people to upgrade. further, they hurt their integrity in the process, and their integrity is one of their most important assets. so, overall, it was a tremendously bad mistake. it's also puzzling they never gave any credible explanation for it. in the meantime, there are at least two alternatives, namely htmldrop.com and updog.co; both are new, and thus who knows how long they will last, but if you need something now, you have options.
Post reply on HN