Yashh is helping me out by beat testing Savoy, and he’s posted some initial thoughts on his blog. He includes a diagram of the database structure (or, most of it, anyway), which will give you a good idea of the kinds of apps Savoy has in place, and explains a bit about how it’s all put together.
One note: Yashh talks about the savoy.contrib.comments app, which I write before the new django.contrib.comments app was released. I’ve debated back and forth about whether to ditch savoy.contrib.comments. It includes some functionality that django.contrib.comments doesn’t (blacklists, whitelists, akismet, etc.), but I’m not sure I really want to maintain it, now that django.contrib.comments doesn’t suck. Obviously, you can always simple choose to use django.contrib.comments instead of savoy.contrib.comments, even if both are in place (in fact, I’m doing that on a client site we’re working on now). What do you think? Is a more advanced comments app worth maintaining now that django.contrib.comments is 100 time less sucky?
001 // Yashh // 09.14.2008 // 11:10 PM
Thanks for the mention. I am sure you are using Savoy comment system on this blog.
002 // Jeff Croft // 09.14.2008 // 11:14 PM
Yes I am! But, again, I’ve considered switching to django.contrib.comments. Can’t decide!
003 // yashh // 09.15.2008 // 7:54 AM
I think that will be a lot of pain. Is it that worth to use django.comments.
004 // Joshua Works // 09.16.2008 // 12:51 AM
Yeah, I’ve flip-flopped on this issue a bit lately, too. Seems like it’d almost be more maintenance to build a comment moderation util (like comment-utils, but with all the niceties you’ve built into Savoy) that works with django.contrib, than just keeping what you’ve got.
Gotta say, the comment-utils method just feels better, and I can imagine if you release Savoy, the bundled comments would be a point of contention, and for legitimate enough reason.
How nontrivial would it be to move your moderation stuff (blacklists, trollish, etc) to a separate model using some of the new comment signals?
005 // Jeff Croft // 09.16.2008 // 5:57 PM
Not entirely sure, but I’ll definitely look into it (I’m also curious to see if/when James Bennett updates his comment-utils app to work with the new django.contrib.comments).
006 // Scott McCracken // 09.17.2008 // 9:29 AM
It’s exciting to hear that you might consider releasing Savoy. I have been working on a similar setup locally, inspired by sites like yours and other great Django sites in the community. One major difference, however, is mine doesn’t actually work! I’ve enjoyed the learning experience, but always enjoy seeing how other people approach similar problems.
In terms of comments: I agree with Joshua Works that the comment-utils feels better, especially now that snippets are available for integrating akismet. However, with comment spam such a global problem, additional features such as blacklist / whitelists would always be welcome additions.
007 // theju // 09.23.2008 // 4:15 AM
I am the student who worked on the new comments system. A couple of features didn’t make it because of the lack of time to document them (I was distracted by pony-seekers :). But the missing features are planned for 1.1 (earlier, if possible). Some of these features are:
Though I haven’t seen your savoy code, I really would love to see how you’ve written your comments app and implemented features like blacklists.