Project Oak Public Meeting Presentation Analysis

What follows is the result of a discussion with ChatGPT (ironic, I know) about the slides presented at the Project Oak public meeting presentation on 5/18/2026.

Overview

This document analyzes a series of public presentation boards displayed during a community meeting regarding the proposed “Project Oak” data center development in Coweta County, Georgia.

The goal of this analysis is not to advocate either for or against the project, but to:

  • Separate factual claims from persuasive framing
  • Identify what information is emphasized versus omitted
  • Examine how the presentation attempts to address community concerns
  • Highlight the broader planning and infrastructure implications suggested by the materials

The presentation itself appears highly polished and strategically structured. Across all slides, the messaging consistently focuses on:

  • Long-term infrastructure legitimacy
  • Regulatory compliance
  • Environmental reassurance
  • Community compatibility
  • Economic upside
  • Visual buffering and concealment

At the same time, several major infrastructure details remain largely absent from the boards themselves, including:

  • Total campus megawatt demand
  • Operator identity
  • Tax incentive specifics
  • Generator counts
  • Traffic volumes
  • Construction phasing timelines
  • Regional grid implications
  • Long-term expansion scenarios

The analysis below reviews each slide individually.


Slide 1 — Site Selection

Core Message

The presentation begins by attempting to establish legitimacy.

The central argument is:

“This project belongs here because the county’s long-term planning framework already envisioned infrastructure-intensive development in this corridor.”

The slide repeatedly references:

  • “critical, long-term infrastructure”
  • “responsibly”
  • “strict local, regional and national requirements”
  • the county’s “2046 Comprehensive Plan”
  • “Industrial Employment Character Areas”

The project is framed as:

  1. An inevitable part of modernization
  2. Compatible with existing planning policy
  3. Economically beneficial
  4. Positioned within designated industrial corridors rather than isolated rural land

Key Observations

The “2046 Comprehensive Plan” Reference

This is the most important part of the slide.

The developers are effectively arguing:

“The county already planned for infrastructure-intensive uses in this area.”

That does not automatically settle the debate, however.

A comprehensive plan is:

  • A planning and policy document
  • A growth-direction framework
  • Not necessarily automatic approval for any specific development

Opponents may still argue that:

  • “Industrial Employment” does not automatically imply hyperscale data center development
  • The scale and implications of modern data infrastructure may exceed what residents envisioned when these planning categories were established

Transportation Corridor Framing

The slide references:

  • Amlajack Boulevard extensions
  • Coweta Industrial Parkway
  • connections between industrial parks

This is intended to reassure residents that:

  • Industrial traffic will remain concentrated within designated corridors
  • Residential streets will not become primary access routes

However, much of this language references “planned” infrastructure rather than existing completed infrastructure.

What the Slide Does Not Discuss

The board contains no meaningful quantitative detail regarding:

  • Electrical demand
  • Water demand
  • Generator infrastructure
  • Tax incentives
  • Traffic volumes
  • Long-term expansion

The presentation begins by establishing legitimacy before revealing actual scale.


Slide 2 — What Is a Data Center?

Core Message

This slide attempts to normalize the concept of a data center and reduce fear.

The presentation frames data centers as:

  • Essential modern infrastructure
  • Quiet and professional environments
  • Critical to daily life
  • Economically valuable
  • Operationally stable

The emotional goal is:

“This is not a dangerous industrial operation. This is where the internet lives.”

Key Observations

Infrastructure Framing

The slide repeatedly connects data centers to:

  • Internet searches
  • Social media
  • Streaming services
  • Emergency services

This positioning attempts to move the project psychologically closer to:

  • Utilities
  • Public infrastructure
  • Essential services

rather than traditional industrial development.

Backup Generators

The presentation states:

“Backup generators automatically turn on in the event of a power outage, which is extremely rare and uncommon.”

This wording is carefully constructed.

The slide does not discuss:

  • Generator counts
  • Fuel storage
  • Testing schedules
  • Noise during testing
  • Emissions

The board focuses on outages while avoiding discussion of routine operational testing.

Cooling Systems

The cooling discussion emphasizes:

  • Quiet operations
  • Efficiency
  • Climate control

However, cooling infrastructure is often one of the largest:

  • Power consumers
  • Noise sources
  • Potential water users

within a data center campus.

These complexities are largely omitted.

Simplified Technical Diagram

The “Data Center Pathway” graphic is intentionally simplistic.

Its purpose is not technical precision.

Its purpose is familiarity.

The audience is encouraged to think:

“This is just part of how the internet works.”

rather than focusing on the scale of the infrastructure.


Slide 3 — Noise Levels

Core Message

This slide directly addresses one of the most common concerns associated with modern data centers: continuous operational noise.

The presentation argues:

“Modern data centers are quiet, engineered facilities that comply with noise regulations and minimize community impact.”

Key Observations

Important Wording

The most important sentence on the slide is:

“The project will be designed to meet applicable County noise ordinance requirements.”

This is legally careful wording.

It does not claim:

  • No disturbance
  • No perceptible noise
  • No operational sound

Instead it claims compliance.

The 40–60 dBA Comparison

The slide compares data center noise to:

  • Libraries
  • Conversation
  • Tractors
  • Semi-trucks

This comparison is designed to frame data centers as:

  • Closer to ordinary ambient sound
  • Far quieter than heavy industry

However, the slide does not address an important nuance:

A constant 24/7 mechanical hum can be perceived very differently than intermittent human conversation.

Humans respond differently to:

  • Tonal noise
  • Low-frequency vibration
  • Continuous nighttime sound

These issues are not discussed.

Property-Line Measurements

The chart references:

“Decibels measured at the property line.”

Important missing context includes:

  • Which property line
  • Daytime vs nighttime measurements
  • Average vs peak levels
  • Weather and terrain effects
  • Generator testing conditions

Appeals to Authority

The slide references:

  • Google
  • Facebook/Open Compute
  • Microsoft

This is intended to create confidence through association with major technology firms.

However, the slide cites design philosophies rather than measured acoustic outcomes from comparable nearby communities.


Slide 4 — Environment: Light, Odors & Stormwater

Core Message

This slide focuses on environmental reassurance.

The central message is:

“This project is regulated, studied, and environmentally manageable.”

Key Observations

FAQ Structure

The FAQ format itself is revealing.

It suggests the developers are responding directly to concerns already circulating publicly.

The questions focus on:

  • Factories
  • Generators
  • Environmental review
  • Stormwater runoff
  • Lighting and glare

“Loud, Smoking Factory” Framing

The first question asks:

“Will this be a loud, smoking factory?”

This is strategically phrased.

It allows the presentation to rebut an exaggerated image rather than addressing more nuanced concerns about:

  • Infrastructure intensity
  • Land-use transformation
  • Utility burden
  • Long-term corridor evolution

Environmental Impact Language

The slide states:

“No anticipated adverse environmental impacts.”

This does not mean “zero impact.”

In regulatory language, it more commonly means:

  • Impacts are expected to remain within allowable thresholds
  • Mitigation measures are considered sufficient

Stormwater Discussion

The presentation emphasizes:

  • Engineered stormwater systems
  • Lack of industrial discharge
  • Compliance with county standards

However, it avoids discussion of:

  • Runoff volume changes
  • Watershed impacts
  • Impervious surface expansion
  • Flooding risk

Lighting

The slide promises:

  • Shielded lighting
  • Reduced spillover
  • Compliance with standards

This is likely intended to reassure nearby residents concerned about:

  • Nighttime brightness
  • Security lighting
  • Loss of rural character

Slide 5 — Utilities: Power

Core Message

This slide is strategically important because power demand is one of the defining characteristics of modern hyperscale data centers.

The central argument is:

“This project will not burden existing utility customers.”

Key Observations

Existing Transmission Infrastructure

The slide states:

“This site is expected to be served by transmission lines that already exist on the property.”

This strongly suggests transmission access was a major factor in site selection.

Modern data centers increasingly locate near:

  • High-voltage corridors
  • Existing substations
  • Utility capacity

“Developer Pays” Framing

The slide repeatedly emphasizes:

  • Developer-funded upgrades
  • No utility rate impact
  • Coordination with utility providers

This is intended to counter fears that:

  • Residents will subsidize infrastructure expansion
  • Local utility rates will increase because of the project

Important Omission: Megawatt Demand

Despite focusing entirely on power infrastructure, the slide never reveals:

  • Total megawatt demand
  • Peak demand
  • Equivalent residential load
  • Expansion capacity

This omission becomes increasingly noticeable.

The Broader Question

The slide narrowly addresses:

“Who pays for direct infrastructure upgrades?”

It does not address:

  • Regional grid planning
  • Future generation expansion
  • Long-term transmission implications
  • Cumulative corridor growth

Slide 6 — Utilities: Water Usage

Core Message

This slide attempts to counter one of the largest emerging national criticisms of data center development: water consumption.

The argument is:

“This project uses surprisingly little water compared to other forms of development.”

Key Observations

Closed-Loop Cooling

The most important technical statement is:

“This project will not have an open-loop cooling system.”

Closed-loop systems generally:

  • Recycle water
  • Reduce continuous consumption
  • Require far less daily makeup water than evaporative-heavy systems

This is a meaningful distinction.

Comparison Against Housing

The slide compares:

  • 6 data centers = 30,000 gallons/day

against:

  • Single-family development = 390,000 gallons/day
  • Multifamily development = 500,000 gallons/day

This comparison is strategically powerful because it reframes the discussion:

“This may use less water than alternative growth patterns.”

Important Assumption

The comparison relies heavily on a footnote assumption:

Closed-loop cooling with water use limited primarily to domestic and humidification loads.

If cooling strategies change in the future, water demand could also change.

Groundwater Protection

The slide repeatedly references:

  • Groundwater protection
  • Agricultural compatibility
  • No industrial discharge

This suggests nearby agricultural and rural concerns were already anticipated.


Slide 7 — Economic Benefits

Core Message

This slide provides the primary justification for why the community should want the project.

The argument is:

“The economic upside outweighs the concerns.”

Key Observations

Broad Statewide Statistics

The slide cites statewide Georgia data center statistics:

  • 176K jobs
  • $25.7B GDP contribution
  • $1.8B tax contribution

These are not project-specific numbers.

The effect is to associate the local proposal with the entire statewide economic ecosystem.

Tax Abatements

The slide includes an important phrase:

“Even with potential tax abatements…”

This strongly suggests incentives or abatements may be part of the project discussion.

However, the presentation provides no details regarding:

  • Incentive structures
  • Duration
  • Tax categories
  • Revenue projections
  • Assessment impacts

Jobs

The slide discusses:

  • Construction jobs
  • Operational jobs
  • Vendor support activity

It claims:

“Large facilities can create +150 long-term positions.”

However, it does not specify:

  • Whether this project specifically will create that number
  • Local hiring expectations
  • Phased employment timing

Community Partnerships

The presentation also emphasizes:

  • Grants
  • Beautification projects
  • Workforce development
  • Nonprofit partnerships

This reframes the operator as:

“A long-term civic partner rather than merely a land consumer.”


Slides 8–11 — Design Details

Core Message

These boards shift almost entirely into visual and emotional reassurance.

The central argument becomes:

“You largely will not see the project.”

Key Observations

Visual Buffering Strategy

The renderings repeatedly emphasize:

  • Mature canopy
  • Topographic variation
  • Terrain profiles
  • Tree buffers
  • Screening

This indicates the developers understand that:

  • Community identity
  • Rural/suburban character
  • Visual change

may be more emotionally important than technical infrastructure details.

Carefully Calibrated Wording

The presentation repeatedly uses phrases such as:

  • “Largely obscured”
  • “Partially visible”
  • “Screened”
  • “Buffered”

This is strategically cautious language.

The boards avoid unrealistic promises of total invisibility.

The Substation

One of the most revealing details is the labeled:

“Substation – 10.12 Acres”

This strongly implies substantial long-term electrical demand.

The size of the electrical infrastructure reinforces the scale of the overall campus.

Site Layout

The campus layout suggests:

  • Multiple large data halls
  • Internal circulation roads
  • Stormwater infrastructure
  • Phased development potential
  • Long-term expansion capability

This is clearly not a small standalone facility.

What the Renderings Avoid

None of the visual simulations depict:

  • Nighttime lighting
  • Generator operations
  • Cooling equipment activity
  • Delivery traffic
  • Security infrastructure prominence
  • Construction phases

The visual environment is consistently:

  • Calm
  • Green
  • Quiet
  • Warmly lit
  • Sparse in activity

This is deliberate emotional framing.


Overall Presentation Assessment

General Strategy

The presentation follows a highly deliberate progression:

  1. Legitimacy
  2. Normalization
  3. Fear reduction
  4. Economic justification
  5. Visual/emotional reassurance

The sequencing is sophisticated and intentional.

What the Presentation Does Well

The materials:

  • Anticipate common public concerns
  • Present a calm and measured tone
  • Avoid overtly aggressive messaging
  • Use legally cautious wording
  • Provide some meaningful technical reassurance
  • Show evidence of real planning and mitigation work

This does not appear to be a casually assembled industrial pitch.

What the Presentation Avoids

The most consequential omissions include:

  • Total electrical demand
  • Regional grid implications
  • Generator scale
  • Operator identity
  • Traffic studies
  • Construction timelines
  • Long-term expansion scenarios
  • Tax incentive specifics
  • AI compute implications

These omissions are notable because they involve some of the largest real-world implications of modern hyperscale infrastructure.

The Underlying Tension

Ultimately, the presentation attempts to reconcile two competing narratives:

Developer Narrative

“This is low-impact, future-oriented infrastructure that strengthens the local economy.”

Community Fear

“This may permanently transform the corridor into major industrial infrastructure territory.”

Importantly, the presentation does not fully disprove the second concern.

Instead, it argues:

  • The transformation is planned
  • The impacts are mitigated
  • The visibility is reduced
  • The infrastructure is regulated
  • The economic value is worth it

That is a very different argument.

Final Conclusion

The boards should not be viewed as a technical disclosure package.

They are better understood as:

A carefully engineered community acceptance presentation.

The real operational and infrastructure story likely exists in:

  • Zoning submissions
  • Utility interconnect filings
  • Environmental studies
  • Traffic analyses
  • Tax negotiations
  • Utility planning documents
  • Construction and phasing plans

rather than within the presentation boards themselves.

Jellyfin – Find Duplicate Movies

1
2
3
4
5
6
7
8
9
SELECT a.path,a.name, a.UnratedType
FROM TypedBaseItems a
JOIN (SELECT name, path, UnratedType
FROM TypedBaseItems
WHERE UnratedType = 'Movie'
GROUP BY name
HAVING COUNT(*) > 1 ) b
ON a.name = b.name
ORDER BY a.name

Random notes regarding Docker and Nextcloud (and in general)

For my own purposes, mostly.

Resetting a user account (when you don’t have smtp configured).
Get the Docker container id:

Enter the Docker container utilizing the id:

Reset the password:

Also, rescanning files:

Unmonitor Ended Series in Sonarr

Occasionally Sonarr downloads a whole old season of a ended series, I presume because someone has posted a better quality version. Normally, I don’t want this to happen, so I’d like a way to turn off monitoring for series that have ended. There’s no UI based way to do this.

Get  yourself DB Browser for SQL Lite, back up your Sonarr database (in Windows, located at C:\ProgramData\Sonarr\sonarr.db at the time of this writing), open the in use one in DB Browser (no need to even stop Sonarr), and run the following:

Then Write Changes.

Remove old machines from Mouse Without Borders

I love Mouse Without Borders, but holy cow do I not understand how it doesn’t have a function to remove old machines from its settings. It seems like a ridiculous oversight. At any rate, I figured out how to do it. This is as of Powertoys v0.83.0. As per usual, you’re poking under the hood, so be forewarned.

In Windows 10/11, the settings for MWB is stored in a .json file found in C:\Users\YOURUSER\AppData\Local\Microsoft\PowerToys\MouseWithoutBorders. AppData is a hidden dir, so you’ll either have to enable seeing hidden dirs or path to it directly. Open the file in a text editor – I use Notepad++ – and head down to around line 45. There you’ll find MachineMatrixString. Delete the machine names you want to remove from MWB and replace them with empty quotes. Head to the next section, MachinePool, and again remove the machine name and the corresponding value following it, separated by a colon (if it’s a long-gone machine from your network, that value may be NONE) and replace it with a colon. You’re going from something that looks like this:

To something that looks like this:

Note that the before settings depict 3 machines and 1 empty slot and the after settings depict 2 machines and 2 empty slots. Mouse Without Borders has 4 slots for machines. If you just delete the machine you want removed and don’t repopulate with empty values, the MWB UI in PowerToys will lock up.

In my experience you can now save this file and don’t even have to restart PowerToys or MWB. Open the UI and click into MWB or, if you were already in MWB settings, click out and back in, and your machine settings should be automatically updated.

Jellyfin – Error in Directory watcher for: “/media/movies” System.IO.IOException: The configured user limit (8192) on the number of inotify watches has been reached.

Correct this error on Jellyfin (Linux):

Debian or RedHat flavor:

Archlinux:

Pi-Hole: DNSMASQ_WARN Maximum number of concurrent DNS queries reached (max: 150)

Resolving DNSMASQ_WARN – Maximum number of concurrent DNS queries reached (max: 150)

  • Connect to pihole via ssh
  • Navigate to /etc/dnsmasq.d/
  • If 02-custom-settings.conf does not exist, create it:
    • sudo nano 02-custom-settings.conf
    • Populate with the below and save :

  • Reboot pihole

CasaOS – Upgrading Containers

Update: As of the latest iteration CasaOS has an option to “Check and then update.” However, when I ran it against PiHole, which needed an update, it came back claiming current. So… these instructions still stand for the moment.


As of the current iteration of CasaOS, there’s no way to one-click yourself an upgrade on a container. Or, rather, there is, but only sort of. It’s all about how the container installed initially.

To check, pull a config file from the container in question:

  1. Settings > choose Export ComposeFile
  2. Open the file in your text editor of choice and search for the image: line. If it says something like “latest” or “develop” you’re good to go:
  3. In this instance, all you need to do is click Save in CasaOS and the latest image will be pulled down and installed. But wait! Keep reading before you do so! If nothing else, jump down to step 7.
  4. If the image has a hard coded version number, you’re going to need to change it to “latest” and save the YAML (as a different name, or take note of the version number, just in case you find you need to revert):
  5. In the event you’ve had to  update your compose file, now comes the sweaty bit. You need to uninstall the app from CasaOS. If you’ve mapped all your data volumes correctly, this should be fine. Just remember to uncheck Delete userdata when prompted:
  6. Once uninstalled, reinstall the app:
    1. Select App Store, then Custom Install
    2. Select the Import icon on the top right and select your YAML file.
    3. All the settings will be loaded in – confirm them and let ‘er rip.
  7. Now, if you’re making a big upgrade, or an upgrade to a big app, things can get pinchy here for a bit. For instance, I upgraded Navidrome, my music server, and CasaOS barfed a message at me saying something akin to the container being unwell. I run PiHole in the same CasaOS instance, and I noticed that my browsing/DNS resolving had become profoundly slow. CasaOS’s nifty little stats didn’t show anything exciting insofar as resource utilization, but the CasaOS page was also profoundly slow and sluggish. I pulled up the terminal for Navidrome and discovered this:
  8. Now, I have a lot of music. A LOT. So I SSH’ed into my device running CasaOS and navigated to the data directory for Navidrome to discover this:
  9. Navidrome was indeed hard at work upgrading its ridiculously large database – as I refreshed I the timestamp on the db-wal file would continue to iterate.
  10. Eventually the database upgrade finished, Navidrome loaded, and the container was healthy and upgraded.

The moral of the story is, be patient! Don’t freak out if CasaOS delivers some kind of ominous warning – dig deeper before doing  something drastic, like killing a running container in the midst of upgrading a critical database. I suppose you could be double safe by making a backup of your apps data directories before attempting an upgrade. I live on the edge. I recommend going through all your containers and updating all of the ones using hard-coded versions with something like ‘latest.’

Jellyfin – Migrating Users

I’m moving from a Windows based instance of Jellyfin to a containerized instance within CasaOS, and I wanted to preserve user data (including view history). Here’s how I did it:

  • Confirm both your source and destination Jellyfin are the same version
  • Export the UserDatas table from library.db for your source instance. You can use DB Browser for SQLite to achieve this – remember to check “Column names in first line”
  • On your destination server, make a backup of library.db and jellyfin.db
  • Again using DB Browser, open the library.db of your destination server. Drop the UserDatas table and import csv created in the prior step to recreate the table (remember to check that the first line contains the column names)
  • Copy jellyfin.db from your source server and overwrite the db from the destination with it. This is important, as this file contains user history data
  • Fire your new Jellyfin instance up and attempt to log in with an existing user

 

Music

In the late 80s teenage me became enamored with industrial and electronic music – very young genres at the time. I had been listening to punk and metal and, thanks to Fishbone, had discovered funk and soul and ska, but it was my part time job at a record store that sucked me into electronic and industrial. Every week I’d dig through the promo cassettes we’d receive and take home a few, chosen solely for their album covers or titles. This is how I discovered acts like Ministry, Consolidated, Die Warzau, PWEI, Nine Inch Nails and especially Meat Beat Manifesto.

A roommate and I started cobbling together used equipment (usually purchased on layaway from the dearly departed Galaxy Music on Stone Mountain Hwy) and learning Twelve Tone’s Cakewalk sequencer – first on DOS, and then Windows 3.1. When my roommate and I parted ways, I bought out all this equipment – an ancient PC, a Roland Juno 2, two Ensoniq Mirage’s (one rackmount, one full keyboard), a Yamaha drum machine I mostly repurposed as a sample triggerer, and all the requisite cabling and MIDI garbage to tie it all together. Armed with this stuff, and an old Yamaha bass, Gibson Flying V, and a no-name acoustic, I would stay up late at night after work and create weird, kind of unclassifiable songs. By 1993 I had enough ‘finished’ material to make an album… so I did. I spent forever trying (and mostly failing) to master these tracks and tie them together. I designed an album cover, and burned exactly one CD, which I shared with no one.

I’ve held onto that CD ever since. I dug it out a few years ago to listen to privately and then – with some trepidation – shared it with my son, who was developing his own musical taste and dabbling in trying to create songs. “This is you!? How old is this? How did you do this back then?”

Listening to it over 30 years later… it’s not bad. In fact, it was kind of ahead of its time, or at least in line with what was considered cutting edge in burgeoning electronic music scene at the time I was making it. It sounds dated, but it’s also fascinating to consider that this stuff wasn’t made with a modern DAW – the samples were recorded onto 3.5 inch floppies, painstakingly manipulated and altered, mostly triggered ‘live,’ and sequenced with Cakewalk, which had only MIDI capability at the time. Many of the samples were me playing, either live or converted from an ancient 4-track cassette recorder. Making this stuff now would be easy. Back then it was insanely time consuming and complex. Much of the grit and grime and audio imperfection and degradation comes from this old process, but I kind of think it sounds better because of this. It somehow sounds more organic and lived-in than the sterile electronic music of today.

The 20 year old me was too insecure to share this stuff with anyone. I wonder what could have happened if I hadn’t lacked the confidence to put myself out there all those years ago. But that wasn’t me. I didn’t share. I quit bands as soon as I felt out of my comfort zone. I still have boxes of old 4-track tapes I haven’t listened to in 35 years – many with musical collaborators who are now dead and gone (including the aforementioned roommate) – 3 ring binders filled with art that no one’s ever seen.

But now I’m old, and we’re in a world so flooded with music and media that putting this out there is like dropping a grain of sand on a beach. My kid didn’t recoil upon hearing it so I figured, what the hell.

https://share.amuse.io/album/josefek-josefek