Hello. I am Paul Kinlan.

I've updated my site's settings to display fewer posts on the homepage, resolving a recent issue I was having with Feedburner.

This post details how I developed a Call Detail Record (CDR) generator for my final year project on telecoms fraud. The generator creates realistic CDRs using a simplified data model, focusing on caller, callee, call type, start time, and duration. Various user models (high, low, business, etc.) are configured with parameters like average call cost, standard deviation, and call frequency for different call types (local, national, etc.), along with likely call times. Random numbers are then generated within these parameters to create a diverse set of CDRs that accurately reflect the modeled behavior.

My Feedburner full text feed is currently broken and I'm unable to identify the source of the problem. This has led me to consider moving my blog away from Feedburner.

UK Amazon Marketplace sellers can now easily link to a searchable, indexed list of their products. Just append your Seller ID (e.g., A30C94ZTNLBKQM) to http://www.kinlan.co.uk/amazon/uk/SellerID. Currently, this only supports up to 20 products and is UK-specific, but US support is coming soon.

My tag directory has a cool new feature: Amazon product integration! It pulls book data from Amazon AWS related to each tag. Right now, it adds links to relevant products, but I'm thinking of adding images soon. This latest addition brings the total number of Web 2.0 APIs used in my mashup to four, including Delicious, Yahoo Search API, and Google Blog Search RSS. Check out the examples for tags like RDF, RSS, and Mashup to see it in action.

My tag directory has been updated to incorporate Del.icio.us integration. It fetches RDF data from del.icio.us to display the most popular tagged items. Explore examples for tags like RDF and RSS using the provided links.

I've just posted the C# source code for serializing and deserializing OPML files using a simple object model. The code demonstrates basic serialization and deserialization, creating an OPML structure with a head, body, and outline elements. While the object model is functional, it's not perfect and could be refined. The example code shows how to create an OPML object, populate it with sample data, serialize it to XML, and then deserialize it back into an object, useful for anyone working with OPML in C#.

My blog has a Technorati rank of 0 with 236 links from 22 sites. Is this the best blog ever? I hope so!

Someone searched for "directory explorer c#" and landed on my site, likely not finding what they needed. This post clarifies how to use C# for directory exploration. It covers using .NET's System.IO namespace, specifically the File and Directory classes, for tasks like checking file existence (File.Exists) and getting a list of subdirectories (Directory.GetDirectories). This information will hopefully be helpful to future visitors with similar searches.

I'm working on a .NET object model for OPML 2.0 to easily serialize and deserialize OPML files. Serialization is working well and creates correctly formatted files thanks to constraints based on the OPML spec. Deserialization is proving tricky as the XML Deserializer isn't enforcing those same constraints, allowing incorrectly structured OPML files to be loaded. I'll share the code and continue working on it.