Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

Next.js: Authentication ※ Best practices for Server Components, Server Actions, and Middleware ※ Patterns like Data Access Layers, API Minimization, and Data Transfer Objects Also, aside from headshots, this video is entirely built in React 🤯

Delba

75,417 subscribers

116,318 views • 2 years ago •via X (Twitter)

Science & Technology Education

Anya Rossi• Live Now

Private livecam show

10 Comments

Delba2 years ago

HQ:

Lee Robinson2 years ago

That background music has me feeling like I'm at a SPA... get it... 😂

Delba2 years ago

Lean back, relax, and roll your own auth :mild-panic:

Mona Aghili2 years ago

As I listened to your warm voice and the background music I found myself waiting for you to say Take a deep breath in and exhale.😅

Delba2 years ago

Haha, yea you need it with auth 💆‍♀️

Bilal2 years ago

Thanks - need more guided meditation videos like this on these gnarly topics. :)

Delba2 years ago

🫡🧘‍♀️

Pedro Duarte2 years ago

legeeeeeeend

Delba2 years ago

The coveted Pedro legend comment 🥹

Fabio Coelho2 years ago

love this video effect 😍

Related Videos

A 1-hour introduction to Next.js and React 🎥 This mini course is designed for beginners, but if you've used Next.js before, hopefully you'll still pick up some new tips. We'll build a quiz app using Postgres, starting from React basics and going all the way to Server Actions!

A 1-hour introduction to Next.js and React 🎥 This mini course is designed for beginners, but if you've used Next.js before, hopefully you'll still pick up some new tips. We'll build a quiz app using Postgres, starting from React basics and going all the way to Server Actions!

Lee Robinson

166,780 views • 2 years ago

🚀 Rocket tracking app with Expo Router and React Server Components! ◆ Started with DOM Components ◆ Migrated to native one route at a time ◆ iOS, Android, web, even runs in Expo Go! ◆ Data fetched securely on the server, no hooks needed ◆ Offline support for layouts, loading, scrolling, animations, transitions, and error states We're just getting started ⚡️

🚀 Rocket tracking app with Expo Router and React Server Components! ◆ Started with DOM Components ◆ Migrated to native one route at a time ◆ iOS, Android, web, even runs in Expo Go! ◆ Data fetched securely on the server, no hooks needed ◆ Offline support for layouts, loading, scrolling, animations, transitions, and error states We're just getting started ⚡️

Evan Bacon 🥓

25,393 views • 1 year ago

Demo of forms with React 19 and Next.js. If you've wondered... "Why does the form clear out my input values?" "How do I pass data from my server action → client?" "How do I handle client / server validation?" "How do I display inline errors next to inputs?" This should help!

Demo of forms with React 19 and Next.js. If you've wondered... "Why does the form clear out my input values?" "How do I pass data from my server action → client?" "How do I handle client / server validation?" "How do I display inline errors next to inputs?" This should help!

Lee Robinson

42,736 views • 1 year ago

This was entirely built using Claude AI in React Native It's made with Reanimated for animations, gesture handler, async storage for data persistence and react navigation in Cursor Composer. You can learn from scratch in our 6-hour course:

This was entirely built using Claude AI in React Native It's made with Reanimated for animations, gesture handler, async storage for data persistence and react navigation in Cursor Composer. You can learn from scratch in our 6-hour course:

DesignCode

65,856 views • 1 year ago

Just shipped a new Next.js template! • Uses Postgres and Drizzle for the database • UI components with Tailwind and shadcn/ui • Email/password authentication with JWTs stored to cookies • Dashboard pages with CRUD operations on users/teams • Basic RBAC with Owner and Member roles • Pricing page (/) which connects to Stripe Checkout • Subscription management with Stripe Customer Portal • Global middleware to protect logged-in routes • Local middleware to protect Server Actions / validate schemas • Activity logging system for any user events It's not finished, and there's probably bugs, but it's time to ship 🫡 • Demo: • Code:

Just shipped a new Next.js template! • Uses Postgres and Drizzle for the database • UI components with Tailwind and shadcn/ui • Email/password authentication with JWTs stored to cookies • Dashboard pages with CRUD operations on users/teams • Basic RBAC with Owner and Member roles • Pricing page (/) which connects to Stripe Checkout • Subscription management with Stripe Customer Portal • Global middleware to protect logged-in routes • Local middleware to protect Server Actions / validate schemas • Activity logging system for any user events It's not finished, and there's probably bugs, but it's time to ship 🫡 • Demo: • Code:

Lee Robinson

362,516 views • 1 year ago

we released our react package build an ai chat w/ interactive components in a few lines of code. add it to your app with: npx tambo full-send we support: - streaming for both messages and components - message history and message threads - state manage for generated components - suggested actions based on available components - component library that uses the react package the react package is open-source. server package will be open-sourced later this year.

we released our react package build an ai chat w/ interactive components in a few lines of code. add it to your app with: npx tambo full-send we support: - streaming for both messages and components - message history and message threads - state manage for generated components - suggested actions based on available components - component library that uses the react package the react package is open-source. server package will be open-sourced later this year.

Michael Magán

65,473 views • 1 year ago

Very excited to announce that Flowsta, the authentication system made possible by Holochain, is feature complete and close to public release. Here's a video with a sneak peek at the dashboard that every Flowsta user gets access to. All user data on Flowsta is stored on Holochain. 1 public hApp (Holochain App) for public data like Agent ID, DID (W3C Decentralized ID), Display Name and Thumbnail. Each user has their own private hApp that encrypts all their private data, like password, email and usage meta data. Nobody can access this data without your password and/or recovery keys. It is mathematically impossible for Flowsta staff or anybody else to access this data without you explicitly granting access. This is game-changing. True decentralized censorship resistant authentication and data. All made possible by Holochain. Our next video will give a sneak peek into the Developer Dashboard for adding Flowsta to any Web app. Not just Holochain apps. AMA.. 🎉

Very excited to announce that Flowsta, the authentication system made possible by Holochain, is feature complete and close to public release. Here's a video with a sneak peek at the dashboard that every Flowsta user gets access to. All user data on Flowsta is stored on Holochain. 1 public hApp (Holochain App) for public data like Agent ID, DID (W3C Decentralized ID), Display Name and Thumbnail. Each user has their own private hApp that encrypts all their private data, like password, email and usage meta data. Nobody can access this data without your password and/or recovery keys. It is mathematically impossible for Flowsta staff or anybody else to access this data without you explicitly granting access. This is game-changing. True decentralized censorship resistant authentication and data. All made possible by Holochain. Our next video will give a sneak peek into the Developer Dashboard for adding Flowsta to any Web app. Not just Holochain apps. AMA.. 🎉

Eric Doriean 🌱

37,060 views • 8 months ago

Can AI agents analyze market data and internal research without a compliance nightmare? We built a secure equity research workflow using the Box MCP server + Anthropic's Claude to analyze NVIDIA. Claude pulls internal research from Box, layers in live market data, and generates a polished report via Box Doc Gen. For asset managers and hedge funds, this solves the trade-off between speed and security. No custom connectors, no data leaving Box, and your existing governance is inherited automatically. Watch the full demo 👇

Can AI agents analyze market data and internal research without a compliance nightmare? We built a secure equity research workflow using the Box MCP server + Anthropic's Claude to analyze NVIDIA. Claude pulls internal research from Box, layers in live market data, and generates a polished report via Box Doc Gen. For asset managers and hedge funds, this solves the trade-off between speed and security. No custom connectors, no data leaving Box, and your existing governance is inherited automatically. Watch the full demo 👇

Box

289,025 views • 27 days ago

MCP is mind-blowing. Here is a genius setup that will earn you a promotion with your manager. I have multiple data sources: data in S3, MySQL, and local files. Using Spice (an open-source project), I can co-locate all of that data behind a single SQL endpoint and augment it using MCP. Before, accessing data was slow, and I had to make multiple requests to get anything. After using Spice, I can query the data much faster (since it's mirrored locally), and I don't have to worry about where the data is coming from. Spice acts as an MCP server, so I can connect to it from my IDE or the Claude Desktop app and have access to all the data. But even more cool than that: Spice also acts as an MCP client, so it can connect to other MCP servers. This is where things get really interesting! Watch the video. I'm querying multiple data sources from my IDE and using the Google Maps MCP server for driving directions.

MCP is mind-blowing. Here is a genius setup that will earn you a promotion with your manager. I have multiple data sources: data in S3, MySQL, and local files. Using Spice (an open-source project), I can co-locate all of that data behind a single SQL endpoint and augment it using MCP. Before, accessing data was slow, and I had to make multiple requests to get anything. After using Spice, I can query the data much faster (since it's mirrored locally), and I don't have to worry about where the data is coming from. Spice acts as an MCP server, so I can connect to it from my IDE or the Claude Desktop app and have access to all the data. But even more cool than that: Spice also acts as an MCP client, so it can connect to other MCP servers. This is where things get really interesting! Watch the video. I'm querying multiple data sources from my IDE and using the Google Maps MCP server for driving directions.

Santiago

142,696 views • 1 year ago

Good news for devs working in Visual Studio Code! The MongoDB MCP Server connects your MongoDB data to AI clients, such as GitHub Copilot in VS Code. Now you can ask for collection schemas and data samples, manage users and access, and generate queries all using natural language, right from your editor. Give it a try 👉

Good news for devs working in Visual Studio Code! The MongoDB MCP Server connects your MongoDB data to AI clients, such as GitHub Copilot in VS Code. Now you can ask for collection schemas and data samples, manage users and access, and generate queries all using natural language, right from your editor. Give it a try 👉

MongoDB

19,994 views • 1 year ago

If u buy a new phone and want to transfer all your data from the old to new phone in one piece .... This video is for you !💪

If u buy a new phone and want to transfer all your data from the old to new phone in one piece .... This video is for you !💪

AFRICAMUSTBEFREE!!!!!!!

53,454 views • 1 month ago

New course: MCP: Build Rich-Context AI Apps with Anthropic. Learn to build AI apps that access tools, data, and prompts using the Model Context Protocol in this short course, created in partnership with Anthropic Anthropic and taught by Elie Schoppik Elie Schoppik, its Head of Technical Education. Connecting AI applications to external systems that bring rich context to LLM-based applications has often meant writing custom integrations for each use case. MCP is an open protocol that standardizes how LLMs access tools, data, and prompts from external sources, and simplifies how you provide context to your LLM-based applications. For example, you can provide context via third-party tools that let your LLM make API calls to search the web, access data from local docs, retrieve code from a GitHub repo, and so on. MCP, developed by Anthropic, is based on a client-server architecture that defines the communication details between an MCP client, hosted inside the AI application, and an MCP server that exposes tools, resources, and prompt templates. The server can be a subprocess launched by the client that runs locally or an independent process running remotely. In this hands-on course, you'll learn the core architecture behind MCP. You’ll create an MCP-compatible chatbot, build and deploy an MCP server, and connect the chatbot to your MCP server and other open-source servers. Here’s what you’ll do: - Understand why MCP makes AI development less fragmented and standardizes connections between AI applications and external data sources - Learn the core components of the client-server architecture of MCP and the underlying communication mechanism - Build a chatbot with custom tools for searching academic papers, and transform it into an MCP-compatible application - Build a local MCP server that exposes tools, resources, and prompt templates using FastMCP, and test it using MCP Inspector - Create an MCP client inside your chatbot to dynamically connect to your server - Connect your chatbot to reference servers built by Anthropic’s MCP team, such as filesystem, which implements filesystem operations, and fetch, which extracts contents from the web as markdown - Configure Claude Desktop to connect to your server and others, and explore how it abstracts away the low-level logic of MCP clients - Deploy your MCP server remotely and test it with the Inspector or other MCP-compatible applications - Learn about the roadmap for future MCP development, such as multi-agent architecture, MCP registry API, server discovery, authorization, and authentication MCP is an exciting and important technology that lets you build rich-context AI applications that connect to a growing ecosystem of MCP servers, with minimal integration work. Please sign up here!

New course: MCP: Build Rich-Context AI Apps with Anthropic. Learn to build AI apps that access tools, data, and prompts using the Model Context Protocol in this short course, created in partnership with Anthropic Anthropic and taught by Elie Schoppik Elie Schoppik, its Head of Technical Education. Connecting AI applications to external systems that bring rich context to LLM-based applications has often meant writing custom integrations for each use case. MCP is an open protocol that standardizes how LLMs access tools, data, and prompts from external sources, and simplifies how you provide context to your LLM-based applications. For example, you can provide context via third-party tools that let your LLM make API calls to search the web, access data from local docs, retrieve code from a GitHub repo, and so on. MCP, developed by Anthropic, is based on a client-server architecture that defines the communication details between an MCP client, hosted inside the AI application, and an MCP server that exposes tools, resources, and prompt templates. The server can be a subprocess launched by the client that runs locally or an independent process running remotely. In this hands-on course, you'll learn the core architecture behind MCP. You’ll create an MCP-compatible chatbot, build and deploy an MCP server, and connect the chatbot to your MCP server and other open-source servers. Here’s what you’ll do: - Understand why MCP makes AI development less fragmented and standardizes connections between AI applications and external data sources - Learn the core components of the client-server architecture of MCP and the underlying communication mechanism - Build a chatbot with custom tools for searching academic papers, and transform it into an MCP-compatible application - Build a local MCP server that exposes tools, resources, and prompt templates using FastMCP, and test it using MCP Inspector - Create an MCP client inside your chatbot to dynamically connect to your server - Connect your chatbot to reference servers built by Anthropic’s MCP team, such as filesystem, which implements filesystem operations, and fetch, which extracts contents from the web as markdown - Configure Claude Desktop to connect to your server and others, and explore how it abstracts away the low-level logic of MCP clients - Deploy your MCP server remotely and test it with the Inspector or other MCP-compatible applications - Learn about the roadmap for future MCP development, such as multi-agent architecture, MCP registry API, server discovery, authorization, and authentication MCP is an exciting and important technology that lets you build rich-context AI applications that connect to a growing ecosystem of MCP servers, with minimal integration work. Please sign up here!

Andrew Ng

142,010 views • 1 year ago

Three Framer components using its Data() API. They’re self contained code components sharing a single state to sync SoundCloud playback, live ticker data, and a fully interactive record player. Sound on 🔊 The video shows various states from staggered first time track use (compensated for arm position), play and pause in one component and affecting another one, arm drag to scrub a track on the vinyl, and a ticker that takes data depending on states.

Three Framer components using its Data() API. They’re self contained code components sharing a single state to sync SoundCloud playback, live ticker data, and a fully interactive record player. Sound on 🔊 The video shows various states from staggered first time track use (compensated for arm position), play and pause in one component and affecting another one, arm drag to scrub a track on the vinyl, and a ticker that takes data depending on states.

Lee Black

15,998 views • 7 months ago

We have data in abundance now. The real value isn't within the RAW Data, but is this data validated and verified? More value in data refinement. We have a solution for this which is validated by 6 years of research and development with the Department of Defense Now securing and validating commercial data from partners like Common Crawl and Panasonic

We have data in abundance now. The real value isn't within the RAW Data, but is this data validated and verified? More value in data refinement. We have a solution for this which is validated by 6 years of research and development with the Department of Defense Now securing and validating commercial data from partners like Common Crawl and Panasonic

Constellation²

10,559 views • 1 year ago

🚨 POC for CVE-2025-55182 that works on Next.js 16.0.6 Here are the exact, battle-tested queries you need — Censys, Shodan, FOFA, ZoomEye, Quake, BinaryEdge, and Nuclei matchers — all tuned specifically to find Next.js RSC / React Server Components instances vulnerable to CVE-2025-55182 (React2Shell). ⸻ ✅ 1. SHODAN QUERY (380K+ ASSETS) Find all servers leaking RSC Server Actions: Basic Query "Vary: RSC, Next-Router-State-Tree" More Aggressive Variant http.headers.vary:"RSC" AND http.headers.vary:"Next-Router-State-Tree" Superwide Coverage "Next-Router-State-Tree" OR "x-nextjs-cache" OR "server-actions" OR "__RSC__" Focused on Vulnerable Cache Indicators "x-nextjs-cache: HIT" "Next-Router-State-Tree" ⸻ ✅ 2. CENSYS QUERY (270K+ ASSETS) (match the screenshot you posted) Exact Censys Search services.http.response.headers.vary: "RSC, Next-Router-State-Tree" Safer Multi-Matcher services.http.response.headers.vary: "RSC" AND services.http.response.headers.vary: "Next-Router-State-Tree" Detect RSC Payload Exposure (critical) services.http.response.body: "__RSC__" Detect Flight Data Leaks services.http.response.body: "server-reference-manifest" ⸻ ✅ 3. FOFA QUERY (CHINA’S OSINT GIANT) (VERY POWERFUL for RSC/Next.js) Exact Header Based header="Next-Router-State-Tree" && header="RSC" Alternative (match screenshot patterns) "Next-Router-State-Tree" && "x-nextjs-cache" For massive result count body="__RSC__" || header="server-actions" ⸻ ✅ 4. ZOOMEYE QUERY ZoomEye scans often catch Node.js apps Shodan misses. Exact Unicode-Ready Query "Next-Router-State-Tree" && "RSC" Advanced app:"Next.js" && header:"RSC" ⸻ ✅ 5. QUAKE SEARCH (360K+ MATCHES) header:"Next-Router-State-Tree" AND header:"RSC" ⸻ ✅ 6. BINARYEDGE QUERY http.response.headers.vary:"Next-Router-State-Tree" ⸻ ✅ 7. QUERY headers:"Next-Router-State-Tree" && headers:"RSC" ⸻ 🎯 8. NUCLEI MATCHER (to detect RSC without scanning payloads) If you want a nuclei detector you can plug into your scanner: matchers: - type: word part: header words: - "RSC" - "Next-Router-State-Tree" - "server-actions" - "__RSC__" ⸻ 🚩 BONUS — THE MOST ADVANCED CROSS-ENGINE QUERY Use this when you want maximum global coverage: "Next-Router-State-Tree" OR "RSC" OR "__RSC__" OR "server-actions" OR "x-nextjs-cache" OR "Next-Server-Action" This identifies: •Next.js App Router •RSC endpoints •Server Actions •Flight data APIs •Pages exposing cache HITs (required for exploitation) •Systems likely vulnerable to CVE-2025-55182 (React2Shell)

🚨 POC for CVE-2025-55182 that works on Next.js 16.0.6 Here are the exact, battle-tested queries you need — Censys, Shodan, FOFA, ZoomEye, Quake, BinaryEdge, and Nuclei matchers — all tuned specifically to find Next.js RSC / React Server Components instances vulnerable to CVE-2025-55182 (React2Shell). ⸻ ✅ 1. SHODAN QUERY (380K+ ASSETS) Find all servers leaking RSC Server Actions: Basic Query "Vary: RSC, Next-Router-State-Tree" More Aggressive Variant http.headers.vary:"RSC" AND http.headers.vary:"Next-Router-State-Tree" Superwide Coverage "Next-Router-State-Tree" OR "x-nextjs-cache" OR "server-actions" OR "RSC" Focused on Vulnerable Cache Indicators "x-nextjs-cache: HIT" "Next-Router-State-Tree" ⸻ ✅ 2. CENSYS QUERY (270K+ ASSETS) (match the screenshot you posted) Exact Censys Search services.http.response.headers.vary: "RSC, Next-Router-State-Tree" Safer Multi-Matcher services.http.response.headers.vary: "RSC" AND services.http.response.headers.vary: "Next-Router-State-Tree" Detect RSC Payload Exposure (critical) services.http.response.body: "RSC" Detect Flight Data Leaks services.http.response.body: "server-reference-manifest" ⸻ ✅ 3. FOFA QUERY (CHINA’S OSINT GIANT) (VERY POWERFUL for RSC/Next.js) Exact Header Based header="Next-Router-State-Tree" && header="RSC" Alternative (match screenshot patterns) "Next-Router-State-Tree" && "x-nextjs-cache" For massive result count body="RSC" || header="server-actions" ⸻ ✅ 4. ZOOMEYE QUERY ZoomEye scans often catch Node.js apps Shodan misses. Exact Unicode-Ready Query "Next-Router-State-Tree" && "RSC" Advanced app:"Next.js" && header:"RSC" ⸻ ✅ 5. QUAKE SEARCH (360K+ MATCHES) header:"Next-Router-State-Tree" AND header:"RSC" ⸻ ✅ 6. BINARYEDGE QUERY http.response.headers.vary:"Next-Router-State-Tree" ⸻ ✅ 7. QUERY headers:"Next-Router-State-Tree" && headers:"RSC" ⸻ 🎯 8. NUCLEI MATCHER (to detect RSC without scanning payloads) If you want a nuclei detector you can plug into your scanner: matchers: - type: word part: header words: - "RSC" - "Next-Router-State-Tree" - "server-actions" - "RSC" ⸻ 🚩 BONUS — THE MOST ADVANCED CROSS-ENGINE QUERY Use this when you want maximum global coverage: "Next-Router-State-Tree" OR "RSC" OR "RSC" OR "server-actions" OR "x-nextjs-cache" OR "Next-Server-Action" This identifies: •Next.js App Router •RSC endpoints •Server Actions •Flight data APIs •Pages exposing cache HITs (required for exploitation) •Systems likely vulnerable to CVE-2025-55182 (React2Shell)

X

10,469 views • 7 months ago

Your Lovable apps are now built to be found. New apps are now server side rendered and discoverable through search engines like Google and AI answer engines like ChatGPT, Claude, and Perplexity. Existing apps get prerendering. Additionally, access Semrush search intelligence in-app. Chat with your SEO data, understand how you’re performing, and improve discoverability. You can also run SEO reviews on demand, and fix all suggestions in one click.

Your Lovable apps are now built to be found. New apps are now server side rendered and discoverable through search engines like Google and AI answer engines like ChatGPT, Claude, and Perplexity. Existing apps get prerendering. Additionally, access Semrush search intelligence in-app. Chat with your SEO data, understand how you’re performing, and improve discoverability. You can also run SEO reviews on demand, and fix all suggestions in one click.

Lovable

175,621 views • 2 months ago

Consistent Hashing Explained Simply Let's break down consistent hashing in a way that's easy to get. It's a handy technique for distributing data evenly across servers. And if you're more of a visual learner, don't miss the attached video which brings this concept to life. Here's how it works: We don't just hash our data keys; we also hash the server names using the same method. This puts everything on a scale, known as the hash space, which we think of as a big circular ring. So, imagine we've got a few servers. We hash them and place them on this ring. We do the same with our data, hashing it by key. To figure out where to store a piece of data, we travel clockwise on the ring from where the data lands until we bump into a server. Like, data key 0 might end up on server 0, and key 1 on server 1. Adding a new server? Only the data near the new server needs to shift. And if a server has to go? Only the data it was holding needs a new spot. But there's a little challenge: sometimes, data doesn't spread out evenly. The fix? Virtual nodes. They're like mini-replicas of a server placed around the ring. The more virtual nodes we have, the better the balance. But there's a catch: more virtual nodes mean more memory usage for tracking them, and it can make the whole system a bit more complex to manage. – Subscribe to our weekly newsletter to get a Free System Design PDF (158 pages):

Consistent Hashing Explained Simply Let's break down consistent hashing in a way that's easy to get. It's a handy technique for distributing data evenly across servers. And if you're more of a visual learner, don't miss the attached video which brings this concept to life. Here's how it works: We don't just hash our data keys; we also hash the server names using the same method. This puts everything on a scale, known as the hash space, which we think of as a big circular ring. So, imagine we've got a few servers. We hash them and place them on this ring. We do the same with our data, hashing it by key. To figure out where to store a piece of data, we travel clockwise on the ring from where the data lands until we bump into a server. Like, data key 0 might end up on server 0, and key 1 on server 1. Adding a new server? Only the data near the new server needs to shift. And if a server has to go? Only the data it was holding needs a new spot. But there's a little challenge: sometimes, data doesn't spread out evenly. The fix? Virtual nodes. They're like mini-replicas of a server placed around the ring. The more virtual nodes we have, the better the balance. But there's a catch: more virtual nodes mean more memory usage for tracking them, and it can make the whole system a bit more complex to manage. – Subscribe to our weekly newsletter to get a Free System Design PDF (158 pages):

Sahn Lam

36,787 views • 2 years ago

Robots enter data centers! 💽 SeRo developed by NAVER LABS, is built for one of the most overlooked but critical tasks in a data center: managing servers in the IT warehouse. It can autonomously load and unload servers, identify their asset numbers, and log their lifecycle data. Physically, SeRo is designed tall to handle racks up to three meters high, maximizing storage density. SeRo also works as part of a larger system. It hands assets to GaRo, an autonomous transport robot, for seamless movement between warehouse and server room. More AI ops, more data centers, more data centers ops... Perfect market for robotics! 🦾

Robots enter data centers! 💽 SeRo developed by NAVER LABS, is built for one of the most overlooked but critical tasks in a data center: managing servers in the IT warehouse. It can autonomously load and unload servers, identify their asset numbers, and log their lifecycle data. Physically, SeRo is designed tall to handle racks up to three meters high, maximizing storage density. SeRo also works as part of a larger system. It hands assets to GaRo, an autonomous transport robot, for seamless movement between warehouse and server room. More AI ops, more data centers, more data centers ops... Perfect market for robotics! 🦾

Lukas Ziegler

30,311 views • 10 months ago

Had a blast talking about Next.js 16 at React Summit yesterday! I built a Chatbot to show off some new features in Next that help you build apps with instant page navs and snappy interactions, even for apps with dynamic personalized data. Here's some highlights from the talk:

Had a blast talking about Next.js 16 at React Summit yesterday! I built a Chatbot to show off some new features in Next that help you build apps with instant page navs and snappy interactions, even for apps with dynamic personalized data. Here's some highlights from the talk:

Sam Selikoff

48,705 views • 8 months ago

I made this site entirely in Figma using Locofy.ai Responsive layout, breakpoints, pages, animations. The code is near perfect and exportable to React w/ styles, components and variables. For simple sites like portfolios and landing pages, you can do everything in Figma.

I made this site entirely in Figma using Locofy.ai Responsive layout, breakpoints, pages, animations. The code is near perfect and exportable to React w/ styles, components and variables. For simple sites like portfolios and landing pages, you can do everything in Figma.

Meng To

32,205 views • 2 years ago