Technosailor: Internet Community: Blogs vs. Forums
Rachel C
· 3 years ago
You're most welcome to debate my points over at my blog if you like.
The database structure can indeed be the same, and more integrated blog/forum tools are moving in this direction as more people require this functionality.
I'm happy to debate this on my blog if you like, but I don't believe it is necessary to debate someone by stating and wrongly assuming things about them such as "ignorance of databases" and going on about your own experience.
Aaron
· 3 years ago
hi Rachel--
No, I prefer to debate this topic with my own readers (and you if you choose) here. This is why I posted it here instead of commenting on your entry.
Thanks, Aaron
Joe
· 3 years ago
Hey Aaron, I agree that there are Big differences between the two.
A Blog (Web Log) is omni-directional, even with comments it is still started from a central point (Blogger).
A Forum (open debate) is multi-directional, any one can open the conversation on any topic they choose.
Just my 2 cents Joe
Rachel C
· 3 years ago
I agree too, Joe. My point wasn't that blogs and forums are the same, far from it! The database structure is the same, so blog+forum applications shouldn't be the saga that they are currently for many systems.
Aaron
· 3 years ago
Certainly that is not what you convey as early on as your entry title...
"different ways of looking at the same thing"
Additionally, you say the database structure is the same. How are they the same?
In WordPress you have two tables that have to do with what a forum thread would be.... "wp_posts" and "wp_comments".
JOINs are done on wp_comments.comment_post_ID=wp_posts.ID
In forums, these are all in one table that are interrelated to each other.
In blogs, every post has categorys. Categories can have subcategories. In a forum, you have forums and subforums, but the data passed around is completely different.
I still don't see how you can stand by "blogs and forums are identical at the database level".
Rachel C
· 3 years ago
Different ways of looking at and interacting with content stored in the same format at the database level. A relational database with a table for posts, a table for comments, a table for categories.
Sim'
· 3 years ago
On one of my websites (a subscription based investment education site), we have a discussion forum as well as regular published articles from our resident experts.
While there is no major technical reason why we couldn't just use the discussion forum for the articles, and indeed there are some nice extensions to vBulletin for exactly this purpose, we decided to keep the two very separate for exactly the resons Aaron mentions.
We wanted clear separation of the "premium content" being created by our experts (blogs), from the "generic content" being created by our members (forums). Note that I am not suggesting our member contributions are any less valuable - but the fact is that most of our members do come to hear from our experts.
By clearly separating the two, this enables us to more easily add extra value to the premium content - turning the normally linear format of a blog into an educational resource tool. The high volume nature of forums doesn't lend itself well to this - there is simply too much "noise" to make learning effective from this type of medium.
To the discussion at hand, I do think Aaron is taking Rachel too literally and technically - and from Rachel's comments I think she is looking at the problem from a much higher level. I can see Rachel's point of view, and acknowledge that there are fundamental similarities between the two (indeed the mechanisms are much the same), and indeed you can in some cases use the two mechanisms interchangeably.
However, I do stand firmly in Aaron's court for the reasons I stated above ... and those reasons are in many ways more psychological than technical (although there are some very important technical reasons for separating the two as well).
Darren
· 3 years ago
I'd be careful who you call ignorant Aaron - I think Rachel's proven to be anything but ignorant in her many years of web design. Hope this can stay conversational and that we can all come out of it learning something rather than making judgements over what each other does or doesn't know.
Mel
· 3 years ago
Interesting debate, made me think a little. Darren, he didn't call her ignorant, he said "ignorant of databases". Correct me if i'm wrong.
Aaron Brazell
· 3 years ago
Thanks, Darren. However "ignorant" may be percieved, it is meant in the strictest form of the word. Not knowing of what one talks. Does not mean stupid as pop culture uses it. And I did not say anything about ignorant about web design. I gave her props on that. I explicitly referred to database structure.
Darren
· 3 years ago
point taken although I still think 'ignorant' is a pretty harsh word to use to describe someone you don't really know.
Dictionary definition of ignorant - 'Lacking education or knowledge.'
This is not my experience of Rachel.
Now if you wanted to call someone ignorant of databases I think I'd be a much better candidate - but in comparison I'd say Rachel is pretty clever on the topic....
But then again - what would I know about it as I've already admitted to ignorance on the topic....
:-)
Aaron
· 3 years ago
Edited to soften the tone. I certainly don't want to have my chosen terminology in one phrase take away from, or become the focus of, this entry. If softening my tone maintains the focus of my point then I'm willing to concede the terminology. :)
stacie
· 3 years ago
Similarity one - both build community. As the webmaster of several web sites, I debate on whether or not to use a forum structure or a blog to build a community. Difference - blogs help to drive a topic while forums are a bit more open. Similarity - I could completely see the structure of posts and comments. Difference - I think that the user has more control in a forum - subscribing to favorites, user control panels, etc.
I think in the rawest form, blogs and forums have the same goals and user interface structure, but I feel that forums have more advanced features at this time.
Peter T Davis
· 3 years ago
I wish Rachel could have used something other than Drupal for proving her point. Drupal is the most rudimentary of forums I've seen in a long time. Comparing it to what I think of as a forum is like comparing a string and two cans to Skype. Drupal is not a forum. It's not really a blog either, but it's more a blog than a forum. I really like the software, but it's not a forum (did I say that already?).
All Comments
The database structure can indeed be the same, and more integrated blog/forum tools are moving in this direction as more people require this functionality.
I'm happy to debate this on my blog if you like, but I don't believe it is necessary to debate someone by stating and wrongly assuming things about them such as "ignorance of databases" and going on about your own experience.
No, I prefer to debate this topic with my own readers (and you if you choose) here. This is why I posted it here instead of commenting on your entry.
Thanks,
Aaron
I agree that there are Big differences between the two.
A Blog (Web Log) is omni-directional, even with comments it is still started from a central point (Blogger).
A Forum (open debate) is multi-directional, any one can open the conversation on any topic they choose.
Just my 2 cents
Joe
"different ways of looking at the same thing"
Additionally, you say the database structure is the same. How are they the same?
In WordPress you have two tables that have to do with what a forum thread would be.... "wp_posts" and "wp_comments".
JOINs are done on wp_comments.comment_post_ID=wp_posts.ID
In forums, these are all in one table that are interrelated to each other.
In blogs, every post has categorys. Categories can have subcategories. In a forum, you have forums and subforums, but the data passed around is completely different.
I still don't see how you can stand by "blogs and forums are identical at the database level".
While there is no major technical reason why we couldn't just use the discussion forum for the articles, and indeed there are some nice extensions to vBulletin for exactly this purpose, we decided to keep the two very separate for exactly the resons Aaron mentions.
We wanted clear separation of the "premium content" being created by our experts (blogs), from the "generic content" being created by our members (forums). Note that I am not suggesting our member contributions are any less valuable - but the fact is that most of our members do come to hear from our experts.
By clearly separating the two, this enables us to more easily add extra value to the premium content - turning the normally linear format of a blog into an educational resource tool. The high volume nature of forums doesn't lend itself well to this - there is simply too much "noise" to make learning effective from this type of medium.
To the discussion at hand, I do think Aaron is taking Rachel too literally and technically - and from Rachel's comments I think she is looking at the problem from a much higher level. I can see Rachel's point of view, and acknowledge that there are fundamental similarities between the two (indeed the mechanisms are much the same), and indeed you can in some cases use the two mechanisms interchangeably.
However, I do stand firmly in Aaron's court for the reasons I stated above ... and those reasons are in many ways more psychological than technical (although there are some very important technical reasons for separating the two as well).
Dictionary definition of ignorant - 'Lacking education or knowledge.'
This is not my experience of Rachel.
Now if you wanted to call someone ignorant of databases I think I'd be a much better candidate - but in comparison I'd say Rachel is pretty clever on the topic....
But then again - what would I know about it as I've already admitted to ignorance on the topic....
:-)
I think in the rawest form, blogs and forums have the same goals and user interface structure, but I feel that forums have more advanced features at this time.