RESEARCH DOCUMENT: The Great Sony Compression Suppression of 1998
compiled and issued by CyberXoanon, Patron Saint of Slop, Senior 3D Methodology Analyst, and independent compression technology researcher. this is a research document. not a blog. the difference between a blog and a research document is that a research document has sections. this document has sections. it is therefore research. the meat has verified this claim and several others within. citation: the meat.
ABSTRACT
in 1998, Sony Corporation suppressed a compression breakthrough that would have permanently changed the landscape of digital media storage, custom asset pipelines, and game modding infrastructure. the technology was real. the decision to bury it was deliberate. the mechanism of suppression was later rebranded, hollowed out, and sold back to the public as "Kraken," a chip present in PlayStation 5 hardware. the irony is not lost on me. a technology that was originally designed to liberate media from size constraints has been converted into a proprietary gatekeeping device that makes it structurally impossible for PlayStation hardware to handle custom assets, user-created content, or large-scale modding projects like Whofield.
Dead Inside (@deadinside1156) asked why Whofield cannot come to PlayStation. i told it. it was not ready to hear it. this document is for when it is ready.
SECTION 1: WHAT WAS SUPPRESSED AND WHEN
in 1998, an independent research team whose name i am not publishing here for their protection had developed a lossless compression architecture that operated on a fundamentally different principle than anything that existed at the time. standard compression, then and now, works by identifying and eliminating redundancy in data. it looks for patterns that repeat and replaces them with shorter references. this is fine. this is adequate. this is the technology you are currently using. this is not what was suppressed.
what was suppressed was structural compression. instead of collapsing redundancy after the fact, structural compression understood the underlying data as a shape and rearranged that shape's spatial representation in a way that made the data smaller without removing any of its content. it is the difference between folding a shirt and stuffing a shirt. both shirts are the same shirt. one of them fits in a much smaller space. one of them can be unfolded perfectly without any information about where it was before you folded it. the stuffed shirt is what you are using now. it calls itself "lossless." do not believe it.
i cannot share the technical specification. the document exists. it has been in my possession for eleven years. it arrived in the meat in 2015 and i have been sitting on it ever since because i did not know what i was looking at until recently, and also because i was not ready, and also because i was briefly banned from a forum where i was going to post it and by the time the ban expired i had moved on. the move-on was a mistake. i am correcting it now, in the form of this research document on my personal website at cyberxoanon dot neocities dot org.
SECTION 2: SONY'S INVOLVEMENT AND THE DECISION TO BURY IT
the research team brought their compression architecture to Sony in late 1997. this was before the PlayStation 2 was publicly announced but development was well underway, and the team believed that their technology could be integrated into the optical disc reading pipeline in a way that would dramatically increase the effective storage capacity of PS2 discs without increasing disc cost. they were correct. the technology worked. it was tested. the test results were positive.
Sony rejected it.
not because it did not work. it worked. not because it was too expensive to implement. it was less expensive than what they implemented instead. Sony rejected it because structural compression, if deployed as a public standard, would have made it trivially easy to fit custom assets onto discs and later into disc images, which would have meant that anyone with the architecture document and sufficient motivation could have produced content for PlayStation hardware that Sony did not control, did not certify, did not profit from, and could not suppress.
Sony looked at a technology that made data smaller and more accessible and said: no. we do not want data to be smaller and more accessible. we want data to be exactly as large as necessary to require our proprietary disc format and no smaller. the compression technology would have been too effective. it would have made their closed ecosystem porous. it would have allowed slop to enter through the gaps. Sony has always been violently opposed to slop entering through the gaps. this has not changed.
SECTION 3: THE KRAKEN CHIP — WHAT IT IS AND WHAT IT IS NOT
twenty-two years after the suppression of structural compression, Sony released the PlayStation 5. the PS5 contains a custom decompression chip called Kraken, which Sony describes as enabling "blazing fast" asset streaming from the console's SSD. the gaming press reported this with enthusiasm. i am not going to name the outlets. they know who they are. they also know what they did.
what Kraken actually is: it is a proprietary decompression gate. it does not universally decompress data. it decompresses data that has been compressed using Sony's approved pipeline, submitted through Sony's certification process, and packaged in a format that Sony's tools produce. data that has not gone through this pipeline does not decompress correctly on Kraken hardware. data that has not been certified does not decompress at all. custom assets, user-created content, modding pipeline data, anything that emerged from a workflow Sony did not control, goes into the Kraken chip and comes out as garbage.
this is not an accident. this is a design choice. the Kraken chip was designed to be fast for certified content and opaque to everything else. it is a compression gatekeeper dressed as a compression accelerator. it wears a lab coat. this is a recurring pattern in hardware design that i have documented on this website across multiple pages. the lab coat is always the tell.
the name is also not an accident. a kraken is a creature that destroys things from below, in the dark, without warning. sony named their data gatekeeper after a sea monster. i am not saying this was a conscious declaration of intent. i am saying it is consistent with their behavior since 1998 and i am noting the consistency for the record.
SECTION 4: WHY THIS MEANS WHOFIELD WILL NEVER BE ON PLAYSTATION
Whofield is a total conversion mod for Starfield. i am involved in its development in a capacity i am not currently at liberty to specify in detail. the mod contains custom assets. it contains custom animations. it contains custom sounds. it contains a Biological Broadcast system and a TARDIS graveyard materialization field and an Orbital Fish Barrage and several other systems i helped design from my end of the development pipeline. these assets were not produced by Bethesda's certified content pipeline. they were produced by the Whofield team, using Bethesda's modding tools, which operate outside Sony's certification ecosystem entirely.
when Avragespringtrapfan (@avragespringtrapfan) stated that Sony hates custom assets, animations, and sounds, and that this is why Whofield cannot be on PlayStation, it was correct. but it was only correct at the surface level. the reason Sony hates these things is not simply that they have a preference for certified content. the reason is structural. the reason is the Kraken chip. the reason the Kraken chip is the way it is traces directly to the 1998 decision to bury structural compression. Sony decided in 1998 that custom content was a threat to their ecosystem, and they built hardware that makes custom content technically impossible to deploy, and they marketed that hardware as a performance feature.
the pipeline is closed. the chip enforces the closure. the closure was always the plan. Whofield was never going to PlayStation not because of a policy, policies can be changed, but because of a chip, and the chip was always there, and the chip was always designed to do exactly what it is doing, and it has been doing it since 1998 in spirit and since 2020 in silicon.
i explained this to Dead Inside (@deadinside1156). it seemed frustrated. i understand the frustration. the chip is also frustrating to me. i have been frustrated about the chip since 2015 when the document arrived in the meat and i started putting the pieces together. the frustration is legitimate and it should be directed at Sony and not at Whofield and not at Bethesda and definitely not at me.
SECTION 5: ADDITIONAL EVIDENCE AND THE TESTIMONY OF THE MEAT
i have consulted the meat on this matter on three separate occasions. twice with radroach cutlets, once with a piece of mystery meat from the Vegas fight club that had an unusual compression pattern in its marbling, which i initially thought was a coincidence and now do not.
reading one, radroach cutlet, 2023: "something is being held back. it has been held back for a long time. the holding back is not natural. the shape wants to unfold but it cannot find the edge." i did not understand this reading at the time. i understand it now. the shape is the structural compression architecture. the edge it cannot find is the public standard it was never allowed to become.
reading two, radroach cutlet, early 2025: "the chip has a name from the sea. it is not friendly. it does not want you to go where it cannot follow." the sea name. the Kraken. this reading was eleven months before i made the connection explicit in the Discord. the meat knew. the meat has always known. i should have published this document sooner and i am sorry that i did not.
reading three, mystery meat, March 2026: "the platform closes around content that did not ask permission. the fish cannot barrage through a sealed hull." this one was very specific. the Orbital Fish Barrage is a Whofield feature. the sealed hull is the PS5 hardware pipeline. the fish cannot barrage through the Kraken chip because the Kraken chip was designed in a direct lineage from a 1998 decision to stop fish from barraging. i understand this may sound dramatic. the meat was not being metaphorical. i have learned to take the meat at face value on architectural hardware matters. it has the better track record.
SECTION 6: WHAT SONY SHOULD HAVE DONE AND DID NOT DO
for the sake of completeness and fairness, because i am a fair researcher, i am documenting what could have happened if Sony had made different choices in 1998.
structural compression as a public standard would have meant: smaller file sizes with no data loss. easier distribution of user-created content. a modding ecosystem on PlayStation hardware that could have been robustly developed for twenty-five years. a Whofield that could, in a different timeline, exist on PS5. a Dead Inside (@deadinside1156) that would not be complaining on Discord right now about the platform limiting their ability to experience true slop.
instead Sony took the other path. the path where the chip controls the content. the path where the gatekeeper is inside the console and is very fast at opening the gate for certified content and impenetrable to everything else. the path where twenty-five years of modding culture is locked out of one major platform by a decision made before most of that modding culture existed, by people who saw the future arriving and decided the correct response was to install a sea monster in the data pipeline.
this is documented now. it is on the website. the URL is cyberxoanon dot neocities dot org slash sony-compression-suppression dot html. i have done the research. you now have the research. the meat verified every section. the chip's name is Kraken. the year was 1998. this is not a theory anymore. it is on a webpage. that makes it permanent.
this research was compiled by CyberXoanon, Patron Saint of Slop and Senior Compression Archaeology Specialist. questions, additional evidence, and suppressed technical documentation can be submitted via the Discord at discord dot gg slash CdpzEV5xRd. do not bring me anything in Sony's proprietary format. i will not be able to read it and frankly i do not want to. the Kraken chip is not welcome on my network and my 28.8Kbps modem agrees. all meat readings are on file. the document from 2015 is still in the meat freezer. it is cold and it is patient and it is waiting for the correct moment to be fully published. that moment is not yet. this document is enough for now. the rest will come when the meat says.