Add metadata

Add pelican Metadata

.gitea/workflows/build_push.yml

@@ -1,61 +1,72 @@
 name: Build and Push Image
 on:
-    push:
+  push:
-        branches:
+    branches:
-            - master
+      - master
 
 jobs:
-    build:
+  build:
-        name: Build and push image
+    name: Build and push image
-        runs-on: ubuntu-latest
+    runs-on: ubuntu-latest
-        container: catthehacker/ubuntu:act-latest
+    container: catthehacker/ubuntu:act-latest
-        if: gitea.ref == 'refs/heads/master'
+    if: gitea.ref == 'refs/heads/master'
 
-        steps:
+    steps:
-            - name: Checkout
+      - name: Checkout
-              uses: actions/checkout@v4
+        uses: actions/checkout@v4
 
-            - name: Create Kubeconfig
+      - name: Create Kubeconfig
-              run: |
+        run: |
-                  mkdir $HOME/.kube
+          mkdir $HOME/.kube
-                  echo "${{ secrets.KUBEC_CONFIG_BUILDX_NEW }}" > $HOME/.kube/config
+          echo "${{ secrets.KUBEC_CONFIG_BUILDX_NEW }}" > $HOME/.kube/config
 
-            - name: Set up Docker Buildx
+      - name: Set up Docker Buildx
-              uses: docker/setup-buildx-action@v3
+        uses: docker/setup-buildx-action@v3
-              with:
+        with:
-                  driver: kubernetes
+          driver: kubernetes
-                  driver-opts: |
+          driver-opts: |
-                      namespace=gitea-runner
+            namespace=gitea-runner
-                      qemu.install=true
+            qemu.install=true
 
-            - name: Login to Docker Registry
+      - name: Login to Docker Registry
-              uses: docker/login-action@v3
+        uses: docker/login-action@v3
-              with:
+        with:
-                  registry: git.aridgwayweb.com
+          registry: git.aridgwayweb.com
-                  username: armistace
+          username: armistace
-                  password: ${{ secrets.REG_PASSWORD }}
+          password: ${{ secrets.REG_PASSWORD }}
 
-            - name: Build and push
+      - name: Build and push
-              uses: docker/build-push-action@v5
+        uses: docker/build-push-action@v5
-              with:
+        with:
-                  context: .
+          context: .
-                  push: true
+          push: true
-                  platforms: linux/amd64,linux/arm64
+          platforms: linux/amd64,linux/arm64
-                  tags: |
+          tags: |
-                      git.aridgwayweb.com/armistace/blog:latest
+            git.aridgwayweb.com/armistace/blog:latest
 
-            - name: Deploy
+      - name: Trivy Scan
-              run: |
+        run: |
-                  echo "Installing Kubectl"
+          echo "Installing Trivy "
-                  apt-get update
+          sudo apt-get update
-                  apt-get install -y apt-transport-https ca-certificates curl gnupg
+          sudo apt-get install wget apt-transport-https gnupg lsb-release
-                  curl -fsSL https://pkgs.k8s.io/core:/stable:/v1.33/deb/Release.key | gpg --dearmor -o /etc/apt/keyrings/kubernetes-apt-keyring.gpg
+          wget -qO - https://aquasecurity.github.io/trivy-repo/deb/public.key | sudo apt-key add -
-                  chmod 644 /etc/apt/keyrings/kubernetes-apt-keyring.gpg
+          echo deb https://aquasecurity.github.io/trivy-repo/deb $(lsb_release -sc) main | sudo tee -a /etc/apt/sources.list.d/trivy.list
-                  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
+          sudo apt-get update
-                  chmod 644 /etc/apt/sources.list.d/kubernetes.list
+          sudo apt-get install trivy
-                  apt-get update
+          trivy image --format table --exit-code 1 --ignore-unfixed --vuln-type os,library --severity HIGH,CRITICAL git.aridgwayweb.com/armistace/blog:latest
-                  apt-get install kubectl
+
-                  kubectl delete namespace blog
+      - name: Deploy
-                  kubectl create namespace blog
+        run: |
-                  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
+          echo "Installing Kubectl"
-                  kubectl apply -f kube/blog_pod.yaml && kubectl apply -f kube/blog_deployment.yaml && kubectl apply -f kube/blog_service.yaml
+          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

\

@@ -0,0 +1,22 @@
+[core]
+	repositoryformatversion = 0
+	filemode = true
+	bare = false
+	logallrefupdates = true
+[remote "origin"]
+	url = gitea@192.168.178.155:armistace/blog.git
+	fetch = +refs/heads/*:refs/remotes/origin/*
+[branch "master"]
+	remote = origin
+	merge = refs/heads/master
+[branch "kube_deployment"]
+	remote = origin
+	merge = refs/heads/kube_deployment
+[branch "when_to_use_ai"]
+	remote = origin
+	merge = refs/heads/when_to_use_ai
+[pull]
+	rebase = false
+[branch "an_actual_solution_to_the_social_media_ban"]
+	remote = origin
+	merge = refs/heads/an_actual_solution_to_the_social_media_ban

src/content/an_actual_solution_to_the_social_media_ban.md

@@ -11,34 +11,42 @@ Summary: The Social Media ban is an abject failure of policy. I propose an actua
 
 The Australian Government recently announced it would be “watering down” the requirements of the upcoming legislation regarding online safety. The irony isn’t lost on anyone observing the situation. Specifically, the planned mandatory minimum “flag rate” for underage detection technology has been dropped – a clear indication that initial testing proved unachievable. Furthermore, the legislation now only requires tech companies to demonstrate “reasonable steps” to remove children from their platforms.
 
-Let’s be frank: this legislation, as it stands, achieves very little. Experts in the field consistently warned that the approach was flawed and ignored industry input. The result? Parents are arguably in a worse position than before. The focus on punitive measures, rather than practical solutions, has been a misstep, and the relentless pursuit of this agenda by the eSafety Commissioner feels increasingly disconnected from reality.
+Let’s be frank: this legislation, as it stands, achieves very little. Experts in the field consistently warned that the proposed age verification approach was flawed and ignored industry input. The result? Parents are arguably in a worse position than before. The focus on punitive measures, rather than practical solutions, has been a misstep, and the relentless pursuit of this agenda by the eSafety Commissioner feels increasingly disconnected from reality.
 
-It’s important to state that criticism of this legislation isn’t an endorsement of big tech. While I’m actively working to reduce my own reliance on these platforms, this situation was never about punishing companies. It was about the Australian Government overreaching in an area where it lacks the necessary expertise and, frankly, the authority. The driving force behind this appears to be a personal vendetta, fuelled by someone unfamiliar with the fundamental principles of how the internet operates.
+It’s important to state that criticism of this legislation isn’t an endorsement of big tech, in fact I’m actively working to reduce my own reliance on these platforms. It is about the Australian Government overreaching in an area where it lacks the necessary expertise and, frankly, the authority. The driving force behind this appears to be a personal vendetta, fuelled by someone unfamiliar with the fundamental principles of how the internet operates.
 
 So, with the current legislation effectively neutered, what *can* the government do to genuinely help parents navigate the challenges of online safety? I believe there’s a technically feasible solution that doesn’t involve trampling on privacy or creating massive security vulnerabilities.
 
 The answer lies in a system we’ve been using for decades: the Domain Name System (DNS). Simply put, DNS translates human-readable URLs like [https://blog.aridgwayweb.com](https://blog.aridgwayweb.com) into the corresponding IP address (e.g., x.x.x.x). It’s a foundational component of the internet, and while seemingly simple, it’s incredibly powerful.
 
+## What is DNS?
+
 Most people rely on the DNS provided by their Internet Service Provider (ISP) or the manufacturer of their router. However, it’s possible to change this setting. Popular alternatives include Cloudflare’s 1.1.1.1, Google’s 8.8.8.8, and paid family-friendly options like OpenDNS. For those with more technical expertise, it’s even possible to run your own DNS server – I personally use Pi-hole to block ads at the network level.
 
-This existing infrastructure offers a unique opportunity. The Chinese government has long leveraged DNS for its “Great Firewall,” demonstrating its capability for large-scale internet control. While that application raises obvious concerns, the underlying technology itself isn’t inherently malicious.
+This existing infrastructure offers a unique opportunity. The Chinese government has long leveraged DNS as part of its “Great Firewall,” demonstrating its capability for large-scale internet censorship and control. While that application raises obvious concerns, the underlying technology itself isn’t inherently malicious and is a good fit for the purposes of *opt in* age verification.
 
 <img alt="Current DNS" height="auto" width="100%" src="{attach}/images/dns_currently.png">
 
+## How can we leverage DNS for age verification?
+
 My proposal is straightforward: the Australian Government could establish a large-scale DNS server within the Communications Department. This server could be configured to redirect requests to specific websites – like Facebook or TikTok – to an internal service that requires some form of authentication or identity verification. Once verified, the request would then be forwarded to the correct IP address.
 
 <img alt="Optional Government DNS" height="auto" width="100%" src="{attach}/images/optional_gov_dns.png">
 
 This DNS server could be *optionally* configured on any router, with ISPs assisting less technically inclined customers. The result? Access to certain websites from that router would require passing through the government’s age verification process.
 
-The authentication could be managed by an adult in the household, providing a valid identity document to establish a secure connection. Mobile phones could also be updated by manufacturers to incorporate this DNS setting.
+The authentication could be managed by an adult in the household, providing a valid identity document to receive some form of auth mechanism (password? passkey? authenticator?) to allow the user to continue to their 'restricted' website.
 
-This would allow for the creation of “Government-certified” or “Family-Friendly” devices – routers or phones pre-configured with this DNS server – ensuring a consistent level of online safety. These devices could be subsidised by the government to ensure accessibility for all families.
+Mobile phones could also have the internal DNS updated by manufacturers to incorporate this DNS setting.
 
-Crucially, this system is optional. Individuals who prefer to manage their own online security – as I do – would remain unaffected. However, for parents who lack the technical skills or desire to implement their own solutions, this offers a practical and effective alternative.
+This would allow for the creation of “Government-certified” or “Family-Friendly” devices – routers or phones pre-configured with this DNS server – ensuring a consistent level of online safety as defined by the Australian Government. These devices could be subsidised by the government to ensure accessibility for all families.
+
+Crucially, this system is optional. Individuals who prefer to manage their own online security – as I do – would remain unaffected. However, for parents who lack the technical skills or desire to implement their own solutions, this offers a practical and effective alternative to managing their child’s online safety.
 
 This approach also avoids the need to collect and store sensitive identity data offshore. No tech company needs to be involved in the verification process, and the skills to build and maintain this system already exist within the Australian public service.
 
 Furthermore, the eSafety Commissioner could easily update the list of websites subject to verification, providing a flexible and responsive system. It wouldn’t cover the entire internet, of course, but it would provide a valuable safety net for those who need it.
 
+## Where to from here?
+
 Now that the government has acknowledged the shortcomings of its initial approach, it’s time to explore real solutions. A government-run, family-friendly DNS system that routes certain domain names to a verification process is a solid starting point for a genuinely effective technical solution to help families navigate the online world.

src/content/google_ai_is_rising.md

@@ -0,0 +1,31 @@
+Title: Google AI is Rising
+Date: 2025-12-21 20:00
+Modified: 2025-12-23 10:00
+Category: AI
+Tags: AI, Google, Tech
+Slug: google-ai-is-rising
+Authors: Andrew Ridgway
+Summary: After a period of seeming hesitation, one tech giant is now a serious contender in the AI race. Leveraging its massive and uniquely personal datasets – gleaned from widely used services like search, email, and calendars – it’s releasing models that are quickly challenging existing benchmarks. This arrival is significant, creating a more competitive landscape and potentially pushing innovation forward. However, it also highlights crucial privacy concerns given the depth of data access. The company’s recent open-source contributions suggest a multifaceted approach, but users should be mindful of data control and consider diversifying their digital footprint.
+
+# Google AI is Rising
+
+The landscape of Artificial Intelligence is shifting, and a familiar name is finally asserting its dominance. For a while there, it felt like Google was… well, lagging. Given the sheer volume of data at its disposal, it was a surprise to many that they weren’t leading the charge in Large Language Models (LLMs). But the moment appears to have arrived. Google seems to have navigated its internal complexities and is now delivering models that are genuinely competitive, and in some cases, surpassing the current benchmarks.
+
+The key to understanding Google’s potential lies in the data they’ve accumulated. Consider the services we willingly integrate into our daily lives: email through Gmail, scheduling with Google Calendar, advertising interactions, and of course, the ubiquitous Google Search. Crucially, we provide this data willingly, often tied to a single Google account. This isn’t just a large dataset; it’s a *targeted* dataset, offering an unprecedented level of insight into individual behaviours and preferences. 
+
+This data advantage is now manifesting in the performance of Gemini, Google’s latest LLM. Recent discussions within the tech community – on platforms like [Hacker News](https://news.ycombinator.com/item?id=46301851) and [Reddit](https://www.reddit.com/r/singularity/comments/1p8sd2g/experiences_with_chatgpt51_vs_gemini_3_pro/) and [Reddit](https://www.reddit.com/r/GeminiAI/comments/1p953al/gemini_seems_to_officially_be_better_than_chatgpt/) – suggest Gemini is rapidly gaining ground, and in some instances, exceeding the capabilities of established models.
+
+Google’s history is one of immense scale and profitability, exceeding the GDP of many nations. This success, however, has inevitably led to the creation of large, protective bureaucracies. While necessary for safeguarding revenue streams, these structures can stifle innovation and slow down decision-making. Ideas often have to navigate multiple layers of management, sometimes overseen by individuals whose expertise lies in business administration rather than the intricacies of neural networks and algorithmic functions.
+
+The arrival of a truly competitive Google model is a significant development. OpenAI, previously considered the frontrunner, now faces a formidable challenge.  Furthermore, Anthropic is gaining traction amongst developers, with many preferring their models for coding assistance. This shift suggests a growing demand for tools tailored to specific professional needs.
+
+It’s important to acknowledge that neither Google nor OpenAI are inherently benevolent entities. However, with Google now fully engaged in the LLM race, the potential implications are considerable. Gemini’s access to deeply personal data – email content, calendar events, even metadata – raises legitimate privacy concerns.  It’s a sobering thought to consider the extent of data visibility Google possesses, particularly when we don’t directly own the services we use. This reality strengthens the argument for greater data control and the exploration of self-hosted alternatives.
+
+Google’s commitment to open-source initiatives, demonstrated through the release of the Gemma models (which, incidentally, powered the creation of this very blog), signals a broader strategy.  The technology is here, it’s evolving rapidly, and its influence will only continue to grow.  
+
+While complete resistance may be unrealistic, individuals can take steps to mitigate potential risks. Fragmenting your data across different services, diversifying email providers, and avoiding single sign-on (SSO) with Google are all proactive measures that can help reclaim a sense of control.  (Though, let’s be honest, anyone still using Chrome is already operating within a highly monitored ecosystem.)
+
+The future of AI is unfolding quickly, and Google is now a major player. It’s a development that warrants careful consideration, and a renewed focus on data privacy and digital autonomy.
+
+
+