Monday, 29 June 2026

​Why the AI Boom Just Priced Me Out of the Hard Drive Market (And Why I'm Switching to Blu-Ray)

 Month-by-month with the original filenames is the absolute gold standard for video archiving. It keeps everything in perfect 

There is a huge misconception about what "data centers" actually do. Most people hear "the cloud" and picture a giant digital attic filled with their old iPhone photos, YouTube videos, and Netflix streams.

But the new wave of **AI data centers** is a completely different beast.

### The Difference Between Storage and AI

Traditional data centers are essentially the world's hard drives. They use standard CPUs and massive banks of hard drives to store, retrieve, and move data. Think of it like a massive library.

AI data centers, however, are built for massive computation. They don't just hold data; they crunch it using energy-hungry GPUs (Graphics Processing Units) to train massive models or generate content in real-time.

Unfortunately for everyday consumers and data hoarders, this AI gold rush is leaving a massive physical footprint:

 * **Massive Power Demands:** A single AI query can use up to 10 times more electricity than a standard Google search.

 * **Massive Hard Drive Demands:** AI doesn't just use fast SSDs. They need traditional, spinning hard drives to store the massive, petabyte-scale datasets used to train the models in the first place.

### The Real-World Cost for Hobbyists

As someone who loves to archive history—saving YouTube streams, Rumble streams, and sports broadcasts—I've built up a personal archive of about 25TB of data. I like knowing my media library is sitting safely in my hands, immune to copyright strikes, platform deletions, or internet outages.

But the AI boom just broke the hobby.

For years, digital hoarders could count on a beautiful trend: storage always got bigger and cheaper. Not anymore. Because tech giants are buying up every hard drive they can get their hands on to build AI infrastructure, retail consumers have been pushed to the back of the line.

**Case in point:** I used to be able to get a 24TB hard drive for around $560. Now? That exact same drive is sitting closer to $1,000.

### My Pivot to Physical Discs

Right now, I have filled three 20TB hard drives, downsized to a 4TB drive, and I am officially down to my last 1TB of free space. Because the hard drive market is so inflated by AI corporate greed, I am changing my strategy.

Moving forward, I am investing in a high-end Pioneer/Asus Blu-Ray burner to transition my archive onto **100GB BDXL Triple Layer discs**.

My archiving strategy is straightforward:

 * Everything is saved onto data discs month-by-month.

 * All original file names are preserved so they can always be cross-referenced.

 * Grouping videos into 93–94GB batches (the true usable space on a 100GB disc) to maximize efficiency.

It sucks that a self-sufficient hobby like data hoarding is getting penalized by a corporate tech race, but switching to physical shelves of Blu-Ray cases feels like the ultimate workaround. It keeps history safe, and it keeps my hard-earned money out of the AI hardware market.

Thursday, 20 November 2025

💾 Blu-ray vs. Digital: Why File Size and Ownership Still Matter

The Unseen Difference: 30GB of Data vs. 4GB of Stream

In the age of 4K streaming, most people believe the quality gap between a physical Blu-ray disc and a digital movie purchase (like from iTunes or Google Movies) has vanished. This couldn't be further from the truth. The difference is measurable, audible, and visible, primarily because of one thing: Bitrate.
1. The Quality Gap: Bitrate and Compression
The core difference lies in the amount of data that streams to your screen every second.
Format Typical File Size (1080p Feature Film) Typical Video Bitrate (Avg.) Audio Quality
Standard Blu-ray (BD-50) 25GB – 50GB 25-40 Mbps Lossless (Dolby TrueHD, DTS-HD MA)
4K Ultra HD Blu-ray (BD-100) 66GB – 100GB 60-120 Mbps Lossless (Dolby TrueHD Atmos, DTS:X)
Digital 4K Stream (iTunes/Vudu) 4GB – 15GB 15-25 Mbps Lossy (Dolby Digital Plus)
Bitrate is the speed at which data is read. The capacity of a standard dual-layer Blu-ray disc (50GB) versus a typical 4K digital file (~10GB) means the digital file has to throw away roughly 80% of the original visual and audio data to achieve its small size. This is achieved through heavy compression.
Video: Heavy compression (using codecs like HEVC) leads to visible artifacts, especially in dark, shadowy scenes or scenes with lots of smoke or complex action. You might notice "banding" (sharp, visible lines in color gradients, like a cloudy sky) and a loss of film grain detail. The higher, sustained bitrate of Blu-ray preserves these nuances.
Audio: This is where the difference is most dramatic. Blu-ray offers Lossless Audio (like Dolby TrueHD or DTS-HD Master Audio). Digital services use Lossy Audio (like Dolby Digital Plus) which compresses the audio stream significantly. On a dedicated home theater system, this difference in soundstage, depth, and dynamic range is instantly noticeable.
2. The Ownership Crisis: DRM and Control
Beyond quality, the most critical argument for Blu-ray is true ownership.
When you buy a digital movie on a platform like iTunes or Google Movies, you are not buying the movie. You are buying a revocable license to view the content on their platform under their rules. This is controlled by Digital Rights Management (DRM).
Content Removal & Editing: Streaming platforms or digital storefronts can, and often do, remove titles if they lose licensing rights. They can also retroactively edit, censor, or change the version of the film you purchased without your permission. Your physical disc is a time capsule of the movie as it was released.
Server Dependency: If the service goes out of business, or if you lose internet access, your entire digital library is inaccessible. Your Blu-ray disc works as long as you have a player and power.
Compatibility: Digital files are tied to specific apps or devices. The disc, following a universal standard, will work on any compatible player worldwide.
Physical media grants you control—digital media grants you temporary access.
📺 Archiving & The Digital Grey Area: Kids' Shows
The challenge you raised—archiving kids' TV shows that only exist in digital stores—highlights the frustrating necessity of personal preservation in the modern media landscape.
The Niche Challenge
Many TV shows (especially children's, animated, and older, less popular network content) do not receive physical Blu-ray or DVD releases because the mastering and distribution costs are too high for the expected sales volume. Digital storefronts become the only way to "own" them.
The Archival Dilemma
Your desire to create a personal archive of these shows (like burning custom Blu-rays) falls into a legal grey area concerning fair use and digital rights.
The Law (General Principle): US and many international copyright laws generally prohibit circumventing DRM (which iTunes and Vudu use) to create copies. Even for personal use, the act of removing the DRM can be illegal under acts like the DMCA.
The Tools (Screen Recording): Tools like ...or ... are often used to screen record protected content. While this side-steps the DRM circumvention argument (it records the output, not breaks the encryption), the end product is still an unauthorized copy for archival use.
The Reality (Personal Archive): While distributing or selling these custom discs is illegal piracy, the personal, non-commercial use of copies for archival purposes is a common practice among media historians and collectors, driven by the fear of content disappearing forever.
The true value of a custom Blu-ray archive isn't just about preserving quality—it's about fighting against the impermanence of digital licenses and ensuring that shows important to your family aren't deleted from history by a server license expiration.

Saturday, 13 September 2025

How to Set up a MediaWiki Site

You've chosen a fun and educational project! Running a home server for a family wiki is a great way to learn about web hosting. Here's a step-by-step guide to help you get your MediaWiki site up and running.

1. Set Up Your Home Server

The first step is to turn a computer into a web server. You'll need to install a software stack that includes a web server, a database, and a scripting language. This combination is often called a LAMP stack (Linux, Apache, MySQL, PHP) or a WAMP stack (Windows, Apache, MySQL, PHP). Using a pre-packaged installer is the easiest way to get started.

  • Operating System: Linux is a popular choice for servers because it's free and highly customizable. However, you can also use a Windows or macOS machine.

  • Software Stack: Install a bundle like XAMPP (for Windows, macOS, or Linux) or WampServer (for Windows only). These packages install Apache, MySQL/MariaDB, and PHP all at once. Download the installer, run it, and follow the on-screen instructions.

Once the installation is complete, you should be able to access a test page by typing http://localhost into your web browser. If you see a welcome page, your web server is running correctly.


2. Install MediaWiki

Now that you have a server environment, you can install the MediaWiki software.

  1. Download MediaWiki: Go to the official MediaWiki website and download the latest stable version as a .zip or .tar.gz file.

  2. Extract and Place Files: Unzip the downloaded file. Find your web server's document root directory. For XAMPP, this is often the htdocs folder. Copy the extracted MediaWiki folder into the htdocs directory. You can rename the folder to something simple, like wiki.

  3. Create a Database: Open the database management tool that came with your software bundle, like phpMyAdmin (accessible via your web server's control panel). Create a new, empty database for your wiki. For example, you could name it my_wiki. You'll also need to create a database user with all privileges for this new database.

  4. Run the Installation Script: In your web browser, navigate to the MediaWiki installation script. If you placed the folder in the htdocs directory and named it wiki, the URL will be http://localhost/wiki. The script will guide you through the setup process. It will ask for your database details (database name, username, and password), the name of your wiki, and your administrator account information.

  5. Save the Configuration File: After the installation is finished, the script will generate a file named LocalSettings.php. You must download this file and place it in the root directory of your MediaWiki installation (i.e., inside the wiki folder).


3. Point Your Domain to the Server

This is the most complex part of the process, as your home internet connection likely has a dynamic IP address, which changes periodically. A domain name needs to point to a stable IP address. To solve this, you'll need a Dynamic DNS (DDNS) service.

  1. Sign Up for a DDNS Service: Choose a DDNS provider. Many domain registrars offer this as an add-on, or you can use a dedicated service.

  2. Configure Your Domain: Log in to your domain registrar's account. In the DNS settings, change the nameservers to point to your DDNS provider's nameservers. Then, in the DDNS service's control panel, add your domain and create a hostname (e.g., wiki.yourdomain.com).

  3. Install a DDNS Update Client: This is a small program that runs on your server computer. It monitors your public IP address. When the IP changes, the client automatically sends an update to your DDNS provider, which then updates your domain's DNS records.

  4. Configure Port Forwarding on Your Router: Your router acts as a gatekeeper for your home network. To allow external traffic to reach your server, you need to set up port forwarding. Log in to your router's admin panel and forward inbound traffic on port 80 (HTTP) and port 443 (HTTPS) to the static local IP address of your server computer.

    • Note: For security, only open these ports when you need the site to be accessible to others. When you're done, you can turn off the web server software or disable the port forwarding rules.

After completing these steps, your domain name should now point to your home server. When the server is running and the internet is on, your family can access the wiki by typing your domain name into their browser.

Host and Play Videos from Your Server

If you want to upload and host your own videos, you'll need a different extension and a video processing tool.

  • Install an extension: The TimedMediaHandler extension is the standard for this. It's used by Wikimedia projects (like Wikipedia) and provides a powerful way to handle video and audio files.

  • Install a video encoder: To play videos in a web browser, they often need to be in a specific format (like WebM or Ogg) and optimized for streaming. The TimedMediaHandler extension uses a tool called FFmpeg to do this on your server. You'll need to install FFmpeg and configure the extension to use it.

  • Upload the video: Once the extension and FFmpeg are set up, you can upload a video file just like you would an image. The wiki will automatically process the file and create a playable player on the page, similar to how an image thumbnail is generated.

Both methods give you the ability to add and play videos, giving your family a much more dynamic and engaging wiki!