> What this is normally called

Is this also what Microsoft calls "Magentic" pattern?

(for a long time i kept reading it as Magnetic pattern)

https://learn.microsoft.com/en-us/semantic-kernel/frameworks...

My hypothesis:

One way to bias the generative output away from ugly generic sloppy defaults and towards something you personally prefer and desire based on your taste ... is to show it examples of what good looks like to you.

It is very hard for us to describe in words why you like a certain thing. But you can spot it when you see it. Or you can describe some aspects of it that you like or dislike after you see it -- but not before.

This approach is more accessible to casual creators -- who do not have formal training and experience to say "use corporate memphis" or "punk fanzine look with grunge typography".

(and this can apply to many fields -- not just visual design)

If this continues to be a thing ...one might actually imagine a good system where we have AGENTS.md with all generic agent instructions and a bunch of harness specific files like CLAUDE.md, GEMINI.md, and CODEX.md that all add whatever nuance and nudging each harness seems to individually require

I like this, but can we not have any of this in the root of the repo cluttering it up with the harness specific instructions for a half dozen plus different harnesses. Something like a dot agents dir

Should we be able to manually rename those history folders to make the session history show up as --resume options in a new folder?

But alongside the marketing blitz they also offer certifications for people who are supposed to execute these projects. Even the most foundational certification exam -- which simply tests your recall on what AWS service is for compute versus networking -- teaches and tests you about "Shared Responsibility Model" that draws the line at what the customer is still responsible for when they use cloud bases IaaS / PaaS / SaaS services.

If businesses are going to cloud but without engaging / listening to competent people who know these basics -- then the blame needs to be somewhat pointed back at those very business leaders I feel.

This is not obscure magical knowledge either that is tightly controlled. Any cloud vendor will freely teach you that. Or even a google search would.

Aws cto is basically opening every presentation with a everything breaks all the time slide, idk where you get that idea they oversell the cloud resilience

They could offer controlled "failure of service" service where they randomly take stuff offline and you have to pay to get it back if you don't have a backup/recovery strategy.

AWS Fault Injection Service

https://aws.amazon.com/fis/

https://docs.aws.amazon.com/fis/latest/userguide/what-is.htm...

The customer CEO never watched that presentation.

Thinking aloud about failure modes / edge cases:

If i create a high quality deepfake image, project it on a large screen and take a photo of that image with an iPhone (+apple verified image secure tag) ... would that resulting image be considered "authentic" by default?

Would digital forensics accessible to lay people still be able to fact-check and call out misuse / fakery of the new secure tag.

It is authentic, in a way. It’s exactly what you took a picture of.

I do wonder how easy that would be to detect, but I can’t help but think some sort of artefacting or something would show up.

The system is not for detecting deepfakes. It is for proving that the data captured by an apple camera's sensor was not altered by some 3rd party hardware or software chain.

Fair enough.

So the chain of trust is ...

Personal credibility of the person taking the photo with iPhone (till the moment picture is taken) + tamper-evident protection against unauthorized or anonymous edits and manipulation (after the iphone photo is published and circulated)

Apple cannot (of course) vouch for the former.

Chunking strategy taken literally. Hmm.

Thanks for the headsup.

it seems they claim to have fixed it :

> September 14, 2026—KB5129195 (OS Builds 26200.9457 and 26100.9457) Out-of-band

> [Remote Desktop Services (known issue)] Fixed: This update addresses an issue affecting Remote Desktop Services (RDS) after installing the September 2026 Windows security update (KB5122880). In affected environments, RDS might become unstable, causing RDP connection and sign-in failures or servers to become unresponsive during Remote Desktop configuration. Related tools, including Microsoft Management Console (MMC), RDS Licensing Diagnoser, File Explorer, and the Windows Update page, might also stop responding.

FWIW, neither the KIR nor the OOB patch did fix the black screen problem for us on Citrix.. waiting for another round of updates... yay.

When you place any piece on the board in any position, you can drag that piece all over the board to "reveal" the painting behind it whenver you move your piece.

Is that intentional or a sneak peek?

That is intentional. The painting isn't a secret, but seeing it all at once with its completed poem is the goal.

Some government bodies and officials post "official" public communications on x/facebook which may not be mirrored or oreserved anywhere else in same format.

There has to be a reasonable way to preserve these comms for public benefit.