16 minutes (960 seconds) also comes up in the questionnaire at the start of the expedition. You are asked, “if you had 16 minutes to live…” which feels potentially thematically relevant.
there seems to be a lot more movement going on now…
Oh wow yeah, the web is really animated this time!
I see only 34, and not much movement. A few minutes ago when it was at 200 it was moving pretty erratically.
Yes. It has slowed down. I dropped from 235 to 27.now back up to 34. Seems movement changes with the connection attempts
Using CTRL+mouse-wheel to change zoom in Chrome causes the dots to move faster and faster…
also if you are on the dot that change’s the other lines colors, they get more slow
16 is a reference to spoilers in NMS
Speed is fluctuating no matter the connections. At 16 and moving quickly now
That security log is in the System Filtering platform, which was the one that changed from activated to cavitated.
There were a few meanings of cavitation given, do any of them match looping? The propeller one?
sorry, too many posts to look through for this info; did you guys do something to fix the quote on project skyscraper?
Yeap, we sent the correct poem
was that the POST you were talking about a while back?
No it was “sending messages” through social tags on Reddit, here, bluesky, and X and tagging @the_architect
thank you so much ![]()
The Royal Flying Corps (RFC) was the British Army’s air service, founded on April 13, 1912 (!!!), responsible for the first military aviation operations in the United Kingdom. The RFC played a decisive role in the First World War and served as a direct precursor to the Royal Air Force (RAF).
Btw if we need to activate the reboot, should we tell the NMS community, if this turns to be official, that could mean, that rebooting, might give them a buff, or a debuff ,we don’t yet know who were looking at logs for right? hurting atlas, or void mother or maybe the players?
also US-GB-ES-FR-MX-DE-CA-IE-BE-AU could be a cypher (the IP logging page)
@the_architect sudo shutdown -r now
Given that the system filtering platform appears to have been denying access to connection attempts (and have been awakened by the WoL), perhaps the forthcoming scheduled connection attempt will actually succeed with the system rebooting the filter during the upcoming connection attempt window?