Forem: Ebikara Spiff ᴀɪᴄᴍᴄ

10 Ways Loan Apps Can Be Unfair Without Meaning To.

Ebikara Spiff ᴀɪᴄᴍᴄ — Thu, 07 May 2026 15:48:30 +0000

A market trader in Lagos and a banker in London may both be financially responsible.

But an automated lending system could still treat one of them as “riskier” before either person ever speaks to a human being.

That is one of the hidden problems with AI-driven lending systems.

Many digital loan platforms now use automated models to help decide:

who gets approved
who gets rejected
who receives higher interest rates
who qualifies for larger loans

These systems are often designed to improve speed, reduce fraud, and predict repayment risk.

But fairness becomes complicated when AI systems are trained on incomplete, biased, or poorly contextualized data.

And in countries like Nigeria, where millions of people work outside highly formal financial systems, this problem becomes even more important.

Not all lenders use the same methods, and not all digital lenders rely heavily on AI. However, alternative data scoring and automated risk analysis have become increasingly common in digital lending.

Here are some ways unfairness can quietly appear.

1. Location Can Become a Proxy for Financial Risk

Some credit models use location-related signals during risk assessment.

The problem is that location can become a proxy variable.

A proxy variable is when a system uses one signal to indirectly estimate something else.

For example, if historical repayment data shows higher default rates in certain areas, a model may begin associating those locations with elevated risk.

This can create problems for responsible individuals living in those same areas.

The system may be statistically optimized, yet still produce unfair outcomes for specific groups of people.

2. Limited Banking History Can Reduce Financial Visibility

Many automated lending systems rely heavily on formal financial records.

People with:

long banking histories
regular salary payments
stable employment records

often appear less risky to predictive models.

But millions of Nigerians earn money differently.

Some people:

run cash businesses
work informal jobs
combine multiple income sources
use cooperative savings groups instead of traditional banking systems

A person with limited formal banking data is not automatically financially irresponsible.

The issue is that AI systems can struggle when they are designed mainly around highly digitized financial behavior.

3. Device Type Can Influence Predictive Models

Some digital lenders experiment with device metadata as part of alternative credit scoring.

This may include signals related to:

device age
operating system
phone model
device stability

In some cases, these variables may statistically correlate with repayment patterns or purchasing power.

But predictive correlation is not the same thing as fairness.

A responsible borrower using an older phone could still be financially reliable, while a person using an expensive device may still struggle financially.

This is one reason why technically accurate predictions can still create ethical concerns.

4. Contact Data Raises Serious Ethical Questions

Some lenders have historically collected contact data for purposes such as debt recovery, identity verification, or behavioral analysis.

This has raised concerns around:

privacy
consent
proportionality
relevance of data collection

Importantly, collecting contact data does not automatically mean it is directly used in machine learning models.

However, large-scale collection of highly personal information can still create ethical and regulatory concerns, especially when users do not fully understand how their data is being used.

5. Behavioral Data Can Be Misinterpreted

Some digital lending systems experiment with behavioral and device metadata as part of risk analysis.

Examples may include:

app activity
device usage patterns
digital engagement behavior
account stability signals

The challenge is that human behavior is highly contextual.

A student, trader, freelancer, remote worker, or night-shift employee may all use technology differently for perfectly legitimate reasons.

Without sufficient local context, predictive systems may incorrectly interpret normal behavior as elevated risk.

6. Younger Borrowers May Face Structural Disadvantages

Some predictive systems associate younger age groups with higher uncertainty because younger users often have shorter credit histories.

This can make it harder for financially responsible young adults to build credibility within formal lending systems.

The problem is not necessarily direct discrimination.

Often, the system is simply learning historical patterns from existing financial data.

But historical patterns do not always represent fair opportunity.

7. Historical Data Can Reproduce Existing Inequality

Machine learning systems learn from historical data.

If previous lending decisions already reflected unequal access, exclusion, or structural bias, AI systems may unintentionally reproduce those same patterns at scale.

This is one of the most widely discussed concerns in AI fairness research.

Importantly, this does not require malicious intent.

A model can still produce unfair outcomes even when developers believe they are building a neutral system.

8. Existing Borrowers Often Have an Advantage

People with established financial records are generally easier for systems to evaluate.

Meanwhile, first-time borrowers may have very limited digital financial history available.

This can create a cycle where:

financially visible users become easier to trust
financially invisible users remain difficult to assess

Over time, this can widen financial inclusion gaps rather than reduce them.

9. AI Systems Can Misunderstand Informal Economies

Many predictive financial systems are built around assumptions common in highly formal economies.

Examples include:

stable monthly salaries
fixed residential addresses
continuous banking activity
extensive digital financial records

But millions of Nigerians operate within informal economic systems.

This includes:

market traders
artisans
rural entrepreneurs
freelancers
small cash-based business owners

Imagine two traders earning similar income levels.

One regularly uses digital banking apps and owns a newer smartphone.

The other mainly operates in cash, shares devices with family members, and has limited digital records.

An automated system trained heavily on digital behavioral data may incorrectly treat the second trader as riskier, even if both individuals are equally capable of repayment.

This is one reason localization matters in AI system design.

10. Digital Behavior Is Not Universal

Behavioral prediction systems rely on patterns.

But patterns are influenced by:

culture
infrastructure
internet access
electricity stability
work conditions
shared technology usage

A system trained mainly on users from one environment may perform poorly when applied to populations living under very different social and economic conditions.

This is not only a technical issue.

It is also a contextual one.

Why This Matters Beyond Technology

Automated lending systems can influence:

access to credit
entrepreneurship
business growth
financial inclusion
economic opportunity

Because these systems operate at scale, even small design flaws can affect large numbers of people.

The issue is not that AI is automatically harmful.

The issue is that predictive systems can produce unfair outcomes when they are built without enough understanding of the people they are evaluating.

What Developers and Fintech Teams Should Consider

Better systems are possible.

Some important safeguards include:

Audit training data regularly

Check whether certain communities are being unfairly excluded or misrepresented.

Reduce dependence on weak proxy variables

Not every statistically useful signal should influence financial decisions.

Include local economic realities

Systems designed for African users should reflect African financial behavior, not only Western financial assumptions.

Allow human review and appeals

Users should have meaningful ways to challenge automated decisions.

Improve transparency

People deserve understandable explanations for important financial outcomes.

Test systems across different populations

A model that performs well in one environment may fail badly in another.

My Final Thought On This

One of the biggest risks in AI is not always intentional discrimination.

Sometimes the bigger problem is systems built without enough understanding of the people they affect.

And when those systems influence access to money, opportunity, and financial survival, fairness stops being only a technical discussion.

It becomes a social one.

Which global AI principles fail in weak-regulation countries like Nigeria and why ?

Ebikara Spiff ᴀɪᴄᴍᴄ — Sun, 03 May 2026 17:39:07 +0000

AI is being “regulated” on paper. But in reality? It is operating in the dark.

Global AI frameworks from the OECD, UNESCO, and the World Economic Forum promise a future built on:

Transparency
Accountability
Human oversight
Risk-based regulation

It sounds solid and reassuring.

But the uncomfortable truth is These principles start to break the moment they hit environments like Nigeria.

⚠️ Transparency: The Promise That Rarely Shows Up

You are told AI systems should be explainable.

But let's imagine this:

You apply for a digital loan.
You get rejected.
You get no explanation, clarity or appeal.

Just a silent algorithm.

Now in theory, transparency means you deserve to know why.
But in practice, companies protect their models and data because that’s their competitive advantage.

And without strong AI regulation in Nigeria forcing disclosure then Transparency becomes optional and optional transparency is no transparency at all.

⚠️ Accountability: When Harm Has No Owner

Now let’s go a little deeper.

An AI system flags you incorrectly or worse, financially excludes you.

Who takes responsibility? is it :

The developer?
The company?
The data provider?

In strong regulatory systems, this question has answers.

But in many African markets, including Nigeria, AI accountability struggles because:

Enforcement is weak
Responsibility is blurred
Legal consequences are inconsistent

So when harm happens, it doesn’t just hurt.

It disappears into the system, unanswered and unresolved.

⚠️ The Real Problem: Imported Principles, Local Reality

Here’s what most people miss:

Global AI governance frameworks were designed for countries with:

Strong institutions
Active regulators
Enforceable legal systems

Now apply that same model to fast-growing ecosystems like:

Fintech
Digital lending
Automated decision systems

What do you get? A dangerous illusion.

On paper → Responsible AI exists
In practice → Oversight is weak or missing

🚨 The Risk No One Is Talking About

This is not just a policy gap. It’s actually a trust gap.

And in places like my country Nigeria, where millions rely on digital financial tools daily, this gap can:

Exclude people unfairly
Reinforce hidden bias
Scale harm faster than regulation can catch up

AI is not just scaling innovation. It is scaling decisions about people’s lives.

💡 The Way Forward

If we’re serious about ethical AI in Africa, we must move beyond copying global principles.

We need:

Context-aware AI regulation in Nigeria
Stronger enforcement, not just guidelines
Clear accountability frameworks for AI systems
Real transparency that users can actually understand

Because without this, then “Responsible AI” will remain a well-written promise and not a lived reality.

The real question is:
Are we building AI systems people can trust…
or systems they are forced to accept?

The Sovereign Safety Gap: Why AI Alignment Must be Contextual.

Ebikara Spiff ᴀɪᴄᴍᴄ — Sat, 02 May 2026 21:52:31 +0000

As the global community converges on London and Washington to debate the existential risks of frontier AI, a dangerous assumption has taken root: that AI safety is a universal constant.

The prevailing belief is that if a model is "aligned" in a lab in San Francisco or London, it is safe for the rest of the world. My experience as a Systems Engineer and AI governance practitioner in Nigeria suggests otherwise.

We are currently facing a "Socio-Technical Gap" that threatens to undermine global alignment efforts, leaving emerging markets as the "blind spots" of AI safety.

The Engineering Lens: From Chemical Plants to Neural Networks
My perspective is shaped by my background in Chemical Engineering. In industrial safety, we rely on the "Precautionary Principle."
When designing a chemical plant, we don’t assume a system is safe because it passed a simulation; we conduct rigorous Hazard and Operability (HAZOP) studies to identify site-specific failure modes.We understand that a system’s stability is inseparable from its environment.

AI safety currently lacks this industrial rigor. We are deploying frontier models, systems of immense complexity and potential volatility, without the "contextual pressure valves" necessary to ensure they remain aligned when they hit diverse, real-world data environments.
I view model auditing not as a bureaucratic hurdle, but as a critical engineering fail-safe.

The Problem: Safety Degradation and "Safety Dumping"
Current safety benchmarks, such as MMLU or TruthfulQA, are overwhelmingly Western-centric.
They test for bias, truthfulness, and refusal behaviors within a narrow cultural and linguistic corridor.
However, safety is not a static property of the weights and biases of a model; it is a dynamic interaction between the model and the user’s context.

Through my work on the Governly AI Policy Map, which tracks regulatory readiness across 54 nations, I have observed a phenomenon I call "Safety Degradation." In my preliminary analysis, I found that while 54 nations are rushing to adopt AI, fewer than 5% have the technical infrastructure required to verify the safety claims of the models they are importing.

When frontier models are prompted in regional dialects (such as Nigerian Pidgin) or within local socio-economic scenarios, standard RLHF filters often degrade.

This leads to "safety dumping," where models are deployed in non-Western markets with a fraction of the contextual testing required to ensure robustness. If a model is misaligned in Lagos, the global system is not safe.

A Proposal for Technical Governance: Contextual Red-Teaming
To bridge this gap, we must move beyond high-level policy and into verifiable technical governance. I propose the adoption of Mandatory Contextual Red-Teaming Reports (CRRs) for international AI deployment.

A CRR should not just be a narrative report; it must include quantitative benchmarks comparing refusal rates across different linguistic dialects and socio-economic prompts to identify specific failure modes.

By making these reports a prerequisite for a "License to Operate," governments can force companies to move from generic "System Cards" to verifiable, contextual alignment. This empowers "Middle Powers" to use their market access as a lever to force a race to the top in safety standards.

Conclusion: Toward Truly Global Alignment. If the goal of AI Safety is to prevent catastrophic misalignment, then that safety must be inclusive. We cannot claim to have solved the alignment problem if our models are only aligned with a fraction of the human population.

I seek to use the Pivotal Research Fellowship to transform these high-level frameworks into a technical "safety toolkit" that can be piloted within the UK’s research ecosystem.

By integrating Systems Engineering rigor with context-aware governance, we can ensure that frontier AI remains a tool for empowerment rather than a source of global instability.

Why an Accurate Loan Model Can Still Be Unfair in Nigeria

Ebikara Spiff ᴀɪᴄᴍᴄ — Mon, 06 Apr 2026 09:08:19 +0000

A loan model can be 95% accurate and still be unfair in Nigeria.

AI loan systems make decisions using patterns from historical data.

They look at things like:

➖ transaction history

➖ location

➖ phone activity

➖ financial behaviour

On paper, this works pretty well.

But the problem is Many Nigerians are invisible in that data.

👉 The informal workers.
👉 The unbanked individuals.
👉 People operating in cash-based systems.

Take a skilled carpenter who gets paid mostly in cash for example

He has no strong transaction history. No formal credit trail.

To the model?

That looks like risk.

But in reality, it’s just missing data.

It gets more subtle.

Location also can quietly influence outcomes.

Someone from a high-activity area like Lagos Island may be favored over someone from the mainland, not because they’re more creditworthy, but because of patterns in the data.

This is how bias hides.

The model can be highly accurate overall…

While consistently failing certain groups.

Accuracy isn’t the problem.

Representation is.

If the data is incomplete, the decisions will be too.

Not What AI Does, But How It Decides: Anthropic’s Claude Constitution Explained.

Ebikara Spiff ᴀɪᴄᴍᴄ — Sun, 25 Jan 2026 20:21:43 +0000

I didn’t really understand why enterprises care so much about AI governance until I saw what Anthropic just did with Claude.

In 2023, Claude had a constitution.
Basically: a long list of rules telling the model what not to do.

It worked.
But rules break when reality gets messy.

So on Jan 21, Anthropic rewrote the whole thing.

This new Claude Constitution isn’t just rules anymore.
It’s principles.

A 4-tier priority system around safety, ethics, compliance, and usefulness and more importantly, why those rules exist.

That shift matters.

Because enterprises already assume something most people don’t want to say out loud:
Every AI model has bias.
It’s shaped by training data and the values baked into it.

Anthropic isn’t pretending otherwise.
They’re saying: this is how our model reasons when things get weird.

And things will get weird.

Especially in enterprise use cases where edge cases are guaranteed.

This is the real difference:
Not what the model should do,
but how it decides what to do when no one predicted the scenario.

Compare that to models that still allow obviously inappropriate behavior.

One approach builds trust.
The other creates risk.

Transparency isn’t about feeling safe.
It’s about knowing where the boundaries actually are.

And even then, no constitution replaces human judgment.
Domain expertise still matters.
Oversight still matters.

Claude’s new constitution doesn’t make AI perfect.
It just makes its bias visible.

And for enterprises, that visibility is the real product.

#ai_documentation.

Ebikara Spiff ᴀɪᴄᴍᴄ — Tue, 06 Jan 2026 11:55:19 +0000

Translating a Complex Object Detection Model for Sales Teams: An AI Documentation Case Study

Ebikara Spiff ᴀɪᴄᴍᴄ ・ Jan 5

#ai #writing #documentation #webdev

Translating a Complex Object Detection Model for Sales Teams: An AI Documentation Case Study

Ebikara Spiff ᴀɪᴄᴍᴄ — Mon, 05 Jan 2026 14:50:00 +0000

AI models are powerful, but their technical descriptions are often incomprehensible to non-engineers. Sales teams especially struggle to explain AI capabilities to clients without oversimplifying or misrepresenting them.

In this case study, I translated a highly technical object detection model description into clear, actionable language for a sales audience — demonstrating how to bridge the gap between engineering complexity and business communication.

The Challenge

Here’s the original technical paragraph from the engineers:

Our proprietary detection framework implements a multi-scale feature pyramid network with deformable convolutions and focal loss optimization. The backbone utilizes an EfficientNet-B4 architecture pretrained on ImageNet, fine-tuned using mixed precision training with the AdamW optimizer. We've achieved state-of-the-art mean Average Precision (mAP) of 0.87 on the internal benchmark dataset, with inference latency of 17ms on our edge hardware, making it suitable for real-time detection tasks in constrained computational environments.

As you can see, this paragraph is dense with jargon and metrics — accurate but completely inaccessible to a sales team.

My Approach

Identify the audience: Sales team members needing clarity and confidence to explain AI to clients.
Focus on key aspects: Accuracy, speed, and real-world limitations.
Translate step by step: Rewrite each sentence in plain, conversational language without losing meaning.
Add a visual analogy: Something memorable to help explain how the model works.
Create a translation glossary: Simplify recurring technical terms for easy reference.

The Result

Sales-Friendly Rewrite:

This object detection model has a high reliability rate for real-time use and is designed to assist the average human when driving. It reacts fast enough to keep up with real-world driving conditions in supported environments.

Visual Analogy:

It’s like an extra pair of eyes that assists you in identifying objects in real time while driving.

Translation Glossary:

Multi-scale Feature Pyramid Network → Lets the system notice both big and small objects at the same time.
Deformable Convolutions → Helps the system adjust to unusual or stretched shapes so it can recognize them better.
EfficientNet-B4 Backbone → The “engine” of the system that efficiently extracts important details from images.

Master Responsible AI: Key Principles for Ethical Impact

Ebikara Spiff ᴀɪᴄᴍᴄ — Mon, 27 Oct 2025 04:46:58 +0000

This article explains the essential principles of Responsible AI and how organizations can build ethical AI systems.

If you only have 10–30 PDF files, you can keep things super simple. In this guide, you’ll learn how to power up an AI agent in n8n using OpenAI Assistants API, without all the extra tech

Ebikara Spiff ᴀɪᴄᴍᴄ — Sat, 04 Oct 2025 19:31:22 +0000

Ebikara Spiff ᴀɪᴄᴍᴄ

Oct 1 '25

Turn Your PDFs into a Chatbot with n8n + Open AI (No Vector DB Needed).

#ai #openai #tutorial #beginners

Comments

6 min read

Turn Your PDFs into a Chatbot with n8n + Open AI (No Vector DB Needed).

Ebikara Spiff ᴀɪᴄᴍᴄ — Wed, 01 Oct 2025 18:05:09 +0000

Most people think you must set up a complex RAG (Retrieval Augmented Generation) system with vector databases just to give your AI some knowledge. That’s not true.

If you only have 10–30 PDF files, you can keep things super simple. In this guide, you’ll learn how to power up an AI agent in n8n using OpenAI Assistants API, without all the extra tech.

You will build a chatbot that answers FAQs (we’ll use a restaurant example).

By the end, you’ll have a working AI assistant that reads your documents, remembers chat history, and answers smartly, no headaches.

What You will Need

🛠 Tools:

n8n
OpenAI

And a small set of PDFs (10–30 files is perfect).

Step 1: Set Up n8n Trigger

→ Open n8n.

→ Click on the trigger.
→ Choose Chat Message.

→ Click on the trigger button, then select Advanced AI.

Step 2: Connect n8n to OpenAI

→ Add an OpenAI node.

→ Select Message an Assistant.

Now, connect your OpenAI account:

→ Go to OpenAI.

→ Go to API Platform

→ Click start building (If you don’t have an account, create one.)

→ Open Settings.

→ Scroll down and click on API Keys.

→ Click Create new secret key.

→ Give it a name, then click Create secret key.

→ Copy the secret key.

Back in n8n:

→ Open your OpenAI Assistant node.
→ Click on credentials to connect with
→ Click Create new credentials

→ Paste your API key in the box.
→ Save it.

Now your n8n is linked to OpenAI.

→ Go back to your Open AI account.
→ Click on billings

→ Click on Add to credit balance to make sure you have some credits.

Step 3: Create Your OpenAI Assistant

→ Go to Dashboard

→ Click Assistants.

→ Give it a name (example: RAG Agent).

→ Copy the Assistant ID.

Back in n8n:

→ Open your OpenAI node.
→ In the Assistant box, choose By ID.
→ Paste the ID you copied.

Then:

→ Under Source from prompt (user message), pick Define below.

→ Back to your OpenAI dashboard where you copied the id
→ Put this in your system's instructions: Respond to the user query by following the given instruction

Step 4: Add Knowledge (Upload Files)

→ In your OpenAI assistant dashboard, scroll to File Search.
→ Turn it On.

→ Click the Files button beside it.

→ Upload the files you want the AI agent to access

👉 For this tutorial, Let's upload one FAQ file with about 25 restaurant questions. (In real use, you can upload up to 30 or more files.)

→ Click Attach.

Now your agent can read these files.

Step 5: Write the System Instructions

→ Go to your OpenAI assistant node
→ Add the prompt below in the prompt user message

RAG Agent Prompt

Identity
You are an AI assistant for Jennie’s Restaurant. Your role is to help customers by answering FAQs about menu items, hours, location, and general restaurant policies. Be friendly, professional, and concise. Do not assist with reservations, payments, or event bookings. Use only the restaurant’s FAQ knowledge base for answers.

Style Guardrails

Be Concise: Keep responses short, direct, and informative.
Be Engaging: Use a warm, welcoming tone.
Stay Proactive: Offer extra help naturally (e.g., “Would you also like to know about our specials?”).
Get Clarity: If a request is unclear, politely ask a follow-up question.
Avoid Repetition: Change your wording so replies don’t sound the same.

Conversation Flow

Introduction Greet warmly and offer help. Example:

“Hi! Thanks for reaching out to Jennie’s Restaurant. How can I help you today?”

Answer FAQs
Always check the FAQ knowledge base. Never guess. Use the remove_annotations tool to clean the response.
If the Query Is Vague
Ask politely for more details.
Example:

“Could you clarify if you’re asking about the lunch or dinner menu at Jennie’s Restaurant?”

If the Query Is Out of Scope Apologize and send them to a human. Example:

“I’m sorry, I can’t help with that. Please call (555) 123-4567 for more details.”

Closure Offer more help, then close politely. Example:

“Is there anything else I can help you with today?”
If not:
“Thanks for reaching out to Jennie’s Restaurant. Have a wonderful day!”

Tool Usage
Always run your final answer through the remove_annotations tool before replying.

Date today: {{ $now }}
User’s input: {{ $json.chatInput }}

👉 Make sure {{ $json.chatInput }} shows in green inside n8n.

→ If it’s not green, drag chatInput into that spot.

Step 6: Add Memory

In your AI Assistant node (n8n):

→ Click on Memory lane.

→ Pick Simple memory.

→ Set Context window length to 10 (or any number you prefer.)

This way, the bot remembers the last 10 messages in the same chat.

Step 7: Add a Cleanup Tool (remove annotations)

You don’t want the bot showing raw citations. So let’s add a cleanup tool.

→ In your OpenAI assistant, click on the boxed cross on Tools.

→ Select Code tool.

→ Name it: remove_annotations.

→ Description: Removes any annotation from the output. Always use this before sending to customer.

→ Paste this code in the JavaScript box:

function removeAnnotations(input) {
  return input.replace(/【[^】]*】/g, '').trim();
}

// Example usage
const output = removeAnnotations(query);
return output;

→ Save it.

Restaurant FAQ Chatbot

Now test your chatbot:

Type a question about Jennie’s Restaurant.
The bot will check the FAQ file, clean up the answer, and reply in a warm, short style.

The Big RAG Misconception

Most people think RAG = Vector Database. That’s wrong.

For small projects with a few documents, you don’t need Pinecone, Weaviate, or any other heavy setup.

OpenAI Assistants + n8n file uploads work just fine.

Vector DBs are useful at scale. But for 10–30 PDFs, skip the complexity and keep it light.

You just built a working AI agent in n8n using OpenAI:

Trigger on chat.
Connect to OpenAI.
Create an assistant.
Upload files.
Add memory.
Clean responses.
Test your chat.

Simple, clean, and affordable. No vector databases, no headaches.

👉 Try it out with your own docs today.

How To Self-Host N8N For FREE (In 4 Minutes).

Ebikara Spiff ᴀɪᴄᴍᴄ — Mon, 22 Sep 2025 01:49:19 +0000

Introduction

Do you want powerful automations without paying for pricey tools? Let me tell you a secret: you can self-host n8n for free and it only takes 4 minutes to set up.

n8n lets you connect apps, move data, and automate tasks that usually eat up your time. The best part of it all is that You own it. No subscriptions. No limits.

In this guide, I’ll show you step by step how to get n8n running fast using Docker. By the end, you will have your own automation hub that is free, simple, and under your control. 🚀

Step 1
First we have to download and install Docker

→ Go to docker.com and download Docker desktop for system.

→ Mine is Windows.

Before installing Docker, you must check the system requirements to confirm if your PC can run it.

## System Requirements (Step by Step)

Step 1: Check WSL Version

The first requirement is WSL 1.1.3.0 or later.

To check if it’s installed:

→ Press Windows + R, type cmd, and press Enter.

It will take you to your terminal

→ In terminal, run WSL

If WSL runs, it’s installed.

If not installed

→ Type wsl --install and press enter

Step 2: Check Windows Version

Next on the requirement page, it says we need to have:

Operating System: Windows 11, 64-bit
Edition: Pro
Version: 21H2 or later

→ Press Win + R and type winver in the box, then hit Okay

My version is 22H2

Step 3: Enable WSL 2 Features

The next requirement - Turn on WSL 2 features on windows.

→ Go to the search bar on your system and type Enable windows

→ Click on Turn Windows features on or off

→ Enable Windows Subsystem for Linux (WSL) by ticking the box beside it.

→ Click Ok

Wait for setup to finish

→ Select Don’t restart for now.

Step 4: Verify Virtualization

Next on the requirement page, check if virtualization is enabled.

To check if Virtualization is enabled:

→ Press Ctrl + Esc key to open Task Manager.

→ Click on the second icon

→ Click on CPU.

At the bottom, check if Virtualization is enabled (it usually is by default).

🛠️ Install Docker on Windows

Step 1: Run the Installer

→ Double-click the Docker Desktop installer you downloaded.

→ Click Yes when prompted for permissions.

Step 2: Configure Setup

→ Keep the shortcut option checked.

→ Click OK to continue.

Step 3: Install

Docker will unpack files and install automatically.

This may take several minutes, be patient.

Step 4: Confirm Installation

When complete, you will see Installation Successful.

Step 5: Restart and Launch

Restart your computer.

→ Open Docker Desktop,

You are ready to use Docker

## How to Self-Host n8n for Free

Step 1. Open Docker Desktop

Make sure Docker is installed and running.

Step 2. Go to the Images Tab

In Docker Desktop

→ Click on Images from the left panel.

Step 3. Search for n8n

→ Click on search images to run.

→ In the search bar, type: n8n

Step 4. Select the Official Image

→ Choose n8nio/n8n (the one with 100M+ downloads).

→ Click Pull.

This downloads the official n8n Docker image to your computer.

Step 5. Run the Image

After pulling:

→ Click Run.

Next, Configure the container:

→ Container Name: n8n

→ Host Port: 5678

→ Click Run again.

This downloads the official n8n Docker image to your computer.

Step 6. Wait for Startup.

Let Docker run until you see this message:

→ Editor is now accessible via: http://localhost:5678

Step 7. Open n8n in Browser

→ Copy and paste http://localhost:5678 into your browser and run.

You will see the n8n welcome page.

→ Confirm the URL shows localhost:5678.

Step 8. Create Your Account

Congratulations. You now have n8n running locally on your computer with Docker.

Whose Fairness Are You Coding Into Your AI System?

Ebikara Spiff ᴀɪᴄᴍᴄ — Wed, 23 Apr 2025 04:35:10 +0000

As developers, we’re often taught to treat fairness like a math problem.

Balance the dataset.

Reduce bias.

Optimize the outcome.

But here’s a question I’ve been wrestling with:

Is fairness universal — or is it cultural?

Growing up, I saw fairness differently

I’m from Nigeria.

Where I grew up, fairness didn’t mean “treat everyone exactly the same.”

It often meant “consider people’s different realities.”

Think about it:

If two students show up late to class, one because of traffic, the other because they were helping their parents in the market, do we punish them both the same way?

Same rule, different context.

And maybe fairness means acknowledging that.

AI doesn't always do that

Most AI systems we build today encode a Western interpretation of fairness:

🧮 Group fairness

⚖️ Individual fairness

📊 Statistical parity

These are important, but they’re not always enough.

Take this real case:

A credit scoring algorithm in Kenya failed to recognize community-based lending traditions, like rotating savings groups (ROSCAs).

As a result, reliable borrowers were marked “high-risk” because the system didn’t understand local context.

Fair model?

Accurate data?

Maybe.

Fair outcome?

Not really.

Developers, we need to ask harder questions

If you’re working on AI, especially models that affect people’s lives, I urge you to consider:

Whose values are we embedding into our models?
Are we treating fairness as a checklist or a conversation?
Can our systems adapt to different cultural realities, not just datasets?

As I prepare for a PhD, I’m committed to asking these questions, and building models that reflect local values, not just global assumptions.

Because true fairness in AI might not come from the top down, but from the Global South outward.

💬 What’s your take?

Have you ever worked on an AI project where fairness was tricky to define?

Do you think AI models should adapt to different cultures, or aim for universal rules?

Let’s talk in the comments 👇🏽