Sticking with intraVnews

I downloaded and installed the new NewsGator trial in a VPC to see how it looks. Maybe I’m still getting used to this whole Outlook news reader thing, but I don’t understand why NewsGator continues to flatten my OPML hierarchy. RSS Bandit, SharpReader and intraVnews all respect my hierarchy. I may not read as much as Scoble, but I am reading over 200 blogs these days and I like to categorize them. Favorites, GDN Workspaces, .NET bloggers, MSFT bloggers, Blogs I only scan the headlines of before I delete them, etc. But when I import that same OPML into NewsGator, it gets flattened into one big list of feeds. Apparently, you can manually move the folders around once they are created, but I’m not interested in doing that 200+ times.

Too bad, because the online services looked cool.

Project Niobe

My teammate Simon has posted details of his managed SDK for Outlook codenamed Niobe. He’s also created a GDN workspace for it. Coolness.

Geek / Blogger Dinner Wed.

I see from Jim, Rory and Scoble that there’s a “Weblog Meetup” on Wed. evening. It’s at a bowling alley. I hate bowling. I mean, I really hate it. As in I’d consider lighting myself on fire to get out of bowling. But this bowling alley has good beer and Wed is not karoke night. So I think I can make it.

More Old Teammate News

Two ex-teammates, Tim Mallalieu and Jeromy Carriere, have a new article on Enterprise Interoperability between .NET and J2EE posted on MSDN Architecture Center. Combined with Simon’s book and the Patterns and Practices interop guide, there’s alot of good guidance on this topic.

Thinking about SPSynd

I’m kicking around SharePoint Syndication again. There are a variety of reasons. I got email from someone @ the SP Web Component Directory about it. According to Scoble, the Front Page team is interested in RSS. And the primary kicker, there’s a project going on in my group internally that is using WSS and wants to expose RSS feeds.

Glad to know it’s popular. Too bad it’s not done and I’m not sure how to finish it.

Generic feed generation works just fine. The problem is customization. I need a user-friendly way (i.e. not hacking XML in the config file) to configure the feeds. Currently, the config file specifies which lists and webs expose feeds as well as the format of the feed for different list templates. I want to move that config so that it can be managed by the administrator using a simple UI, not the XML file. But that leads to questions: Do I try and stash my config data into the existing web and list configuration via the standard object model or do I bite the bullet and store it somewhere else (i.e. another DB)? What’s the best way to add admin of the feed to the existing admin pages? Frankly, I don’t know the answer to these questions.

One way to solve this problem would be to completely refactor the solution. Instead of relying on the WSS object model, I would leverage the WSS web services. This would let me run the feed generator outside of the confines of WSS. Basically, I’d just be translating formats – the output of the web services into RSS and OPML. This would be really great for hosted WSS since it wouldn’t require any change to the WSS site itself. However, doing the security right for this scenario would be a pain in the ass. WSS web services use transport level authentication which means it’s difficult to “hop” credentials across servers.

I don’t know if the answers to these dilemmas are out there in the blogosphere, but I figured I might as well put the questions out there.