Anyway, I posted it on bluesky with the #GlitchingReality
1 Like
2 Likes
I know sometimes when you post a link to an image, the system will do this and save it locally in case the url becomes invalid in the future, for archival reasons…
But the band going through it on the left side is certainly strange 
As is your repost without context 
Our collective inability to remember what has even occured here, certainly fits in to the kind of things the architect wanted us to report to fellow operators, so this definitely falls under the #glitchingreality umbrella… if not the #mandelaeffect umbrella.
3 Likes
are you able to get ahold of that image on the left with the band through it?
Don’t worry about it, it looks to be using the identical source url to the one posted by @Morse. It may have just been an accidental copy/paste as you were trying to post it elsewhere.
It was also posted here: June 1 2026 - Structural Analysis - London Reality Glitch - #272 by DetectiveGamerTreg, however with a different source url.
And as @toddumptious mentions, the system does use locally sourced copies of images. I am however not quite sure why it would show as an actual edit if you do not even recall posting it in the first place. Makes an accidental copy/paste seem unlikely.
Is this some sort of diff? Is the artifacting on the left image normal for this kind of log?
Just seems to be an effect applied on top of it by the website, as the image itself isn’t altered
Guess it’s to indicate the edit ?
2 Likes
That’s so trippy. Thanks for looking anyway!
Don’t make me get dressed and head out again tonight to check. I got work at 4am tomorrow 
4 Likes
Maybe it was an accidental copy/paste after all, then the system realised it was the same identical image, so instead of creating a local source again, it decided to adjust (edit) it to the existing url it matched with, but leaving the previous somewhat affected with the banding?
Looks like one is lower res. Might be a compression thing from it being uploaded?
Ah, it’s possible that Discourse removed the linked photo and replaced it with its own, local copy. I suspect you may have originally pasted the link to the image at project-skyscraper.com and Discourse “helpfully” converted it to just the image since there was nothing else at the link.
Maybe you’re right, but I’ll stay very doubtful, I received the notifications for the likes only less than an hour ago, even though they appear to be from the 1st june
That’s why I found this post.
1 Like
In this reply I see the top image using the same url as I mentioned earlier: June 1 2026 - Structural Analysis - London Reality Glitch - #272 by DetectiveGamerTreg
the e3abe96c79674e994c569680ed5df567a675f382, while the one below now comes up with a completely new and third ID 853d4734283d31110ac8f60114604eecf5d6820f
While the actual source from @Morse used f0507b62dbfaf539fbc8039d428b9f05a3ede031, which your initial repost also linked to: June 1 2026 - Structural Analysis - London Reality Glitch - #181 by AlexWinter
The ‘system’ works in mysterious ways I guess. I give up on trying to learn more about this investigation. I’d rather go with the ‘there is always time for one more …’
Final edit:
Apparently there is one original file (853d4… 375 x 500) and the others are optimized versions (e3abe… 562 x 750 and f0507… 562 x750)
5 Likes