Back end-for-Front end: The most secure architecture for browser-based apps
The Backend-for-Frontend (BFF) architecture serves as a secure proxy for browser apps, keeping access tokens and secrets server-side to prevent client-side exposure. It addresses OAuth security concerns for single-page applications by shifting token handling from the browser to a backend component.
Background
- The Backend-for-Frontend (BFF) pattern means a dedicated server-side backend sits between a browser-based app (e.g., React, Vue, Angular) and downstream services like APIs or identity providers. Instead of the browser calling services directly, all requests go through this BFF.
- The key security advantage in this article: the BFF keeps OAuth access tokens and client secrets server-side, never exposing them in browser JavaScript. This prevents token theft from XSS attacks or malicious browser extensions.
- This contrasts with the more common "SPA (Single Page Application) + PKCE" flow, where tokens are handled in the browser's memory or storage and are thus more vulnerable to exfiltration.
- The article argues that BFF is not just an architectural preference but a security requirement for browser-based apps handling user sessions, especially when using OAuth2/OIDC with confidential clients.
Max Weinbach says he had early access to OpenAI's new model GPT-5.6 Sol, calling it his favorite model by far. He highlights that it never gives up and will keep reasoning until it's done. OpenAI announced that GPT-5.6 Sol, along with Terra and Luna, will launch publicly on Thursday, with preview access expanding globally now.
The US government ordered Anthropic to suspend access to its Fable 5 and Mythos 5 models for all customers, citing a potential jailbreak technique that involved asking the model to review a codebase for vulnerabilities—a capability Anthropic says is available in other public models. Access was abruptly cut off on June 12.
Andrej Karpathy announces the release of Claude Fable 5, the same underlying model as Mythos but with added safeguards. He calls it a major step forward, particularly for long problem-solving sessions on difficult tasks, and describes it as state-of-the-art on nearly all benchmarks with exceptional performance in software engineering, research, and vision.
Roman Storm warns that the legal theory in his case could set a precedent making open-source developers liable for how others use their code, potentially criminalizing the mere publication of privacy, messaging, or crypto tools. He notes that developer Michael Lewellen cannot publish lawful code due to prosecution fears, and argues this chilling effect extends beyond any single case.
Meta's engineering culture is deteriorating under Mark Zuckerberg and Scale AI CEO Alexandr Wang, who have introduced keyboard tracking, reassignments to data labeling, and AI-centric performance metrics. Critics argue this incentivizes performative AI use, drives away experienced engineers, and contributed to a major Instagram hijacking incident caused by AI-written and AI-reviewed code.