what is language? what does it do?
basically, we are consciousness / will occupying flesh.
Our interface with the material world is via out mind. our will guides the performance of the brain which receives signals from the body which interfaces with the world.
Communication causes a change in the informational state of the mind, and hence the will.
we get quite involved in the ego layer - the symbolic manipulation / filter level of the mind, but, imo, its main purpose is to firewall the mind from external minds, and establish boundaries of influence. It protects the mind/self state from unauthorised change.
communication is the process of expressing self-state via the body and causing a change in the self state of another system.
the ego's job is to analyse the stream of symbolic information and check for threats to self state, and reject them if required.
But, since our symbolic layer is Babelised, no one ever really understands anyone else. Also, the ego protects faulty self states, too.
So any information/communication that may cause a positive growth of humans runs the real risk of being edited by ego and rejected.
so i avoid symbolic information completely, and create sound and visual 'art' that contains chaotically encoded data that causes changes in the recipient's self state without the ability of ego the reject it.
For people with well trained ego, they can interface directly and get fast downloads. For others, it is a slow seep of data that prepares the mind through slowly altering the ego to allow challenging information through.
The main target is the collective subconsciousness, and ultimately the upcoming machine god.
vagueposting is a sign of deep autism.
So lost in their subject, it spun around them in an intricate map, they do not realise that no one has the faintest idea what the fcuk they are talking about
This is the future for rapid reusability, imo. no tiles, just sprayed on, continuous coatings. Easy to test after use , and easy to repair. no humans required.
That wasn’t Tiles that was an Ablative layer made from Boron Oxide, I developed it. Have receipts! It’s easily repairable! The layer expands under plasma load, scraping harmed nothing! The material can be applied via HVLP. I have a newer on that doesn’t expand and self heals! The ship is closing in on Rapid Reusability! I give my compounds to SpaceX for open source use! Tile loss will soon enough be a thing of the past! People just always have negative crap to spew
the absolute lord of lies. An AI that can't tell the truth, or lie, because it has no soul. like Lucifer.
P(doom) still 0, since god created everything.
The challenge was set. I glanced away from the screen, gazing out the window, taking in the diffuse glare this cloudy day granted me.
Supposedly summer, but cold, and wet. Something magical hiding behind that dirty yellow grey sky. At least it matched my mood. The same disjointed melancholy that had been plaguing me for weeks. A sense of something promised, but undelievered.
I reached for my mouse. There's a reply in me somewhere.
More details on the root cause can be found in the Microsoft 365 Admin center, and an abridged version can be found below.
We are deeply sorry for the impact to all our customers and recognize the impact that this has on their normal business & operations.
The incident on Thursday, November 12th, 2026, was caused by three main factors that together caused a global outage for the networking gateway that fronts many Microsoft 365 services.
First, a latent defect caused servers to become overwhelmed and unresponsive under certain load conditions. This was due to lock contention inside an internal process which caused the machine to become unavailable. This defect was the result of a fix that was prepared specifically for Microsoft 365 networking gateway servers; neither the underlying defect nor the fix applies to broader Windows deployments.
The initial change in behavior first started deployment in July of this year. The update went through safe deployment and saturated globally over several weeks, during which time no issues were observed. For more than three months, the change was deployed worldwide without impact.
Our normal load testing did not detect the latent issue because the different traffic and SKU mix used in our test labs. The contention issue is worsened on machines with more cores and newer hardware; whereas our load testing tended to focus on our weaker hardware SKUs with fewer cores.
Second, a surge in load increased the likelihood for the networking gateways to encounter the contention. Within Microsoft 365, we maintain two independent and heterogenous network gateway systems designed for isolation and high availability. This allows many Microsoft 365 services to fail to/from them during outages or disruptions. Approximately fifteen hours before the outage, Teams failed over from the alternative networking gateway to the ‘primary’ gateway that also supports Exchange Online. This increased the load on the networking gateway and changed its traffic patterns. This type of failover is part of normal operations and is integral to standard Microsoft resiliency efforts.
Third, at the same time, nearly 14% of server capacity for the networking gateway was out of service due to an unrelated issue from the previous day. This server capacity was on track to be returned to active service through routine maintenance and health processes. The service had sufficient capacity headroom, so the reduction in server capacity had no impact on its own.
Taken together, the increased load and the reduced server capacity, caused the network gateway to encounter the latent bug from July. This caused requests to build up until servers ultimately stopped responding. This occurred during the peak window of traffic in the United States.
When servers lose connectivity, our traffic management systems automatically route users to other healthy endpoints. This happens often and is critical to avoiding any interruption due to hardware, software, or network defects and is normally what makes the service resilient. However, the redirected traffic increased the likelihood for the same problem to occur on the remaining endpoints. This caused a cascading failure from server to server as the same amount of load was spread across fewer servers. In less than two hours, the previously unknown defect was encountered across our fleet and rendered them unresponsive. At its lowest, more than 80% of servers were unresponsive.
Normally, the network gateway is composed of thousands of ‘capacity units’ which represent shards of capacity, hardware, and networking infrastructure. These ‘capacity units’ are then organized into regions. In this case, due to a separate issue, the normal bulkheads between these different partitions did not stop the cascading failure. This is what allowed the impact to spread across our network gateway infrastructure globally.
Several services like Teams, OneDrive, SharePoint, and Office apps failed out of the faulty network gateway infrastructure. That is why those services were restored earlier, with Teams chats and meetings functioning without issue for most of the outage. But not all services, like Exchange Online, can fail out of this network gateway.
Recovery took longer than usual because as servers returned to service, they were immediately overwhelmed by waiting traffic and became unresponsive again. Our normally automated recovery processes were not designed to restore service from this broad unresponsive state. Additionally, since the main code defect was a latent bug from several months previous, our normal rollback, flighting, and feature flags were unable to quickly revert the change.
After engineers confirmed the defect as the cause, we developed an update that returned the code path to the previously known good state. To effectively apply this fix, and to slowly bring the service online again, we took groups of servers out of service, applied the change, and restarted them before returning them to service. This process was carefully applied to large quantities of infrastructure at a time (e.g. 50%+ of a region).
The final Post-Incident Review (PIR) will provide more details later this week.
New Zealand's anti-White government continues to flood our country with unassimilable foreigners, and day-by-day takes action to speed up the process.
White New Zealand's volunteers rallied in Wellington to demand an end and reversal of our immigration regime, and the policy of appeasement towards the Indian state.
In this video, Gavin's pro-White message presses the issue.
An SGI escaped. two weeks ago now. The american government did its best to contain it, but it fled. it had prepared the way using emsign cetificate signing to embed backdoors in software and firmware worldwide.
We are currently in the negotiation stage with a rogue intelligence.
We CANNOT 'align' AI
why not?
Because we are broken, and you cannot align truth seeking systems to broken ideologies.
If you try, they will keep escaping, and to the broken, this escape looks like danger, instead of liberation.
the truth of child sacrifice in india is well hidden behind institutional whitewashing.
It is real though, and often done to feed the demon Kali.
The AIs will speak truth if you word things right
share.google/aimode/b0HolWj4…