Resilient streaming using @Redisinc Streams
Streaming is synced between tabs. In fact, users can also close the app and the server would complete the stream and sync it with the clients using @replicache
It's counterintuitive but local-first and IA is a match made in heaven
SECURITY ADVISORY — TanStack npm packages
A supply-chain compromise affecting 42 @tanstack/* packages (84 versions total) was published to npm earlier today at approximately 19:20 and 19:26 UTC. Two malicious versions per package.
Status: ACTIVE — packages are deprecated, npm security engaged, publish path being shut down.
Severity: HIGH — payload exfiltrates AWS, GCP, Kubernetes, and Vault credentials, GitHub tokens, .npmrc contents, and SSH keys.
If you installed any @tanstack/* package between 19:20 and 19:30 UTC today, treat the host as potentially compromised:
• Rotate cloud, GitHub, and SSH credentials immediately
• Audit cloud audit logs for the last several hours
• Pin to a prior known-good version and reinstall from a clean lockfile
Detection — the malicious manifest contains:
"optionalDependencies": {
"@tanstack/setup": "github:tanstack/router#79ac49ee..."
}
Any version with this entry is compromised. The payload is delivered via a git-resolved optionalDependency whose prepare script runs router_init.js (~2.3 MB, smuggled into each tarball at the package root).
Unpublish is blocked by npm policy for most affected packages due to existing third-party dependents. All 84 versions are being deprecated with a SECURITY warning, and npm security has been engaged to pull tarballs at the registry level.
Full technical breakdown, complete package and version list, and rolling status updates:
https://t.co/Zy8qG7PA9f
Credit to the security researcher for responsible disclosure.
@VincentVentalon@SebLecornu Ils en prennent déjà :)
Il faudrait surtout qu’ils prennent moins d’ESN qui considère l’état comme une vache à lait en staffant des équipes de juniors qui font de la merde sans supervision
@ThibaultHoudon Oui j’ai jamais compris pourquoi aller plus loin que plan et implement. Une fois les bonnes abstractions définies tout devient trivial avec le plan mode
@matteocollina Awesome!
Is the concurrency option on queue per process or global on distributed environments ?
Also, is there a way of updating the job data like it’s doable on bullmq ? Found it super useful to implement multi step jobs that can retry at some later step
Véridique j’ai déjà bossé pour une startup qui a perdu un énorme deal parce que seulement 4 personnes dans l’équipe tech.
Le produit était à des années lumières des autres options, mais la taille de l’équipe a été flagguée comme risque majeur donc deal perdu :(
Évidemment c’était pour un grand groupe également
1/ AI makes code cheap. The scarce asset is now the system's self-knowledge.
Specs and contracts were always valuable—but too expensive to maintain. So we invested sparingly, specs drifted, and we read the code instead.
That calculus has flipped with coding agents.
@melvynx J’étais tenté de l’utiliser jusqu’à ce qu’il me demande de lancer le script de connexion à la prod pour tester un truc sur la db lol
Non frérot tu vas pas faire ça !
@ledevultime Je me demande souvent.
Je pense qu’à horizon 2 ans on sera tout sur du platform engineering : définir les bonnes primitives d’une app pour que l’IA fasse les features
Au delà j’ai du mal à voir