Archives for category: General

Although I’ve expressed approval for the new Facebook redesign, it’s obvious that many, many people hate it. If you’ve been on the new Facebook for more than a few milliseconds, you would have figured this out.

Let’s analyse this disapproval. Firstly, every single Facebook redesign or new feature, since it went mainstream, has been criticised by users. Everyone seems to hate them.

  • News Feeds 2007
  • Applications/Platform 2007
  • Beacon Ads 2008
  • New Facebook 2008
  • News Feed Redesign 2009

With the exception of Beacon Ads 2008 (and hopefully News Feed Redesign 2009), all users have gotten used to them and realised the potential and usefulness of the new features or redesign. This is obvious.

A Little Poll Comes Along

Some guy develops a Facebook app, covered by TechCrunch: Facebook Poll: 94% Of Users Don’t Like Redesign. This is an area which I really, really like to think about all the time: statistical bias. In a specific area: how bias is achieved through ignorance.

Main gist: there are three barriers to entry in this voting system.

  1. Giving a crap.
  2. Clicking through to the poll.
  3. Installing the application to vote for the poll.

People that feel that the Facebook redesign sucks will go ahead and have an initiative to ask Facebook to change it, because it apparently sucks. They pass all three barriers, because they have a drive to be against the Facebook redesign.

Others that feel that the design is indeed a pretty good design, and the “yes” people accept it as the status quo, and don’t make any noise about it. Therefore, many of them don’t have the initiative to fight against the naysayers, and go through the trouble of installing the application, so therefore we see a lesser-than-actual “yes”-sayer audience.

Another Facebook-related bias is the outrage against the Facebook Terms of Service change. Although probably less than 0.1% of people really cared about it (and that’s a pretty high estimate, since that’s about 200,000 people) are the ones who made the most noise and had the biggest audience. Not saying that’s a bad thing—it can be an important matter to concerned users—but that’s the reality of it.

Do you think anyone that didn’t really care about the Terms of Service changes had any initiative to argue for it?

No.

Recently, I’ve been experiencing a high CPU usage by the process syslogd in Mac OS X 10.5.2 Leopard, coupled with strange Console.app behavior. If you’re experiencing this as well, give this a shot and see if it works (at your own risk.)

syslogd

FIrst, you should check if this is a problem on your system, which is usually caused by large asl.db files. Open Terminal.app (Applications/Utilities/Terminal.app) and enter the following:

du -hs /var/log/asl.db

and hit enter. If it shows that your asl.db file is pretty huge (mine was 80MB) you’ll want to run this fix. If it isn’t, a rampant syslogd is probably not due to the asl.db file, but instead some application doing a lot of logging. Open Console and look if there’s any applications that are logging a lot, like if you see ” — last message repeated 500 times —“, that’s probably what is causing syslogd to own a lot of CPU.

If asl.db is huge, do the following. You’ll first have to enable a root user to your system. Then, go to Terminal, and enter the following (enter one by one, and hit enter afterwards):

sudo launchctl stop com.apple.syslogd
sudo mv /var/log/asl.db /var/log/aslold.db
sudo touch /var/log/asl.db
sudo launchctl start com.apple.syslogd

You will be asked to enter the root password on the first command, while subsequent commands will automatically be authenticated as root.

Once you do this, the syslogd process should restart, but the CPU it uses should be next to nothing. Hope this helped.