Going to try for this one

Reviewed-on: #12

.gitea/workflows/build_push.yml

@@ -1,5 +1,8 @@
 name: Build and Push Image
-on: [ push ]
+on:
+    push:
+        branches:
+            - master
 
 jobs:
     build:
@@ -40,3 +43,19 @@ jobs:
                   platforms: linux/amd64,linux/arm64
                   tags: |
                       git.aridgwayweb.com/armistace/blog:latest
+
+            - name: Deploy
+              run: |
+                  echo "Installing Kubectl"
+                  apt-get update
+                  apt-get install -y apt-transport-https ca-certificates curl gnupg
+                  curl -fsSL https://pkgs.k8s.io/core:/stable:/v1.33/deb/Release.key | gpg --dearmor -o /etc/apt/keyrings/kubernetes-apt-keyring.gpg
+                  chmod 644 /etc/apt/keyrings/kubernetes-apt-keyring.gpg
+                  echo 'deb [signed-by=/etc/apt/keyrings/kubernetes-apt-keyring.gpg] https://pkgs.k8s.io/core:/stable:/v1.33/deb/ /' | tee /etc/apt/sources.list.d/kubernetes.list
+                  chmod 644 /etc/apt/sources.list.d/kubernetes.list
+                  apt-get update
+                  apt-get install kubectl
+                  kubectl delete namespace blog
+                  kubectl create namespace blog
+                  kubectl create secret docker-registry regcred --docker-server=${{ vars.DOCKER_SERVER }} --docker-username=${{ vars.DOCKER_USERNAME }} --docker-password='${{ secrets.DOCKER_PASSWORD }}' --docker-email=${{ vars.DOCKER_EMAIL }} --namespace=blog
+                  kubectl apply -f kube/blog_pod.yaml && kubectl apply -f kube/blog_deployment.yaml && kubectl apply -f kube/blog_service.yaml

kube/blog_deployment.yaml

@@ -0,0 +1,24 @@
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: blog-deployment
+  labels:
+    app: blog
+  namespace: blog
+spec:
+  replicas: 3
+  selector:
+    matchLabels:
+      app: blog
+  template:
+    metadata:
+      labels:
+        app: blog
+    spec:
+      containers:
+      - name: blog
+        image: git.aridgwayweb.com/armistace/blog:latest
+        ports:
+        - containerPort: 8000
+      imagePullSecrets:
+        - name: regcred

kube/blog_pod.yaml

@@ -0,0 +1,13 @@
+apiVersion: v1
+kind: Pod
+metadata:
+    name: blog
+    namespace: blog
+spec:
+    containers:
+        - name: blog
+          image: git.aridgwayweb.com/armistace/blog:latest
+          ports:
+              - containerPort: 8000
+    imagePullSecrets:
+        - name: regcred

kube/blog_service.yaml

@@ -0,0 +1,13 @@
+apiVersion: v1
+kind: Service
+metadata:
+  name: blog-service
+  namespace: blog
+spec:
+  type: NodePort
+  selector:
+    app: blog 
+  ports:
+    - port: 80
+      targetPort: 8000
+      nodePort: 30009

src/content/the_failing_social_media_ban.md

@@ -0,0 +1,53 @@
+Title: The Failing Social Media Ban
+Date: 2025-06-19 20:00
+Modified: 2025-06-20 20:00
+Category: Politics
+Tags: politics, social meda, tech policy
+Slug: social-media-ban-fail
+Authors: Andrew Ridgway
+Summary: The Social Media ban is an abject failure of policy. Education and the use of the much better existing tools is the key
+
+## 🎯 The Goal: A Legal Framework to Protect Kids
+
+The Australian government’s or should I say Julie Inman's plan to ban social media for teens has sparked on going debate. While the intention is noble—protecting minors from online risks—it’s clear the technical and legal hurdles are massive. This government concept of relying on “facial aging” or “Proof of Age” APIs are prone to privacy violations and data breaches, the government should focus on **legal accountability**. Parents already have tools that let them make decisions about their children’s tech use without needing to hand over photos of their ID. The governments current approach is mired in bureaucracy and the tech world does not thrive in that environment. Instead of trying to outsource the problem to consultants, the government should **educate parents on the tools already available**.
+
+## 🧩 The Problem: Tech Giants Won’t Do It
+
+The government’s plan to enable Inman's vision is to use facial recognition or “age-based” filters. This was flawed from the start. These systems are expensive, unreliable, and not designed for the scale of a national rollout. Even if a company like Meta or Google could do it, they’d **never** do it for the same reason: ** There is no money in the equation**. The only alternative is to outsource to consultants, but those consultants are not equipped to handle the complexity. The government’s plan is a joke, no one is going to build a system that’s 100% accurate, secure, and compliant with privacy laws and those that *maybe* could have no insentive to. No amount of chest thumping by The E-Safety Commissioner will change this fact and throwing frankly meaningless pieces of paper from our legislative assembly will do little more than make them laugh
+
+## 🛠️ The Tools Parents Already Have
+
+Parents (Is it parents? is it in fact fiefdom creation on behlaf of Julie Inman?) must give up on the idea of the government fixing this. , parents should be using the **tools already in their homes**. These tools are **free, secure, and effective**. Some examples include (and I use in my own home):
+
+*   **Fritz Box Parental Controls** (https://en.fritz.com/service/knowledge-base/dok/FRITZ-Box-7530/8_Restricting-internet-use-with-the-FRITZ-Box-parental-controls/) - Allows blocking of websites and apps, setting time limits, and creating user profiles.
+*   **Microsoft Family Safety** (https://www.microsoft.com/en-au/microsoft-365/family-safety) - Provides screen time limits, content filters, and activity reporting.
+*   **Nintendo Parental Controls** (https://www.nintendo.com/au/apps/parental-controls/) - Allows managing game time, content restrictions, and communication settings on Nintendo devices.
+*   **Google Family Link** (https://families.google.com/familylink/) - Enables remote monitoring, app management, and location tracking for children's Android devices.
+*   **Apple Family Sharing** (https://support.apple.com/en-au/105121) - Allows sharing purchases, subscriptions, and location information with family members.
+
+These tools let parents **block apps, limit screen time, and monitor online activity** without needing to share sensitive data. They offer parents full control over what is available and are not dependant on some arbitrary list governed in legislation (which is in an of itself an indicator of how backwards this legislation is)
+
+## 📚 The Real Solution: Education, Not Tech
+
+The government’s plan is a **mistake**. Instead of trying to build a new system, parents should be **educating themselves on the tools already available**.
+
+### 🔄 Flexibility for Every Family
+
+*   **Approved apps**
+*   **Blacklisted content**
+*   **Screen time limits**
+*   **Privacy controls**
+
+These tools let parents **make decisions tailored to their children’s needs**. No one-size-fits-all approach. It gives parents autonomy over their online decision making whilst better respecting everyones privacy, including the childs. Already Julie is making calls to expand the list, this is unacceptable, it is no one but MY choice what is acceptable in my house and for my family. 
+
+## 🧩 Why the Government’s Plan Fails
+
+The government’s plan is a **disaster**. It’s not about fixing the problems of social media use in teens, it’s about giving the perception they are doing something about it using archaic methods and tools that don't go to the root cause. The tools parents already have are **better, cheaper, and more secure**. The only way to make this work is for the government to **stop trying to solve a social problem with tech** and **focus on the real solution: education and parental autonomy**. Stop Letting Julie create her cartel and create her own version of the Chinese firewall
+
+## 📝 Summary: The Right Tools, Not the Tech
+
+The government’s plan is a dead monkey. Instead of trying to build a system that’s 100% accurate and secure, parents should be using the **tools already in their homes**. These tools are **free, effective, and preserve privacy**. They let parents **make decisions about their children’s tech use on a true case by case basis** without needing to hand over sensitive data.
+
+## 🧩 Final Thoughts
+
+The Government's plan, at the behest of Julie Inman, is a **disaster**. It’s not about fixing the problem with social media, it’s about creating the perception they are solving a problem that is already solved. Parents should be using the **tools already in their homes**. The real solution is not to expect a government to fix this, but to **educate themselves on the tools that already exist**. Until we accept that this is our responsbility the problem will continue propogate because the only place it can be fixed is in the home.

src/content/when_to_use_ai.md

@@ -1,111 +1,82 @@
-# When to use AI
+Title: When to use AI 
+Date: 2025-06-05 20:00 
+Modified: 2025-06-06 08:00 
+Category: AI, Data 
+Tags: ai, python 
+Slug: when-to-use-ai 
+Authors: Andrew Ridgway 
+Summary: Should we be using AI for ALL THE THINGS!?
 
-A question coming up professionally for me a lot recently is “when to use AI” or put another way, "Why can't AI do this?" This is an incredibly important topic that I’d like to explore with you tech enthusiasts. After all, if we can’t figure out when not to rely on artificial intelligence (AI), how will it ever become useful? Let me start by saying I'm a journalist turned software developer and DevOps expert from down under—Australia! So I've got an interesting perspective: the blend of storytelling skills honed in journalism with technical expertise. And let’s face it, humor is my best friend when explaining tech concepts.
+
+# Human Introduction
+Well.. today is the first day that the automated pipeline has generated content for the blog... still a bit of work to do including
+
+1. establishing a permanent vectordb solution (chromadb? pg_vector?)
+2. Notification to Matrix that something has happened
+3. Updating Trilium so that the note is marked as blog_written=true
+
+BUT it can take a note from trilium, generate drafts with mulitple agents, and then use RAG to have an editor go over those drafts.
+
+I'm particularly proud of the randomness I've applied to temperature, top_p and top_k for the different draft agents. This means that each pass is giving me quite different "creativity" (as much as that can be applied to an algorithm that is essentially munging letters together that have a high probability of being together) It has created some really interesting variation for the editor to work with and getting some really interesting results.
+
+Anyways, without further ado, I present to you the first, pipeline written, AI content for this blog
 
 ---
 
-## Scenarios Where AI Just Isn't Cutting It
+# When to Use AI: Navigating the Right Scenarios
 
-### The Spreadsheet Saga
-Recently I was building a spreadsheet that felt like climbing Mount Everest without oxygen masks—let's call this one the "shudders" project for now (I promise I'll explain later). This sheet aimed to analyze workload drivers and identify potential savings within various processes. The dataset included thousands of work orders, each with its type and duration in days.
+Okay, so I've been getting this question a lot lately: "When should we use AI?" or even more frustratingly, "Why can't AI do this?" It's like asking when to use a hammer versus a screwdriver. Sometimes AI is the perfect tool, other times it's better left in the toolbox. Let me break down some scenarios where AI shines and where it might not be the best bet.
 
-### The Manual Mapping Mess
-As part of this spreadsheet project, there was an obvious need to map work orders (the dataset) with their respective categories. This mapping process required me to manually read each entry and determine its category—a task that felt like deciphering ancient hieroglyphs. Enter the world of Gen AI! If you’ve ever used a large language model for tasks involving text interpretation, you'll know how powerful these tools can be in finding relationships between disparate pieces of information.
+## The Spreadsheet Dilemma: Where AI Can help, and where it hurts
 
-However, this was not an ideal scenario to deploy such technology:
-1. **Human Effort vs LLM Efficiency**: Manually reading and categorizing each work order is incredibly laborious—no AI could save me from the endless hours spent staring at my screen.
-2. **Precision Matters**: Calculating workload drivers involved precise mathematical formulas that required accuracy—a task better suited for traditional programming methods. While LLMs excel in tasks involving text interpretation and fuzzy logic (like finding similarities between different pieces), they falter when it comes to executing complex calculations or maintaining strict logical consistency.
+**Scenario:** Mapping work types to categories in a spreadsheet with thousands of entries, like distinguishing between "Painting," "Repainting," "Deck Painting," or "Stucco Repainting."
 
-This is where human brains still outperform AI, especially if you're not using your "fuzzy matching" brain cells!
+**Where AI Helps:**
 
----
+*   **Fuzzy Matching & Contextual Understanding:** AI excels at interpreting relationships between words (e.g., recognizing "Deck Painting" as a subset of "Painting"). However, traditional methods with regex or string manipulation fail here because they lack the nuanced judgment needed to handle ambiguity.
 
-## Scenarios Where AI Shines Brightly
+**Where AI Struggles:** 
 
-### The Text Interpretation Triumph
-Imagine you have a dataset of customer reviews and need insights into common themes—this could be an ideal task for Gen AI! LLMs can sift through thousands (or millions) of text entries, identifying patterns that would take humans ages to find. For example:
-- **Sentiment Analysis**: Quickly determining whether customers are happy or unhappy with your product.
-- **Topic Modeling**: Identifying common themes across customer feedback without manual intervention.
+*   **Precision Over Ambiguity:** Calculations requiring exact values (e.g., average durations) are better handled by deterministic algorithms rather than AI’s probabilistic approach.
 
-### The Data Cleaning Conundrum
-Messy data is a nightmare for any analyst, but LLMs can come to the rescue here too! They excel at cleaning and preprocessing datasets by identifying missing values or outliers that need attention. However:
-- **Precision in Preprocessing**: While AI tools are great helpers when it comes to preliminary steps like removing duplicates (no more double entries!), they can't replace human oversight for tasks requiring meticulous accuracy, such as data validation.
+**Traditional Methods Are Easier for Deterministic Problems:**
 
----
+*   **Formula-Based Logic:** Building precise formulas for workload analysis relies on clear, unambiguous rules. AI can’t replace the need for human oversight in such cases.
 
-## The Bottom Line
+## When AI Shines: Contextual and Unstructured Tasks
 
-AI is a powerful tool with its own set of strengths and weaknesses. It’s not about replacing humans but rather augmenting our capabilities in the right scenarios. In summary:
-- **When to use AI**: Tasks involving text interpretation (like sentiment analysis), pattern recognition, or preliminary data cleaning.
-- **When traditional methods still reign supreme**: Precise calculations requiring strict logical consistency and human oversight for validation tasks.
+**Scenario:** Automating customer support with chatbots or analyzing social media sentiment.
 
-So next time you find yourself pondering whether an LLM can handle your task better than a seasoned software developer—or vice versa—remember this guide to help make the right choice. Cheers, mate! Happy coding (and not-so-happy spreadsheeting)! 🚀
+**Why AI Works Here:**
 
----
+*   **Natural Language Processing (NLP):** AI understands context, tone, and intent in unstructured data, making it ideal for tasks like chatbot responses or content analysis.
+*   **Pattern Recognition:** AI identifies trends or anomalies in large datasets that humans might miss, such as predictive maintenance in industrial settings.
 
-**Edit notes:**  
-- Use bold for headings, italics for emphasis.  
-- Keep paragraphs short for readability.  
-- Add humor and relatable examples.  
-- Avoid code examples, focus on scenarios and reasoning.  
+**Why Traditional Methods Don't:**
 
-Feel free to edit or tweak any part of my draft as needed. After all, what’s tech writing without some collaboration? Let's get those edits rolling! 🎉
+* **There is no easily discernable pattern:** If the pattern doesn't exist in a deterministic sense there will be little someone can do without complex regex and 'whack a mole' style programming. 
 
-<|end_of_thought|>
+## Hybrid Approaches: The Future of Efficiency
 
-<|begin_of_solution|>
+While traditional methods remain superior for precise calculations, AI can assist in setting up initial parameters or generating insights. For example:
 
-# When to use AI
+*   **AI Proposes Formulas:** An LLM suggests a workload calculation formula based on historical data.
+*   **Human Checks Validity:** A human ensures the formula’s accuracy before deployment.
 
-A question coming up professionally for me a lot recently is “when to use AI” or put another way, "Why can't AI do this?" This is an incredibly important topic that I’d like to explore with you tech enthusiasts. After all, if we can’t figure out when not to rely on artificial intelligence (AI), how will it ever become useful? Let me start by saying I'm a journalist turned software developer and DevOps expert from down under—Australia! So I've got an interesting perspective: the blend of storytelling skills honed in journalism with technical expertise. And let’s face it, humor is my best friend when explaining tech concepts.
+## Key Takeaways
 
----
+1.  **Use AI** for tasks involving:
+    *   Unstructured data (e.g., text, images).
+    *   Contextual understanding and interpretation.
+    *   Pattern recognition and trend analysis.
+2.  **Stick to Traditional Methods** for:
+    *   Precise calculations with deterministic logic.
+    *   Tasks requiring error-free accuracy (e.g., financial modeling).
 
-## Scenarios Where AI Just Isn't Cutting It
+## Conclusion
 
-### The Spreadsheet Saga
-Recently I was building a spreadsheet that felt like climbing Mount Everest without oxygen masks—let's call this one the "shudders" project for now (I promise I'll explain later). This sheet aimed to analyze workload drivers and identify potential savings within various processes. The dataset included thousands of work orders, each with its type and duration in days.
+AI is a powerful tool but isn’t a one-size-fits-all solution. Match the right approach to the task at hand—whether it’s interpreting natural language or crunching numbers. The key is knowing when AI complements human expertise rather than replaces it.
 
-### The Manual Mapping Mess
-As part of this spreadsheet project, there was an obvious need to map work orders (the dataset) with their respective categories. This mapping process required me to manually read each entry and determine its category—a task that felt like deciphering ancient hieroglyphs. Enter the world of Gen AI! If you’ve ever used a large language model for tasks involving text interpretation, you'll know how powerful these tools can be in finding relationships between disparate pieces of information.
+**Final Tip:** Always consider the trade-offs between precision and context. For tasks where nuance matters, AI is your ally; for rigid logic, trust traditional methods.
 
-However, this was not an ideal scenario to deploy such technology:
-1. **Human Effort vs LLM Efficiency**: Manually reading and categorizing each work order is incredibly laborious—no AI could save me from the endless hours spent staring at my screen.
-2. **Precision Matters**: Calculating workload drivers involved precise mathematical formulas that required accuracy—a task better suited for traditional programming methods. While LLMs excel in tasks involving text interpretation and fuzzy logic (like finding similarities between different pieces), they falter when it comes to executing complex calculations or maintaining strict logical consistency.
-
-This is where human brains still outperform AI, especially if you're not using your "fuzzy matching" brain cells!
-
----
-
-## Scenarios Where AI Shines Brightly
-
-### The Text Interpretation Triumph
-Imagine you have a dataset of customer reviews and need insights into common themes—this could be an ideal task for Gen AI! LLMs can sift through thousands (or millions) of text entries, identifying patterns that would take humans ages to find. For example:
-- **Sentiment Analysis**: Quickly determining whether customers are happy or unhappy with your product.
-- **Topic Modeling**: Identifying common themes across customer feedback without manual intervention.
-
-### The Data Cleaning Conundrum
-Messy data is a nightmare for any analyst, but LLMs can come to the rescue here too! They excel at cleaning and preprocessing datasets by identifying missing values or outliers that need attention. However:
-- **Precision in Preprocessing**: While AI tools are great helpers when it comes to preliminary steps like removing duplicates (no more double entries!), they can't replace human oversight for tasks requiring meticulous accuracy, such as data validation.
-
----
-
-## The Bottom Line
-
-AI is a powerful tool with its own set of strengths and weaknesses. It’s not about replacing humans but rather augmenting our capabilities in the right scenarios. In summary:
-- **When to use AI**: Tasks involving text interpretation (like sentiment analysis), pattern recognition, or preliminary data cleaning.
-- **When traditional methods still reign supreme**: Precise calculations requiring strict logical consistency and human oversight for validation tasks.
-
-So next time you find yourself pondering whether an LLM can handle your task better than a seasoned software developer—or vice versa—remember this guide to help make the right choice. Cheers, mate! Happy coding (and not-so-happy spreadsheeting)! 🚀
-
----
-
-**Edit notes:**  
-- Use bold for headings, italics for emphasis.  
-- Keep paragraphs short for readability.  
-- Add humor and relatable examples.  
-- Avoid code examples, focus on scenarios and reasoning.  
-
-Feel free to edit or tweak any part of my draft as needed. After all, what’s tech writing without some collaboration? Let's get those edits rolling! 🎉
-
-<|end_of_solution|>
+🚀