Goldman

What UUID version does auth.users.id use today (v4?) ? Also, with PostgreSQL supporting UUID v7, would you recommend using v7 for new tables? Any plans or reasons to support v7 for Auth IDs, or should we stick with the IDs generated by Supabase Auth? @dshukertjr

Spent 30 mins debugging Server Actions. I was sending a TipTap JSON object and some fields were silently stripped. Turns out it’s not Next.js it’s React Server Actions serialization. Server Actions made me forget we always stringify data before sending it to server

@timneutkens Spent 30 mins debugging Server Actions. I was sending a TipTap JSON object and some fields were silently stripped. Turns out it’s not Next.js it’s React Server Actions serialization. Server Actions made me forget we always stringify data before sending it to server

@dshukertjr @supabase Found it. I was looking in the Authentication tab earlier, but it’s under Project Settings > JWT Keys...

@Maxvhanamane @supabase You should be able to configure it from the auth setting in the dashboard, but did you already look there?

@supabase @dshukertjr how can I reduce the jwt access token expiry time in Supabase? The default seems to be 1 hour. Is it possible to change it?

any updates?

@JioCare @Airtel_Presence @airtelindia

@supabase @kiwicopple @AshwiniVaishnaw DNS is still not resolving in India. Are there any regulatory or government-related restrictions involved? Would appreciate a clear update so we can plan accordingly. Seeing lot of speculation on X can you clarify what’s actually happening?

@JioCare I am not using JioFiber. I am facing this issue on my Jio mobile SIM (Jio cellular data). Please visit this site to understand what is going on status.supabase.com

@Maxvhanamane Hi Max, we understand your concern and we are here to help. Please DM your location, registered number and JioFiber ID and elaborate the issue you are facing for further assistance - Mohit twitter.com/messages/compo…

@JioCare @reliancejio When are you going to fix the problem? It is affecting the users...

Hey @supabase saw the recent outages were mostly in other regions and thought I was safe but now India connectivity issues too. Spent 1hour restarting the project and debugging before checking the status page. Can’t access login on my dev app right now. Any update on AP-South-1?

@timneutkens @infinterenders Got it, that makes sense.. appreciate the clarification and RFC link.I didn’t realize it came straight from the React RFC. Confused me at first, but after using App Router + RSC in production, the architecture feels kind of genius.

@Maxvhanamane @infinterenders "use client" was created by the React team, in a React RFC, it's a React feature. Here's the docs: react.dev/reference/rsc/… Next.js team wasn't involved in the decision. Only Shopify Hydrogen was using RSC at the time.

the reason the app router hate in the history of web dev, most updates are additive app router was transformative by default here the noise comes the engineers that lost there intuition for years, react was a client side thing for many of us that got them mental model where everything happens in the browser. app router forced developers back to a Request/Response model (like PHP or Rails) but wrapped in React syntax . Comparing the App Router to "old school PHP" is a lazy, surface-level take from people who aren't looking under the hood The "PHP" comparison comes from a place of fear and misunderstanding. php bros kinda feels stop reinventing us lol the funny thing is people see async function component() with a db call and immediately think we went back to 2005 and started writing php includes again that reaction only makes sense if you freeze your mental model at “server renders html, browser gets a dead document” but that’s not what’s happening under the hood in the old php way you hit a url, the server runs a script, it concatenates strings into html, sends it to the browser, and that’s it. the process ends. the browser gets a dumb document. if you want interactivity you bolt on some jquery after the fact. request → response → full page reload. every click resets everything . the app router is not even doing that. when you write an async server component in Next.js, you are not generating a static blob of html and calling it a day you are generating a react server component tree that tree is serialized through the react flight protocol and streamed to the client. the browser is not just “rendering html.” it is running React, receiving a structured payload, diffing it against the existing tree, and merging it into the live client tree. php is page level ownership. one request owns the whole page , render cycle decides everything. you either cache the entire page or you don’t. it’s a blob man the app router is component level ownership one component can be fully static and cached forever. another can be dynamic and revalidated every request. another can stream in with suspense boundaries all you get in the same route it’s heaven idk why people won’t choose heaven that’s not request → response. that’s hybrid synchronization between server and client and the biggest difference nobody talks about: state continuity in php, every navigation is a hard reset your video stops your input state dies. your scroll position jumps everything is rebuilt from zero. in the app router, when you navigate, the server doesn’t send a new document. it sends an rsc payload react applies a minimal patch client components that didn’t change stay mounted their state survives. your video keeps playing, sidebar doesn’t reset. php was templating asf next is ui orchestration this is architectural orchestration across network boundaries, with granular caching, streaming, partial hydration, and state preservation baked in at the framework level. seeing async in a component and calling it “php again” is like seeing a new database and calling it “just sql.” if you ask a senior engineer why they hate the app router , the word "cache " will come up in just 10 seconds. To be fair, the noise obscures the fact that the App Router solves Impossible Problems in the history of web Dev ;) the end of loading spinners using streaming and suspense , you can send the "shell" of a page instantly and pipe in the data-heavy parts as they arrive no more blank white screens the noise is the sound of thousands of developers having their "muscle memory" erased that’s it more than that if you got next is framework that you don’t need just move off you have got skills issues of not choosing next :)

@infinterenders What about react compiler? it handles most of the memoization right?

React.memo looks like performance work, but most of the time it’s just extra bookkeeping. You’re not removing work, you’re adding a check. Every time a parent renders, React first shallow-compares the previous props with the next ones. That comparison itself costs time, usually around 0.01 ms. Re-running a small component function is also cheap, roughly 0.02 to 0.05 ms. If memo doesn’t bail out, which is very common in real apps, you now pay for both. Compare plus render. That’s already slower than just rendering. You can see this clearly in the profiler. Take a simple component and log how long it takes to render. The time is basically noise. Now wrap it in React.memo and pass an inline function or an object prop. The render still happens, but now the comparison runs every time too. Inline callbacks break memo. Object props break memo. Children break memo. The key detail is that the comparison still runs even when memo fails. Lists make this worse fast. Memoizing 200 list items means 200 shallow prop comparisons on every parent render. In real applications, most of those comparisons fail and most of the items still render. The total render time often goes up, even though the commit count sometimes goes down. People see fewer renders and assume it’s faster, without looking at the actual duration. Then comes the follow-up mistake. Memo doesn’t seem to “work,” so useCallback and useMemo get added. Now there are dependency arrays everywhere. Logic is split across hooks. Refactors become risky because reference identity suddenly matters. All of this to save a render that costs a few hundredths of a millisecond. React.memo does have a real place. Heavy components that take multiple milliseconds to render, stable props, and a p

@schlimmson Is React Native Web actually production ready for serious web apps, or is separate React (web) + React Native (mobile) still the safer choice? What issues do teams hit in practice? I’d love to see a detailed video on this.

This is how it looks before adding framer motion animations.

This is how it looks before adding framer motion animations...

@mysticwillz Either you are setting the same state value, or you haven’t created a new object reference when updating the state....

You’re in a frontend interview. They ask: "Your React state updates but the UI doesn’t re-render. Why?"

Added drag-and-drop functionality to the Chapters section. Now users can reorder chapters by dragging them or drag and drop them into the trash can to delete.....