Blog by email
Some blogging tools offer the ability to email your posts (http://wiki.wordpress.org/?pagename=How%20To%20Blog%20By%20Email) directly to your blog, all without direct interaction through the blogging tool interface. WordPress offers this cool feature. Using email, you can now send in your post content to a pre-determined email address & voila! Your post is published!
Monday, November 19, 2007
Link Manager
The Link Manager is the place where you can manage all your links to other websites, blogs, etc. You can create different categories here in which you can place links pointing to other websites or blogs. These websites or blogs can be those which you regularly visit or which are cool, or with whom you are exchanging links or those who've paid you to place their links on your BLOG. ;)
The Link Manager is the place where you can manage all your links to other websites, blogs, etc. You can create different categories here in which you can place links pointing to other websites or blogs. These websites or blogs can be those which you regularly visit or which are cool, or with whom you are exchanging links or those who've paid you to place their links on your BLOG. ;)
Pretty Permalinks
Permalinks are the permanent URLs to your individual weblog posts, as well as categories and other lists of weblog postings. A permalink is what another weblogger will use to refer to your article (or section), or how you might send a link to your story in an e-mail message. Because others may link to your individual postings, the URL to that article shouldn't change. Permalinks are intended to be permanent (valid for a long time).
"Pretty" Permalinks is the idea that URLs are frequently visible to the people who click them, and should therefore be crafted in such a way that they make sense, and not be filled with incomprehensible parameters. The best Permalinks are "hackable," meaning a user might modify the link text in their browser to navigate to another section or listing of the weblog. For example, this is how the default Permalink to a story might look in a default WordPress installation:
/index.php?p=423
How is a user to know what "p" represents? Where did the number 423 come from?
In contrast, here is a well-structured, "Pretty" Permalink which could link to the same article, once the installation is configured to modify permalinks:
/archives/2003/05/23/my-cheese-sandwich/
One can easily guess that the Permalink includes the date of the posting, and the title, just by looking at the URL. One might also guess that hacking the URL to be /archives/2003/05/ would get a list of all the postings from May of 2003. Pretty (cool). For more information on possible Permalink patterns in WordPress, see Using Permalinks.
Permalinks are the permanent URLs to your individual weblog posts, as well as categories and other lists of weblog postings. A permalink is what another weblogger will use to refer to your article (or section), or how you might send a link to your story in an e-mail message. Because others may link to your individual postings, the URL to that article shouldn't change. Permalinks are intended to be permanent (valid for a long time).
"Pretty" Permalinks is the idea that URLs are frequently visible to the people who click them, and should therefore be crafted in such a way that they make sense, and not be filled with incomprehensible parameters. The best Permalinks are "hackable," meaning a user might modify the link text in their browser to navigate to another section or listing of the weblog. For example, this is how the default Permalink to a story might look in a default WordPress installation:
/index.php?p=423
How is a user to know what "p" represents? Where did the number 423 come from?
In contrast, here is a well-structured, "Pretty" Permalink which could link to the same article, once the installation is configured to modify permalinks:
/archives/2003/05/23/my-cheese-sandwich/
One can easily guess that the Permalink includes the date of the posting, and the title, just by looking at the URL. One might also guess that hacking the URL to be /archives/2003/05/ would get a list of all the postings from May of 2003. Pretty (cool). For more information on possible Permalink patterns in WordPress, see Using Permalinks.
Comment Spam
Comment Spam refers to useless comments (or trackbacks, or pingbacks) to posts on a blog. These are often irrelevant to the context value of the post. They can contain one or more links to other websites or domains. Spammers use Comment Spam as a medium to get higher page rank for their domains in Google, so that they can sell those domains at a higher price sometime in future or to obtain a high ranking in search results for an existing website.
Spammers are relentless; because there can be substantial money involved, they work hard at their "job." They even build automated tools (robots) to rapidly submit their spam to the same or multiple weblogs. Many webloggers, especially beginners, sometimes feel overwhelmed by Comment Spam.
There are solutions, though, to avoiding Comment Spam. WordPress includes many tools for combating Comment Spam. With a little up front effort, Comment Spam can be manageable, and certainly no reason to give up weblogging.
Comment Spam refers to useless comments (or trackbacks, or pingbacks) to posts on a blog. These are often irrelevant to the context value of the post. They can contain one or more links to other websites or domains. Spammers use Comment Spam as a medium to get higher page rank for their domains in Google, so that they can sell those domains at a higher price sometime in future or to obtain a high ranking in search results for an existing website.
Spammers are relentless; because there can be substantial money involved, they work hard at their "job." They even build automated tools (robots) to rapidly submit their spam to the same or multiple weblogs. Many webloggers, especially beginners, sometimes feel overwhelmed by Comment Spam.
There are solutions, though, to avoiding Comment Spam. WordPress includes many tools for combating Comment Spam. With a little up front effort, Comment Spam can be manageable, and certainly no reason to give up weblogging.
Comment Moderation
Comment Moderation is a feature which allows the website owner and author to monitor and control the comments on the different article posts, and can help in tackling comment spam. It lets you moderate comments, & you can delete unwanted comments, approve cool comments and make other decisions about the comments.
Comment Moderation is a feature which allows the website owner and author to monitor and control the comments on the different article posts, and can help in tackling comment spam. It lets you moderate comments, & you can delete unwanted comments, approve cool comments and make other decisions about the comments.
Verifying Pingbacks and Trackbacks
Comments on blogs are often criticized as lacking authority, since anyone can post anything using any name they like: there's no verification process to ensure that the person is who they claim to be. Trackbacks and Pingbacks both aim to provide some verification to blog commenting.
Comments on blogs are often criticized as lacking authority, since anyone can post anything using any name they like: there's no verification process to ensure that the person is who they claim to be. Trackbacks and Pingbacks both aim to provide some verification to blog commenting.
Sunday, November 18, 2007
Pingbacks
Pingbacks were designed to solve some of the problems that people saw with trackbacks. The official pingback documentation (http://www.hixie.ch/specs/pingback/pingback) makes pingbacks sound an awful lot like trackbacks:
For example, Yvonne writes an interesting article on her Web log. Kathleen reads Yvonne's article and comments about it, linking back to Yvonne's original post. Using pingback, Kathleen's software can automatically notify Yvonne that her post has been linked to, and Yvonne's software can then include this information on her site.
There are three significant differences between pingbacks and trackbacks, though.
Pingbacks and trackbacks use drastically different communication technologies (XML-RPC and HTTP POST, respectively).
Pingbacks support auto-discovery where the software automatically finds out the links in a post, and automatically tries to pingback those URLs, while trackbacks must be done manually by entering the trackback URL that the trackback should be sent to.
Pingbacks do not send any content.
The best way to think about pingbacks is as remote comments:
Person A posts something on his blog.
Person B posts on her own blog, linking to Person A's post. This automatically sends a pingback to Person A when both have pingback enabled blogs.
Person A's blog receives the pingback, then automatically goes to Person B's post to confirm that the pingback did, in fact, originate there.
The pingback is generally displayed on Person A's blog as simply a link to Person B's post. In this way, all editorial control over posts rests exclusively with the individual authors (unlike the trackback excerpt, which can be edited by the trackback recipient). The automatic verification process introduces a level of authenticity, making it harder to fake a pingback.
Some feel that trackbacks are superior because readers of Person A's blog can at least see some of what Person B has to say, and then decide if they want to read more (and therefore click over to Person B's blog). Others feel that pingbacks are superior because they create a verifiable connection between posts.
Pingbacks were designed to solve some of the problems that people saw with trackbacks. The official pingback documentation (http://www.hixie.ch/specs/pingback/pingback) makes pingbacks sound an awful lot like trackbacks:
For example, Yvonne writes an interesting article on her Web log. Kathleen reads Yvonne's article and comments about it, linking back to Yvonne's original post. Using pingback, Kathleen's software can automatically notify Yvonne that her post has been linked to, and Yvonne's software can then include this information on her site.
There are three significant differences between pingbacks and trackbacks, though.
Pingbacks and trackbacks use drastically different communication technologies (XML-RPC and HTTP POST, respectively).
Pingbacks support auto-discovery where the software automatically finds out the links in a post, and automatically tries to pingback those URLs, while trackbacks must be done manually by entering the trackback URL that the trackback should be sent to.
Pingbacks do not send any content.
The best way to think about pingbacks is as remote comments:
Person A posts something on his blog.
Person B posts on her own blog, linking to Person A's post. This automatically sends a pingback to Person A when both have pingback enabled blogs.
Person A's blog receives the pingback, then automatically goes to Person B's post to confirm that the pingback did, in fact, originate there.
The pingback is generally displayed on Person A's blog as simply a link to Person B's post. In this way, all editorial control over posts rests exclusively with the individual authors (unlike the trackback excerpt, which can be edited by the trackback recipient). The automatic verification process introduces a level of authenticity, making it harder to fake a pingback.
Some feel that trackbacks are superior because readers of Person A's blog can at least see some of what Person B has to say, and then decide if they want to read more (and therefore click over to Person B's blog). Others feel that pingbacks are superior because they create a verifiable connection between posts.
Subscribe to:
Posts (Atom)
