nigel = {
    "username": "Nigel1992",
    "location": "Netherlands 🇳🇱",
    "main_os": "Linux 🐧",
    "previous_main_os": "Windows 🪟",

    "interests": [
        "Kodi",
        "Python",
        "Linux",
        "Android / Waydroid",
        "ESP32",
        "Raspberry Pi",
        "IPTV",
        "Networking",
        "Automation",
        "Hardware"
    ],

    "philosophy":
        "Build → Break → Understand → Fix → Improve → Automate → Share"
}

I've been working with computers and Windows for many years.

A few years ago I started exploring Linux more seriously. Around two years ago I made the switch and Linux became my main everyday operating system.

Today, most of my projects and experiments revolve around Kodi, Python, Linux, Android/Waydroid, ESP32, Raspberry Pi, IPTV, networking and automation.

I enjoy solving the kind of problems that make you think:

"Surely there has to be a way to make this work..."

Usually, there is. 😎

📺 NLZiet Kodi Add-on Unofficial Kodi video add-on for the Dutch streaming service NLZiet. Highlights 📺 Live TV 📅 EPG / Now & Next 🔐 OAuth2 authentication 📡 IPTV Manager integration 💾 Caching 🖼️ Artwork / Fanart 🐧 LibreELEC compatibility

🎬 Videoland Kodi Add-on Unofficial Kodi video add-on for the Dutch streaming service Videoland. Highlights 🎬 Movies 📺 Series 📑 Episode navigation 👤 Profiles ❤️ Watchlist 🏠 Home sections ▶️ Kodi-native playback

Kodi is one of my biggest development interests.

Kodi
 │
 ├── Python Add-ons
 ├── Video Add-ons
 ├── Streaming APIs
 ├── OAuth2 Authentication
 ├── IPTV Manager
 ├── IPTV Simple Client
 ├── EPG
 ├── PVR
 ├── InputStream
 ├── Caching
 ├── Dependency Management
 ├── Kodi Repositories
 └── LibreELEC Compatibility

I especially enjoy taking streaming services and integrating them into a native Kodi experience.

My media experiments go beyond individual Kodi add-ons.

I've worked and experimented with:

IPTV Simple • IPTV Manager • Xtream Codes • EPG • Catch-up TV • Timeshift • NextPVR • Kodi PVR • InputStream • LibreELEC

My Raspberry Pi 5 also serves as a platform for experimenting with:

📺 Kodi • 📡 IPTV • 🔊 Bluetooth Audio • ⏯️ AVRCP • ⌨️ Kodi Keymaps • 🔄 Auto-connect • 🖥️ HDMI • ⚡ Performance Tuning

          WINDOWS 🪟
              │
              │
      Main OS for many years
              │
              ▼
      Started exploring Linux
              │
              ▼
       Learned by tinkering
              │
              ▼
       Switched primary OS
         ~2 years ago
              │
              ▼
           LINUX 🐧
        Main OS today

Windows was my main operating system for many years.

That gave me hands-on experience with:

Windows 11 • Hardware • Drivers • Networking • Software Troubleshooting • Performance Optimization • System Tweaking • PowerShell • CMD • PC Maintenance

Windows is still an important part of my technical experience even though it isn't my primary desktop anymore.

I started using Linux seriously a few years ago, and around two years ago I switched to Linux as my primary operating system.

I've used and experimented with:

Xubuntu • Kubuntu • Ubuntu • LibreELEC

And worked with:

Bash • APT • Flatpak • Snap • Docker • X11 • Xorg • Mesa • V4L2 • Bluetooth • USB • Networking

Break something → figure out why → fix it → learn from it.

One of my favorite rabbit holes is getting Android applications to behave properly inside Linux.

Waydroid
 │
 ├── ADB
 ├── Android Shell
 ├── Google Services
 ├── Google Accounts
 ├── Account Visibility
 ├── SQLite Databases
 ├── Package Management
 ├── App Permissions
 ├── Camera / V4L2
 ├── Multitouch
 ├── Logcat
 ├── dumpsys
 ├── Backup / Restore
 └── App Compatibility Debugging

Some of my most-used Android debugging tools:

adb
logcat
dumpsys
pm
am
getprop
sqlite3

I've spent plenty of time digging through Android internals, permissions, package state, account visibility and system databases to understand why applications behave differently inside Waydroid.

If an Android app works perfectly on a phone but breaks inside Waydroid, I don't just want to know that it broke.

I want to know why.

I've experimented extensively with the ESP32-2432S028R — Cheap Yellow Display / CYD.

ESP32 CYD
 │
 ├── ESP32
 ├── ILI9341 Display
 ├── Resistive Touch
 ├── ATGM336H GPS
 ├── GPS Antennas
 ├── CH340 Serial
 ├── Flash / Partitions
 ├── Firmware
 ├── ESP32 Marauder
 ├── Bruce
 ├── Wardriving
 └── Multiboot Experiments

Embedded projects are especially fun because debugging suddenly involves both software and physical hardware.

My Raspberry Pi 5 is another platform where software and hardware experimentation come together.

Raspberry Pi 5
      │
      ├── LibreELEC
      ├── Kodi
      ├── IPTV
      ├── Bluetooth Audio
      ├── AVRCP
      ├── Kodi Keymaps
      ├── Auto-connect Scripts
      ├── HDMI Configuration
      └── Performance Tuning

Sometimes a website doesn't quite work the way I want it to.

So I change it. 😎

One of my projects is a Vinted Country & City Filter, adding additional client-side filtering functionality.

I've also experimented with dark-mode and interface modifications.

JavaScript • DOM Manipulation • Client-side Filtering • Userscripts • UI Tweaks • Dark Mode

If I have to do something repeatedly, sooner or later I'm probably going to script it.

Automation
 │
 ├── Waydroid Backups
 ├── Waydroid Restore
 ├── Android Studio AVD Backups
 ├── Android Studio AVD Restore
 ├── Linux System Scripts
 ├── Bluetooth Auto-connect
 ├── Kodi Automation
 ├── Application Data Backups
 ├── External Drive Backups
 └── System Configuration

Why do something manually ten times when you can spend an afternoon automating it? 😎

I've also experimented with Docker for running and testing services without having to install everything directly onto the host system.

Docker
 │
 ├── Containers
 ├── Services
 ├── Media Servers
 ├── NextPVR
 ├── Testing Environments
 └── Linux Integration

Kodi Repositories • Streaming Add-ons • NLZiet • Videoland • NASA+ • Xtream/XC • IPTV Utilities • Stream Troubleshooting

Waydroid Utilities • Android Studio • V4L2 • Webcam Integration • Multitouch • System Tweaks • Backup & Restore

Vinted Userscripts • Client-side Filters • Dark Mode • UI Enhancements

Thunderbird Add-on Experiments • Ollama Integration • AI-assisted Automation • Development Utilities

I've also worked and experimented with:

🎮 PSP-3000 • 🔓 ARK Custom Firmware • 🏠 Homebrew • 💿 PS1 → PSP Conversion • 🎮 POPS • 💾 microSD Adapters • 📁 FAT32 • 💽 Large SD Cards

Linux tools + old hardware = a surprisingly fun combination.

Networking is another area I frequently experiment with and troubleshoot.

Networking
 │
 ├── TCP/IP
 ├── IPv4
 ├── IPv6
 ├── Wi-Fi
 ├── OpenVPN
 ├── VPNs
 ├── Routers
 ├── Port Configuration
 ├── Wireless Adapters
 ├── Wi-Fi Repeaters
 └── Troubleshooting

The most interesting networking problems are usually the ones where:

"Everything looks correct... but it still doesn't work."

A large part of how I learn technology comes from troubleshooting.

        SOMETHING BREAKS
               │
               ▼
          "Well... why?"
               │
               ▼
        Check the obvious
               │
               ▼
      Obvious stuff is fine
               │
               ▼
       Go down rabbit hole
               │
               ▼
        Find weird cause
               │
               ▼
            FIX IT
               │
               ▼
          AUTOMATE IT
               │
               ▼
        Put it on GitHub

Hardware I've worked and experimented with includes:

PCs • Laptops • Raspberry Pi • ESP32 • Android Devices • USB Hardware • Webcams • Bluetooth • Wi-Fi Adapters • SD Cards • Displays • GPS Modules • Routers

AI is an important part of my development workflow.

I use AI tools for:

Rapid Prototyping • Debugging • Code Analysis • Research • Documentation • API Exploration • Refactoring • Edge Cases • Learning • Automation

It allows me to explore ideas, investigate unfamiliar systems and prototype solutions much faster.

But the rule stays the same:

Test it. Understand it. Make sure it actually works.

IDEA
 │
 ▼
RESEARCH
 │
 ▼
PROTOTYPE
 │
 ▼
BREAK SOMETHING
 │
 ▼
DEBUG
 │
 ▼
UNDERSTAND THE PROBLEM
 │
 ▼
FIX IT
 │
 ▼
TEST IT
 │
 ▼
AUTOMATE IT
 │
 ▼
DOCUMENT IT
 │
 ▼
GITHUB 🚀

A lot of my projects start because:

I need something. It doesn't exist. Or the existing solution doesn't quite do what I want.

So I try building it.

I also enjoy sharing fixes and experiments because the weird technical problem I spent hours solving today might save someone else those same hours tomorrow.

        BUILD
          ↓
        BREAK
          ↓
      UNDERSTAND
          ↓
         FIX
          ↓
       IMPROVE
          ↓
      AUTOMATE
          ↓
        SHARE
          ↓
        REPEAT