every single day there is an acquisition on here. what's going on in the macro?
24,625 karma · joined December 9, 2015
ai engineer pod/news: https://latent.space/
conference: https://ai.engineer
devrel/devtools: https://dx.tips/
personal blog: https://swyx.io/ideas
book: https://learninpublic.org/
but you can also email username [at] ai dot engineer
---
meet.hn/city/37.7792588,-122.4193286/San-Francisco
Socials:
- x.com/swyx - youtube.com/@swyxtv
every single day there is an acquisition on here. what's going on in the macro?
saving people a click:
CVE-2026-22775: DoS in devalue.parse due to memory/CPU exhaustion
> Effects: A malicious payload can cause arbitrarily large memory allocation, potentially crashing the process. SvelteKit applications using remote functions are vulnerable, as the parameters are run through devalue.parse If you don’t have remote functions enabled, SvelteKit is not vulnerable
CVE-2026-22774: DoS in devalue.parse due to memory exhaustion (Yes, this is very similar to the previous CVE. No, it is not the same!)
> Effects: A malicious payload can cause arbitrarily large memory allocation, potentially crashing the process SvelteKit applications using remote functions are vulnerable, as the parameters are run through devalue.parse If you don’t have remote functions enabled, SvelteKit is not vulnerable
CVE-2026-22803: Memory amplification DoS in Remote Functions binary form deserializer
> Effects: Users can submit a malicious request that causes your application to hang and allocate arbitrarily-large amounts of memory
CVE-2025-67647: Denial of service and possible SSRF when using prerendering
> Effects: DoS causes the server process to die SSRF allows access to internal resources that can be reached without authentication from SvelteKit’s server runtime If the stars align, it’s possible to obtain SXSS via cache poisoning by forcing a potential CDN to cache an XSS returned by the attacker’s server (the latter being able to specify the cache-control of their choice)
CVE-2025-15265: XSS via hydratable
> Effects: Your users are vulnerable to XSS if an attacker can manage to get a controlled key into hydratable that is then returned to another user
i just checked and in 2025 there was at least 2 outages a month every month https://x.com/swyx/status/2011463717683118449?s=20 . not quite 3 nines.
if i were doing what you do i might set up a lot of rate limits/anomaly detection in case some weird unintended invalidation causes a weird spike in your dependency graphs. is there good practice there for anomaly detection other than "setup a bunhc of dashboards and be on call"?
oo that sounds like a cool insight. like just do a trailing 20-30 token average of estimated temperature and look for variance like one might do a VO2 max
https://thinkingmachines.ai/blog/defeating-nondeterminism-in...
1a. temperature=100000 is interesting too. obviously "ideal" temperature lies somewhere between 0 and 100000. has anyone ablated temperature vs intelligence? surely i'm not the first person to this idea. commonly people try to set temp=0 to get "deterministic" or "most factual" output but we all know that is just Skinner pigeon pecking.
1b. can we use "avg temperature" as a measure in the way that we use perplexity as a measure? if we see temperature as inverted perplexity with some randomness thrown in, are they basically the same thing inverted? or subtly different?
1c. what's the "avg temperature" of most human communication? whats the "avg temperature" of a subset of "good writers"? whats the "avg temperature" of a subset of "smart writers"?
2a. rerun this negative exercise with constrained vocab to english
2b. RL a model to dynamically adjust its own temperature when it is feeling 1) less confident 2) in brainstorm mode
2c. dynamically inject negative temperature every X tokens in a decode, then judge/verify the outcome, to create high variance synthetic data?
its hard for me to follow the train of thought on 2 because negative temp is essentially not that different from ultrahigh temp in practice.
my nonexpert impression is jeff keeps much more of a public profile. hence the natural celebrity goes to him. was this not true way back in the day?
interesting - why use cloudflare vs say hf inference or modal? and is this replicate-cloudflare or normal cloudflare?
also are there sqlite-duckdb sync engines or is that an oxymoron
i mean, addy has literally been at google 14 years, i think internal network has outweighed the external one here
but its this poke: https://poke.com/ verified because TFA is cited in this page https://poke.com/explore
the sign up is very annoying fair warning.
i just released the full AIE workshop covering Manus' product surface area if anyone is also out of the loop and wants to catch up: https://www.youtube.com/watch?v=xz0-brt56L8
(no vested interest am just friends w Ivan who works there. also as a singaporean i guess this is a small W for the Singapore AI scene)
> hundreds of millions of parameters
lol
lmao, even
mind at least naming what to look out for when evaluating PaaSes?
isn't it sensitive to disclose this kind of info when you don't have to? are you worried about your employees all demanding raises when they see this?
does it NOT already do this? i dont see the difference. the image doesnt show any before/after so i dont see any difference