Slashdot Mirror


Weblog System Features Compared

prostoalex writes "The question of the best weblogging system out there arises quite often, especially after the new licensing scheme introduced by MovableType. Here's a rather detailed breakdown of currently popular blogging and content management systems. Out of 11 software packages, 10 run on any server with variations of Perl/PHP and MySQL/PostgresSQL, and one requires Windows and .NET Framework. 4 are licensed under GPL, 3 are under BSD. Mark Pilgrim explains why licensing is suddenly important."

32 of 269 comments (clear)

  1. Great site & Favs by netfool · · Score: 5, Informative

    Though it's aimed more at CMS's rather than blogs, it's definatley a great place to try out multiple CMS's before installing them.

    Check it out - OpenSourceCMS

    My current favorites:
    Mambo
    Wordpress
    E107
    and last but not least Geeklog

    --
    Left 4 Dead Gaming Group - http://www.l4dgg.com
    1. Re:Great site & Favs by millette · · Score: 3, Informative

      Also check out CMS Québec, the Oscom matrix and the CMS matrix - mostly for CMSes, but blogs often fit that category too.

    2. Re:Great site & Favs by dealsites · · Score: 3, Interesting

      This is not a troll, but I've seen tons of these sites suffer from a slashdotting. Now I understand that the Slashdot crowd can deliver quite a punch, but many of these Open Source CMS systems have too many mysql database queries per page. That will reduce your capacity even further than bandwidth. Especially on a popular shared hosting plan. I'm a huge Postnuke fan and I usually have about 25 people on my site at a time (max), and one day got slashdotted. I saw the number of users grow to about 350 online at one time (based on a 5 minute interval). The page slowed down some, but I was suprised that it stayed up the whole time.

      Disclaimer: I'm not sure how MANY people it actually takes to bring down a page, but this was a huge number of visitors for my site. Anyone know how many people are on Slashdot at any given time?

      --
      New deal processing engine online: http://www.dealsites.net/livedeals.html

  2. You Missed the BEST CMS out there by ScurvyDawg · · Score: 4, Informative


    GeekLog is the best and most secure PHP CMS out there.
    On top of this it is easy to use and setup.

    How you missed GeekLog I will never know.

    1. Re:You Missed the BEST CMS out there by Doctor+Crumb · · Score: 5, Informative

      Geeklog is great, but it is seriously lacking protection against comment spam. I've made a patch to require a delay before submitting a comment. I would love to have some other protections as well, but haven't needed to code up blacklists or anything yet. One neat suggestion was to disallow anonymous comments that had more than 2 links in them.

    2. Re:You Missed the BEST CMS out there by ScurvyDawg · · Score: 3, Informative

      There are a number of ways you can deal with the comment spam. The simplest is change the word comment to something else in your language file. This makes it tough for robots to find you. Another is to install the IP Ban hack by the fellow from Pigstye.

      I don't see a few comments as a serious issue when they are easily dealt with.

      Within your config.php there is already the ability to have a speedlimit for comments, so I don't know why you would make a hack for it.

  3. CityDesk by tomblackwell · · Score: 4, Interesting

    You can also manage a site quite nicely with CityDesk, by Fog Creek. The owner, Joel Spolsky, is an interesting guy who has been the subject of some debate on Slashdot over the years.

    Whatever your opinion of him, he makes good software.

  4. my own? by ferrocene · · Score: 3, Interesting

    Seriously, have any other /.'ers created their own system? Sure, mine sucks as I just used it to learn php, but it's still cool to programmatically create tables from a flat text file somewhere and append a date.

    --
    Most folk'll never lose a toe, and then again some folk'll...
    1. Re:my own? by DrEldarion · · Score: 5, Funny

      Why, when I was your age, we wrote static HTML pages! None of this fancy-schmancy dynamic drek! When we wanted to update our weblog we would open up the HTML file and put the text right in there! And we liked it!

    2. Re:my own? by kfg · · Score: 4, Insightful

      And some of us ( who might have a certain infamy for not having a weblog ) are having a bit of trouble understanding why we wouldn't like doing it that way now.

      Could someone please edify me (and consequently the rest of the viewing audience who might not yet have weblogs) why we might find it desirable to use dynamic methods to update and display a plain text journal?

      And for us old time teletype jockeys who are jacks of all trades but masters of only vi who have never figured out what an IDE might possibly be good for, how do the benefits of weblog packages offset the disadvantages that are the raison d'etre of this Slashdot article, vis a vis, licensing issues (not to mention their attendant prices).

      KFG

    3. Re:my own? by TwinkieStix · · Score: 3, Informative

      Simply put, it's more organized. It's got categories, user permissions, a web editing interface, RSS feeds, and a search engine. The search engine alone is enough when you have hundreds of entries or more and you don't want a GIANT bandwidth sucking page or you don't know the order of the words or phrases you are searching for.

    4. Re:my own? by AJWM · · Score: 3, Informative

      Seriously, have any other /.'ers created their own system?

      Yeah, twenty years ago, in C. Some of the original sites have updated the software a bit, but the "classic" software is still in use. (I have done some work on modernizing the technology, but that got put on the back burner -- I may start it up again.)

      (Some might argue that CoSy wasn't really blogging software. Well, aside from the obvious agreement that the web didn't exist then, so by definition it couldn't have been, there were several Big Names who used Byte Magazine's site (BIX) as just such -- Jerry Pournelle, for example.)

      --
      -- Alastair
  5. Let the predictable comments begin by L.+VeGas · · Score: 5, Funny

    "The best weblogging system is one that doesn't let lame people talk about themselves. Search enginges should ignore them too."

    "Hey don't be so stuck up. I blog for fun. If you don't want to read it, don't. Besides, lots of people like reading about me massaging my mom's feet."

  6. Re:The Best Webloging system is slashdotted here. by eltoyoboyo · · Score: 3, Funny

    That $3.95 a month for 1GB of capped data transfer seemed like such a bargain at the time....

    --
    Have you Meta Moderated t
  7. phpBB Blog and phpBB Fetch All by Anthony+Boyd · · Score: 3, Informative

    If you run a phpBB forum, you can grab my add-on phpBB Blog to turn a forum into a blog. Also, I have a beta available of the next release. I'd love input.

    Also, since this is the Open Source world where cooperation is welcomed, I thought I'd mention that phpBB Fetch All is a blog system that I didn't know about when I made phpBB Blog. phpBB Fetch All is superior to my system, although it is also bigger and more complicated. But it sure looks good.

  8. Chart of features only by Octagon+Most · · Score: 3, Insightful

    This "rather detailed breakdown" is a nice comparison of features, but hardly answers the question of which package is the best. The chart itself says that it "displays attributes of different user-installed blog software packages side-by-side for comparison." There's nothing about usability or other subjective criteria. It is a comprehensive collection of information though. I guess that's good for some people but I bet plenty want a comparison of how easy/flexible they are to use and maintain. Personally I would also like to see a comparison to the hosted services like Blogger.

    As I've said before, if accumulation of features were all that mattered, we'd all love Microsoft Office.

  9. LiveJournal by lostchicken · · Score: 5, Informative

    The code that runs LiveJournal is open source. It's not that much of a pain to deploy, and when it's working, it's the most powerful I've seen. Many stand alone clients for posting, all kinds of things. Set one up, use it as your own weblog, host your friends' weblogs.

    --
    -twb
    1. Re:LiveJournal by moosesocks · · Score: 3, Interesting

      Even better...

      Use the LiveJournal servers, but syndicate the RSS feed into your own blog.

      This way, you can get the best of both worlds, allowing you to intergrate the blog into your own site while using all of LJ's kickass features such as the huge array of WYSIWIG clients availible. It cannot be beaten.

      --
      -- If you try to fail and succeed, which have you done? - Uli's moose
  10. Also, side-by-side CMS comparison matrix by Brent+Nordquist · · Score: 5, Informative

    at The CMS Matrix; you can pick up to 10 you want to compare.

    --
    Brent J. Nordquist N0BJN
  11. Good timing by image · · Score: 3, Informative

    Just this weekend I decided to move my own personal site over to a CMS/Blog system to make updating it even easier. I spent a while doing similar research, and ultimately ended up chosing Bloxsom as the right tool for my needs. It took me only 15 minutes to set everything up, and only a few more hours to write my first plug-in. Blosxom probably isn't the right tool for most applications, but for a personal site it met my needs precisely. In fact, I even migrated another site off of Moveable Type that same weekend.

    Again, I documented the (rather brief) decision making process here.

  12. slashdot's journal by cheese_wallet · · Score: 3, Informative

    I don't use it myself, but it seems that slashot's journal is essentially a free blog.

  13. Movable Type has a fair license... by telbij · · Score: 4, Insightful

    All these Movable Type bloggers whining about the new licensing scheme is getting a little old. Sure I agree that the new licensing move is stupid (considering the quality of the product), but they have every right to go and shoot themselves in the foot if they want.

    As far as the individual blogger is concerned, the lesson is this: use a tool that will allow you to migrate your data. Tools will continue to advance, and you can always redesign, but your archives the only irreplaceable part of the whole equation. In the case of Movable Type, you are already ahead of the game because every other blogging tool in existence imports MT data.

    Why you migrate is a non-issue. You could just as easily be forced to abandon a GPLed package because it is no longer being upgraded and you need the latest features. Even if you write your own CMS, you still run the risk of not having time to add the features you need! Paying a license fee is just one of many considerations you need to make when picking a CMS.

  14. Why WordPress Is Poised To Take Over by WombatControl · · Score: 5, Insightful

    I've had a site running on MT for the past two years, with nearly a year's worth of Blogger entries before that. About 4,000 individual entries and over 6,000 comments dating back over three years. One would think that migrating a site of that size would be a royal pain in the ass.

    WordPress imported the whole thing in a matter of minutes. It's easier to upgrade from MT2.6 to WordPress than it is from MT 2.6 to MT 3.0.

    WordPress is fortunate to have hit its stride just as the MT licensing brewhaha was hitting. WP 1.2 has all the features of MT, runs faster, and is completely open source and GPL licensed. It's a bit of a paradigm shift from MT - you have to get used to a dynamically-run system rather than static templates, but once you grasp the power it brings it offers a lot of new potential for blog development. Plus, there are a lot of talented hackers who have been turned off by MT licensing and will be developing WP plugins instead. WP even has features that MT doesn't - for instance automated link management. That alone makes it worth the upgrade.

    Plus, future versions will support multiple blogs under one interface, some more commenting controls, and other features. I'd expect as WordPress captures marketshare the development of new core features and plugins will increase as well.

    That's a big selling point - even if the WP developers wanted to pull the rug out under free users like Six Apart did, they couldn't. WordPress is GPL software, meaning freedom is but a fork away. Mark Pilgrim's piece does an excellent job of detailing why that freedom is so important. It's another reminder of why open source software is better than proprietary software in terms of flexibility and licensing.

    1. Re:Why WordPress Is Poised To Take Over by Jordy · · Score: 3, Interesting

      I'm sticking with MT myself.

      I don't really want to run MySQL. I don't really want to maintain it. It is just not something I want to deal with. MT lets me use a little local database.

      I really really don't want dynamic pages. I just don't need it. I have had zdnet link to my blog which caused a trillion avantgo clients to hit it. I just don't need queries to MySQL and PHP being run all the time. Actually PHP by itself wouldn't be so bad if it cached everything in a local file the first time the page required it as long as it supported if-modified-since and ranges correctly.

      I actually kind of like the idea of TypeKey. Of course nothing prevents you from implementing TypeKey support in WordPress.

      I simply don't care about silly licensing issues. I mean, for a single non-commercial blog, nothing has changed.

      I have an upgrade path. Sooner or later WordPress will probably integrate a local databse and real caching. When that happens if it is better than MT, I'll migrate. I just don't see the point in migrating right now.

      --
      The world is neither black nor white nor good nor evil, only many shades of CowboyNeal.
  15. Scoop? Slashcode? by MAXOMENOS · · Score: 4, Insightful

    I'm a little surprised that Scoop and Slashcode aren't being considered for blogging software. They're a little complex maybe, but they've been used for blogging pretty successfully. For example: DailyKos is a pretty successful 'blog, and it does very well on Scoop (which runs Kuro5hin). Beastbay used to run Slashcode.

    1. Re:Scoop? Slashcode? by jalefkowit · · Score: 3, Informative

      They're not considered because for personal blogs they are probably more trouble than they're worth. I manage The Oceana Network, a group blog on global efforts to defend the oceans, for my employer, Oceana. (Disclaimer: the opinions expressed here are mine alone and not those of Oceana, yadda yadda.) The Network is based on Scoop.

      For a blog like ours, that handles posts from a large group of authors and that needs to be able to support very long discussions, Scoop is fantastic. Give it an inexpensive Linux/BSD box all to itself and it is a very, very nice and flexible online community platform.

      However, if you fit the profile of the typical single-author blog author, installing Scoop probably isn't for you. It's a tricky process, requiring "now edit your httpd.conf"-type steps that are just not realistic to expect from someone on a virtual hosting setup. (Not to say that it can't be done -- just that it's not realistic to expect many people to do it.)

      And Scoop's primary benefit -- its very nice moderated comment system -- is wasted on a personal blog, where no post will ever get more than a few comments. (I know that ours doesn't have that many yet either, but we've only been up and running for a couple of weeks... give us time :-) )

      For those users, MT, WordPress, etc. are much better solutions -- easier installs, and just enough features to be useful without overcomplicating things.

      If your blogging ambitions are grander than a simple personal site, though, Scoop is great -- definitely check it out if you haven't already.

  16. Re:The best blogging "system?" Please. by WombatControl · · Score: 4, Insightful

    Are you nuts?

    You try manually managing 4,000 entries without going completely bonkers - including permalinks, comments, and extended entries. The whole point of blog software is that you have a system that manages permalinks, organizes information, allows for open exchange, etc. Those are all things that require some kind of infrastructure. Blogging software is really just a specialized form of CMS, and anyone who argues that sites consisting of thousands of pages doesn't need some form of content management and control is quite frankly a complete and utter lunatic.

    Or to take your logic, who needs a computer? What is a computer? A device that just does mathematical calculations. If you can't figure out insanely complex matrix operations and vector math, then your're probably not very smart anyway. All those super-elite people can use a slide rule to handle all the intense computation for them. If you pay for computers, you're a sucker...

  17. Pivot by verloren · · Score: 3, Informative

    Switched from Blogger to Pivot last week, and so far it's working well. The key attractions for me were greater control and the minimal server requirements (PHP is about it). It works great, there are some really nice touches in there, and it's being actively developed.

    Cheers, Paul

  18. Perfect Timing by Salamander · · Score: 5, Informative

    Wouldn't you know it? I just spent much of the weekend converting my site from my own homegrown weblog codebase to pMachine. Here's the new version (with an entry about the change), and the old version for comparison. According to the table, b2evolution and WordPress would be equally good fits, perhaps even slightly better because they support assigning an entry to multiple categories like my old code but unlike pMachine Free, but when I tried them all out at opensourceCMS that really wasn't the case. I strongly recommend that you check out candidates there, because a lot of the small things make a difference. Here are some examples:

    • What kinds of markup is allowed in posts? In comments? Is it plain HTML, or a stripped-down square-bracketed subset like bbCode, or both, or neither? Which are you comfortable with? How about your users who leave comments? If it's real HTML, how are various cross-site scripting and other exploits prevented?
    • Are commenters allowed to register so they can have persistent profiles? Are they forced to register? Either/or?
    • Does the post entry format allow things like saving drafts, posting to the future, setting expiration dates?
    • Does the system have things like time offsets (between where you are and where your site is hosted)? Are the paths that it uses configurable, so you can make it work with different directory structures? How "tunable" are things in general? This can be a huge headache if you get halfway into your transition and you find something that just won't work properly in your environment without hacking the code.
    • Do you really like the way the templating system works? You really won't know until you try some customization, so fiddle a bit with the layout. Move stuff around, add links to other parts of your site, etc.
    • If you're converting from another system, are there automatic conversion tools? How well do they really work? Again, you have to try to see, and not just on opensourcecms either. If there are no converters, how hard would it be to write one? Does the database schema (and/or file layout) make sense to you? Is it similar conceptually to what you have now? Does it require complex relationships between tables/fields that would be hard to maintain as you suck in your old content? Is there any information in your old content that there's no place for?

    These sorts of things, none of which are covered in a mere checklist, really matter when you actually take the plunge. Trying stuff out on opensourcecms is a great first step, but then you should actually download the real thing and really try to run a test version of your own site on it for at least an hour or so, to see if you can truly tweak it to your liking. Only then will you be able to make a decision that will really satisfy you.

    --
    Slashdot - News for Herds. Stuff that Splatters.
  19. stay away from PHPnuke by SethJohnson · · Score: 3, Informative


    Not that it's expressly a weblog system... it's frequently used as such, though.

    I just wanted to drop in a slam on phpNuke because of all the security problems I've had with it. The modules created by third-parties frequently haven't had rigorous security testing and are prone to exploits. If you want to increase your chances of your server being hacked, publish using phpNuke and a few modules. The brazillian script kiddies rabidly chase servers running phpNuke everytime a new exploit is found.
  20. snipsnap by bblfish · · Score: 3, Informative

    They are missing SnipSnap, an fantastically easy to install java GPLd blog/wiki server. Try it out at snipsnap.org.

  21. Re:GPL misconception by exhilaration · · Score: 3, Informative

    What the guy above is trying to say is that you can't RETROACTIVELY change the license to GPL'ed software. If version 1.0 was GPL, you can make version 2.0 non-GPL. But anybody can take version 1.0 and continue working on it, forking it into a new product, and there's nothing you can do about it. That's because the license to 1.0 can never be changed - that "permanence" is in the GPL.