人家ifanr网站可是第一时间就放出各种小道消息，什么“symbian下第一个原生twitter客户端”之类的，还有某个博客又把gravity称为“S60上第一款twitter软件Gravity”，结果到最后人家网站开始组织团购……不得不让人怀疑他们的居心……
其实不就是twitter客户端么，s60上用wirelessIRC上twitter还是很好的，某些博客的博主啊……少见多怪……
Linux、Android、Networks、PHP，所有我感兴趣的技术……
Monthly Archive for 三月, 2009
昨天就修改了yegle.net这个域名的指向，但是到目前为止feedsky服务器还是解析不出来现在的ip，尝试修改http://feed.feedsky.com/yegle/的feed源地址，指向http://yegle.net/feed/，提示404错误。
既然有自己的稳定的空间，为啥还要把feed往外托管？还是这么垃圾的一个托管服务？
修改了feed.yegle.net的指向，然后用.htaccess重写到http://yegle.net/feed/，对feedsky的唯一留恋也没有了。就这样吧，再见feedsky。
现在twitterfeed.com和douban上都能正常解析feed.yegle.net了，嗯
是的，我回来了！
深思熟虑后，买了个支持ipv6的国外虚拟主机。在用教育网的同学们你们应该知道这个意味着啥：不需要代理，就能直接登录这个博客了。
使用ipv6，从教育网上传速度在60K左右，下载速度是70K左右，外网速度未知，应该不会太差。现在的配置是5G/500G/ssh/ipv6，价格是$9.95/month。贵了点，等研究出怎么绑定多个域名后找人合租去～
有了ssh的好处是……我可以建ssh tunnel来做代理了……直接能翻墙的socks代理哦～
有想租用这个空间的同学可以去这里看看
昨天去b.g.o上搜东西的时候看见的，发出来大家看看吧，挺好的
事情的缘由，我不是特别清楚，根据我的猜测，大概是这样的：
有人提交了一个xorg-xserver的version bump request，gentoo的一个developer回复了一句：
“As if we didn’t already know…”,并告诉bug reporter在x11的overlay里已经有xorg-xserver的1.6.0版
然后另一位又指出提交bug的这个人已经知道x11的overlay里有xorg-xserver的新版。
之后的情况只是猜测了。
根据后面那位大大火气很大的文字以及此bug当前的状态REOPENED，猜测有一个developer将此bug关闭了，引起了众人的不满。
原文如下：
——- Comment#6 From Caleb Cushing 2009-03-01 11:49:24 0000 ——-
it allows me to know the status of the bug. It allows me to know whether or not
you would prefer to spend your time complaining about the existence of a bug
than doing your job, fixing the bug. It allows me to know whether or not I have
to spend time doing your job to fix the bug, since it is my job to make sure
that this kind of thing is handled in my tree.
right now you are the kind of person that thinks being a volunteer is a
privilege and not a responsibility. You think that because you don’t get paid
that you don’t have to do it. I assure you that if you look at most non foss
volunteer jobs you either have to do your job or quit. it is the same in open
source. perhaps I’m judging you wrongly.
but you’ve spent more time discussing the existence of a bug than working on it
(my perception as the other bug hasn’t been updated). being cc-ed to a bug
doesn’t require you to respond to it daily. it requires you to report if their
is something to report.
you’ve also closed a bug that wasn’t fixed as fixed waisting my time and yours.
you could have chosen to ignore the bug until you have something to say,
instead you choose to waste your time trolling bug reporters who may have
legitimate reasons to track version bump progress.
your awareness of the issue isn’t my concern. your devotion to any actual
responsibility is.
and don’t go about saying, “don’t talk if you aren’t willing to help”. I’m
helping in my own way. if you’ll excuse me I promised zmedico a patch and
documentation for said patch, to portage.
So I’ll just be blunt, can I expect at least a masked 1.6.0 in the tree within
a week? or do I have to do it myself.
now, are you going to continue to waste both our time?
近期评论