Hol up, Layer 8 Era. Imma let you finish, but there’s a lot going on in this one, so I figured we needed a table of contents.

Public Cloud

Like AWS but built on excess compute resources that people are rewarded for contributing.

Functional Management System

Managing all of the work to make these things happen and rewarding it accordingly.

The Free Market

Place to exchange goods and services with a crypto currency that’s worth $0.

Metadata Content Type

We need a better way to manage data, so let’s establish a single source of truth.

Content Moderation Jawn

We also need a way to moderate data so sick fuckos don’t create degen shit.

Something Something Crypto Something

Yea, yea, I know…tech bros ruined this one. But, I swear, there’s still hope!

Single Sign On

Aggregate, control and prosper from your personal data instead of Google.

Some AI Thing

Obviously we need some AI thing instead of the closed source nonsense.

Thank you, the internet. Also, Kanye Swift is kind of beautiful, no cap

Thank you, the internet. Also, Kanye Swift is kind of beautiful, no cap

So, there’s an old joke in IT that the most terrible issues are always “Layer 8 errors”, i.e., user errors.

Similar to a PEBKAC error - Problem Exists Between Keyboard And Chair - it’s another discrete way for a tech person to make fun of you lowly mortals.

Sort of like this:

Thanks, Dilbert

Thanks, Dilbert

To understand the layer 8 error and, eventually, the point I’m getting to, there is this thing called the OSI Model (Open Systems Interconnection) which describes how the seven layers of the internet function, from the physical servers, aka THE CLOUD, to the application, with all the magic doohickeys in between.

This terribly boring graphic was genuinely the least boring graphic of the OSI Model I could find. Also, the first.

This terribly boring graphic was genuinely the least boring graphic of the OSI Model I could find. Also, the first.