Hello. I am Paul Kinlan.

I'm disappointed with Blogger BackLinks. I thought they'd automatically pull in links to my posts from Google Blog Search, but they don't. Users have to manually add them, which isn't ideal. I plan to create a version that automatically queries Google Blog Search and updates my page with backlinks from there.

This blog post asks readers for their opinion on including event announcements related to blog post topics. For example, if a post is about Apple Macs, I wonder if readers would like to know about Mac Expos. Similarly, for a post about World War 2, it asks if announcing related events like commemoration days would be useful. Readers are invited to share their thoughts in the comments or via email.

James Manning left a comment on my blog post about compression, pointing to a Microsoft article about built-in decompression support in .NET 2.0 for SOAP replies. While I appreciate the comment, Yahoo APIs don't use SOAP, so it won't be helpful in that context. However, this information could be useful for working with Amazon APIs, which do have a SOAP interface.

The IE team has announced that some CSS hacks used to fix issues in IE5 and IE6 won't work in IE7. This means web developers targeting IE7 will need to update their sites to address these breaking changes. The IE team encourages developers to check for common CSS hacks and replace them with standards-compliant code or conditional comments. While a CSS-based solution would be ideal, there currently isn't a standard for this issue, prompting a call to action for developers to update their code and support the move towards better standards compliance.

In a follow-up to my previous post about the scarcity of Bluetooth libraries for desktop PCs, Mark Arteaga brought 32feet.net to my attention. This site offers a managed Bluetooth library which I plan to investigate further. Initial impressions from the sample code suggest it's straightforward to use, with device discovery appearing as simple as calling a function and communication happening via streams.

I just discovered that Latricia updated the XML::Feed CPAN module to merge RSS/ATOM feeds into one ATOM feed. This is awesome! I had a similar idea for AJAX Tagger 2.0, where I wanted to offer a combined feed of all tagged results. If this module works as advertised, I can use it directly instead of building my own tool. This might be a better solution than my initial plan of using OPML.

This post discusses the security implications of cross-domain XMLHttpRequest access. While some argue that such access increases the risk of phishing attacks and unauthorized data access, others contend that these risks are minimal and that the benefits of cross-domain access, such as reduced bandwidth costs for "mash-up" applications, outweigh the potential downsides. The current security model, which requires proxying requests through the originating server, is seen as costly. I propose a server-side security model where third-party servers can control which clients can directly access their data, addressing the bandwidth theft concerns.

I'm considering compressing Yahoo Search results from my proxy, as suggested in a Yahoo Developer Blog post. I'm unsure if it's easy, worthwhile, and where to implement it (client-side or proxy-side). I'll need to handle browsers without compression support. Any advice?

My recent blog posts seem to be using trackback links automatically. Apologies to Blogger for the unintended behavior, however, I maintain my earlier criticism regarding the insufficient documentation provided for this newly launched feature.

I'm developing a complex new version of the AJAX Tagger (2.0) with enhanced features for adding data to journal entries. However, I'm curious if there's still interest in a simpler version like the original AJAX Tagger. Please share your thoughts and comments!