Talk:Sloot Digital Coding System

message: This is literally my first major article clean-up so please go easy on me.
I had some colleges translate and verify some translations of the wikipedia article as well as their sources where available, and re-wrote some major portions of the article.  A few notes:
* The source text literally says, translated, ... Sloot moved to Utrecht where his wife was also from. ... I don't know if this some dutch phrase meaning he met and married his wife or literally they're just saying "his wife was also from here so that's why they moved".  Anyway, it doesn't seem that relevant anyway so I didn't press on to figure out what was meant.
* I don't know really what happened between Jos van Rossum and Sloot.  Some texts say the partnership, directly translated, "stranded", "ended", "was deserted".  I don't know if the partership went sour, or if it simply just ended on good terms, or if Rossum ran out of money, etc -- no sources to back up anything other than the business partership ended.
My edits are mainly a mashup of the German & Dutch Wiki Pages and their sources, translated by Google, with some human assistance translating / verifying but I know zero Dutch/German and none of my translaters were native, ... so they aren't perfect.  I likely introduced some inaccuracies.  I'm going to attempt to find a better translater and clean it up further.  Among some claims I left out for one reason or another:
* There seems to be some agreement that Sloot is the subject of conspiracy theories, but there really aren't any reliable sources to say that, and given the nature of the claim I left it out, pending some sort of reliable source.
* Can not figure out a reliable timeline of the guys job's pre-1995.  Some have sources, some don't, -- I put it together with reasonable certainy that it's accurate but may not be totally perfect.
* Same with the company name's post-1995.  Dipro, Davoc, are among the company names that seemed to float around Sloot, .. I just left those out because no source / no clue, but the rebranding as The Fifth Fource is a certainty.
The last couple paragraphs don't flow together very well, -- they could be written better, but they are better than they were. 
Probably most importantly, little attention is paid to the technical detail and implausability of the system.  I will try to clean this up later.
nezZario (talk) 08:02, 9 June 2017 (UTC)
thread_title: 2017 Cleanup

message: A Dutch "hyve" about his invention.
http://de-broncode.hyves.nl
http://jan-sloot.hyves.nl
The above URLs point to a game website, now. Somebody should check with the way-back machine.--37.182.149.65 (talk) 23:13, 12 September 2016 (UTC)
thread_title: Untitled

message: "this is orders of magnitude greater compression than the best currently available technology.[when?]"
That When? tag is meaningless. Whoever put it there wants to know whether Sloot's claimed performance was better than 1999 tech, or 2012 tech. But because what he claimed isn't possible, it's better than any tech that will ever exist.173.58.37.123 (talk) 12:05, 10 November 2012 (UTC)
thread_title:  When? 

message: Mr. Van Wijck above said there was a patent. Can it be linked to in the external links section?
--37.182.149.65 (talk) 23:18, 12 September 2016 (UTC)
thread_title:  Patent 

message: he has said "its not data compression"
"recipes can be transferred without the data actually being transferred"
So basically its a signal telling the computer to use software that is already on the computer but its broken down so you cant access it even tho its there.
So either he was doing a scam or looking for fame.--Apemonkey1 (talk) 07:26, 10 February 2019 (UTC)
thread_title:  "data compression " Was it? 

message: "The full source code was never recovered"  The company had the patent so it was never lost!
The company was headed by the philips guy had the patent which was granted in 1996 for 6 years so lasted 6 years after his death! Sounds like conspiracy nuts have been here! --Apemonkey1 (talk) 07:35, 10 February 2019 (UTC)
thread_title:  "The full source code was never recovered"  The company had the patent so it was never lost! 

message: Do anyone has the book? Can you please translate it and/or share the ebook version?
Need as many informations as possible to deduce the principles used by the system itself.
The patents are actually messy that whoever studying the patents need to re-read it again and again for different interpretation.
There's a problem with the second patent. By using first patent as reference, the so called reference memory in the second patent seems to refer something that is entirely different that what was told to the public.
I'm pretty damn sure it's not used to store the so called *all possible values* as external storage to be used by all other devices (this misleading part screwed up almost everyone's brain). It's used to compare image blocks. Comparing color values between 16x16 blocks(single block of 16x16 - each p has 256 colors), comparing pixel in the block with other 2560 blocks (single frame - 2560 blocks, therefore each p has 2560 colors) and comparing pixels in the frame with other 39 frames (compare current frame with OLDER FRAMES. 40 frames - each p has 102400 colors, 1 pixel in a block x 2560 blocks x 40 frames = 102400 colors). It works the same way as 'indexed color' method in order to reduce the redundancy but do not consider it is 'indexed color' method. The reason why to not consider it as the same method as 'indexed color' method is because you need to know that Jan Sloot seems to be messing with something that is in a different league. His methods seems not limited by binary data limitation (as in bit and byte size, file size). Therefore, you need to think that, the indexing methods he used didn't even consider file size into the equations. With this clear, you can try thinking something different instead of repeating the same thinking process again.
The difference between first and second patents is that, first patent is the single image version of the system (and also older) while the second patent is the video version (and newer). Therefore, you can use first patent as reference to analyze the system. Once you do that, you will notice that, there's no so called reference memory in the first patent. Why do only the second patent has the thing called as reference memory? It's obvious that, it is used as temporary storage to reduce redundancy for video version where you need to store some frames to reduce redudancy according to Jan Sloot METHODS before applying algorithms and code those resulting data into smaller key.
By using reference memory, he reduced redundancy in image sequences. Then, with his KEY decoder, he reduced duplicates in data. Please remember this before any of you try to analyze the system again.
So... Please stop spreading the words where "all possible values is stored into the reference data" which is misleading. That is one powerful trap that prevents people to try thinking about this illogically.
Since the system is not about compressing data, my speculation about the system after considering all these informations I know is that, the system either use some sort data structure that use block code as coordinates to rebuild the data or numbers to be used in bunch of formulas similar to analog signal to rebuild the data. I'm a bit skeptical about the latter method because if it's true. then people would have already reproduced the system by now. Therefore, I'm more inclined towards the former method where some sort of data structure that doesn't use INDEXES but COORDINATES to rebuild data. This might be the unknown region. The prerequisites would be that, there must be a lot of small redundant sections and the coordinates data must be small. I could be wrong about the prerequisites. This is after all, just a speculation of mine. There's too many stuffs that is missing. The book might hold the informations SOME people needed. Especially on how to ignore the binary limitation. (Please don't talk on how binary limitation is not a limitation. That's bullshit. Else, Kolmogorov Complexity is a hoax)
I don't care how you skeptics think but, do not force me to think the same way as you. There's a lot of problems with Jan Sloot's case. Most of skeptics seems to be younger generations. In the old time, video buffering was a pain in the ass to wait for. It's not as fast as what you can see today. This makes the fact that playing 16 videos at the same time is a big problem for you to ignore. That's ONE. Every investor involved are fully aware of the old technologies limitations. That' TWO. That's all. <edited: I remembered my third point wrongly, they didnt take a look at the box, but listened for harddisk sound. http://www.gids.nl/techno/jan-sloot.html>
I myself aware about the limitations on data size all of you skeptics mentioned. That only applies to binary data. Is it not? Is it wrong to try consider something that works outside of your knowledge? OUR problem is that, IT IS TOO HARD for us to try and think about stuffs illogically. I think this might be a long-term problem.
Sorry for any grammatical mistakes since I'm not good with language you see.
Whoever read this and still analyzing the system, I hope that, with the informations I shared here, can help you try solving SCDS with different methods this time. Too many people stuck on the same problem known as "all possible values" for many years. SDCS smells something that's not limited by bit size.
Someone please translate "de broncode" book and share with us.175.143.213.79 (talk) 05:33, 2 March 2019 (UTC)
thread_title:  Need Translated De Broncode