Already? The movie only just came out! Nice work.
Our Django Book is Launched
51–60 of 136 posts
Re: Our Django Book is Launched
#52It always puts a bad taste in my mouth when information/knowledge is locked behind a pay-wall. It frustrates me when I think that someone somewhere is getting turned down from what they want to learn from because they had no money to pay for it or doesn't have the means to pay for it. I know the authors should profit but why can't they do something like https://mitpress.mit.edu/sicp/ or http://debian-handbook.info/ o…
you just forgot to read the part that says:
Can't Afford the Book? If you're struggling with finances and can't afford it, let us know and we'd be happy to send you a free copy. Drop us a note at 2scoops@cartwheelweb.com.
Re: Our Django Book is Launched
#53It always puts a bad taste in my mouth when information/knowledge is locked behind a pay-wall. It frustrates me when I think that someone somewhere is getting turned down from what they want to learn from because they had no money to pay for it or doesn't have the means to pay for it. I know the authors should profit but why can't they do something like https://mitpress.mit.edu/sicp/ or http://debian-handbook.info/ o…
Disclaimer: I'm one of the authors.
First, if you can't afford to buy the book, then do as we asked on http://django.2scoops.org. Email us and we'll send you a copy. Money should never be in the way of education.
Second, this book took hundreds of hours to write. For weeks we've put in 12-14+ hour days putting it together. We did it instead of working in an office or doing consulting. If we don't charge then we can't put this sort of thing together and maintain it.
Unless, of course, you want to sponsor us to do this sort of work. ;-)
Re: Our Django Book is Launched
#54[deleted]
Re: Our Django Book is Launched
#55It always puts a bad taste in my mouth when information/knowledge is locked behind a pay-wall. It frustrates me when I think that someone somewhere is getting turned down from what they want to learn from because they had no money to pay for it or doesn't have the means to pay for it. I know the authors should profit but why can't they do something like https://mitpress.mit.edu/sicp/ or http://debian-handbook.info/ o…
If you look further down the page it says that they are happy to send free copies to people that can't afford it. Which shows you didn't even bother to read their website before complaining.
Tell me. Do you donate all your time to sharing knowledge for free, or do you work a nine to five job like most people?
Have you written a book yourself that you subsequently released for free, or you just trying to dictate what other people should do with their hard work?
Clarification: The info about getting free copies is on http://django.2scoops.org/ rather than the blog post
Re: Our Django Book is Launched
#56Considering purchasing since I was thinking of diving into django for my next project.. If I buy the PDF now, and you eventually release an EPUB or other format, will I get access to those files (with updates) as well?
Honestly, I don't know enough about ePub distribution to answer you. I would love to do that though.
ePub is important to me as well. Mostly because it's the format that http://readmill.com supports.
(I'm aware I can convert it to ePub myself)
Re: Our Django Book is Launched
#57Just finished the first chapter and I'm probably not putting it down again (after I write this comment). This feels like something Django really needed (or I needed for Django), despite its extensive documentation. I find analogies are very helpful for my understanding and the ice cream one is perfect. The fact that "Each Chapter Stands On It's Own" is the great too!
Re: Our Django Book is Launched
#58[deleted]
Re: Our Django Book is Launched
#59Just finished the first chapter and I'm probably not putting it down again (after I write this comment). This feels like something Django really needed (or I needed for Django), despite its extensive documentation. I find analogies are very helpful for my understanding and the ice cream one is perfect. The fact that "Each Chapter Stands On It's Own" is the great too!
I'm one of the authors. Can we use "I find analogies are very helpful for my understanding and the ice cream one is perfect." as a quote on the site?
Re: Our Django Book is Launched
#60Earlier quoted context omitted.
A brief read of the sessions docs throws up three concerns 1. Stuffing a lot into a session cookie (the term can easily exceed he 4096 bytes limit suggests that this is not designed just to store session ids) 2. There is implication of one site secret key - a flaw in Flask which it's dangerous was supposed to fix - but even so there is the implication the MAC check guarantees No one has played with the cookie. This i…
Yes, if you change the defaults and don't read the docs it is possible to get in trouble.
That seems disingenuous - a read of the docs indicates to me that the default is to store a lot of app specific info on an encrypted cookie - what is stored on that cookie? Admin rights? Total credit in dollars? Discount codes? That's app specific but if the implication is its trustable then a lot of attack vectors just opened up. who chooses the encryption? Is a new key generated per user / session? If so how is that stored and looked up? Any lookup drops the secure vs speedy trade off and so you need not store anything in the session cookie
Yes it is possible to make a app insecure - we do it all the time. My question is how to generically and sensibly reduce the attack surface - you know, best practises.
I just do not see the trade off of "encrypt everything onto a cookie and use that instead of cache lookups" as one I am willing to take - but I would like to know if I am in a minority, if there is evidence backing either side etc
Edit: this appears to have been typed out of my bottom - the parents has pointed out the clearly marked defaults for django that meet seemingly most or all of my concerns above - but I cannot reply just yet (not sure why it might be a enforced Cooling off period) so this is the best way to say mea culpa