harika bir kıvama gelmeye başlamıştır onun porno kalçaları ve teni tam hayalini kurduğu kadın porno resimleri profiline uyduğunu anlayan genç adam kuzenlerine porno gif geldiğinde onun odasına gelerek kirli sepetinden porn birkaç kullanılmış don alarak sikini sürterek fantezi sex resim yaşamak ister odaya gelir ve kullanılmış külotuna porno sikini değdirdiği sırada içeri kuzeni gelir onun sex hikayeleri bir şeyler karıştırdığını anlayan kız hemen sepetin porno izle oradaki donunun dışarıda olduğunu görür

When Blogs Go Big and Bad

by

I recently noticed a seemingly increasing amount of negative comments on growing blogs. Comments vary from “You used to be cool but now you suck” to comments bearing a warning signal “Don’t continue like this or I will unsubscribe” to more constructive criticism.

There are different strategies you can follow when you are becoming increasingly popular. Which path you take depends on your goals and whether your blog is a hobby or a (potential) business. Do you keep on doing what you are doing or are you going to deliver more content. Most importantly, are you continuing on your own or are you going to expand?

Becoming more popular also means a changing audience that may be more demanding. Can you maintain the same quality as before? And how do you manage a growing team of (guest) bloggers that you will very likely do not know personally? These are just some of the problems a growing blog may face and that you should take into account before taking it to the next level.

If your blog is your hobby I think your main goal is that both you and your readers should be satisfied. Listen to your commenters and their (constructive) criticism and be open and transparent in the process you are going through. Transparency is what mainly seems to be lacking on the (wannabe) professional blogs that are picking up their posting pace or expanding their editorial team.

One of my favorite design blogs/magazines PSDtuts recently experienced first hand what it is like to go big and ran into a major problem. One of the contributing editors duplicated a Photoshop tutorial. PSDtuts handled the situation in possibly the best way they could with total transparency:

Today we’ve had to unfortunately remove a tutorial due to copyright issues. As all creatives should, we take copyright very seriously here at PSDTUTS. The tutorial in question has been removed, the author has not been paid and I’ll personally be investigating further to get in touch with the original author to apologize and ensure everything is sorted.

The reaction of most of their readers? Respect.

What to do when your readers are complaining you are growing big and bad? Be honest and transparent. Admit you are going through a transfer phase and trying to adjust to the new situation. If you can’t get your new big blogging act together don’t be afraid to radically change your approach. Do you want to be big and bad or rather small and good?

Choosing between Twitter, live blogging or fast publishing

by

I love it when bloggers write about conferences I cannot attend. Blogs and Twitter are my main resources to stay in touch with conferences such as the Web 2.0 Expo in San Fransisco last week. Bloggers take different approaches to cover conferences which all have their advantages and disadvantages. The main three approaches are using Twitter, live blogging tools or fast publishing.

Twitter

Twitter is a useful tool to stay in touch with both conference organizers and attendees. Stay up-to-date with schedule changes, keynote transcriptions and videos and people in the room. Twitter is used more and more often by speakers to answer questions from the audience or from people who are not attending the conference. The downside of such interaction is that there are always people out there to get their 140 characters of fame and add a lot of noise to the signal.

One of my favorite uses of Twitter during conferences is a backchannel people can send their posts to. During the Next Web conference in Amsterdam a few weeks ago a backchannel was created where all posts that included #nextweb were posted. By following the backchannel you can get information from everyone actively participating in providing content from the conference.

Live blogging

CoverIt Live is one of the most popular tools used for live blogging. It provides an easy and instant way to provide your blog readers with the latest news without having to refresh the page:

Your commentary publishes in real time like an instant message. Our ‘one-click’ publishing lets you drop polls, videos, pictures, ads and audio clips as soon as they come to mind. Comments and questions from your readers instantly appear but you control what gets published.

It is an excellent solution for blog visitors if you are “live reading” the blog. However, for archival (and SEO) purposes I am not too fond of using such tools. For example, I wanted to check out Mashable’s post on Matt Mullenweg Announces Related Posts and Themes for Photo Bloggers. If you use an external service such as CoverIt Live the content is not actually a part of your blog but it is embedded into your blog from their server. The fact that your content is embedded has consequences for indexing and finding the content. Be aware when using such tools that your live coverage will not be indexed nor be part of your blog’s archive.

Fast publishing

This is my personal preferred method of blogging conferences and keeping up with conferences. At the Next Web Conference we covered the whole conference with only two people and took turns in covering the keynotes. After a thirty minute keynote we would have another thirty minutes to turn our notes into a blog post and publish it online. While thirty minutes to edit your notes is not much it provides you with just enough time to turn them into a coherent blog post.

Why do I prefer fast publishing over Twitter or live blogging? Your blog is not as good as its latest post, it is the archive that counts. Which is your preferred method?

Trackback Declared Dead… Again!

by

Trackback is one of the major blog features that has been declared dead over and over again. This recently led Kyle Eslick from Hack WordPress to ask his readers “Does WordPress Need Trackbacks Any More?” Eslick’s own answer is straightforward: “In my opinion, blogging has outgrown the trackback and the pingback has made it irrelevant.”

The question is not so much if spam or the Pingback killed the Trackback but rather if the medium has rendered it obsolete. The medium and practice of blogging are entangled in the blog software and with the introduction of Pingback the inter-blog notification system became automatic instead of manual. When I described the difference between the manual Trackback and the automatic Pingback in On Using Manual and/or Automatic Link Notification Systems I also described how I mainly relied on Pingbacks.

Gathered from the discussion in the comments (and the slowly disappearing Trackback URI on blogs) it seems that especially the newer generation of bloggers, including myself, is not aware of the Trackback feature let alone use it. Does that mean that WordPress, or any other blog software for that matter, should remove the feature? If Trackback is only being used by spammers should we keep that little Trackback box that hardly anyone uses?

I am sure users would raise hell if WordPress would remove the Trackback feature because as Martin Emmerich comments: “Trackbacks and pingbacks are the threads of the blog web and part of the blogging culture.” Trackbacks play(ed) an important part in our blogging culture and they have helped to shape the blogosphere as we now know it.

So what should we do with the Trackback? Should we do anything at all? Anil Dash from Movable Type, who developed the trackback, replied to a first wave of “trackback is dead” declarations in 2005 that we should fix its problems:

Finally, the familiarity and utility of TrackBack, especially now that current-generation tools reduce the likelihood and reward value of spamming, means that there can be a base for a new generation of TrackBack, featuring necessities like authentication and richer content payloads. Throwing the baby out with the bathwater in regards to TrackBack would be as silly as throwing out email because it’s been abused.

Mend it, don’t end it! :)

Did Pingback fix TrackBack sufficiently to render it obsolete? Should we remove obsolete features from the already abundant options in the blog software interface? Troy Duncan shares my wish of further developing conversational techniques: “Instead of removing choices, I would like blogging platforms to develop more ways to extend the conversation.”

Do You Care Where Your Comments Are?

by

The discussion surrounding the previously addressed Commenting Issues in the Blogosphere heated up again this weekend with Robert Scoble claiming that the Era of blogger’s control is over. When I asked the question: Where Do You Leave Your Comments? I only dealt with commenting on blogs:

When bloggers are quoting other bloggers and you want to comment on the issue, where do you leave your comment?

There are three different options:

1. Comment on the the original post
2. Comment on the post that quoted the original post
3. Start a new post and use trackback/pingback to notify the other two posts

However, we are increasingly using other services and social networking sites to engage in the conversation. The feature to auto-post your latest blog post on Twitter is a very popular way to promote your blog post. It also means that you may receive comments on your blog post in the form of a Twitter reply.

I notice that I reply differently on blog posts when I comment on Twitter than on the actual blog post itself. When commenting on a blog post I feel the need to sit down, reflect and spend some time on formulating a valuable comment. However, when I comment in the form of a Twitter reply I am not only limited to 140 characters but I also feel my comment is part of a time sensitive flow. This means that my comments are not only shorter but that it also lowers my personal barrier of commenting, I can write a quick and short reply.

I recently commented on a blog post with a Twitter reply suggesting some corresponding literature. The author then asked me if I could comment on the blog post also which I then did. This is the problem we are currently dealing with. Should we care where our comments are, that the conversation is increasingly scattering around the blogosphere? Should we cling onto our blog as the central aggregation point of our conversation?

Friendfeed suggests that the issues of distributing commenting in the blogosphere seems to have moved beyond control. It is the perfect tool to keep up with your friends’ feeds but it also allows you to bring the conversation to Friendfeed. The situation is getting more and more dispersed. We use centralizing features such as CoComments to keep track of where we leave our comments but the conversation is only visible to us and not to others who would like to participate.

I don’t care where my comments are, as long as I am aware of them. This is the issue that we need to address which is an infrastructural issue as Matthew Hurst from the Data Mining Blog points out:

What is being lost in the conversation is the fact that the infrastructure of the blogosphere, due to its somewhat amateur evolution process, has not managed to fix some of the serious issues that have troubled it from the past. Commenting is exactly one of those things. As the value and use of comments evolved, and as the distribution mechanisms of content evolved, little effort has been made to bring commenting along with it. What has happened, is the appearance of a number of hacks on top of the base infrastructure to get around this issue. Perhaps the exception to this is the RSS 2.0 commenting mechanism.

Do we need an infrastructural fix or should we just “give up control” and focus on the conversation taking place? Robert Scoble doesn’t care where his comments are, do you?