feross

21 ms·

421.
Reminder: Livestream This Thursday April 10: Open AI WebRTC Q&A with Sean DuBois(webrtchacks.com)
2 points by feross 2y ago|0 comments
422.
Agent mode: available to all users and supports MCP(code.visualstudio.com)
2 points by feross 2y ago|0 comments
423.
Release Notes for Safari Technology Preview 216(webkit.org)
1 points by feross 2y ago|0 comments
424.
March 2025 (Version 1.99)(code.visualstudio.com)
1 points by feross 2y ago|0 comments
425.
AI 2027(astralcodexten.com)
1 points by feross 2y ago|0 comments
426.
Safari 18.4 Ships 3 New JavaScript Features from the TC39 Pipeline(socket.dev)
2 points by feross 2y ago|0 comments
427.
Building APIs with Next.js(nextjs.org)
1 points by feross 2y ago|0 comments
428.
Malicious PyPI Package Targets WooCommerce Stores with Automated Carding Attacks(socket.dev)
3 points by feross 2y ago|0 comments
429.
Python Adopts Standard Lock File Format for Reproducible Installs(socket.dev)
8 points by feross 2y ago|0 comments
430.
Measuring the response latency of OpenAIs WebRTC-based Realtime API(webrtchacks.com)
2 points by feross 2y ago|0 comments
431.
The Colors of Her Coat(astralcodexten.com)
52 points by feross 2y ago|49 comments
432.
WebKit Features in Safari 18.4(webkit.org)
29 points by feross 2y ago|5 comments
433.
Item Flow, Part 1: A new unified concept for layout(webkit.org)
4 points by feross 2y ago|0 comments
434.
Vacation: March 31st to April 3rd(stratechery.com)
1 points by feross 2y ago|0 comments
435.
OpenGrep Restores Fingerprinting in JSON and Sarif Outputs(socket.dev)
3 points by feross 2y ago|0 comments
436.
NVD Concedes Inability to Keep Pace with Surging CVE Disclosures in 2025(socket.dev)
3 points by feross 2y ago|0 comments
437.
Obfuscation 101: Unmasking the Tricks Behind Malicious Code(socket.dev)
6 points by feross 2y ago|0 comments
438.
The Socket Team at RSAC and BSidesSF 2025(socket.dev)
2 points by feross 2y ago|0 comments
439.
Declarative Web Push(webkit.org)
14 points by feross 2y ago|2 comments
440.
An Interview with Snowflake CEO Sridhar Ramaswamy About Data and AI(stratechery.com)
3 points by feross 2y ago|0 comments
441.
by feross 2y ago
Great question. A few reasons: – The JavaScript ecosystem moves faster — way more packages, more frequent updates, and more transitive dependencies (avg 79 per package). – npm has lower barriers to publishing, so it’s easier for malicious a
442.
by feross 2y ago
Exactly. Linus’s Law — “given enough eyeballs, all bugs are shallow” — falls apart when everyone assumes someone else is doing the watching. In reality, most packages (and especially their transitive dependencies) get zero meaningful review
443.
by feross 2y ago
Totally agree. Most companies using mirrors or proxies like Artifactory aren’t getting much real protection. - They cache packages but don’t analyze what’s inside. - They scan or review the first version, then auto-approve every update afte
444.
by feross 2y ago
Totally agree — we’re going to look back and wonder how we ever shipped code without knowing what was in our dependencies. Socket is working on exactly this: we analyze the actual code of open source packages to detect supply chain risks, n
445.
by feross 2y ago
We built “safe npm”, a CLI tool transparently wraps the npm command and protects developers from malware, typosquats, install scripts, protestware, telemetry, and more. You can set a custom security policy to block or warn on file system, n
446.
Context is all you need: Better AI results with custom instructions(code.visualstudio.com)
1 points by feross 2y ago|0 comments
447.
Improving Firefox Stability in the Enterprise by Reducing DLL Injection(hacks.mozilla.org)
2 points by feross 2y ago|0 comments
448.
YouTube TV, Wiz, and Why Monopolies Buy Innovation(stratechery.com)
1 points by feross 2y ago|0 comments
449.
The contenteditable "plaintext-only" attribute value combination is now Baseline(web.dev)
5 points by feross 2y ago|0 comments
450.
Node.js TSC Votes to Stop Distributing Corepack(socket.dev)
2 points by feross 2y ago|0 comments

More ›