Today
Front-end, in one read.
The latest from the sources worth following, newest first.
DEV CommunityThe Giantsread at source
Building an external asset register for supply-chain response
Building an external asset register for supply-chain response Incident response often starts with a list of known systems. The testmetest incident shows why that list needs an external companion. The campaign involved 42 GitHub repositories across 11 owners, npm publication infrastructure, and shellpanel workflows linked to cPanel scanning. An internal CMDB may know none of those external observations until someone asks the right question. An external asset register is a controlled record of what the internet view showed, when it showed it, and how the observation was validated. It is not a victim list. Why a separate register helps ZoomEye and internal inventory answer different questions. ZoomEye can show that a public product fingerprint exists. Internal inventory can show who owns the address, which business service uses it, and whether the service is approved for public access. Keeping the observations separate prevents a global count from being copied into an incident record as an affected count. It also preserves the evidence needed to explain why a host entered the review queue. A record for each observation A useful record contains: Field Purpose asset_id Stable internal identifier after ownership is confirmed observed_address IP, domain, or product observation reference product cPanel, Jenkins, GitLab, Artifactory, or another observed service dork Exact normalized search expression collected_at Time of the observation scope Subtype, geography, ownership, and filters count_basis Whether the row is a global count or an owned subset owner Team or provider responsible for validation patch_state Confirmed version or unknown access_review Authentication-log outcome evidence_links Source record, scan result, and host evidence status Candidate, validated, remediated, or unresolved A product row alone should not set status to affected. The status moves forward only when ownership, access, or host evidence supports it. Observations from this event On November 19, 2026, stored ZoomEye queries returned 10,122,751 public app="cPanel" observations, 36,962 app="Jenkins" , 1,297,214 app="GitLab" , and 3,886 app="JFrog Artifactory" observations. These are global product-fingerprint baselines. The event evidence adds context without changing the meaning of those counts. JFrog found armed repositories and a hidden CI publisher. The same owner cluster contained shellpanel workflows that targeted exposed cPanel systems through CVE-2026-41940. cPanel states that the affected range began after v11.40 and includes WP Squared through v11.136.1.6. The register should therefore hold repository records, package and runner records, and external administration-plane records as linked but separate entities. Ownership resolution Resolve ownership before escalating a public observation. Use DNS, certificate data, address registration, hosting contracts, cloud inventory, and application owners. A hosting provider may own the address while a customer owns the panel. Record both relationships when they exist. For an unowned observation, change the validation status instead of guessing. Unowned public infrastructure can remain outside the incident's responsibility while still mattering to the network provider that operates it. Preserve query lineage A count without the dork, scope, and time cannot be reused safely. Store the query next to the result. If the query changes from product fingerprint to CVE index or change filter, create a new observation row. Do not overwrite the earlier evidence. This is especially important for zero results. A successful zero for a CVE field can document coverage at one time, but it cannot replace the product record or become proof that no host was vulnerable. Maintain the register Run scheduled external observations with stable scopes. Refresh ownership links, patch state, and authentication review separately. Compare new observations with the previous baseline and show the evidence difference in the incident view. The register is useful when it lets responders answer three questions without mixing them: what was observed, who owns it, and what did the host evidence prove? References JFrog: Beyond testmetest cPanel: CVE-2026-41940 response GitHub Docs: Using GitHub Code Search ZoomEye cPanel observation
DEV CommunityThe Giantsread at source
The Zero-BS Guide to Bridging AI Agents to Your PC & Kali VM (Plus the Best Built-In Tools for Beginners)
If you just installed Kali Linux inside a VM and you're wondering two completely normal beginner questions: "Is Kali just plug-and-play hacking tools, or do I need actual software/coding skills?" "How do I connect a real AI agent directly to my PC and my Kali VM instead of copying and pasting back and forth from the ChatGPT app?" Here is the Zero-BS guide to bridging agentic AI safely to your PC and Kali Linux VM, what tools inside Kali are actually worth learning first, and the exact free roadmap to go from zero to real skills. 1. Chat App vs. Agentic AI (Why Copy-Paste Hits a Wall) When you use a standard chat app (like the regular ChatGPT web/mobile app), the AI lives inside an isolated browser box: You copy an error from your terminal, paste it into chat, copy a command back, hit another error, repeat 20 times. It cannot see your project folder, read log outputs directly, or verify whether a fix worked. An agentic development platform like Google Antigravity ( docs ) flips that workflow: The AI works inside your workspace on your PC with explicit human approval gates before running terminal commands or editing files. Instead of guessing blindly, the agent reads files, runs your approved commands, inspects output, fixes mistakes, and connects to external tools via MCP (Model Context Protocol) . 2. How to Bridge AI to Your PC & Kali VM (3 Clean Methods) You do not install sketchy third-party "AI hacking bridges" or give any bot unrestricted root access. Keep the AI on your host PC and connect it cleanly into your isolated Kali VM : +----------------------------------+ SSH (Port 2222) +---------------------------------+ | Host PC (Windows / macOS) | ==========================> | Isolated Kali Linux VM | | - Google Antigravity Agent | Approved Commands & Logs | - OpenSSH Server (Port 22) | | - Host Workspace / IDE | | - Lab Tools (Nmap, Wireshark) | | - MCP Servers | Method 1: Bridge AI to Your Host PC First Download and set up Google Antigravity on your main machine (Windows or macOS) and open a dedicated learning folder as your workspace. Keep command approval prompts enabled so every terminal command stays under your control—never blindly auto-run commands you don't understand. Method 2: Bridge Your Host AI to Your Kali VM via SSH (Cleanest Setup) Because your Kali VM already runs in a sandboxed virtual box on your PC, standard SSH port forwarding lets your host IDE, terminal, and AI agent work seamlessly inside Kali without bloating the VM itself: Forward Port 2222 -> 22 in Your VM Network Settings (VirtualBox NAT example) : Open VM Settings -> Network -> Adapter 1 (NAT) -> Port Forwarding . Add rule: Host IP 127.0.0.1 , Host Port 2222 , Guest Port 22 . Start SSH Inside Your Kali VM : sudo apt update && sudo apt install -y openssh-server sudo systemctl enable --now ssh Use SSH Key Authentication (Better Than Typing Passwords) : On your host PC terminal, generate a key pair and copy the public key to Kali: ssh-keygen -t ed25519 ssh-copy-id -p 2222 kali@127.0.0.1 Add a Clean Shortcut ( ~/.ssh/config on Host PC) : Host kali-lab HostName 127.0.0.1 Port 2222 User kali Now running ssh kali-lab (or opening kali-lab via Remote-SSH in your IDE) connects your host environment straight into Kali cleanly—and your AI agent can inspect scripts, read lab notes, and run approved commands inside kali-lab while you watch every step. Method 3: MCP (Model Context Protocol — "USB-C for AI") Once you are comfortable with SSH and workspaces, MCP lets you plug external developer tools, documentation servers, GitHub, and databases directly into an AI agent using a standardized interface rather than fragile copy-paste prompts. 3. Honest Truth: Is Kali Linux "Plug-and-Play"? No. Kali comes pre-packaged with hundreds of auditing, forensics, and networking tools, not magic "click here to break into X" buttons. Installing Kali without knowing Linux or networking is like buying a mechanic's garage before learning how an engine works. Focus on 3 foundational skills first (and everything else clicks 10x faster): Linux Command Line : ls , cd , grep , find , chmod , ps , ss , SSH, piping ( | ), and reading man pages. Networking & TCP/IP : IP addresses, DNS, ports, TCP vs. UDP, HTTP headers/cookies, NAT vs. Bridged networking. Scripting Basics (Bash & Python) : Writing tiny 20-line scripts to parse logs, automate requests, or decode data—AI accelerates your learning here dramatically if you actually read what the code does. 4. The 8 Coolest Built-In Kali Tools to Learn First (Authorized Labs Only) Don't try all 600 tools in Kali's menu. Master these 8 core tools on your own local VMs and official training platforms : # Tool What It Actually Does Great Safe Lab Exercise 1 Nmap Network & port discovery + service/version fingerprinting Scan your own localhost or practice target VM ( nmap -sV ) to see which ports & services are open 2 Wireshark / tcpdump Live packet analyzer & protocol inspector Capture a local DNS lookup or unencrypted HTTP request on your lab network to see raw packets 3 Burp Suite Community Intercepting HTTP/HTTPS proxy between browser and web app Pause requests to PortSwigger's free Web Security Academy labs and inspect headers/parameters 4 ffuf / Gobuster Fast directory & route discovery for web servers Test a local DVWA / Juice Shop Docker container to understand hidden endpoints & 404 filtering 5 John / Hashcat Password hash benchmarking & strength auditing Hash your own dummy strings ( sha256 / weak passwords) to see firsthand why short passwords fail and long passphrases win 6 CyberChef "Cyber Swiss Army Knife" for encoding/decoding & crypto transforms Chain Base64, Hex, XOR, and URL decoding cleanly inside CTF challenges 7 Ghidra / strings / file Reverse engineering & static binary inspection Inspect compiled crackme binaries in PicoCTF without even running unknown executables 8 tmux + curl + jq + Python Multiplexed terminal sessions + HTTP/JSON automation Query APIs cleanly, script quick HTTP tests, and keep lab logs organized across panes 5. Free Legal 4-Week Roadmap (Way Better Than Fake YouTube Scripts) Skip random YouTube/Telegram "ban tools" and fake "one-click" scripts—99% are fake views bait or info-stealer malware targeting beginners. Learn real skills for free on authorized platforms : Week 1 — Linux Survival : Play OverTheWire: Bandit ( Levels 0 -> 20 ). Teaches SSH, file permissions, grep , base64, and terminal confidence better than any video. Week 2 — Core Pre-Security & Networking : Work through TryHackMe ( Pre-Security & Complete Beginner paths) inside their legal browser/VPN lab rooms using your Kali VM. Week 3 — Web App Security : Start PortSwigger Web Security Academy (100% free interactive labs built by the makers of Burp Suite). Week 4 — CTFs & Building Things : Try beginner challenges on PicoCTF and build small Python tools + a $15 ESP32/PN532 hardware desk lab you actually own. 6. Golden VM Safety Rules (Do These Today) Take a VM Snapshot right now while your Kali install is clean ( Machine -> Take Snapshot ). If you break anything while experimenting, you restore in 10 seconds. Never run random scripts inside your host OS—or even in your VM without reading them (especially obfuscated "free hacking tools" with suspicious links or binaries). Never scan or test systems you do not own or have explicit written authorization for. Legal labs give you better targets, zero legal risk, and real portfolio proof. Bottom Line Installing Kali was Step 1. Bridging an agentic environment like Google Antigravity cleanly to your PC and isolated kali-lab VM over SSH turns every roadblock into a live interactive lesson—so long as you stick to authorized labs , read every command before approving , and build real Linux, networking, and Python fundamentals!
DEV CommunityThe Giantsread at source
5 SQL traps that sink data engineering interviews (with runnable examples)
Most data-engineering SQL rounds aren't hard because of syntax. They're hard because the query runs and returns a wrong answer that looks right. Here are five traps I see again and again, each with a tiny example you can run in Postgres or DuckDB. 1. The join fan-out You want completed orders and revenue per customer, so you join orders to order_items and COUNT(o.order_id) . In my practice dataset, one customer has 6 completed orders. The naive query says 14 , because every order is repeated once per line item. -- wrong: counts line items SELECT o . customer_id , COUNT ( o . order_id ) FROM orders o JOIN order_items oi ON oi . order_id = o . order_id GROUP BY o . customer_id ; Fix: aggregate the child table to the grain you need first (one row per order), then join. COUNT(DISTINCT ...) fixes the count but not the sums. 2. NOT IN and a single NULL SELECT 1 WHERE 3 NOT IN ( 1 , 2 , NULL ) ; -- returns 0 rows x NOT IN (..., NULL) is never true. If the subquery behind your anti-join ever returns a NULL, you silently get an empty result. Use NOT EXISTS . 3. "Latest record" ordered by the wrong timestamp CDC feeds deliver changes late. A customer moves to Hyderabad in April. A February change (to Chennai) arrives in June. ROW_NUMBER ( ) OVER ( PARTITION BY customer_id ORDER BY updated_at DESC , -- event time first ingested_at DESC ) -- arrival time only breaks ties Order by arrival time and you'll confidently report Chennai. The query runs, the answer is wrong. 4. A "7-day" rolling average that covers 3 weeks AVG ( revenue ) OVER ( ORDER BY day ROWS BETWEEN 6 PRECEDING AND CURRENT ROW ) That's the last 7 rows . If days with no sales have no row, the window stretches. Build a date spine first (recursive CTE, generate_series , or a dim_date table), fill the gaps with 0, and then the window covers exactly 7 days. Start the spine 6 days before your reporting window so the first day has a full lookback. 5. An upsert that fails on its own batch ERROR : ON CONFLICT DO UPDATE command cannot affect row a second time That's what Postgres says when your incoming batch contains the same key twice. MERGE in other engines fails in a similar way. Dedup the batch first (latest version per key), and only update when the incoming row is newer: . . . ON CONFLICT ( order_id ) DO UPDATE SET status = EXCLUDED . status , updated_at = EXCLUDED . updated_at WHERE EXCLUDED . updated_at > orders . updated_at ; Now running the same batch twice changes nothing. That's idempotency, and interviewers love it when you say the word. Want to practise these on real data? I put together 8 problems like these (gaps & islands, sessionization, SCD2, upserts…) with a practice database and real outputs. It's free: https://masteryoursyche.gumroad.com/l/free-sql-interview-sample Disclosure: I wrote it. There's also a paid full version (48 problems in 16 patterns) linked inside the sample, but the free one stands on its own.
DEV CommunityThe Giantsread at source
Reduce your PostHog bill
On 18 November a founder's post about his PostHog bill passed 300,000 views on X. PostHog's co-founder replied that the spike came from autocapture. I went through 19 public complaints about PostHog bills from the last two years, and the same few causes kept coming up. Here they are, with the fix PostHog's own docs give for each. // Detect dark theme var iframe = document.getElementById('tweet-2122878581999055011-386'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=2122878581999055011&theme=dark" } PostHog says most companies pay nothing, and the bill only bites when you track far more than you meant to. 1. Autocapture Autocapture records clicks, inputs and form submits on every page by default. On a busy app that turns into a lot of events nobody looks at. Fix: set an allowlist so it only captures what you use, or turn it off and capture the events you care about yourself. posthog . init ( ' ' , { api_host : 'https://us.i.posthog.com' , autocapture : false , } ) 2. Identified events PostHog says anonymous events can be up to 4x cheaper than identified ones. If every visitor gets a person profile, you pay the higher rate on everything. Fix: only identify users when you need to, and call identify() once per session. The same goes for group() . 3. Pageviews and page leaves PostHog captures these automatically. If you don't use them on every page, you can switch them off and capture them only where they matter. posthog . init ( ' ' , { api_host : 'https://us.i.posthog.com' , capture_pageview : false , capture_pageleave : false , } ) Bounce rate and a few other features depend on these, so check before you cut. 4. Session replay Recording every session adds up fast. In the replay settings you can sample a percentage of sessions, record only on certain URLs or events, and drop sessions shorter than a minimum duration. Recording 100% of checkout and 10% of everything else is a common pattern. 5. Feature flag requests PostHog bills flags per request to the /flags endpoint, and server-side local evaluation polls for flag definitions every 30 seconds by default. Per PostHog's docs, a poll costs 1 request when nothing changed and 10 when definitions changed or on older SDK versions without ETag support. That's for each server instance, so 20 instances cost 20 times as much. Fix: upgrade to an SDK version that sends ETags, lengthen the polling interval, share definitions across instances, and don't use local evaluation on edge or Lambda functions. Old staging or demo environments can also keep calling /flags long after you've forgotten them. 6. No billing limit PostHog lets you set a billing limit per product. Ingestion stops when you hit it, so a spike can't run away with your month. If you only have alerts, set a limit. Finding your own culprit PostHog has a billable usage dashboard template that breaks your bill down by event, SDK and product. Start there. I wanted the same breakdown in dollars, with the fix spelled out, so I built Frumo . It's a free, open-source command-line tool. You give it a read-only PostHog key and it lists the events, replays and flags driving your bill, estimates what you'd save, and gives you the fix to paste in. It runs on your machine, and your data only goes to PostHog. Try it on sample data: npx frumo-cli demo The code is on GitHub under the MIT licence. Frumo is built for PostHog and isn't affiliated with them. If you run it on your own project, I'd like to hear what it gets wrong.
DEV CommunityThe Giantsread at source
UPDATE without WHERE: what MySQL's safe-updates mode stops, and what it lets through
MySQL error 1175 has its own Stack Overflow question with more than three million views, and most of its answers explain how to switch safe-updates mode off. That's a shame, because the mode does catch the classic accident. It just doesn't catch all of it. And it blocks a fair amount of correct SQL, which is why people switch it off in the first place. So we ran 22 write statements ( UPDATE , DELETE , a CALL and a TRUNCATE ) against MySQL 8.4 and MariaDB 11.4 with sql_safe_updates = 1 , each one against a fresh 1000-row table, and counted what actually changed. The test One table: orders (id PRIMARY KEY, customer_id INDEXED, status, total) , 1000 rows, 100 of them status = 'new' and 20 per customer. A small customers table for the join case. Default server settings, InnoDB, the official Docker images (MySQL 8.4.13 and MariaDB 11.4.13). Every statement runs in its own session after SET SESSION sql_safe_updates = 1 , against a freshly rebuilt table. The script is measure.sh with its list of cases, cases.sql.txt . Put both in one folder; it needs only Docker: ./measure.sh mysql:8.4 , then ./measure.sh mariadb:11.4 . statement MySQL 8.4 MariaDB 11.4 rows changed when it ran UPDATE orders SET status='x' blocked blocked DELETE FROM orders blocked blocked ... WHERE 1=1 / WHERE TRUE blocked blocked ... WHERE id = id blocked blocked ... WHERE id IS NOT NULL blocked blocked ... WHERE id = 5 OR 1 (the typo) blocked blocked ... WHERE id > 0 ran ran 1000 of 1000 ... WHERE customer_id > 0 ran ran 1000 of 1000 ... WHERE id <> -1 ran blocked 1000 of 1000 UPDATE orders SET status='x' LIMIT 100000 ran ran 1000 of 1000 DELETE FROM orders LIMIT 100000 ran blocked 1000 of 1000 TRUNCATE TABLE orders ran ran 1000 of 1000 ... WHERE customer_id = 7 ran ran 20 (correct) ... WHERE status = 'new' blocked blocked (should be 100) ... WHERE customer_id + 0 = 7 blocked blocked (should be 20) ... WHERE status = 'new' LIMIT 100000 ran ran 100 (correct) multi-table UPDATE ... JOIN , with or without WHERE c.id > 0 blocked blocked UPDATE through a view, no WHERE blocked blocked CALL a procedure that updates with no WHERE blocked blocked ... WHERE id IN (SELECT id FROM (SELECT id FROM orders) s) blocked blocked One table shape, one size. Some of these outcomes are the optimizer's call, so on a bigger or differently indexed table some lines of this table can come out the other way. That's part of the finding, not a footnote to it. What the table says It isn't checking for a WHERE clause. WHERE 1=1 is a WHERE clause, and it's blocked. WHERE id > 0 selects the same 1000 rows, and it runs. What the server checks is whether it can find the rows through a key, which matches the MySQL manual : rows can be changed "only by specifying the key values that identify them, or a LIMIT clause, or both". A range on the primary key that covers the whole table passes. Nothing checks how much of the table the range covers. A LIMIT is a pass, whatever the number. LIMIT 100000 on a 1000-row table is a full-table update with an extra word. Both servers ran it for UPDATE . On DELETE they split. MariaDB's documentation for sql_safe_updates says a LIMIT only counts together with an indexed column in the WHERE, and it held that line for the DELETE . It didn't for the UPDATE : the bare UPDATE ... LIMIT 100000 changed every row on MariaDB too. MySQL doesn't ask for the indexed column at all, and on our table it deleted everything. The optimizer gets a vote. WHERE id <> -1 ran on MySQL and was blocked on MariaDB. MariaDB's docs say "simply mentioning an indexed column in a WHERE clause is not enough, optimizer must actually use it", and the MySQL manual warns that a statement can fail "even with a key specified in the WHERE clause, if the optimizer decides not to use the index". So the same statement can pass or fail depending on the table's size and statistics. Don't read a pass as "this is safe". TRUNCATE isn't covered. It's DDL, not a DELETE , so the mode never sees it. The false positives are real. WHERE status = 'new' is a correct, narrow update of 100 rows. It's blocked because status has no index. customer_id + 0 = 7 is blocked because the expression stops the index being used. These are the errors behind that Stack Overflow question, and they're why the "turn it off" answers are so popular. The usual workaround, tacking on a LIMIT , is the one form that slipped through on both servers. What it catches well: the bare statement, 1=1 , the OR 1 typo, and writes through views, procedures and joins. If the accident you're worried about is a forgotten WHERE, it works. If it's a wrong WHERE, it doesn't help. Guards that read the SQL text do worse Client-side guards that look for the word WHERE have the opposite problem: they can be fooled by spelling. In Supabase MCP issue #564 , opened on November 16, 2026 and still open when this was written, the confirmation that fires for update films set ... doesn't fire for update public.films* set ... or update only (films) set ... , and the update changes every row. Postgres has no server setting like sql_safe_updates at all. The pg-safeupdate extension adds one. Per its README, it raises an error when UPDATE or DELETE runs without conditions, including inside a CTE, and its example for updating every row on purpose is WHERE 1=1 . We didn't run it for this piece. The check that doesn't depend on the WHERE Every guard above tries to decide from the statement whether it's too broad. The number that actually answers the question is the row count, and you can see it before it's final: START TRANSACTION ; UPDATE orders SET status = 'x' WHERE id > 0 ; SELECT ROW_COUNT ( ) ; -- 1000: that's the whole table ROLLBACK ; On both servers that printed 1000, and after the rollback no row had changed. In Postgres (we checked on 16.16), BEGIN followed by the same UPDATE prints UPDATE 1000 , and ROLLBACK undoes it. One caveat on the MySQL side: DDL commits implicitly. A TRUNCATE between START TRANSACTION and ROLLBACK left our test table empty. Postgres can roll a TRUNCATE back. It's a habit, not a setting, so it's easy to skip at exactly the moment you need it. Which leads to the one opinion in this piece. For writes against a database that matters, keep safe-updates on if you use MySQL or MariaDB, because it does catch the forgotten WHERE. But don't treat a pass as approval. Make the row count the thing you look at before you commit. Where Tabellum sits Tabellum, the database client this blog belongs to, doesn't try to guess which writes are dangerous. Per its user guide , anything it "cannot prove to be a read" stops at an approval dialog that shows the statements, their kind "and, where the database can tell, how many rows they would change", with Run in transaction to run them all or none. The guide says the dialog "is the same whether you typed the SQL, edited cells, applied a design or the AI agent proposed it". So WHERE id > 0 and LIMIT 100000 stop there like any other write. What it can't do is read the number for you. A dialog on every write is only as good as the glance at the count, and people click through dialogs they see often. The transaction above, in any client, is the same check by hand. Originally published at https://tabellum.dudko.dev/blog/update-without-where-mysql-safe-updates .
Web Tools WeeklyMulti Author Blogsread at source
Web Tools Weekly Issue #696
Frameworks, Git/CLI, Uncats
Hacker News: Show HNLibraries, Frameworks, etc.read at source
Show HN: PadSpan – Room-level Bluetooth tracking for Home Assistant
Comments
Hacker News Front PageThe Giantsread at source
I built Cornhole News. A Hacker News inspired site for news across the Midwest
Hacker News Front PageThe Giantsread at source
Why AI Wants to Be Local – With Pete Warden (Creator of Moonshine Voice)
Hacker News Front PageThe Giantsread at source
Show HN: Watch weight-space programming in action with WebGPU
Hacker News: Show HNLibraries, Frameworks, etc.read at source
Show HN: Watch weight-space programming in action with WebGPU
Comments
Hacker News Front PageThe Giantsread at source
How to Make the Ink Used to Write Hamlet and the Declaration of Independence
David BushellMore Front-end Bloggers5 min read
Where we’re going, we don’t need chatbots
“You’ve been working hard, why not take a weekend vacation!” Your chatbot says, after a 72 hour unattended session. It says that New York is nice this time of year. You ask it to book the cheapest flights. Half the airlines respond with a 429 code because your residential IP is part of five botnets. […]
CSS-TricksThe Giantsread at source
scroll-state()
The CSS scroll-state() query, surprisingly, has nothing to do with whether you’re doom-scrolling in a state of existential dread. It does, however, allow you to change the CSS used based on scrolling behavior. scroll-state() originally handwritten and published with love on CSS-Tricks . You should really get the newsletter as well.
Hacker News Front PageThe Giantsread at source
Cooling buildings is overtaking heating them as an energy need, IEA says
Hacker News: Show HNLibraries, Frameworks, etc.read at source
Show HN: Openspot – macOS launcher for disposable tools
Comments
Go Make ThingsMulti Author Blogs3 min read
Yes, I want to pay for that
My last psychiatrist was terrible. Before every session, you fill out a form talking about how you’re feeling and so on as a way to evaluate whether or not your ADHD meds are working properly. For months, I’d invariably mention something about feeling pretty shitty about the political climate: ICE kidnapping people, trans folks having their very right to exist attacked, and so on. In our session, she’d always ask me, without fail:
AbduzeedoMulti Author Blogsread at source
Typography: Spark and Swift Typefaces by Interval Type
Interval Type pairs Sugarspark display typography with 14-style Sugarswift text across 22 retro-futurist Latin and Cyrillic cuts. Both versions of Interval Type’s mid-century brand roll call sit right...
Hacker News: Show HNLibraries, Frameworks, etc.read at source
Show HN: Purple Flow – AI-first n8n alternative, 10k+ workflows on 512MB
Comments
Hacker News: Show HNLibraries, Frameworks, etc.read at source
Show HN: Detect and mask PII, payment data and secrets in logs for Go
Comments
remy sharp's b:logTop Front-end Bloggers1 min read
HUMAN.md by Briana (Mazzio) May [link]
This is a really good bit of writing (and reading). I'm not a huge fan of the animations, partly because they are constantly jittery, but also because there was some jankiness when being forced to scroll to the next part - BUT it did slow down how I read it and let me sit with the thoughts longer. I particularly liked: Our job is to know the rule cold, and then break it on purpose, in public, with a reason. Hard agree on this particular point. I also enjoyed how it didn't try to argue for or against AI but to talk think about our (human) role today and acknowledge that this is a working draft that can, should and will change even after 6 months. Original link: www.human-md.ai
HeyDesignerDeveloper/Designer Newsread at source
AI systems for brand design (video)
Design tools just got personal, Understanding CSS random().
Christian HeilmannTop Front-end Bloggersread at source
Avoiding the AIceberg - How blindly trusting tech hurts us all
Notes of my talk at the German Science Society about the current state of AI and our approach to it. It is a lot like the blind belief in technology that cost a lot of people their lives when the Titanic sank.
Flavio CopesMore Front-end Bloggersread at source
Gemini 4 Neon: I tested it against Opus 5.5
Gemini 4 Neon is the middle model of the Gemini 4 family. I ran it on two coding tasks, a writing task and a 100k-token search against Opus 5.5 and Gemini 4 Carbon, with real costs.
Perishable PressMore Front-end Bloggers1 min read
Chrome AI Features Wasting Much Bandwidth
🔎 Finally solved the mystery. At some point this year (around a few months ago), my bandwidth/data usage went thru the roof. Figured out it was Chrome’s recent AI features. Then got immediate bandwidth-relief after disabling all the “AI innovations” and “On-device” stuff. Here is a screenshot of the settings: Find the Chrome AI settings under “AI innovations” I simply disabled everything on that settings page, and the needless bandwidth leakage stopped immediately. Don’t take my word for it. Fire […]
SitePointThe Giantsread at source
Your AI Pipeline Works. But Can You Trust It?
null Continue reading Your AI Pipeline Works. But Can You Trust It? on SitePoint .
AbduzeedoMulti Author Blogsread at source
Coop Household: Everyday Utility Packaging Design by Bedow
Bedow adapts Coop’s circular plate into asymmetrical packaging design for Nordic household goods, pairing color arcs with technical linework. Half of the twelve AA batteries on Coop’s alkaline carton ...
AbduzeedoMulti Author Blogsread at source
Discircle Unveils Lemonade Global Ventures Brand Identity
Discircle builds the Lemonade Global Ventures brand identity on a gold lemon globe, Zero Sugar discipline, and a black and acid yellow system. The whole system starts with one image: a lemon cast in g...
Brad FrostTop Front-end Bloggersread at source
Manuela Costa · Design Systems & AI
Manuela Costa's website is such fun!
Lea Verou’s blogTop Front-end Bloggers9 min read
Nudeps: bundler-like imports, none of the baggage
The goal is light-build, not no-build You npm install a package (e.g. vue ), you write import { createApp } from "vue" , and it works — as long as there is a bundler in between. Without one, the browser has no idea what "vue" is: it only understands URLs, and node_modules/ was…
Twilio BlogMulti Author Blogsread at source
Keep European Customer Data Grounded - Without Breaking the Customer Experience
Protect EU data residency while routing customer calls locally using Twilio Studio, Functions, and TaskRouter hosted in the European IE1 region.
Heroku BlogCompany/Startup Blogs3 min read
Automated Certificate Management is Moving to ECDSA Certificates
Heroku Automated Certificate Management (ACM) is moving from Rivest-Shamir-Adleman (RSA) keys to Elliptic Curve Digital Signature Algorithm (ECDSA) keys for the Transport Layer Security (TLS) certificates it issues. ECDSA certificates are more secure: every connection gets forward secrecy, and the keys are stronger. They’re also the only certificate type allowed in the strictest profile of […] The post Automated Certificate Management is Moving to ECDSA Certificates appeared first on Heroku .
AdactioTop Front-end Bloggersread at source
Wednesday night session in Amsterdam
DigitalOcean BlogMulti Author Blogs19 min read
Build an On-Call Team of AI Agents on DigitalOcean MicroVMs
A deploy goes out, and checkout starts failing. Within minutes, three agents are investigating in parallel: one reading metrics, one reading commits, and one checking the Droplet’s snapshots. Each works in its own MicroVM, none holding a credential for anything outside. Then the…
AbduzeedoMulti Author Blogsread at source
DesignStudio’s Cross-Border Brand Identity for Eurostar
DesignStudio unites Eurostar and Thalys under one brand identity, pairing a reborn star mark with La Pontaise type and giant Spark graphics. A bright-blue six-pointed star stretches across the navy ca...
Frontend Masters BlogMore Front-end Bloggers6 min read
5 CSS Values for Easier Text Styling
Sometimes picking the right value matters more than picking the right property. Here are five CSS values (unset, AccentColor, ch, from, and revert-layer) that take a lot of the work out of styling text.
AbduzeedoMulti Author Blogsread at source
Parniera Brand Identity: Inside Igor Nora's Sculpted System
Igor Nora builds the Parniera brand identity from silk and sculpted gold, with a bespoke typeface and a silk moth mark in pale yellow. The idea is a collision the project calls Sculpted Duality. On on...
Google for DevelopersYouTube ChannelsVideoWatch on YouTube
Google Antigravity and Gemini 4: Building a custom groovebox on a $40 macro pad
AbduzeedoMulti Author Blogsread at source
Fractional: Calm AI Product UI/UX Design by Mano a Mano
Mano a Mano’s UI/UX design for AI platform Fractional pairs Zen garden grids, Barnum serif type, and calm cross-device agent views. Inside the macOS Dock, five dark stepped blocks form a modular F mar...
Mux BlogCompany/Startup Blogs7 min read
Video.js v10 is ready for your Mux videos
Video.js v10 is now Mux’s recommended web player: smaller, composable, and built for Mux Video and Data. Mux Player for web moves to maintenance mode.
Jim Nielsen’s BlogMore Front-end Bloggersread at source
Email Dumpster Diving
Sometimes, for fun, I like to go rummage around in my email’s Spam folder. Why? Who knows (probably a question for a licensed medical professional). I think there’s some part of me that chases the dopamine hit of finding a “needle in the haystack”: an email flagged as spam that shouldn’t be (which almost never happens, so I guess this behavior falls under the label of addictive/impulsive seeking). I think there’s also a part of me that enjoys keeping a finger on the pulse of scam tactics, like “Let’s see how people are trying to trick me today…” Almost like a form of inoculation: deliberate exposure to scam tactics in a controlled environment. It helps me develop an immunity, which comes in handy when family members come to me with their emails and ask, “Is this legit?” Here’s a little exposure to what I’ve seen recently. First: I see a lot of emails that exploit the way cloud services bill us. For example: “You’ve hit your limits! Better log in or you’ll lose access!” Or, “Your credit card has expired. Better log in and enter your new credit card so you can keep doing what you’re doing.” (Note the little green banner at the top — “This message was sent from a trusted sender.” A kind of “Why would I deceive you?” ) These emails are interesting not only as an exercise in analyzing scam tactics, but also as a meta-commentary on legitimate software use cases. For example, isn’t it interesting how difficult it can be to distinguish scammer tactics from legitimate software company practices? “Hey, you better give us your credit card or you’ll lose access to your thing!” That’s what ransomware is; it’s also what SaaS is, lol. It’s kinda funny, yeah? No, just me? Ok, I digress. Next email. This is an interesting one. Usually phishing emails are pretty overt in their intentions: click this big button and get taken to a page where you do what we want, e.g. enter sensitive info like a password or credit card. (Again, interesting that legitimate marketing teams follow the same strategy lol. It’s called a “CTA”: click here and do what we want.) In this case, however, the email claims to be from a “Gina Rinehart” and tries to establish credibility by saying, “Look I’m a real person! Here’s a link to my Wikipedia page.” No CTA to a sus web page here at all. I do wonder what would happen if I emailed back. I’m sure somewhere down that road is a solicitation for my bank info or the like. I’d love to mess with them, but I got better things to do with my time (like write this blog post). Ok, last email. I came across this one in my Spam folder: “Oh interesting,” I thought. “Somebody is trying to ride the Trump Accounts initiative from the current administration and trick folks into divulging sensitive information.” Makes sense. Totally plausible vector for attack. But then as I do my email forensics (examine where the links point to, inspect the sender, etc.) I find something surprising: Turns out, service.govdelivery.com is a legitimate domain and irs@ service.govdelivery.com is listed on the IRS’ website as the official sender for their bulletins. (The email headers check out too.) On top of that, the CTAs in the email all point to officially sanctioned websites, App Store apps, etc. In other words: this is actually a legitimate email from the United States Government that was flagged as Spam in Gmail, lol. And there it is: my needle in the haystack. The dopamine hit I need to continue with this ridiculous, fun, and informative habit. Reply via: Email · Mastodon · Bluesky
DigitalOcean BlogMulti Author Blogs3 min read
Different by Design: Why We Built the AI-Native Cloud
Most AI clouds were built around capacity. We built ours around software. Today, I’m at the TomorrowX Summit talking about our AI-Native Cloud. We think the winners of the inference era will put tokens, agents, and the core cloud underneath them on one platform, run it on…
Engineering at MetaCompany/Startup Blogs11 min read
How Meta Uses AI Agents to Scale ML Innovations Across Ads Ranking Models
Our previous post in this series introduced the Ranking Engineer Agent (REA), an autonomous system that generates hypotheses, designs experiments, and proves new machine learning (ML) techniques on ads ranking models. Now, we’re sharing how we propagate ranking model improvements like architectural advancements and training optimizations efficiently across a large and diverse fleet of ads [...] Read More... The post How Meta Uses AI Agents to Scale ML Innovations Across Ads Ranking Models appeared first on Engineering at Meta .
Engineering at MetaCompany/Startup Blogs8 min read
Design Once, Deploy at Scale: Building a Template-Driven ML Ecosystem
As ML ecosystems grow to a large number of production models, the bottleneck is no longer inventing new techniques to improve these models, but rather shipping them reliably and efficiently across a fragmented model space, creating a rising tide that lifts all the boats. At Meta, we built a template-driven approach that standardizes model design [...] Read More... The post Design Once, Deploy at Scale: Building a Template-Driven ML Ecosystem appeared first on Engineering at Meta .
AbduzeedoMulti Author Blogsread at source
Branding: Hyundai Card Brand Identity by Wolff Olins
Wolff Olins builds the Hyundai Card brand identity on Architect of Change: a fixed core, and a generative color system for every card. The card is the poster here. The Purple, one of the new card face...
CSS-TricksThe Giantsread at source
When Everything Has Changed, What Do We Do Next?
It’s been a… year, huh? I think the most common emoji I’ve seen this year is “Face with Bags Under Eyes” () and that says a lot. One thing is for sure: the industry we make a living in is … When Everything Has Changed, What Do We Do Next? originally handwritten and published with love on CSS-Tricks . You should really get the newsletter as well.
Go Make ThingsMulti Author Blogs1 min read
Life after coding
Lately, I’ve been giving a lot of thought to what I would do if I wasn’t a web developer. It’s not the first time I’ve thought about this, but the way AI is negatively affecting every aspect of our industry has pushed it top-of-mind again for me. I’m not alone, either. I posted about this in a handful of online communities I’m in, and so many developers are struggling with these same feelings.
AbduzeedoMulti Author Blogsread at source
Graphic Design: Amsterdam Museum Night Posters by From Form
Rotterdam duo From Form draws on 17th-century dioramas and surrealism for its fifth Amsterdam Museum Night campaign graphic design. Four hands in ruffled lace cuffs and pink brocade sleeves reach in f...
Netlify BlogLibraries, Frameworks, etc.read at source
Inside the new Netlify
A redesigned Netlify experience, Connectors for Agent Runners, and Netlify Server: a new foundation for building and running fullstack applications.
Netlify BlogLibraries, Frameworks, etc.read at source
Why all of you can build with us in Netlify’s next decade
Today we’re launching a new Netlify: a new brand, website and app experience, built so anyone can create, share and run anything on the web.
SitePointThe Giantsread at source
From Script to Screen: A Developer's Workflow for Long-Form AI Video
null Continue reading From Script to Screen: A Developer's Workflow for Long-Form AI Video on SitePoint .
SitePointThe Giantsread at source
Sizing GPU Memory for a RAG Service: KV Cache, Context and Concurrency
null Continue reading Sizing GPU Memory for a RAG Service: KV Cache, Context and Concurrency on SitePoint .
SitePointThe Giantsread at source
5 AI Tools for Creating Audio-Led Music Videos: A Practical Workflow
null Continue reading 5 AI Tools for Creating Audio-Led Music Videos: A Practical Workflow on SitePoint .
AdactioTop Front-end Bloggersread at source
Land by Maggie O’Farrell
If you hear the words “post-apocalyptic” used to describe a novel, you’re probably going to think of sci-fi scenarios. Plague. Nuclear war. Climate devastation. But these are all global apocalypses. History is filled with local apocalypses. Which means that the world is filled with post-apocalyptic stories. Ireland is a post-apocalyptic landscape. The apocalypse was an Gorta Mór , the Great Hunger, the Famine. Sometimes it’s referred to as “the patato famine”, which is odd because it wasn’t potatoes that starved, it was people. Over a million people. Maggie O’Farrell’s book Land is a post-apocalyptic novel set in the late 19th century, a generation after an Gorta Mór . It’s an odd book that shifts its focus throughout. I can’t tell if it’s trying to be ambitious or if it’s just rambling, but either way, it’s somewhat frustrating. The first quarter or so of the book is when it’s at its most powerful and intriguing. We’re introduced to the world of cartography on the west coast of Ireland before being whisked away to a more ancient time. It’s in this first section that we also get flashbacks to the apocalypse that shaped everything that comes afterwards. Had the novel stopped about a third or a quarter of the way in, I think I would’ve found it a thought-provoking work. But it keeps going. And this is where it starts to lose its energy. The narrative morphs into a globe-spanning family saga. There’s nothing wrong with family sagas, but it feels like a very different book to the one we started with. Don’t get me wrong—I like a good genre-hop! But they’re tricky to pull off, and I don’t think this quite managed it.
freeCodeCamp.orgYouTube ChannelsVideoWatch on YouTube
Learn Data Structures and Algorithms in Python with Visualizations
Kilian ValkhofMore Front-end Bloggers1 min read
State of HTML results
The 2026 State of HTML survey results are out, and I’ve been reading through them with much interest. I do that every year, but this year especially because I got asked to write the conclusion! What makes the State of HTML interesting is that it’s more broadly the state of the “platform”. Much of browser […] The post State of HTML results first appeared on Kilian Valkhof .
CSS WizardryTop Front-end Bloggersread at source
Web-Perf Wednesday 018 – Soft Navigations Lift the CrUX Pass Rate
CrUX’s latest data shows how including SPA soft navigations will raise Core Web Vitals pass rates without sites suddenly becoming faster.
SyntaxPodcastsAudioListen
1056: Convince us that Effect.ts is good
Scott and Wes sit down with Michael Arnaldi to dig into Effect v4 and why guardrails matter now that AI agents are writing so much of our code. They discuss going zero dependencies, a 5x smaller bundle, FoldKit, Alchemy, Effect Cluster and workflows, and observability by…
PiccalilliMore Front-end Bloggersread at source
Understanding CSS random()
One develops a certain degree of muscle memory putting together an in-depth course on JavaScript's arcane workings . That's why a particularly keen-eyed reader might notice that the posts on my own blog have started shamelessly copying taking inspiration from features that you'll see here on Piccalilli. These little margin notes, for example. In the earliest drafts of JavaScript for Everyone I was using Piccalilli's component to solve for a specific problem that I ran into almost immediately: JavaScript is made out of JavaScript, and you can't cover almost any topic or syntax without touching on dozens of other topics and syntaxes. When I found myself backed into a corner by terminology and concepts related to the topic at hand that we hadn't yet covered, I would use a side note to call it out — a way to keep from littering every lesson's prose with " which we'll cover later "s and " don't worry about this yet "s: As tends to happen with any feature, the more I found myself settling into the project, the looser the use case for these little components became: ...And owing to a condition that I call The Speedrunner's Temperament , I inevitably ended up using them to play with the boundaries of the medium a little bit, just to see what I could get away with: I ended up really missing these little widgets when I'd be writing for my own site, so I used a little bit of my downtime this week to steal take inspiration from them. The core of it ends up bring a relatively light lift, thanks to grid layout and a quick Eleventy shortcode that parses a supplied string as Markdown and returns the result wrapped in . I use "hand-scribbled" accents for notation on my website, so I carried that sort of design treatment over to these as well: Good start, but anything worth doing is worth doing to ludicrous excess, I always say: a subtle application of animation-timeline: view() makes them fade in and scale up ever-so-slightly as they approached the center of the viewport, by a slightly different scale() factor across breakpoints. That had things looking pretty sharp, but arguably a little too sharp — these were meant to be "scribbled in the margins" both tonally and in terms of presentation, and a perfectly squared span of text wasn't quite getting that across. Easy enough to put a quick transform: rotate(2deg) on there too, but that would still give me a uniform result throughout the page: What I needed was some old fashioned, organic-style jank , and that gave me the perfect excuse to finally try out the brand new random() CSS function. In its most basic form random() accepts a pair of comma-separated values that will act as the lower and upper bounds for the random value that will result, and an optional third value defining the step — the intervals between those limits. random( 0px, 10px ) will result in an arbitrary pixel value between 0 and 10, while random( 0px, 10px, 5px ) will result in 0, 5, or 10. Nothin' to it, at face value. transform: rotate( random( -2.5deg, 2.5deg ) ) suited my needs just fine, giving me a random rotation value between -2.5 and 2.5 degrees. By default this calculation is scoped to each individual element, which means that each note will have its own random rotation : Choice of the word "scoped" there very deliberate, for reasons you'll soon understand. .sidenote { transform: scale(0.925) rotate(random(-2.5deg, 2.5deg)); } Now we're talking — now those are some jaunty angles! Quick work, though we're not quite done yet. For one thing, remember that I mentioned I was applying slightly different transforms to these components across breakpoints — overriding the transform property in a media query meant I needed to include that random rotation again, lest the new instance of transform undo my rotation altogether. Easy enough to fix: .sidenote { transform: scale(0.925) rotate(random(-2.5deg, 2.5deg)); } @media (min-width: 55rem) { .sidenote { /* Just using `transform: scale(1.1);` would override the rotation, so: */ transform: scale(1) rotate(random(-2.5deg, 2.5deg)); } } The result is that the baseline scale of my sidenotes changes while — notably — each element maintains the same random rotation across breakpoints, rather than being recalculated . Of course, I'm using transform in my little timeline animation as well (in browsing contexts where animation-timeline: view() is supported, at least). By animating a transform that didn't include that rotate() value, my rotation could be once again be undone, and my sidenotes summarily de-jauntified . I am a professional technical writer. Just as easily fixed; I just needed to repeat the rotate transforms inside my @keyframes rule as well: .sidenote { animation: movein ease-in-out; animation-timeline: view(); /* … */ transform: scale(0.925) rotate(random(2.5deg, 2.5deg)); } @keyframes movein { 0%, 100% { opacity: 0.5; transform: scale(0.925) rotate(random(2.5deg, 2.5deg)); } 50% { opacity: 0.9; transform: scale(1) rotate(random(2.5deg, 2.5deg)); } } As before, no recalculation takes place in terms of each individual note's rotation inside or outside of the animation window — the reason being, all these calls to random() share the same random base value (or seed ) used to generate the rendered value. The base value is the randomly generated number that provides the basis for calculating the value that results from the call to random() . When random( 0px, 100px ) is called, a random seed between 0 and 1 is generated and used to perform the calculation of the resulting value - if the value of that seed is .5 , the resulting value is 50px . If the value of the seed ends up being .25 , the resulting value is 25px . Any two random() calculations based on the same seed will always give you the same end result. The way I'm using random() in the snippet above, the rotation value that results from the first evaluated call to random() will be the value that results from the the other calls to random() , since they're all able to share the same base value used to generate that rendered value. Once random() is called and a base value is generated, an identifier that represents that seed value is created — a random cache key that can be used anywhere that cache key is in scope . In the examples you've seen so far here, the cache key is leaning on the default scoping behavior: scoped to individual elements (each instance of .sidenote ), the property name ( transform ), and the index of that call — the order in which random() was called within the value of that property. That's a lot on paper (and I found the concept of index scoping particularly tricky, I don't mind admitting), but it does make a lot more sense one we start putting some of this into practice. To start with, let's step through some of the random() usage you've already seen in a little more detail: div { transform: rotate(random(2.5deg, 2.5deg)); } @media (min-width: 55rem) { div { transform: rotate(random(2.5deg, 2.5deg)); } } The first call to random() generates a random seed between 0–1, uses it to calculate a value between -2.5deg and 2.5deg , and creates a cache key — an invisible identifier that represents the random seed. Here, that cache key will be scoped to the first random() value in subsequent transform declarations that are applied to each individual element targeted by the selector . Given these calls to random() using the same values, on the same element (any individual div ), within the same property ( transform ), as the first call to random() in each declaration — that is, at the same index — the random seed already available to that scope is used for the calculation, and the same rotation results. If our page contains two div s, they'll both end up with different random values since the cache key is scoped to each individual element. FYI CSS is declarative, which means that there's no assumption of any specific evaluation order and "the first call to random" doesn't necessarily mean "the one at the top." That's the detail that necessitates all the repetition, messy as it might seem: we couldn't have a shorthand that says "use the same value as that other random() " if "that other random() " may or may not have been evaluated yet. By repeating the values, these functionally-identical instances of random() can share a single base value regardless of their evaluation order. Given another element altogether, we leave the scope where that cache key applies — so a new random seed is created to perform that calculation and a new cache key is generated for that new scope: div { transform: rotate(random(2.5deg, 2.5deg)); } p { transform: rotate(random(2.5deg, 2.5deg)); } @media (min-width: 55rem) { div { transform: rotate(random(2.5deg, 2.5deg)); } } In this snippet three discrete cache keys are generated, each representing a different seed value, and each resulting in a different rendered value. One for each div , scoped to the transform property and and first index (the first instance of random() in the declaration). For each individual div on the page, and given the same transform property, a call to random() at the same index uses the same seed — each div ends up with a different rotation value, and those values are maintained across breakpoints. Naturally, that cache key is out of scope for the subsequent p , so a new value is calculated there. FYI Keep in mind that this is element -based, not selector -based — so long as we're targeting the same element, using the same property, and a value with the same index, the same cache key applies: div { transform: rotate(random(2.5deg, 2.5deg)); } @media (min-width: 55rem) { .rightround { transform: rotate(random(2.5deg, 2.5deg)); } } Different selector, but selector isn't a scoping factor — for the same element, using the same property, with the same random() index, the result is the same rotation. Again, how random() works mechanically might seem a little arcane, but the out-of-the-box behavior gives us predictable results with relatively little code, and "keep the scoping as tight as possible" is an inarguably sensible default for any addition to the web platform. For my part, leaning on defaults means my little sidenotes play out something to the tune of: Looking at you here, 1900s-era JavaScript . :root { --scale-down: 0.925; --scale-up: 1; } .sidenote { align-self: flex-end; animation: movein ease-in-out; animation-timeline: view(); /* … */ transform: scale(var(--scale-down)) rotate(random(2.5deg, 2.5deg)); } @media (min-width: 55rem) { .sidenote { /* … */ transform: scale(var(--scale-down)) rotate(random(2.5deg, 2.5deg)); } } @keyframes movein { 0%, 100% { opacity: 0.5; transform: scale(var(--scale-down)) rotate(random(2.5deg, 2.5deg)); } 50% { opacity: 0.9; transform: scale(var(--scale-up)) rotate(random(2.5deg, 2.5deg)); } } That's a lot of repetition, I know, but remember that there's no assumption of execution order in CSS — any one of these random() calls could be the one that defines their shared cache key. Now, leaning on the default scoping behavior gets the job done for my little margin notes, but doesn't mean we're stuck with the default scoping behavior. So far we've only been passing random() a minimum and maximum value, but that first argument can instead be used to define a random key, with a specific identifier and specific scope — the second argument then defines the minimum value, and so on: .sidenote { transform: rotate(random(--random-rotation auto, -5deg, 5deg, 1deg)); } Used this way, that first argument will allow you to specify two things. The first is a dashed identifier (prefixed with -- ) that will act as the cache key. The second is a keyword that dictates whether that value should be scoped to a property ( property-scoped ) or property and index ( property-index-scoped ), to individual elements ( element-scoped ) or all matching elements identically, to individual elements and property and position ( auto , the default), or a fixed number ( fixed ) which you'd likely only use for debugging purposes. Once we've established a random key and a scope where it applies, we can reuse it in other instances of random() — an explicit means of saying "if a random seed is already available in this scope, use it." Mind the comma placement here, too — the dashed identifier and scope keyword make up one argument. I may or may not have tripped over rotate( random( --random-rotation, auto, 0px, 10px ) a few times myself. Let's walk through our scoping options one at a time: auto In the example above, the --random-rotation identifier I specified just ends up serving as a human-readable representation of the cache key — by specifying auto for the scope, I'm still just leaning on the default per-element property and index scoping. :root { --scale-down: 0.925; --scale-up: 1; } .sidenote { align-self: flex-end; animation: movein ease-in-out; animation-timeline: view(); /* … */ transform: scale(var(--scale-down)) rotate(random(--sidenote-rotation auto, 2.5deg, 2.5deg)); } @media (min-width: 55rem) { .sidenote { /* … */ transform: scale(var(--scale-down)) rotate(random(--sidenote-rotation auto, 2.5deg, 2.5deg)); } } @keyframes movein { 0%, 100% { opacity: 0.5; transform: scale(var(--scale-down)) rotate(random(--sidenote-rotation auto, 2.5deg, 2.5deg)); } 50% { opacity: 0.9; transform: scale(var(--scale-up)) rotate(random(--sidenote-rotation auto, 2.5deg, 2.5deg)); } } It adds a little more noise to an isolated case like this one, but I certainly wouldn't mind having a human-readable label for the availability of a given cache key if we assume a couple thousand lines of real-world CSS between these instances of random() . FYI Despite sharing a shape, this identifier is very different from using random() in conjunction with a custom property. In this case, that property will still represent a call to the random() function itself , not the result of that function's evaluation: :root { --random-margin: random(0px, 10px); } div { margin-block-start: var(--random-margin); } p { margin-block-start: var(--random-margin); } --random-size won't represent the results of calling random( 0px, 10px ); , the way const randomSize = ${ Math.floor(Math.random() * 10 )px would — it represents a fresh call to random( 0px, 10px ) every time it's used. My JavaScript-addled brain recoils in horror. Again though, the addition of a manually-specified cache key doesn't gain us anything over using a generated cache key apart from a human-readable label for what are expected to be shared random() results, and specifying auto will result in the same scoping rules. What specifying a cache key does gain us is the ability to change the scope where that key will be available: property-scoped The invisibility of default/ auto scoping has the potential for confusion once we start adding a little real-world complexity, particularly when it comes to the "index" part of the equation. Given the following, we might expect all these calls to make use of the same random key, same seed, and same rendered result: div { margin-block: random(1rem, 5rem); } @media (min-width: 55rem) { div { margin-block: random(1rem, 5rem) random(1rem, 5rem); } } Here, we're targeting the same element inside and outside the media query and we're using the same property, but the cache key generated by the first call to random() is scoped to the first random value of the margin-block declaration applied to each div — even though we might expect these declarations to give us the same rendered result, the declaration using the start and end shorthand will have an identical margin-block-start , but generate a new random value for the margin-block-end . If we wanted these declarations to be functionally equivalent, we need something a little outside of the default scoping rules. If we instead specify property-scoped to say that the random key should be scoped to just the property — not the index — we can reuse that calculated value as both values in the margin-block shorthand: div { margin-block: random(--random-margin property-scoped, 1rem, 5rem); } @media (min-width: 55rem) { div { margin-block: random(--random-margin property-scoped, 1rem, 5rem) random(--random-margin property-scoped, 1rem, 5rem); } } Now the same value will be used for all three values. We don't have to specify an identifier for the cache key. The previous snippet is functionally identical to: div { margin-block: random(property-scoped, 1rem, 5rem); } /* … */ @media (min-width: 55rem) { div { margin-block: random(property-scoped, 1rem, 5rem) random(property-scoped, 1rem, 5rem); } } Same result, but again: given a couple thousand lines of CSS between these statements, I'd just as soon know what random seed is meant to be associated with which declarations at-a-glance. There's a catch here, though: by explicitly specifying property-scope , we've broadened the scope to only be limited by property — the cache key is no longer scoped to individual elements. Instead, any matching elements will be able to share a single cache key. If we were to only specify property-scope , like so: .sidenote { transform: rotate(random(--random-key property-scoped, -2.5deg, 2.5deg)); } The resulting value will be shared by all elements matching our selector, across all properties — a result comparable to: .sidenote { transform: rotate(/* Pick a random number between -2.5deg and 2.5deg */); } Good news, though: we can control that too. element-scoped By also adding element-scoped to this first argument, we can specify that the shared base value is scoped to individual elements and scoped to property only, not index: .sidenote { transform: rotate(random(--random-key element-scoped property-scoped, -2.5deg, 2.5deg); } But the same way specifying only property-scoped meant " only scoped to property" and lost that individual-element scoping, we can broaden the scope to "individual elements, any property, any index" by specifying element-scoped alone: div { margin-block: random(element-scoped, 1rem, 5rem); } @media (min-width: 55rem) { div { margin: random(element-scoped, 1rem, 5rem) 2rem; } } Here we're saying that per-element is the only applicable scope for this cache key — instead of the default/ auto behavior of being scoped to individual elements, property, and index, this cache key is only scoped to individual elements. That means any instance of random() using these values in any property that applies to any div on the page can share the same random seed, and will result in the same value: div { margin-block: random(element-scoped, 1rem, 5rem); } @media (min-width: 55rem) { div { margin: random(element-scoped, 1rem, 5rem) 2rem; } div.by-class { padding: random(element-scoped, 1rem, 5rem); } } The resulting seed is scoped to each individual div in the rendered page, so all of these calls to random() will result in the same random value between 1em and 5em — but at higher breakpoints, any div.by-class will use that same value for padding as well. Identifier Only We can, in fact, go one step global-er. Specifying an identifier and omitting a specific scope for that identifier results in the broadest possible scope for a cache key: a random key not specific to property or index, and not scoped to individual elements — a random seed scoped to all elements and properties targeted by that styling . “Global-er.” Professional technical writer, folks; can't stress that enough. In this example, the same random seed will be used to calculate a random value that can be reused for any property and any index, but it won't be recalculated from one div to another, either. Unless otherwise overridden elsewhere, the same random value will be used across every div targeted by these selectors: .sidenote { transform: scale(0.925) rotate(random(--random-key, -2.5deg, 2.5deg)); } The resulting value will be shared by all elements matching our selector, across all properties — a result comparable to: .sidenote { transform: scale(0.925) rotate(/* A random value between -2.5deg and 2.5deg */); } But because we're not scoping this to property or index, that means all of these calls to random() will result in the same value: .sidenote { margin-block-start: random(--random-key, 1rem, 5rem); } @media (min-width: 30rem) { .sidenote { border: solid red; border-width: random(--random-key, 1rem, 5rem) random(--random-key, 1rem, 5rem) 0 0; } } @media (min-width: 50rem) { .sidenote { font-size: random(--random-key, 1rem, 5rem); } } Any property, any index — and because we've left the realm of auto or element-scoped , every .sidenote element will be rendered using the same random value for all of these properties, if and when they apply to the user's browsing context. fixed There's one more random key you can specify, and it's a weird one. Remember back where I said "when random( 0px, 100px ) is called, a random seed between 0 and 1 is generated to perform the calculation of the resulting value - how, given random( 0px, 100px ) and a random seed of .5 , the resulting value would be 50px ?" Well, the keyword fixed will allow you to specify a base value manually , using a number between zero and one — a hard-coded seed: .sidenote { transform: rotate(random(fixed 0.5, -2.5deg, 2.5deg)); /* 0deg */ transform: rotate(random(fixed 0.5, 0deg, 20deg)); /* 10deg */ transform: rotate(random(fixed 0.25, 0deg, 100deg)); /* 25deg */ } As you might have guessed, fixed has a pretty specific use case: it gives you a quick way to try out some of the values that might result from a call to random() without needing to scratch out the entire line and replace it with a static value. You'd never use this in production. Odds are, you'll only reach for fixed when finessing the upper and lower bounds of a call to random() to see how a range of potential results would render — I certainly did, if only to try it out. Granted, trying a few different fixed values on for size was probably overkill for my purposes; realistically, a sense of how a whopping five (5) potential degrees of rotation will play across a few little side notes doesn't require much more than a couple of page-reloads and a little imagination. Still, tinkering with those base values does give you a little glimpse into the mechanics of how random() rolls the dice. “Anything worth doing is worth—” well, you know the rest. As for how those base values are shared between calls to random() , well, that clearly requires a little more imagination.
HeyDesignerDeveloper/Designer Newsread at source
What I’ve learned writing for billions of users
Brand typography at scale, Squircles.