Dropbox refuses Public folder in new accounts
Today, a dropbox email came in with the following content:
After July 31st, the Public folder will no longer be created in new Dropbox accounts. If your application uses the functions of the Public directory, we recommend switching to the / shares API. In existing accounts, the Public folder will function as before.
Sharing is completely transferred to the link mechanism introduced in April, which means that in new accounts it will no longer be possible to get a direct link to the file from the dropbox. For those for whom this function was critically necessary, you can look towards Cubby.
After July 31, we will no longer create Public folders in any new Dropbox accounts. If your app depends on Public folders, we recommend switching to the / shares API call. Public folders in existing accounts, however, will continue to function as before.
After July 31st, the Public folder will no longer be created in new Dropbox accounts. If your application uses the functions of the Public directory, we recommend switching to the / shares API. In existing accounts, the Public folder will function as before.
Sharing is completely transferred to the link mechanism introduced in April, which means that in new accounts it will no longer be possible to get a direct link to the file from the dropbox. For those for whom this function was critically necessary, you can look towards Cubby.