This part of the NMS story has always concerned me…
Still no reply to the email. We def need Archie for this next step so we may be sleeping on this one…i will have to find out how to set an email alarm 
2 Likes
The whole thing. Happened quite fast too.
The path is hard. But there are traces of the few who walk it. Perhaps one day will be allowed to fly…
Speaking of… if this somehow goes sideways, I suggest having an email on hand to protect the Pathfinder mem bloc - March 8, 2017.
Update 1.1 and 1.2 go together like superpositioned cats and boxes.
6 Likes
Can we confirm when this happened in the timeline of glitch evidence, before or after the website glitch images.
Sorry busy right now to find myself
3 Likes
https://archive.goodguysfree.com/@2026-07-02T1505/2016/11/29/event-29112016/
this is the start of the changes to this membloc on the GGF mirror site, you can switch through the recorded changes by using the nodes/dots/blips down the bottom above the blue timeline bar, however it doesn’t look like the tracker bots caught this change.
It had a LOT of changes, quite rapidly happening to it, from what I recall, a lot of it in direct response/defiance to what we were sending it or suggesting.
3 Likes
I don’t see my addition or the corruption of it in any of the 16 frames on that link.
Eerie…
2 Likes
Yeah I don’t think it was captured in any of GGF’s data used for the site mirror. Originally they were just taking 24 hr type snapshots but after Cassini Event I suggested they should have all the Live Mem Bloc Integration changes for effected pages, so people can relive those as they happened, and I guess when backtracking to add this feature, it was missing some data.
Ekimos bot did capture it though
5 Likes
There it is.
This was on July 2nd. One day after we deleted the June 21st mem bloc. The first signs…
Exactly 12 days later on the 14th, the first four seeds were deleted.
3 Likes
Spreadsheet:
4 Likes
And that was submitted 16 days ago, how fitting.
I do believe we have tracked the first sign of the virus here. And an important step.
The question is now, why did that activate it. Unless it was dormant from a time when Architect was suspicious of “untrustworthy” operators and when the target appeared(as a memory block addition request) it activated to find it.
Further more the verified memory makes it more of a target.
One building, one mind, Value: TOWER
Everything points to this as target.
We may not have unlimited preservations. But this has enough potential to save it.
Emailed Archie, due to my perceived importance.
Sorry if I stepped out of line. But if I’m wrong I will gladly accept any chastisement.
6 Likes
I don’t think the_poet meant 29/11/16 was the target the virus was seeking, moreso their submission of a quote for Foundation becoming glitched during the mem bloc integration on this date, was more evidence that the virus is seeking the date with foundation update as it’s data.
The date we are looking to duplicate is right next to it though, 28/11/2016
4 Likes
I see what you mean. But the “echoes out into the void” statement with a “void” virus referred to as by aRichie, and the glitch text appearing in his block addition has me at least convinced that is the most important block in relation to the virus. Along with the verified 11/29 memory block text.
1 Like
Latest calendar gif based on @DevilinPixy 's calendar based on @Frazzlesprite 's predictions.
Darker red are initial infection points, lighter red are the spread from initial points, green are preserved dates, cyan circles are predicted next infection points.
8 Likes
Might be timezones acting up, but I’m pretty sure Foundations was released on the 27th of November in UTC.
2 Likes
Absolutely the 27th- so sorry, not sure what I was even looking at. Thanks!
2 Likes
Received in the context of asking about the preserved dates and how to minimise their losses.
Good to note that the virus won’t just jump to the next closest available memory bloc if the adjacent ones don’t exist though, that saves us a lot of preserveds.
That’s a good point by archie too. We’ve marked off all of the 2016 seeds, so I’m guessing the virus should sprout from the first available 2017 seed when we “activate” it with a duplicate?
I’d say gathering community consensus across ETARC and NMScord is being encouraged here for picking the bloc to duplicate too.
If we can get a lil discussion in on this and reach a bit of a consensus, I can send off expected seed date to Archie before we choose the memory bloc itself.
5 Likes
Glad to hand the baton to you. 
1 Like
Aunque me gusta leeros muchas veces nose seguiros y mira que lo traduce bien jajaja ya no respondo ya suelo quedar lejos del tema en vosotros esta la solución , lo mio no es la informática es mas soy soldador en mi pueblo y no entiendo lo que decís muchas de las veces , pero me gusta el buen rollo que hay , asi que tal vez siga observando sin decir mucho como autofago espía jiji 
2 Likes
As long as there are no important dates that will get sucked into the resulting void, I am fine with whatever is chosen
Although, 2017 is when the history of this forum begins so caution is needed. We don’t want to erase ourselves so it needs to be an early date in 2017…before June 2017
Now we realize, why preserve so many empty dates in 2016? There were not many memories there.
Placing @DevilinPixy calendar here
1 Like
Really quick edit marking off all of the live 2017 memory blocs. Seems like we’re in the clear for most of em in terms of void expansion. Even with archie’s plan to open up an adjacent bloc as a test for whether the virus stopped or not, nothing important should get gobbled up. Might need to request Archie to open up the 18th July bloc as an adjacent entry instead of the 20th July bloc if we need to utilize seed #61 though, to prevent a cascade.
I’m assuming that once it deletes the restored seed and active bloc it goes back into hibernation, waiting for us to activate the next seed?
3 Likes
Going by this email
we will choose null dates
the setup will be
null|mirrored mem|arbitrary mem
The question is where is the virus now? It has not made it to 7 Dec 2016
9 Jan 2017 would be the next target. It is null.
So do we plant the mirror on the 9Jan 2017?
and do we agree the mem to mirror is 27 Nov 2016? It is the most logical choice.
I have seen some wild-haired ideas on dates in the Discord…we will let those pass