存档八月 20, 2006

台湾博客惊叹大陆网民热情

看过刘苏怡比较耸人听闻的新闻标题,我觉得我这个题目也挺有冲击力。

“遨遊天地任我行”http://www.dearjohn.idv.tw是一个台湾的blogger,正好最近一篇文字提到跟我很相近的想法,就是跟对岸的blogger(相比台湾来说,我们就是对岸了)增进沟通。

事情的起因来自李亚鹏最新的一篇博客文章,浏览数回复量超级惊人,是他们台湾blogger无法想象的一个高度。当然,台湾的blogger也很少有上千的feedburner订阅数,而在donews就有好几个,keso甚至已经超万,堂皇迈入万元户的行列。

我想这也是很多港台媒体工作者、艺人喜欢在新浪开博客的原因,他们可以得到大陆网民众多的回复响应。这是其他地方无法达到的效果。而我虽然也有http://dlbaobei.com这个独立域名,但是donews巨大的号召力也让我驻留在此。

边栏加入了港台博客最新文章的列表链接,有对港台地区的博客感兴趣的朋友可以经常来看看。有喜欢的,我又没有看到的港台博客,也欢迎您回复推荐给我。谢谢。

大家可以到这里看最新的港台博客内容聚合。无需注册。
http://dlbaobei.com/viewthread.php?tid=111&extra=page%3D1

施主席,拜託李亞鵬幫你連署可能比較快!
| 06/08/14 15:02
| 權方位觀點
相信最近有不少人注意到一則新聞,就是王菲、李亞鵬的小孩有唇顎裂這件事,我日前也針對新聞報導中的歧視字眼專文討論過了,今天是要說的是因為這則新聞,延伸出一件讓我訝異到下巴都快要掉下來的發現。

這件事的男主角李亞鵬於2006年8月12日早上10:08:19在他新浪的部落格上發表了一篇感想:感謝。文中提到了他的一些現況和感想,文情並茂,真誠感人,雖然不曉得是否是本人所寫,至少也算是對外界的關心有了一個具體的回應。然而,看了他的部落格,令我最訝異的是,從8月12日早上至今,大概才兩天多的時間,已經有1267289人看過這篇文章,是一百二十六萬多人次喔;一共有19242篇迴響(評論),多達386頁,看都看不完!

以台灣最當紅的部落格--彎彎的網誌來說好了,平均每天的瀏覽人次大約是10-15萬左右,每篇文章的回應大約是200-300篇,已經是台灣相當了不起的指標性網站了,但和李亞鵬的部落格比起來,根本還是小巫見大巫而已。

當然,大陸上網人口是台灣的不曉得多少倍,點閱人次和回應人次比我們多都是正常的,但我真的沒有想過竟然可以多到這麼離譜!或許,這個議題剛好在大陸很火,李亞鵬和王菲又都是相當知名的藝人,動見觀瞻,但如果他們隨便在部落格上寫一篇文章,兩天的時間,就可以有上百萬人看得到,兩萬人的回應,這是一種多麼可怕的傳播力量?如果他寫的不是感謝,而是某種偏見或是煽動文字,會造成什麼樣的破壞力?這種網路使用的規模,恐怕不是成長在蕞爾小島的我們所能想像的。

就連大陸新浪網的首頁,也貼出了「李亞鵬博客單篇文章,創新浪博客訪問記錄」的號外,可見這種爆發力恐怕連大陸同胞也有點出乎意料之外,我想,換成國內任何一家BSP,主機是否能負荷得了都還成疑問吧?

我倒不是要長他人志氣、滅自己威風,只是在訝異這股力量之餘,我們或許可以開始思考,同樣用華文創作的台灣人,是否應該多關心對岸博客的發展現況,試著進入他們的社群去瞭解他們的文化,多增加兩岸的溝通管道,撇開繁簡意識形態的問題,善用這股華文網民的力量,跳脫自我設限的迷思呢?

评论(9)

我们从失败中可以学到更多

在donews的新闻里看到这个《Kiko之死引发的Web 2.0思考》,题目耸人听闻,也有些莫名其妙。看题目还以为是某个web2.0应用导致了kiko这个人的死亡。

Kiko其实是一个在线日历应用,跟google calendar类型相同,它是最早出现的此类应用。

kiko无法继续下去,最后决定是八万美元拍卖。我觉得很难有下家购买它,价格不菲,而且前途渺茫,因为google实在是很难打败的,八万美元不过是google的一簇牛毛罢了。当kiko最火爆的时候,肯定不会认为自己只有这个价。(包括豆瓣也是如此,我记得当时有新闻说豆瓣几百万卖了,阿北在blog澄清,另外也笑称怎样也不能这么便宜,当然,豆瓣仍然健在)

Richard White 是一个界面设计师,看上去有点像金凯瑞。他的blog上写了一片文字,介绍一些经验教训。我觉得这比什么吹牛B的文字都有意义有价值。每个想进入Web2.0的朋友都应该读一读。

原文链接:
http://height1percent.com/articles/2006/08/18/actual-lessons-from-kiko

Actual lessons from Kiko

Posted by Richard White 2 days ago

With all of the buzz about Kiko’s demise (and how Web 2.0 going with it) I thought, as a member of the Kiko team, I’m in a good position than most to give a detailed explanation of what we learned and what went wrong. Be warned, this post will be long on facts and stories so if you’re looking for assumptions and hand waving I’d suggest reading some other posts :)

First, a few common questions:

Did you see Google Calendar coming?

Yes. It had been in internal beta for over a year and not all the Googlers at the ‘plex are good at keeping secrets. The launch that really surprised us was 30boxes.

Did Google Calendar kill Kiko?

No. One of our biggest traffic days was when Google Calendar was released because we were mentioned in all the new stories as one of their top competitors. In fact, we repositioned Kiko to take advantage of a market that most other players, including Google Calendar, were neglecting: users outside the US. We added options like Monday week start and different date formats. We setup a wiki and let our users translate Kiko into 11 languages. And we moved away from a US-only SMS reminder system to one that worked internationally. At last count 60-70% of our users are from outside the US.

That said they did have an impact on our ability to garner press for our re-launch (see below) but it wasn’t a case of Google coming into the calendar space and crushing us as some people have suggested.

Where was the business model?

Everything was predicated on getting a critical mass of users. Without that there’s no point in coming up with alternatives and if you do achieve it then you can monetize through the usual channels (ads and premium accounts). I agree with the 37signals argument that having paying customers forces you to hone in on what that market wants, and that probably would have done us a lot of good, *but* that’s not why we went under (see next question). Many people seem to disagree with me on this point so feel free to post your counter arguments (or links to them).

Why did you guys decide to call it quits?

We didn’t have the capital, and not just in the monetary sense, to take Kiko where we thought it would successful: the small business / OEM market. The team was burned out and we decided that it was time to find someone else to carry the torch. We did not run out of money. In fact, we pulled up well short of the end of our runway. So if you’d like to make the argument that our lack of a business model did us in, go for it, but it has little basis in reality. For more about this, read my Kiko eulogy.

And now, what I learned on my web 2.0 voyage
Stay focused

Justin mentioned this on his post mortem write-up but I’ll elaborate a bit more. We were on track to release the new version of Kiko in the middle of January, when we *lost focus* and starting working on something totally different altogether. This was obviously a suicidal move in hindsight as it cost us 2 months: Kiko 2.0 launched on March 15th instead of January 15th. During that time two important things happened:

1. 30Boxes came out of nowhere and launched on Feb 14. Thus becoming the new internet calendar darling.
2. Screenshots of Google calendar were leaked and posted all over the internet.

The combination of those two events meant we got very little press coverage for our launch (or re-launch) since everyone was holding their breath for Google Calendar or fixated on 30boxes.
Release early, but not too early

You always hear “Release early, release often”, especially if you hang around Paul Graham crowd, but the footnote that doesn’t get enough airplay is that you shouldn’t release too early (queue the sophomoric jokes in 3.. 2..). You only get one shot to impress people; don’t blow it because they won’t coming back next week to see if you’ve improved. Kiko 1.0 was released in September 2005 and was met with much fanfare for being one of the first AJAX calendars on the web. Unfortunately, the user interface was pretty bad (which is how I pushed my way onto the team) and people generally said “wow that’s cool… next!” The obvious problem is that when we launched version 2.0 I think the general reaction was “Kiko? Seen it. Hey how bout that new Google Calendar coming out?”.
Too many features killed the cat

It didn’t look it at first, but if you played around with Kiko 1.0 for 15 minutes you found out that there was a *lot* of functionality under the hood. Problem was that we felt we needed to bring *all* of that functionality over to Kiko 2.0. I mean you can’t cut features between versions, right? Wrong. We should have cut features, probably about 40% of them and launched.

This also contributed to our late launch and slowed us down after the launch because we had so many features to maintain.
You must have a plan for escaping the Technosphere

To a degree, it didn’t matter how many posts we got on TechCrunch, LifeHacker or Scoble; we would still be stuck in the same Technosphere duking it out with Google, 30Boxes and everyone else. You can make a nice living just pimping your wares in the technosphere (which is what I’m attempting with SlimTimer) but if you ever want to gain any real traction as an online calendar service you have to target the cubicle dwellers and their Outlook calendars that only exist outside the sphere. Techie users are fickle, transient and demanding. You can spend all of your time implementing ATOM feeds and hCalendar export and never be the better for it.

We didn’t have a plan for how to go mainstream, which, in hindsight, was a prerequisite for our success. We would have needed capital to do old school PR, marketing and sales and develop a sync service for Outlook. That said, I don’t think either of Google Calendar or 30Boxes have managed this feat either.

Regardless, we were feeling pretty good about ourselves around the middle of April. We were running neck and neck with 30boxes, according to Alexa, and we thought that the release of Google Calendar might be good because it would push one of the other big players into acquiring a calendar application to compete. 30boxes had stated that they didn’t want to be bought out so, as the #3 player, things were looking hopeful. Things didn’t pan out, but that’s okay. None of us were ever had a Lexus on hold; we were just happy to be in the fight.

So, What’s next for me? Well the ‘next big thing’ for me is already here: SlimTimer, online time tracker and the solution to the scourge of timesheets, launched to positive reviews a month ago and I’m working hard to keep the momentum going.

评论(1)

港台的博客在说什么?

从小受到的教育方式的不同,造成了我们和港台的blogger沟通并不多,可以从各个国内blogger的blogroll或者友情链接上看出来,基本上没有几个有繁体中文的链接。

他们在想什么?他们在说什么?其实很简单,看他们的blogger就是了。可是也许是我们国内太注重内部循环发展,或者是说眼光只是注意到大陆这片地区,很少有人介绍港台方面的blogger。

我最近有意的收集一些有意思的blogger,希望能在近期介绍一些给大家。

评论(4)

links for 2006-08-20

留言

什么是podcast

我个人意见认为,凡是不能使用apple itunes或者什么软件订阅的,都不能算是podcast。因为它们根本没法下载到我的ipod上听,那算个屁播客啊。

国内有这种服务的provider,只有podlook。其他的providers真是应该好好反思反思了。





留言

如何跟踪Blog Network世界的最新消息?

看到这个题目,不要以为我会写很多。其实大家只要订阅下面这个站点的Feed就好了。
www.blognetworkwatch.com

可以看到的是,最近9Rules动作频频,吸收了不少新的blogger。

Recent Articles

SchwarzTech has joined 9rules
Rohdesign joins 9rules
9rules adds Rida Al Barazi
b5media is seeking Business Bloggers
Descending Ashtray joins 9rules
Delicious Days has joined 9rules
Knit like a Man joins 9rules
Instablogs goes baggy chasing after shoes
Matt @ San Fransisco - 8/23 - 8/25
Simple and Loveable has joined 9rules
Deeply Shallow joins 9rules
thirteenCents and 9rules
Podcast interview with Aaron Brazell
9rules adds Brad Garland
Brandon Milford joins 9rules
John Evans (Syntagma) interviewed at Blog Republic
Bright Meadow has joined 9rules
Watchtan has joined 9rules
Tifffany and Andrew join 9rules
Ben Bleikamp joins The Blog Herald

留言

美国消费者满意度指数,苹果击败Dell及HP

在个人计算机市场上Apple领先Dell和HP等大品牌,不过我们比较奇怪的是为何Dell的满意度也很高?难道是他们对美国国内市场的照顾更加周到?

其他方面的第一名如下:

汽车方面,丰田第一。

新闻网站,CNN.com,USAToday.com,ABCNews.com等,排名都差不多。

网站Portal前三强,Yahoo,AOL和MSN。

搜索引擎,Google第一。

消息来源:
http://www.theacsi.org/second_quarter.htm

评论(3)