Hello.

I've taken my feed off Squeet due to repeated updates to old posts, which wasn't very useful given the low subscriber count. This change should prevent further issues.

I contacted Feedburner support about a full text feed issue, and received a helpful and quick response within 10 minutes. They explained that feeds are limited to 256k and suggested reducing the number of posts or post size to stay within the limit. I am very impressed by their responsiveness to public feedback.

I'm exploring Microsoft's Simple List Extensions for RSS and looking for real-world examples of their implementation. I'm particularly interested in seeing how these extensions can be effectively utilized and would appreciate any insights or examples.

My Atom feed was truncating the description text, making it look odd. I've fixed the problem and hope it didn't affect my readers too much.

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.

I encountered an issue where my FeedBurner RSS feed wasn't displaying any article content. I've implemented a fix, and you should now be able to access the feed through the FeedBurner icon at the top left of the title. Alternatively, you can subscribe to the ATOM feed at http://www.kinlan.co.uk/atom.xml.

My site's bandwidth usage spiked mid-month, and I discovered the culprit was MSN Bot repeatedly accessing my Atom.xml feed. It was hitting my feed every minute, consuming a significant portion of my bandwidth. The bot is apparently part of a syndication search engine, constantly checking for new content. I added a robots.txt file to throttle the bot's access frequency, which solved the issue.

I had this brilliant idea to create a merged RSS feed using client-side processing. The idea was to have a main RSS feed that linked to other feeds. My custom XML would include a list of sources. Then, using XSLT in the browser, the client could merge these external feeds into a single view. It worked perfectly locally! However, I hit a roadblock with cross-domain security restrictions when I uploaded it to my server. The browser wouldn't let me pull in feeds from other domains due to security concerns. Additionally, client-side XSLT processing isn't universally supported. So, even if the security issue wasn't there, many feed readers wouldn't be able to display the merged feed. In the end, the project failed. But, I learned a lot about browser security, XSLT limitations and client/server interactions!