Finally, starting tommorow evening (if we’re lucky the new server will be ready by this time), pinetd2 will go in production mode on ooKoo.org
This is a big step toward debugging, and will help me to kill most existing but yet unknown bugs in pinetd2.
Remember that pinetd2 is multicompatible. When updating, tables structures will be updated, but if downgrading they will be reverted to their original state.
Pinetd on ohloh results in something like that :
I just got bored, that’s ENOUGH of all the spam overflowing from many places to my blog, so I decided to get rid of DotClear, and make my own blog engine.
This is probably going to take a bit of time (understand « a while », if I ever really start writing it) and it’ll probably require at least the latest version of PHP (understand PHP 5.3.0, or not).
This new stuff will provide a new system for trackbacks (they will be signed using an SSL key, and if someone trackbacks with a new - unknown - key, you’ll have to approve that key before), better comment management (ban a user/ip and all its posts will disappear, also spam detector included, and finally a few spam-detection and annoy-the-spammers systems).
Anyway stay tuned.
Btw if anyone can provide me with design, it’ll be welcome.
If you didn’t hear before about pinetd, let me tell you more about it.
Initially, when PHP3 was out, I wrote a mail server using php. It was initially using xinetd to be run, then PHP/NC was born. PHP/NC (NC = Non-Connu) was a normal build of php 3, including a few more functions about sockets manipulation. It wasn’t really safe, but allowed more control over sockets in php.
Then, PHP4 was released, and a socket extensions was there too…