ironing our pants into the universe

Just a little update to say that paid work, unrelated to Sux0r, is taking priority until the Christmas holidays.

Before I disappear for a few weeks, I've made a few changes to the Naive Bayesian categorization algorithm. What I did was change the "fake probability" condition in an attempt to compensate for skewed training sets. The discussion is here. The code can be obtained via CVS.  I'm running the changes on the demo site (i.e. the site you are currently reading) and am getting decent results.

Placebo, or math? Code review welcome.

Everyone seems to hate CVS except me.

Over the years I've used Perforce, and MS Visual SourceSafe, but at the end of the day hosting on SourceForge in trandem with $79 USD for SmartCVS solves my problems.

I feel your need to flame, I feel your pain, but honestly I don't care. My two issues with CVS have always been UTF-8 and branching. And as a guy who dealt with Perforce branches in a fortune 500 company, I can be realistic and say most chose drama and staff turn-over instead of branching. The rest take a serious look at GIT. As for UTF-8, SmartCVS solves that just fine.

One problem I did encounter was that SmartCVS locks files. This is very "the other version control system" in the sense that it encourages check-out before coding and checking-in. That's fine when the organization asks of it. For sux0r it's ridiculous.

To disable this feature on OS X, open the Info.plist file within the SmartCVS.app in a text editor. You will find following lines:

<key>Properties</key>
<dict>
<key>apple.laf.useScreenMenuBar</key>
<string>true</string>
</dict>

Add another key-string pair:

<key>Properties</key>
<dict>
<key>apple.laf.useScreenMenuBar</key>
<string>true</string>
<key>smartcvs.permissions.disable</key>
<string>true</string>
</dict>

This will disable the permission setting feature. Good to go, commando style.

I've added rudimentary support for Atom 1.0 in CVS so that I could add PHP.Net and Moongift in the Feeds.

Rudimentary in the sense that some opinion leaders feel their blogs deserve a recursive relative link parser that, once failing to fallback on xml:base, should work that much harder to build the absolute link provided by everyone else to their content. The code can't do that yet.

The suxRSS class is very little concerned about correctness. It is very more concerned that random technocrats tend to form random committees and invent random ways to open their data in an effort to leverage their less than random entrepreneurial plans. And sux0r can lazily comply when the winner writes the history book.

Anyway, those wanting these changes will have to wait until the next release. Or get their hands dirty and have a look in CVS. 

My goal is to be able to parse a very smart person's Atom feed, my want is people use RSS 2.0 and not Atom 1.0. But hey, I use GNU nano so what do I know?