Hello.

The OPML output functionality in my AJAXTagger is now fixed! There was a bug caused by Internet Explorer's lack of support for the __proto__ construct, affecting how the script determined an object's type. This fix resolves the issue, ensuring compatibility with IE6 and IE7.

The related Wikipedia articles feature in AjaxTagger v1 is temporarily broken due to an update in one of the Yahoo Perl Proxy Scripts for AjaxTagger v2. I plan to fix it soon.

I've figured out how to incorporate OPML into the upcoming version of the AJAX Tagger, enhancing its functionality. More details coming soon!

Just a quick update on what I've been up to. I'm still working on AJAXTagger v2 whenever I can. It's coming along, but I ran into a few JavaScript issues. Big shoutout to the Dream Projections blog for a post that really helped me figure out how to call JavaScript Object methods with setInterval – super useful for the priority queueing system I'm building.

This post kicks off documenting the requirements for the next version of AJAXTagger. The goal is to create a successful application (by my definition) by outlining features across functional areas, UI/UX, client/server-side business logic, data access, and dependencies. Key features include easy journal tagging, related information retrieval (tags, articles, blogs, websites), diverse search provider integration, streamlined results presentation, image inclusion, and efficient article pulling/saving. The UI should minimize user effort, provide immediate feedback, and offer information hiding. Performance is crucial, targeting IE6/7 and Firefox, with emphasis on minimal server round trips, client-side optimization, and error handling. Data storage is preferably client-side, with external access optimized for speed and resilience. External dependencies include various search engines/services, while internal constraints involve limited server access and reliance on HTML, JavaScript, and XmlHTTPrequest.

I'm trying to be more diligent about documentation, but PDC distractions and the new MSN Search API have me sidetracked. The API's SOAP format and seeming redundancy with existing RSS search options make me question its value. Maybe I'll integrate it into AJAXTagger v2 if I can avoid feature creep. Check out my blog for MSN Search and Start.com developer program resources.

Yahoo! Publisher Network (YPN) now offers ad category targeting, similar to Google AdSense. This feature allows publishers to specify categories for their ads, resulting in more relevant ads for their audience. I'm excited about the potential of this for my own site and hope Google implements a similar feature in AdSense. I'm even considering incorporating this into future versions of AjaxTagger.

This is the sixth part of my series on the failures of my first AJAX application, AJAXTagger. While I initially hoped it would be useful for everyone, it mainly ended up benefiting just me by simplifying the tagging process for my blog posts. Although it didn't meet my initial grand expectations, it was a valuable learning experience. The next version will prioritize my needs but also consider features that could benefit other users, ultimately adding value for my readers.

This is the seventh post in my series about the failures of my first AJAX application. My biggest failure? No one used it! I had these grand visions of tons of users, but it turned out I was the only one. So, I'm changing my strategy. I've started this blog to centralize all information about the AJAXTagger. My next step is promotion! I need users to try it, break it, and give me feedback. Email me or leave a comment with your suggestions!