SummitPost.org

And apologies from me. My assertion that cookies are so limited in size just isn't true. It's just because when I did web programming years ago it either was true due to browser limitations or we were just so scared of crashing the servers by uploading massive cookies on every request that we wished it were true. My bad. Fill your cookie up with your book manuscript and have fun.

sjarelkwint wrote:MVS, i'll take through another channel about this, you can do it but in php you need a P3P cookie setting which ain't allowed no longer in IE6.

Also it seems that it is hard to protect it since I found some solutions but all give the solution the make an easy hack into the databasxe of summitpost which can't be the point ...
Seems like it is hard to create a thing like this where it is impossible to change some of the cookie so you can make a hack out of it ...

EDIT: just because ...

Welcome to the real world of software engineering! (buggy, non-compliant, and if it's "easy," ur doing it rong )

It just occurred to me, that an alternative to this cookie scheme, is to edit your submission beforehand in Word or even an ascii editor, and then upload it when you are done. I know that isn't elegant (e.g., likely to add to system slowness, buggy, software-dependent), but it seems -- remarkably -- to work. I realize that a simple procedure is nowhere as good as one that requires programming in circles to make something really complex and cool, but some people like simple procedures that work.