OpenAI Deprecates 'user' Field in Responses API, Splits It Into Two Distinct Parameters

·1 views

OpenAI has deprecated the 'user' field in its Responses API, replacing it with two separate parameters: 'safety_identifier' and 'prompt_cache_key'. The original field had conflated end-user safety attribution with prompt-cache routing, two functions with different lifecycles and privacy requirements. The 'safety_identifier' is meant to be a stable, pseudonymous token tied to a specific account, while 'prompt_cache_key' is used to route requests sharing reusable prompt prefixes. Developers are advised to use hashed or HMAC-derived identifiers rather than raw user data for the safety field, keeping personal information out of API payloads. Simply copying the old 'user' value into both new fields is discouraged, as it misses the opportunity to properly separate identity tracking from cache routing logic.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Why Payment Reconciliation Matters More Than Webhooks Alone

Payment systems rely on webhooks to sync transaction states, but server outages, worker failures, and delayed events can leave an application out of sync with the payment provider. Reconciliation is the process of comparing internal records against provider data to detect and fix these discrepancies. Common gaps include payments marked pending that have already failed, successful charges never reflected in the app, or refunds that remain unprocessed locally. A robust reconciliation flow must be idempotent, handle out-of-order states, and treat mismatches as normal distributed system behavior rather than rare edge cases. Without it, customers may lose access they paid for, or retain access they should not have.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Builds AI Tool That Cross-Checks Claims Using Source Metadata Dates

A developer created 'The Verifier', an AI-powered research assistant designed to fact-check public claims by simultaneously searching for both supporting and contradicting evidence. The tool was inspired by concerns that AI systems can confidently present outdated information that was once accurate, rather than outright fabrications. Instead of returning a single answer, The Verifier investigates each claim from two opposing directions and places the evidence side by side. A key feature is its use of source metadata — such as publication and modification dates — to determine which evidence is more recent and therefore more reliable. This approach allows the system to explain contradictions transparently, for example flagging that two conflicting Starbucks CEO sources are both legitimate but from different points in time.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How a RAG System Splits Into Knowledge and Query Pipelines Explained

A developer tutorial series on building a Retrieval-Augmented Generation (RAG) system explains how its components organize into two distinct pipelines. The knowledge pipeline handles ingesting, processing, and indexing raw information from sources like Notion or Slack so it can be retrieved later. The query pipeline takes a user's question, retrieves relevant stored knowledge, and passes it as context to a large language model to generate an answer. The separation mirrors how search engines like Google crawl and index content separately from serving search results. The article dives deeper into connector and ingestion layer roles, showing how source-specific connectors fetch and structure raw records before they enter the broader pipeline.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Seeks Validators for React Cross-Site Events SPFx Web Part Sample

A new read-only React SPFx web part sample has been submitted to the PnP SharePoint Framework repository via pull request, awaiting community validation. The web part aggregates Microsoft 365 group calendar views from up to eight SharePoint team-site sources using Microsoft Graph calendarView access through PnPjs. It features timezone-safe event normalization, per-source error and retry states, and accessible Fluent UI rendering, with required delegated Graph permissions documented in the README. Local testing confirmed all 10 Jest tests passed alongside TypeScript, Sass, lint, webpack, and production packaging checks. Developers with SharePoint Online access are invited to test real tenant scenarios — including permissions, time zones, partial failures, and narrow layouts — and share findings on the pull request.

0 comments Read more at DEV Community