# don't Published articles for don't. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Preventing Destructive Actions with Step-up Authentication DevFeed: [Preventing Destructive Actions with Step-up Authentication]() Original publisher: [Read original article]() Author: Jessica Temporal Published: 2026-09-17T00:00:00Z Content type: tutorial Language: en Sources: [Auth0 Blog]() Topics: [MFA](), [Auth0](), [Security](), [cursor](), [App](), [Next.js](), [passwords]() Tags: [agentic](), [agents](), [auth0](), [cursor](), [don-t](), [mfa](), [next-js](), [prompt](), [security]() ### AI overview This tutorial explains how to protect a destructive "reset all scores" admin action in a Next.js Agentic Arcade app with Auth0. The implementation combines an admin role check with a fresh MFA step-up challenge before the reset request is sent, helping prevent a stale session from triggering the wipe. ### Source excerpt Cursor built a "reset all scores" feature from a single prompt, gated by a fresh MFA step-up. ## Kelet: Building a durable workflow to diagnose AI agent quality failures DevFeed: [Kelet: Building a durable workflow to diagnose AI agent quality failures]() Original publisher: [Read original article]() Author: Almog Baku Published: 2026-06-18T00:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [agent observability](), [Orchestration](), [Artificial Intelligence](), [AI-assisted coding]() Tags: [agents](), [ai-agents](), [ai-quality](), [architecture](), [bugs](), [community](), [don-t](), [orchestration](), [traces]() ### AI overview This article explains how Kelet diagnoses recurring quality failures in production AI agents by processing sessions, accumulating hypotheses, and reasoning across many occurrences. It describes why durable workflows are needed instead of a single agent loop or LLM call. ### Source excerpt Almog Baku, co-founder and CEO of Kelet AI built an AI that diagnoses failing AI agents in production. Here's how he did it and why it needed durable workflows. ## A symmetric-key approach to post-quantum Web PKI DevFeed: [A symmetric-key approach to post-quantum Web PKI]() Original publisher: [Read original article]() Author: Adam Langley Published: 2024-04-07T00:00:00Z Content type: opinion Language: en Sources: [ImperialViolet]() Topics: [Cryptography](), [Post-Quantum](), [Encryption](), [TLS (Transport Layer Security)](), [public key](), [Security, Privacy and Abuse Prevention](), [kerberos]() Tags: [cryptography](), [dns](), [don-t](), [kerberos](), [post-quantum](), [public](), [public-key](), [tls]() ### AI overview The article proposes using DNS records and shared symmetric keys with multiple certificate authorities to help authenticate a Kyber key agreement between a client and server. It notes that initial public-key connections to the authorities would still require large post-quantum signatures and raises privacy and policy concerns because authorities could observe which servers clients contact. ### Source excerpt (I think this is worth pondering, but I don't mean it too seriously--don't panic.) Are the sizes of post-quantum signatures getting you down? Are you despairing of deploying a post-quantum Web PKI? Don't fret! Symmetric cryptography is post-quantum too! When you connect to a site, also fetch a record from DNS that contains a handful of "CA" records. Each contains: a UUID that identifies a CA ECA-key(server-CA-key, AAD=server-hostname) A key ID so that the CA can find "CA-key" from the previous field. "CA-key" is a symmetric key known only to the CA, and "server-CA-key" is a symmetric key known to the server and the CA. The client finds three of these CA records where the UUID matches a CA that the client trusts. It then sends a message to each CA containing: ECA-key'(client-CA-key) -- i.e. a key that the client and CA share, encrypted to a key that only the CA knows. We'll get to how the client has such a value later. A key ID for CA-key'. Eclient-CA-key(client-server-key) -- the client randomly generates a client-server key for each CA. The CA record from the server's DNS. The hostname that the client is connecting to. The CA can decrypt "client-CA-key" and then it can decrypt "server-CA-key" (from the DNS information that the client sent) using an AAD that's either the client's specified hostname, or else that hostname with the first label replaced with *, for wildcard records. The CA replies with Eserver-CA-key(client-server-key), i.e. the client's chosen key, encrypted to the server. The client can then start a TLS connection with the server, send it the three encrypted client-server keys, and the client and server can authenticate a Kyber key-agreement using the three shared keys concatenated. Both the client and server need symmetric keys established with each CA for this to work. To do this, they'll need to establish a public-key authenticated connection to the CA. So these connections will need large post-quantum signatures, but that cost can be amortised over ## Running Node.js in Docker for local development DevFeed: [Running Node.js in Docker for local development]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2020-09-14T04:00:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Docker](), [Node.js](), [Containers](), [Development](), [Front end]() Tags: [apps](), [benefit](), [buildchains](), [containers](), [dependency](), [development](), [docker](), [don-t](), [easy](), [frontend](), [hassle](), [inside](), [insights](), [know](), [local](), [need](), [node-js](), [onboarding](), [running]() ### AI overview This tutorial explains how to run Node.js buildchains and applications in Docker containers during local development. It presents containerization as a way to isolate application dependencies, simplify onboarding, and reduce conflicts between projects. ### Source excerpt You don't need to know Docker to benefit from running local dev Node.js buildchains & apps inside of Docker containers. You get easy onboarding, and less hassle. ## Cutting the Cord: Removing Craft CMS 3 Plugins DevFeed: [Cutting the Cord: Removing Craft CMS 3 Plugins]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2019-03-19T13:56:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Content Management System]() Tags: [cms](), [craft](), [don-t](), [fantastic](), [functionality](), [insights](), [let-s](), [need](), [plugins](), [times](), [unplug]() ### AI overview This tutorial explains how to remove unnecessary Craft CMS 3 plugins by using functionality available natively through Twig and Craft CMS services. It focuses on replacing three plugins with built-in capabilities while exploring Craft CMS's broader functionality. ### Source excerpt Plugins are a fantastic way to add functionality to Craft CMS 3. However many times, you don't need them at all. Let's unplug! ## Why to Avoid .htaccess Files When You Control Apache Server Configuration DevFeed: [Why to Avoid .htaccess Files When You Control Apache Server Configuration]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2016-11-24T04:43:00Z Content type: opinion Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Web Development](), [nginx](), [hosting]() Tags: [apache](), [configure](), [don-t](), [file](), [htaccess](), [insights](), [nginx](), [performance](), [server](), [using](), [webserver](), [you-re]() ### AI overview This article argues that .htaccess files add performance overhead in Apache because each request can trigger repeated searches, merging, and reconfiguration. It recommends placing directives in the main Apache server configuration when available, noting that modern web servers such as Nginx do not use .htaccess files. ### Source excerpt Every CMS under the sun has you configure a .htaccess file if you're using Apache. Don't do it!