📄 model_comparison_20260421_164638.json 10,551 bytes Apr 21, 2026 📋 Raw

[
{
"model": "phi4:14b",
"timestamp": "2026-04-21T16:43:58.963823",
"tests": {
"titles": {
"elapsed": 20.4,
"raw_output": "json\n[\n \"Migrating from Google Calendar to Nextcloud's Self-Hosted CalDAV Server: Lessons Learned\",\n \"Transitioning Family Schedules from Google Calendar to a Private, Self-Managed CalDAV Setup\",\n \"Challenges and Solutions in Migrating from Google Calendar to Radicale for Home Use\"\n]\n",
"extracted": [
"Migrating from Google Calendar to Nextcloud's Self-Hosted CalDAV Server: Lessons Learned",
"Transitioning Family Schedules from Google Calendar to a Private, Self-Managed CalDAV Setup",
"Challenges and Solutions in Migrating from Google Calendar to Radicale for Home Use"
]
},
"draft": {
"elapsed": 12.2,
"compliance": {
"compliant": false,
"issues": [
"HALLUCINATION: Includes specific fictional timestamps"
],
"banned_words_found": [],
"has_code_blocks": true,
"word_count": 606,
"char_count": 4439
},
"grounding": {
"grounding_score": 1.0,
"checks": {
"radicale_mentioned": true,
"caldav_mentioned": true,
"cloudflare_mentioned": true,
"tailscale_mentioned": true,
"beelink_mentioned": true,
"python_mentioned": true
},
"well_grounded": true
},
"preview": "### Migrating from Google Calendar to Radicale: Lessons Learned\n\nThe Why\n\nIt all began with a simple family dinner. As my wife and I discussed the growing concern about data privacy and sovereignty, we realized that our reliance on Google Calendar was more than just convenient\u2014it felt risky. Our calendar contained not only work meetings but also our kids' school schedules and family events. We wanted to take control of our digital life.\n\nThe Stack\n\nWe decided to migrate to Radicale, a lightweight CalDAV server, hosted on a Beelink X1 Mini PC running Ubuntu 20.04 LTS. To handle email no..."
},
"seo": {
"elapsed": 1.2,
"raw_output": "json\n{\n \"excerpt\": \"Embarking on a migration from Google Calendar to Radicale revealed unexpected challenges and solutions in data privacy management.\",\n \"tags\": \"data privacy, calendar migration, Radicale\",\n \"meta_description\": \"Learn how we transitioned from Google Calendar to Radicale, focusing on data sovereignty while managing family schedules.\"\n}\n"
}
}
},
{
"model": "qwen2.5-coder:14b",
"timestamp": "2026-04-21T16:44:32.652022",
"tests": {
"titles": {
"elapsed": 23.5,
"raw_output": "json\n[\n \"From Google Calendar to Self-Hosted CalDAV: A Technical Migration Guide\",\n \"Migrating Your Calendar from Google to a Self-Hosted CalDAV Server\",\n \"Switching from Google Calendar to Self-Hosted CalDAV: A Step-by-Step Process\"\n]\n",
"extracted": [
"From Google Calendar to Self-Hosted CalDAV: A Technical Migration Guide",
"Migrating Your Calendar from Google to a Self-Hosted CalDAV Server",
"Switching from Google Calendar to Self-Hosted CalDAV: A Step-by-Step Process"
]
},
"draft": {
"elapsed": 28.3,
"compliance": {
"compliant": false,
"issues": [
"BANNED_WORDS: potential, robust, enhance"
],
"banned_words_found": [
"potential",
"robust",
"enhance"
],
"has_code_blocks": true,
"word_count": 542,
"char_count": 4078
},
"grounding": {
"grounding_score": 1.0,
"checks": {
"radicale_mentioned": true,
"caldav_mentioned": true,
"cloudflare_mentioned": true,
"tailscale_mentioned": true,
"beelink_mentioned": true,
"python_mentioned": true
},
"well_grounded": true
},
"preview": "### From Google Calendar to Self-Hosted CalDAV: A Technical Migration Guide\n\n#### The Human Moment\n\nWhen my wife and I decided to migrate from Google Calendar to a self-hosted solution, it wasn't just about the technology. It was about taking control of our data and ensuring that our family's privacy remained intact. With concerns growing around data sovereignty and the potential risks associated with using third-party services, we knew we needed a solution that allowed us to manage our schedules without sacrificing control.\n\n#### The Stack\n\nOur chosen stack includes Radicale, a self-hosted Ca..."
},
"seo": {
"elapsed": 2.9,
"raw_output": "json\n{\n \"excerpt\": \"Learn how to migrate from Google Calendar to a self-hosted CalDAV solution for enhanced data control and privacy.\",\n \"tags\": \"Google Calendar, CalDAV, self-hosting, data sovereignty, technical migration\",\n \"meta_description\": \"Migrate your family's calendar from Google to a self-hosted CalDAV server for better control over your data.\"\n}\n"
}
}
},
{
"model": "gemma4:latest",
"timestamp": "2026-04-21T16:45:27.399756",
"tests": {
"titles": {
"elapsed": 31.8,
"raw_output": "json\n[\n \"CalDAV Migration: Moving Calendar Data from Google Accounts (v3 API) to Nextcloud (v25.0.3)\",\n \"Decommissioning Google Calendar: A Step-by-Step Guide for Self-Hosted CalDAV Implementation\",\n \"Error Handling and Protocol Conversion: Migrating GCal Events to SabreDAV on Ubuntu 22.04\"\n]\n",
"extracted": [
"CalDAV Migration: Moving Calendar Data from Google Accounts (v3 API) to Nextcloud (v25.0.3)",
"Decommissioning Google Calendar: A Step-by-Step Guide for Self-Hosted CalDAV Implementation",
"Error Handling and Protocol Conversion: Migrating GCal Events to SabreDAV on Ubuntu 22.04"
]
},
"draft": {
"elapsed": 13.7,
"compliance": {
"compliant": false,
"issues": [
"HALLUCINATION: References Google Calendar API (we used webhook/email parsing)"
],
"banned_words_found": [],
"has_code_blocks": true,
"word_count": 668,
"char_count": 4868
},
"grounding": {
"grounding_score": 0.67,
"checks": {
"radicale_mentioned": true,
"caldav_mentioned": true,
"cloudflare_mentioned": false,
"tailscale_mentioned": false,
"beelink_mentioned": true,
"python_mentioned": true
},
"well_grounded": true
},
"preview": "# CalDAV Migration: Moving Calendar Data from Google Accounts (v3 API) to Radicale (Self-Hosted)\n\nThe initial trigger for this project was simple, and frankly, unsettling. Our daughter pointed out that she had to log into three different services just to check the schedule for our family dinner. The core issue wasn't the complexity of the calendar itself; it was the fact that our critical life data\u2014our shared appointments, our kids\u2019 school commitments\u2014was scattered across cloud endpoints owned by third parties. We needed the data to reside within our controlled network boundary. Data sovereign..."
},
"seo": {
"elapsed": 4.2,
"raw_output": "json\n{\n \"excerpt\": \"The challenge was data fragmentation: shared family calendars were spread across disparate cloud endpoints. This guide details migrating CalDAV data from Google's v3 API implementation to a self-hosted Radicale instance.\",\n \"tags\": \"CalDAV, Data Migration, Google API v3, Radicale, Self-Hosted Calendar\",\n \"meta_description\": \"Migrate shared calendar data from Google Accoun" } } }, { "model": "llama3.1:8b", "timestamp": "2026-04-21T16:46:17.092512", "tests": { "titles": { "elapsed": 13.6, "raw_output": "[\n \"Migrating from Google Calendar to a Self-Hosted CalDAV Server\",\n \"CalDAV Migration from Google Calendar: Lessons Learned and Best Practices\",\n \"Transitioning from Google Calendar to a Custom CalDAV Implementation\"\n]", "extracted": [ "Migrating from Google Calendar to a Self-Hosted CalDAV Server", "CalDAV Migration from Google Calendar: Lessons Learned and Best Practices", "Transitioning from Google Calendar to a Custom CalDAV Implementation" ] }, "draft": { "elapsed": 6.6, "compliance": { "compliant": false, "issues": [ "BANNED_WORDS: moreover, utilize" ], "banned_words_found": [ "moreover", "utilize" ], "has_code_blocks": true, "word_count": 509, "char_count": 3469 }, "grounding": { "grounding_score": 1.0, "checks": { "radicale_mentioned": true, "caldav_mentioned": true, "cloudflare_mentioned": true, "tailscale_mentioned": true, "beelink_mentioned": true, "python_mentioned": true }, "well_grounded": true }, "preview": "**Migrating from Google Calendar to a Self-Hosted CalDAV Server: Our Experience with Radicale**\n\nAs an engineer, I've always been mindful of the data we collect and store. My wife and I recently decided to switch our family's calendar management system from Google Calendar to a self-hosted CalDAV server using Radicale. The primary reasons for this move were family privacy and data sovereignty.\n\n**The Problem with Google Calendar**\n\nWe had grown accustomed to the convenience of Google Calendar, but as we added more family members to the shared calendar (our kids, our daughter's soccer schedule,..." }, "seo": { "elapsed": 1.5, "raw_output": "Here is the metadata for the blog post:\n\njson\n{\n \"title\": \"Migrating from Google Calendar to a Self-Hosted CalDAV Server: Our Experience with Radicale\",\n \"excerpt\": \"We recently switched our family's calendar management system from Google Calendar to a self-hosted CalDAV server using Radicale, citing concerns for family privacy and data sovereignty.\",\n \"tags\": \"calendars, google calendar, ca"
}
}
}
]