Turn on Fluid! https://vercel.com/fluid — we specifically designed it to make full stack as efficient as self hosting servers

Multiplying onchain economies. Working on interfaces /comint and intelligence @tenfold
Past: AI and crypto rubinovitz.com

We’re working on this a ton. Any examples that come to mind?

Risk @Stripe prev: wallets @bitski, search @airbnb | https://www.castsense.xyz/ 

Alchemist. 
Block Builder. 
Creator.
Degen. 
Ethereum dev. 
Farcaster Framer.

Definitely want to accept crypto at some point. Dealing with the fiat currency payment systems is hell and it’s a good reminder of why I’m long term bullish on crypto

We’re investing quite a bit on v0 full stack capabilities: integrations, better server-side code execution support, etc. thanks for the feedback!

We support /llms.txt on AI SDK:

crypto user researcher /openux || 
internet-native mysticism /manansh

We’re investing quite a bit on v0 full stack capabilities: integrations, better server-side code execution support, etc. thanks for the feedback!

We support /llms.txt on AI SDK: https://sdk.vercel.ai/llms.txt

Building @warpcast and @farcaster / dad / like to read, cook, ski, code

Immutable hashed assets should always send immutable cache control headers. If you’re using a custom CDN you need to handle purging etc for pages that set cache-control. On Vercel like you said we do this automatically and we don’t recommend putting other CDNs in front as it causes cache coherence issues.

building fiids.xyz, bondes.xyz and wyat.live

weird internet kid. word rotator. yapping on /okbanger. playing with @wannanaplabs. curating in /cameron | dev + vet + HBS. 
seemore.tv/cameron 🫡

This is being fixed now. We just shipped better support for Tailwind configs. We will have a dedicated section of Community for themes that you can fork.

Cron jobs: what DX would you like? They’re http endpoints so fairly easy to test.

Backups: are you referring to KV / Postgres? Those are transitioning to Marketplace and you now get the full power of Upstash and Neon, at same price, but with an integrated experience on our console.

Not anymore with vercel.com/fluid — we designed it to precisely solve the Achilles heel of serverless: waiting on I/O and timeouts

Elevating onchain creators @brightmoments @ampsfun @nodefoundation

Heard. We’re cooking on a bunch of ideas in this direction.

I’d love to hear feedback about Next / Vercel / v0 / AI SDK etc from this part of the world.

We proudly host and power some amazing crypto projects on our platform and always looking to get better.

I dream of a social network of software. It’d be interesting to explore what Farcaster Frames x v0.dev could look like.

Imagine if shipping was as easy as posting.

vercel

/frontend dev・founder/decentralized data wrangler /blockhead・UI/UX abstractionist・DeFi/web3 builder・dropout・24・prev /dydx, ritual.net・x.com/darryl__yeo

It’s harder than it sounds. The naive way of doing it can also result in overloading the function instance and degrading performance.

The very attractive thing about the 1:1 request to function model was a complete eradication of the “noisy neighbor” problem that e.g.: VPSs suffer from. 

tl;DR: We focused on quality first then optimized.

Fun OSS encounter story: 15 years ago, the WebSocket spec just came out and preliminary implementations were live. I wanted to prototype a little in-browser MMO, but the one implementation out there was node.websocket.js by an Argentinian fella named Guillermo Rauch.

Guillermo's library was only half-working for what I needed, so I ended up forking it and rewriting it entirely (https://github.com/shazow/node.websocket.js). I suggested some of the changes upstream, we discussed over email. I built my demo using my fork, while Guillermo also did a rewrite that became socket.io which was fantastic! So good that I didn't feel the need to keep working on my fork.

It's funny to think that there's an alternate universe where I went on to build the urllib3 of nodejs websockets.

It wasn't until yesterday that I realized: That Guillermo is the same @rauchg who went on to create /nextjs and founded @vercel. I didn't stand a chance! 🙇

Open source doesn’t happen in a vacuum and it’s the result of sharing and learning from the work of others. Great memories of the beginning of socket.io and @shazow.eth’s part in the story.

A doodler and computerer. I like permissive/permissionless open source, smart contracts, p2p systems, room-scale VR, and NixOS.

shazow.net

Currently: WhatsABI

Tongue in cheek given there’s no doge content :P

Memes

@stackdotso. Prev CTO/cofounder of mirror. strangechances

Frontend

cma.xyz. Founder /paragraph, ceo /mirror, previously at Google & Coinbase 