Neuralpedia 1.0 : Complete
The first draft of the Neuralpedia
Hi there! There is a lot more paywalled content coming down the pike in the next few days (See n' Touch : Moo Oink Squawk , haptic , new episode.) That's the stuff you're here for.
This project is essential infrastructure for new releases, though.
I have been releasing content at least weekly for many years. The complete sprawling discography is over 600 files. It’s the most extensive in its category, depending on how you do the math. Top 10 by any measure I can conceive.
I’m proud of that. Still, saturation is a big risk unless I improve navigation. Bliss Blank has angelically maintained the Neuralverse spreadsheet. I am indebted. I also need to do some automated content organization and delivery.
The Neuralpedia is one step in that process. I used the podcast page to host it. I hope to expand with an independent github -> pages setup soon, and then a distinct content delivery system. One step at a time, though. This is a good step. It was a heavy lift.
The Neuralpedia does the following:
- Catalogues (almost) all content to date, with dates, lengths, themes, and series
- Organize existing content into over 50 series. Some are sequential, such as the Deep Dream State and Augmented. Some are thematic, such as “Mouth Time.”
- Organize content according to technical features such as “haptics”
- Organize content by preference filters, such as fd
- Places all of the content data on the open web
- Creates the foundation for a database driven UI for you
The Neuralpedia does not:
- Create a record that is free of errors. This will occur over time, but there are gaps. I’m fixing a lot of it, and propagation can be slow, so give it some time to settle.
- Substitute for content warnings. I want the content organization to be publicly accessible. Interstitials are annoying and they're not necessary for an organizational project. I’ve kept the descriptions minimal and politely phrased. My first “series” page was frankly insufferable, so I stripped it out. I’m keeping descriptions minimal while I figure out how to best balance description and safety!
- Anticipate every vector of interest. That’s impossible. I aim for comprehensive, but it’ll never be exhaustive.
I think this is exciting. It’s not new content – that’ll come out rapidfire now. Steps to a Patron-oriented content system, though, will do a lot to improve your experience. I am thankful for you!
