ironing our pants into the universe

• Support for microformats hcard specification in user profile page
• AGPL exception for templates (html/css/graphics), simple permissive terms
• Template tweaks: changed admin menus, sprinkled some javascript in photos, etc
• purge_orphans script in supplemental directory to clean up deleted images and corrupted link tables
• Ability for a user to reset their lost password (TODO: translate)
• Support for Atom 1.0 in suxRss()
• Regex improvements in suxHtml2UTF8()
• Fixed a problem where Naive Bayesian filtering was redundantly re-scanning items when limit was not yet reached
• New option in config file allows you to turn off Naive Bayesian categorization and automatic bookmark scanning, in case you want to use sux0r as a vanilla blog. (update your config.php files accordingly)
• Updated symbionts: Scriptaculous 1.8.2, TinyMCE 3.2.1

And again, for those going "My god, it's full of ugly..." I redirect you to this post. 2.0.1 is a hold-me-over until the next time, where I hope to have new templates.

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.

Sux0r's default skin is utilitarian but that doesn't mean it's doomed to ugly stick beatings forever. Last week I used sux0r to build Shie Kasai dot com. I was able to re-skin it in one afternoon. I am also working with a designer from Moldova on some new default sux0r partitions. Promising designs are in the works.

I have added an exception in the README so that files in the 'templates' and 'media' directories can be licensed under simple permissive terms i.e. your pick of any LGPL compatible license instead of the more accosting AGPL. To be clear, this means that you can create templates / HTML / CSS and not share them. We, the sux0r development group, distribute our templates under the AGPL.

All this and more in the next release of sux0r. Of course, CVS is always there for those who want to get their fix.

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?