Readit NewsIt’s possible `/` redirects but other hidden routes phish. If someone gets e.g.: a fake password reset email, it might help the attacker bypass sanity checks users make.
Rauchg commented on Falsehoods programmers believe about TCP lwn.net/Articles/990281/... · Posted by u/todsacerdoti
Falsehoods programmers believe: TCP/IP can be coherently mapped to the OSI model.
Falsehoods programmers believe: the OSI model
Rauchg commented on Show HN: A fast OSS voice assistant swift-ai.vercel.app/... · Posted by u/Rauchg
Looking at the git repo (https://github.com/ai-ng/swift), it was made by some web developer, not Vercel. Likely OP (Vercel CEO) just made a mistake posting it as a "Show HN".
I've been acting mostly as the 'ideas guy' and helping with the architecture / QA. It's a great way for me to dogfood Vercel and build empathy as a user in an external org, using external services.
> The code below is all you need to stream text with Chrome AI and the Vercel AI SDK. ... `chromeai` implements a Provider that uses `window.ai` under the hood
Leave it to Vercel to announce `window.ai` on Google's behalf by showing off their own abstraction but not the actual Chrome API.
Here's a blog post from a few days ago that shows how the actual `window.ai` API works [0]. The code is extremely simple and really shouldn't need a wrapper:
const model = await window.ai.createTextSession();
const result = await model.prompt("What do you think is the meaning of life?");
Someone in our community created a provider and I wanted to showcase it.
It’s nice insofar with very little abstraction, runtime, and bundle size overhead, you can easily switch between models without having to learn a new API.
If I went back in time, I would have called it Routing Middleware or Routing Handler. A specific hook to intercept during the routing phase, which can be delivered to the CDN edge for specialized providers. It’s also a somewhat advanced escape hatch.
Since OP mentions logging, it’s worth noting that for instrumentation and observability we’ve embraced OpenTelemetry and have an instrumentation.ts convention[2]
[1] https://nextjs.org/blog/next-15-5#nodejs-middleware-stable
[2] https://nextjs.org/docs/app/api-reference/file-conventions/i...