Nucleus 3.0 has just released over the weekend. I finally back from Toronto and upgraded to it. But since all the plugins issues with Radek's split from Nucleus and starting BlogCMS, I'm still missing a few plugins. Also, many plugins/functions/XHTML CSS validation need to be done.

Update:
- NP_RSSItem still broken
- NP_BlogWithOffset and NP_PageLinkList still not working fixed

Missing:
- NP_PDF
- NP_Poll
- NP_Chat
- NP_Weather
- NP_ExtraSkin
- NP_Table

Misc.:
- Fix plugins that not use sql_table, supportsFeature fix later
- Fix plugins that not use createItemLink fix later

Fedora 2 was released this week, after download and install it. I struck on setting up WLAN. It was caused by a race condition from my housemate's router. Now it's all working.

I even installed synaptic on FC2.... it's the perfect toy for a upgradeholic like me.

I have been doing a lot of coding for Nucleus lately. It's mostly plugin work and some core hack. I'm planning to contribute to this project since it's a cool software that I'm sure can helps make better. Also, I want some experience on PHP/MySQL and web application development.

On the other hand, finally able to turn on FancyURL for the site! However, now I have to visit all functions to make sure all plugin works with FancyURL (many are broken). Also, posts are need update to point to the right URL.....

Update:
- NP_PDF has the wrong URL and permlink and formating is screwed up
- NP_Print has // in the URL
- Some links have blog/blog or blog/blog/blog It actually just how FancyURL works....
- NP_WIE's spy mode has wrong member URL
- NP_RSSItem didn't work
- RSS 2.0 skin still using the non fancy URL format Fixed
- PageLinkList doesn't work Fixed, thanks to Radek
- Need to test FancyURL off

So, my friend Stephen working for Hutchison Wireless in Hong Kong gets a 3 UMTS phone. He invited me to join the 3.hk on-line videoconferencing service. However, it only supports MS Netmeeting.....

It's just that H.323 (or Netmeeting's implementation?) uses dynamic ports for connection. So, you can only get it to work by putting your PC on the DMZ. Of course, I can't do that since I don't want to put a machine on the net unprotected (yes, there is personal firewall... but....) and I'm running a web server which is behind the firewall happily using port forwarding. To make it more complicated, my new housemate Martin might want to use Netmeeting as well.

I would think standard like H.323 have take into account for working in different enviroment, but did it? Maybe I shoudl take a look into it.

Did I say it's suck not able to get it to work?

Update: So, I saw some posts on the Internet regarding who's to blame. here...

It basically said H.323 is developed standard before NAT is widely used and it is working for many routers.... right! But NAT is deployed in millions of home around the world now and what to blame here? I just hope they fix this in the future.

NetMeeting h.323 and a NAT router