Last updated by Mmeal Comments (6)

A weblog, or blog, is arguably one of the fundamental DNA pieces of most types of social networking site. The simplest form of personal publishing, it allows for text-based notes to be published in reverse-chronological order. Commenting is also an important part of blogging, turning an individual act of publishing into a conversation.

Elgg's blog expands this model by providing per-entry access controls and cross-blog tagging. You can control exactly who can see each individual entry, as well as find other entries that people have written on similar topics using your same tags. You can also see entries written by your friends (that you have access to) and see them in your activity river (the entries flow in your activity page).

  • What is cross-blog tagging? What's useful for? Where do I find other entries on similar topics and see entries written by my friends?

  • It's usefull to exchange with foreign blogs...  

  • Exchange what? Posts? When do you need to exchange? I think I've never used it.

    What differences with the wire?

  • Not sure what's being asked here - the difference with the wire is the amount of content available, the comment system, tinymce integration...

    Tagging allows for a form of topical searching.  Tag clouds show the top tags in differing sizes relative to their frequency, clicking on a tag will show other content that shares that tag.

  • How can i subscribe to a blog?. I Created a blog post now i want the other user to subscribe to the blog so that they receive the updates of the blog

    Is their any plugin for that. I am using Elgg 1.8 version

  • that's an interesting angle ;-) like groups' notifications where users manage notifications and so.. get 'notified' via site messages, email etc. i reckon that to do the same - blogs would need to create it's own access collection for each blog so that users can 'subscibe' (set their notifications) -- a bit of coding here and there in the blog's start.php code should fix this up -> create_access_collection('<access-name>", <blog_guid>) and your're done ;-)