My-Website

修改了一下這個版型的 node.tpl.php，給每一篇文章的底部加上了個小貼紙，這樣一來，有需要的人，或是支持這個小地方的，可以透過小貼紙，方便你把它給加到你常用的 web2.0 的 list 裏頭。目前放了四個 web2.0 的小貼紙，分別是 HEMiDEMi , del.icio.us , digg 和 Technorati 。 ...

一早收到一封來自 Bluehost 的老闆 Matt Heaton 的來信，裏頭洋洋灑灑地寫了一堆 @@ Bluehost 是這個網站（drakeguan.org）架站的地方，每個月要價大約 300 塊新台幣，一次以付一年的費用為單位。它提供你 50GB 的空間、一個免費的 domain name、等等等等 … 他的來信指出，因為 Bluehost 提供給使用者用的 Cpanel 導致他們的 server 有非常大量的 file access，於是他（Bluehost 的老大）下了命令進行修正，但這個修正在還來不及通知使用者的情況下就進行了，導致有數小時的 email 功能無法使用，至於為什麼不立刻通知使用者，是因為他們發現，光是要通知所有的使用者，就要花去 18 個小時，而這個問題太緊急了，不立刻處不行，blah blah。重點是，對於他這麼一位公司的大頭（President）來說，他大可不用親自寫信給所有人，可見這事件很嚴重，而他也立刻意識到（一天之內）要事後立刻發信給所有人。我很欣賞他這麼負責任的作法，相當的欣賞，真是有擔當的人，哈。 下頭是他的來信： Dear Bluehost.com Customer, I am writing today to give you some important information regarding your Bluehost.com account. As many of you know Bluehost.com uses Cpanel, a third party product, as our control panel to allow customers to manage their sites. While this is normally a good thing, it also takes much of the control away from us and sometimes forces us to live with deficiencies that we would normally not tolerate. Lately Cpanel has become so slow and cumbersome that despite buying some of the highest end hardware available some sites are sluggish at best and extremely slow at worst. This was never acceptable to us and we tried to work with Cpanel to resolve our issues, but it is clear to us that our issues will never be at their forefront. So what do we do? Yesterday was my breaking point. A customer called in to complain of a slow site. I checked it myself and the server load showed it was running fine. Clearly it wasn’t, and I wanted to know what was causing his issues. To make a long story short Cpanel was hitting every server’s hard drive array close to 50,000 times per day more often than it needed to (Based on my rough calculations). Our server monitoring was not doing its job and our customers bore the brunt of these issues. There wasn’t an easy fix and our servers were all grinding to a halt. We had to implement a custom fix and it had to done immediately. The main issue causing these problems was mail related. About 70% of all users had to have their mail moved to a new system and converted to a new storage method. I made the difficult decision to execute these fixes immediately without notifying all our customers first because of a couple of reasons. First, to mail all our users with our current system takes approximately 18 hours (We could do faster, but then many emails would be denied by large ISPs because too many emails come form a single source too quickly), and second because it was causing such a severe problem with all our servers that it simply couldn’t be delayed. It was causing so many sites to run poorly that we acted as fast and effeciently as we could. This made many users email temporarily unavailable. No emails should have been lost in the transition. It simply wouldn’t allow you to log in while mail was transitioned from one platform to another. Again, we greatly regret having to do this without prior notification, but the benefits were exactly what we hoped for. While all server issues aren’t immediately resolved, the VAST majority of problems we were seeing on all servers are virtually gone. You should now see a SUBSTANTIAL improvement in almost all areas of your site including mail issues, script execution time, and overall responsiveness of your hosting experience. Next week we will provide a link to a user monitoring service that will allow you to monitor your server (From our perspective) to see basically what we see, and know if issues you are experiencing originate on our end or if some other factor is involved. We have more speed improvements being worked on aggressively right now and in the near future those details will be made available as well. I know this email is lengthy, and I congratulate those that made it this far :) I just wanted you to know that I care about what happens to your sites, and not just because you pay me to care. I don’t get to be as technically involved as I used to be because of trying to run the company, but I realize now that a change is needed. I may not be the best admin out there, but I care the most and will always be your advocate to making your hosting experience better. All users (All 210,00 of you) can ALWAYS email me directly at - matt@bluehost.com Thanks for your support, Matt Heaton / President Bluehost.com

下午在逛中國大陸的 drupal 社群 時，發現到老苗的行走日记 ，有沒有發覺，網站的版型很相像呀。我猜他和我的版型一樣，都是修改自 The Guy Wilkins Band 這個網站，感覺挺有趣的。 有圖有真相，放上三個網站的圖出來，讓大家比較一下。 The Guy Wilkins Band 老苗的行走日记 drakeguan.org

繼上上週開始，一直會有一些廣告留言出現，都是色情網站之類的。剛開始是一天三四封，覺得還好，就手動刪一下，後來有天一次出來個十封垃圾留言，有點火大了。 ...

最後，我選擇使用 Akismet module 來處理討人厭的 comment spam。 當初不使用 captcha，是因為，一來我的小站真的很小，開張不久；二來覺得很麻煩。像我自己，如果想留個言回覆時，遇到要求你要註冊或是來個 captcha 的，就會有點懶。 ...

今天下午手賤，想安裝一下 CCK，結果發現之前有安裝了，然後 drupal 官方抓到的 CCK 版本比較新，就想說自己先手動移除舊版的，這樣應該比較好。結果不小心把 node_revision 整個 table 砍掉，所有的文章都不見了!!! ...

剛剛看到右邊的 Recent comments 多了一堆留言，非常的多，然後都是英文，就猜到是被攻擊了，留張圖紀念好了 @@; 除了最上頭的那個留言是「真人」留的以外，其它都是惡意程式留的吧！（如果是人工打的，那這一位到處留垃圾廣告的人也太遜了）網路垃圾實在很討人厭，為了阻擋他們，已經做了「留言一定要先經過 Preview 這個程序」了，實在不想放上個「辨識碼」，要求每個人要輸入裏頭的數字或英文。

這個改編自某網站 的 CSS template，因為沒注意到一些細節，在 Firefox 1.0.7 嚴格的把關下，破功了…變得支離破碎的。 經過一陣子的奮鬥之後，終於解決啦。 ...