Blog through mail

Among other thing, the user’s experience requires a direct satisfaction of the desir. So, if it’s about blogging, one should do it directly. Hence, for that purpose, there are some plugins and applets based upon the xml_rpc. Nonetheless, one could achieve that with the e-mail client. What would be the benefit for the user?

Mainly to use an existing service instead of installing something more and opening an other service. That would be very satisfying if on the server-side a wide range of format can be handle, of course. By this way, one could send to the blog a document as attachment. Send a document from the desktop or a wordprocessor is nowadays a current service. Obviously one could blog with the e-mail client itself, though in this case, text-formatting and adding pictures or else, really depend upon the composer; otherwise one has to notify all that with some tags (html or else). Sure, it’s less friendly in this case and even the best featured composer won’t be able to notify the categories; at least it’s not a problem for the title, simply written in the subject line, and the date. Same problem with a document attached, one needs some special strings to specify its categories. Last but not least, managing the blog through mail is possible but will require more instructions for the user to learn. However, there’re not a lot of task, hence, not a lot to learn.

At this stage one can conclude that, for a blog service, blogging through mail is only an option and not a substitute of the web-application. There’re too much conditions, changing the blog’s chrome make more sense from the application itself but, in case of some incompatibility with a browser, the mail service could solve that. So, it’s up to the user to blog only through mail, in any other way that’s a good auxillary to the web-application.

While that prevents to install and open an other service, that requires to create an other account in the e-mail client, and yes, a lot of people don’t know how to do. So, an other reason keep that optional. Registration will rely upon the user’s e-mail adresse and a password, the resulting e-mail account will be the user’s e-mail adresse @ the service.com. (e.g user@isp.com -> user.isp@service.com) It won’t be a good idea to base the URL of the user’s blog upon that, since that will reveal the isp and somewhat the e-mail adresse (e.g user-isp.service.com). So, let’s the user pick an username, despite the fact that one loses the advantage of an unique identifier.

But what would be the advantage for the blog service? Frankly, none: one has to set up a mail server, plus the gears to pass all the various messages in the web-application. Compare to that, the xml-rpc is less costly, though it could be a nasty vector of attack. Conclusion, unless an other plug-in or a suitable composer, that not seems to be a good option to maintain.

Publicités

Laisser un commentaire

Entrez vos coordonnées ci-dessous ou cliquez sur une icône pour vous connecter:

Logo WordPress.com

Vous commentez à l'aide de votre compte WordPress.com. Déconnexion / Changer )

Image Twitter

Vous commentez à l'aide de votre compte Twitter. Déconnexion / Changer )

Photo Facebook

Vous commentez à l'aide de votre compte Facebook. Déconnexion / Changer )

Photo Google+

Vous commentez à l'aide de votre compte Google+. Déconnexion / Changer )

Connexion à %s


%d blogueurs aiment cette page :