Can you provide a link to the source image you are actually using? I have just checked your image with the file format identification and I do not see the same bytes at the addresses shown.
Im using the full version here:
http://s3.amazonaws.com/cdn.superlumina-6c.com/wp-content/uploads/2014/05/30185102/contact.png
I personally feel there is more to the Superlumina-6c.com site than has been brought to light. Especially since the “theme” of the entire site is centered around the issues of the latest Elizabeth video. Also, the pic in the Long-range communications blog is at least superficially the same as the back ground image in the WakingTitan.com homepage when you click on the next glyph.
2 Likes
How is TriD returning a high chance for that image to be JPG and not even mentioning PNG, when this source is actually a PNG?
Edit:
My bytes at address 800-816: 2A E0 8F FE E8 8F F0 C6 D9 33 B8 72 E5 8A 7C 4E
First 8 bytes that indicate a PNG signature: 89 50 4E 47 0D 0A 1A 0A
I am not seeing that in your image provided from TriD
sorry the file format break down was from the other pdf image… The one that looks like the ship. uploaded the wrong trid file.
Ok, no problem, that clears things up a bit 
but the data bits seem to be the same… When i try to edit them in the jpg it glithes more, when i try to edit it in the png the png literally wont render past that point…
On a side note, PNG images often return false positives for mp3 marker FF FB (MPEG-1 Layer 3 file without an ID3 tag or with an ID3v1 tag )
PNG uses a checksum system of the CRC32 algorithm, which detects corruption and is therefor hard to glitch using more standard methods.
makes sense, so you cant change the bytes without updating the checksum, and all the image recovery software out there is atrocious
Something like that, yes. You would have to rewrite the data after decoding CRC32, re-calculate it and attach it to the edited data.
As for image recovery tools, most of them will not fix glitch effects as they are basically created for fixing the actual formatting in case a file gets damaged in different ways. It does not recognize a glitch effect that has been applied and sees it as correct data.
A good JPEG tool I would recommend is JPEGsnoop, although not made to fix things, it can show a lot of very useful information.
1 Like
Were you aware of a post on the reddit waking titan megathread thread discussing the aspect of viewing the contact page in ie8 which revealed items not available in ie10/11? He used ie8 as the browser because it was of the version used as the dates given on the web page. His username is timetravelbeard.
1 Like
I don’t know if this may aid you in analyzing the png
I will have a look, assuming this is the comment in the Waking Titan Megathread you refer to:
That is the one.
1 Like
My background is structural design, which gives me experience in trouble-shooting and problem solving. I also play NMS and find this ARG intriguing. I hope I can provide something worthwhile.
2 Likes
Looks just like WordPress left-overs as someone else stated as well. Some of the old dates he finds come from themes/plugins used, like this eCommerce plugin that comes with the Pexeto theme ‘Story’, which is the main theme that was used creating Superlumina:
Comment on Protected: Order – June 17, 2014 @ 08:39 PM by WooCommerce
See WP theme here:
http://pexetothemes.com/demos/story_wp/
I bet you will recognize the front page scroll.
Running into password protections also has everything to do with WordPress. I would not even suggest trying to crack these protected pages. Does not look like there is much of interest to be found.
1 Like
The Data Compression For NLTT pic glitch and the Data Compression For NLTT title glitch on the Data Compression For NLTT page itself be a clue relative to data compression?
There are three glitching entities on the site;
- Data Compression For NLTT pic on the main blog page
- Data Compression For NLTT title on the Data Compression For NLTT blog page
- Infamous Contact page pic
Could these be a composite clue?
I think they were just placed there by the Atlas Foundation to point out clues, the same way glitched areas were found in previous sites.
So, the obvious next question is what is the clue(s)? Are they graphics based? Code based? An aspect of the text itself?