We did a lot of research and thrashed it out for ages on the mailing list, and couldn't find a better solution. If you have one, please feel free to propose it on the django-devs list.
Mercurial's graphlog extension, the hg glog command (or hg log -G) which creates an ascii revision graph in your terminal. I'd assume hgk uses the same algorithm, but that's not certain, so I'd like to see how it compares with hgview
I'm sorry you don't like the CSRF protection in Django.
Well it's not that I don't like it as much as it doesn't like me: I saw the warning about javascript, but javascript is activated in my Camino so I didn't worry to much, and then it rejected me. Repeatedly. Which I could only link to my pretty systematic refusal of cookies.
hgview seems to be very similar to hg glog. hgk seems to use some other sorting algorithm altogether.
Well it's not that I don't like it as much as it doesn't like me
Oops, sorry, I was thinking that you were referring to my Django CSRF work for some reason, not the CSRF protection on this blog, which I had completely forgotten about.
I do implement CSRF protection on this blog using cookies. My reasoning is basically the same as for Django, though. I don't know of an adequate solution that doesn't use cookies, apart from using AJAX for every POST, which I'd like to avoid.
If you have cookies disabled, the reason that you might not have this problem with other sites is that most haven't given a thought to CSRF, and many have flawed solutions.
hgview seems to be very similar to hg glog. hgk seems to use some other sorting algorithm altogether.
how very bizarre
I do implement CSRF protection on this blog using cookies. My reasoning is basically the same as for Django, though. I don't know of an adequate solution that doesn't use cookies, apart from using AJAX for every POST, which I'd like to avoid.
I don't mind it much, it's just that there's a warning that javascript needs to be enabled to go past the spamcheck, but none that cookies be enabled to go past the CSRF.
I added a warning about the cookies now, thanks! — luke
Comments §
btw your crsf protection stuff also requires cookies. That's vile.
@masklinn:
http://lukeplant.me.uk/uploads/hgview-shot2.png
I'm sorry you don't like the CSRF protection in Django. The rationale behind the implementation is here: http://code.djangoproject.com/wiki/CsrfProtection
We did a lot of research and thrashed it out for ages on the mailing list, and couldn't find a better solution. If you have one, please feel free to propose it on the django-devs list.
Mercurial's
graphlogextension, thehg glogcommand (orhg log -G) which creates an ascii revision graph in your terminal. I'd assumehgkuses the same algorithm, but that's not certain, so I'd like to see how it compares withhgviewWell it's not that I don't like it as much as it doesn't like me: I saw the warning about javascript, but javascript is activated in my Camino so I didn't worry to much, and then it rejected me. Repeatedly. Which I could only link to my pretty systematic refusal of cookies.
hgview seems to be very similar to
hg glog.hgkseems to use some other sorting algorithm altogether.Oops, sorry, I was thinking that you were referring to my Django CSRF work for some reason, not the CSRF protection on this blog, which I had completely forgotten about.
I do implement CSRF protection on this blog using cookies. My reasoning is basically the same as for Django, though. I don't know of an adequate solution that doesn't use cookies, apart from using AJAX for every POST, which I'd like to avoid.
If you have cookies disabled, the reason that you might not have this problem with other sites is that most haven't given a thought to CSRF, and many have flawed solutions.
how very bizarre
I don't mind it much, it's just that there's a warning that javascript needs to be enabled to go past the spamcheck, but none that cookies be enabled to go past the CSRF.