Dear Web2py users,

the link to the book is broken and you can find the new (temporary) link to 
the book here: 
https://www.dropbox.com/s/fuik35ayg686de3/web2py_manual_5th.pdf?dl=0

One the one side there is an easy fix to a broken link, replace all 
references to the new URL.
Yet the problem is bigger and I am very upset.

I use Dropbox and Dropbox has a public folder. Everything in this folder 
had a public direct link. I keep the web2py book there along with talks, 
code, etc. and a lot of material I have shared with you over the years, 
with my students, and collaborators. These links have been published in 
various places outside my control.

Dropbox has decided to drop support for a default public folder since 
September 1, and required that I share it explicitly. I tried that and to 
my surprise two bad things happened:
- the new links are different than the original links so they are broken 
anyway
- the content of the folder becomes searchable and I do not want that. I 
wanted direct links to the content but I do not want everybody to see 
everything.

I emailed them but looks like they have made their mind. Although they 
provide a solution to sharing they do not provide a solution to the broken 
links to previously shared content. I have been a long term fanboy of 
Dropbox but they made a huge mistake and I will probably be moving all my 
files somewhere else. This issue is bigger than the link to the web2py 
book. 

When I find a new reliable home for my public files, I will replace the 
link in the web2py repo.
I apologize for the inconvenience.

Massimo

-- 
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
--- 
You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to