There’s of course dozens of ways of connecting your blog to Facebook and Twitter, but here’s a relatively easy method that works for me. What you need is a self-hosted WordPress blog – this recipe won’t work on WordPress.com hosted free blogs.
Gravatars and other externally loading dynamic content in blogs considered harmful
I’m a happy user of Gravatars (globally recognized avatars) that allow my face to show up next to comments I write to practically any blog site. However, I’ve recently realized that Gravatars (at least their current implementation) have a major flaw that will really inconvenience its users in the long run.
The basic problem is that blog posts and their comments are timestamped entities, which stay static forever (theoretically) after they have been created. A blog becomes an archive that with the help of permalinks allows others to refer to specific posts or comments, thus enabling the whole blogsphere, of sending messages between blogs. But if this archive contains information that is loaded from external sources, and thus is liable to change, the blog post no longer stays inert.
Now, a common practice is to include images or embed videos from other sources to a blog post. Anyone understands that if the video clip or other external media disappears from the referenced URI, then the blog post will lose part of its content, making its remaining parts and its commentary partially meaningless. However, it is easy to see that the cause is missing data.
Loading more dynamic content becomes problematic. Any external source that is likely to produce different content will make the blog post very difficult to understand later on. For example, embedding something like “today’s newscast” from a news agency, and commenting that, will be quite confusing if the shown content will actually each day show that day’s newscast, and not the one from the day the blog post was made.
All of this is quite simple, and probably most bloggers intuitively know that they should link to and embed stuff from as permanent sources as possible.
So what’s my problem with Gravatars? Some of you may have figured it out. While a gravatar image may not change very often, one should consider that Gravatars have been around only for a few years. Let’s take a longer view. My Gravatar image shows me at the age of about 30 years. When I’m fifty, I’ve probably updated by Gravatar image to show my current visage. However, when I do this change, all the hundreds of blogs I’ve commented on in the last 20 years will suddenly show a 50 year old man as a commenter.
This problem is even more acute to teens. When you’re 12 years old and commenting on your friends’ blogs, it’s nice to have your own face in there, probably with a funny grin on it. But after 10-15 years when you’re a respected professional and your Gravatar icon shows you wearing a business suit, your friends’ blogs will seem pretty weird, with you in your suit hanging out with teens.
Gravatar could of course fix this, by allowing users to have historical images that are sent to older blog postings. This would require a change in the API so that the call to get a Gravatar image based on an e-mail address would also include the date of the comment. Changing the API and getting all implementations to upgrade will be a challenge, but not doing it will simply break the system as people age, change contexts, and change their Gravatar images accordingly.
Tags: blog, gravatar, dynamiccontent, archive, future
Spämmisuojalla apua kirjojen digitointiiin
Päivitin WordPressin versiosta 2.1 versioon 2.5 (2.1:stä on löydetty pahoja turvallisuusongelmia, Technorati jopa lähetti erikseen mailin jossa kehotti päivittämään). Samalla vaihdoin captcha-pluginin recaptcha-pluginiin. Idea tässä pluginissa on, että sen sijaan että vain kysellään vaikeasti näkyviä turhia sanoja, kysytään kommentin kirjoittajalta sanoja, joita kirjojen digitointiprojekteissa ei ole koneellisesti pystytty tunnistamaan. recaptcha kysyy aina kaksi sanaa, joista toisen recaptcha-palvelu jo tuntee ja toista ei. Jos se tunnettu menee oikein, voidaan olettaa, että vastaaja on ihminen, ja samalla se toinen sana saatiin tunnistettua – ehkä. Käytännössä recaptcha syöttää saman sanan useamman kerran eri puolille, jotta se saadaan varmennettua. Mutta näin helppoa on maailman parantaminen.
The trend for good companies and valuable employees
On the 12th of September the pedagogical faculty of the University of Helsinki hosted a panel talk Siltamat (in finnish) where, among others, Esko Kilpi was talking about how the frontline companies in far east are conducting business. It was refreshing to see someone actually use hype words like “web 2.0″, “blog” and “wiki” in a meaningful way. Here’s a summary.
Instead of the static business models of the industrial era, the information age and globalization make everything dynamic and changing. This means that the relationship companies have with their customers, and with their employees, must be a learning relationship. The relationships must be evaluated and adapted constantly.
Because the problems tackled in the information age have already become too complex for individuals to handle, the unit that functions, learns, and is evaluated, is no longer an individual employee, but a group of employees, often called a team, group, or department. The traditional way of evaluating role based competences of people is no longer meaningful, since the relationship is dynamic and learning, and people will move from one role to another constantly. Replacing them are as adaptation and learning abilities, and evaluation more often than not happens through peer review.
Each unit (team, department) must communicate and collaborate. If each person just does his own job, the company is soon in trouble. Employess no longer need to learn everything that relates to their role, but rather they need to know where they can get help. The three things that an employee in a new role should find out are:
- Who has done this before? Who can I ask?
- What has been done before? What has it been based on?
- Where is the best expertise?
In order for these answers to be available, employees and teams need to reflect on their work. And the organization must make reflection possible by giving people the time to do that. And reflection is meaningless unless things can be changed. This means that the conclusions of reflection should be fed back to the system, so that the ways of working can be improved based on the findings. The employees themselves thus must have the power to change the rules they work under.
With current technologies, reflection is most naturally done using personal blogs within the company. And instead of just writing, a lot can be podcasted – images of designs, or audio/video recordings of designers discussing a complex issue. The more popular a blog is, the more valuable information that individual is sharing with his colleagues, and the more valuable that individual is for the company.
The company itself should be presented in a wiki. Every employee can edit the wiki pages, and thus the ever-increasing knowledge (or intellectual capital) of the company is not stuck within the heads of employees, but is shared with everyone as best as possible. Any and all documents, people, and resources should be tagged. Not with keywords from a closed vocabulary, but actually tagged with freeform tags (folksonomies). Information cannot be categorised into a tree structure of folders anymore, since most of the complex information should be present in several places. The network hierarchy needed is most easily represented by tags.
Because of the learning nature of relationships and the constant changes in company realities, deep hierarchies of managers are no longer appropriate. Instead of forming permanent departments, employees should form short-lived unofficial teams, groups, or pairs across intraorganizational boundaries as needed (emergent resource allocation). This also means that there is no such thing as repeatable processes, since things change all the time. This makes many quality standards, such as the ISO 9000, meaningless.
Summary: people need to adapt, learn, and share; evaluation is done based on the contributions of the indivudal to the organization, often using peer-review; sharing is done using blogs and wikis; people are allowed to reflect on their work and rules of working are changed accordingly. All this gives the company more flexibility and provides an advantage in the current market, where the focus is moving from mass production to customized production, and companies need to adapt and accomodate changes in the market rapidly.
Twitter
LinkedIn
Facebook
Youtube
Flickr
SlideShare
Google