正在加载视频...

视频加载失败

加载此视频时出现问题。这可能是由于临时网络问题，或视频可能不可用。

🧵1/2 Socket Programming in C: Server-Side Basics - Set up a server using socket(), bind(), and listen(). - Accept client connections with accept(). - Send and receive data over TCP. Video 1: Server-Side in C! Video 2: Client-Side Programming will be uploaded soon—stay tuned! 🖥️

trish

35,239 subscribers

2,925,659 次观看 • 1 年前 •via X (Twitter)

教育科学技术

Anya Rossi• Live Now

Private livecam show

11 条评论

trish 的头像

trish1 年前

Video 2: Client-Side Programming

Vivek Galatage 的头像

Vivek Galatage1 年前

Additionally, this is a great resource too -

trish 的头像

trish1 年前

Oh nice, thanks for sharing

Sasha Fly-Style 🇺🇦 的头像

Sasha Fly-Style 🇺🇦1 年前

Hi! Where can I find your vim/neovim setup? It is cool, I like it.

trish 的头像

trish1 年前

oh sure, I will make a post for this setup

Lenny 的头像

Lenny1 年前

Great video! Would love a follow up for handling multiple clients!!

trish 的头像

trish1 年前

Thanks ☺️

Anurag Hagawane 的头像

Anurag Hagawane1 年前

Tried it today morning, C is fun!

Anirban Kanungoe 的头像

Anirban Kanungoe1 年前

Wow

_joYPad 的头像

_joYPad1 年前

Wich editor is this, you are using here?

trish 的头像

trish1 年前

I'm using neovim

相关视频

❌ Avoid resolving a promise in a server component and block rendering. ✅ Resolve the promise in the client side with `Reac.use()`

❌ Avoid resolving a promise in a server component and block rendering. ✅ Resolve the promise in the client side with `Reac.use()`

George Moller

47,215 次观看 • 1 年前

In LiveView, we keep the state in one place - the server - and it simplifies a lot. But sometimes the state on the client is preferred, or even necessary, and we can't use LiveView for that part. Unless we have a LiveView that runs on the client 👀 Using Popcorn, we managed to run LiveView fully in the browser – here's a POC 🎉 The approach is to have a fully client-side LiveView rendered by a server-side one, and they can communicate with each other. Try it out:

In LiveView, we keep the state in one place - the server - and it simplifies a lot. But sometimes the state on the client is preferred, or even necessary, and we can't use LiveView for that part. Unless we have a LiveView that runs on the client 👀 Using Popcorn, we managed to run LiveView fully in the browser – here's a POC 🎉 The approach is to have a fully client-side LiveView rendered by a server-side one, and they can communicate with each other. Try it out:

Elixir by Software Mansion

13,559 次观看 • 10 个月前

New video showing off the Cloudflare Developers Agent Framework just landed showing off my favorite features: ✅ Synchronized Agent state and client-side ✅ SQL storage (sorry uncle bathrobe) ✅ Durable Execution of third party YouTube APIs ✅ Human in the Loop ✅ Client + Server RPC

New video showing off the Cloudflare Developers Agent Framework just landed showing off my favorite features: ✅ Synchronized Agent state and client-side ✅ SQL storage (sorry uncle bathrobe) ✅ Durable Execution of third party YouTube APIs ✅ Human in the Loop ✅ Client + Server RPC

Craig Dennis

25,157 次观看 • 1 年前

If you’re playing on MonkeyTilt, the outcome might already be decided BEFORE you bet “The cryptography behind every bet has always been sound” We tested it It isn’t... we sent two different client seeds for the same nonce same result both times the server is ignoring the client seed entirely the player has ZERO influence on outcomes — what we did — opened the MonkeyTilt provably fair verifier with a revealed server seed entered nonce 1 → got 3.04x changed the client seed same server seed, same nonce → 3.04x changed it again → 3.04x the client seed has ZERO effect on the outcome — why this matters — in a provably fair system the outcome is derived from: -server seed -client seed -nonce the client seed exists so the player contributes randomness the server CAN’T predict if it’s ignored the server knows every outcome BEFORE you bet the hash commitment proves nothing because the server already controls all the inputs — not a frontend bug — we checked the network traffic the verifier sends a WebSocket request with: -client seed -server seed -nonce the server receives different client seeds and returns the same result anyway request 1 → client_seed “Clientseed123456789” → 3.04x request 2 → client_seed “NEWSEED12345” → 3.04x this is the server ignoring input not a display issue — live bet traffic — placing a Limbo bet returns: -random_multiplier -total_payout -round_closed that’s it no hash no seed reference no nonce no proof seeds are fetched from a separate endpoint game engine and seed system are DISCONNECTED — nonce verification — you can only verify nonces you’ve already played in a real system all outcomes are predetermined once the server seed is committed - they’re deterministic blocking future nonces suggests results don’t exist until you bet — summary — -client seed ignored by server -no cryptographic proof in bet responses -game engine and seed system DISCONNECTED -nonce verification restricted this isn’t provably fair it looks like provably fair UI on top of server side RNG MonkeyTilt should probably address this anyone can verify this themselves in 60 seconds - open the verifier, change the client seed, watch the result stay the same

If you’re playing on MonkeyTilt, the outcome might already be decided BEFORE you bet “The cryptography behind every bet has always been sound” We tested it It isn’t... we sent two different client seeds for the same nonce same result both times the server is ignoring the client seed entirely the player has ZERO influence on outcomes — what we did — opened the MonkeyTilt provably fair verifier with a revealed server seed entered nonce 1 → got 3.04x changed the client seed same server seed, same nonce → 3.04x changed it again → 3.04x the client seed has ZERO effect on the outcome — why this matters — in a provably fair system the outcome is derived from: -server seed -client seed -nonce the client seed exists so the player contributes randomness the server CAN’T predict if it’s ignored the server knows every outcome BEFORE you bet the hash commitment proves nothing because the server already controls all the inputs — not a frontend bug — we checked the network traffic the verifier sends a WebSocket request with: -client seed -server seed -nonce the server receives different client seeds and returns the same result anyway request 1 → client_seed “Clientseed123456789” → 3.04x request 2 → client_seed “NEWSEED12345” → 3.04x this is the server ignoring input not a display issue — live bet traffic — placing a Limbo bet returns: -random_multiplier -total_payout -round_closed that’s it no hash no seed reference no nonce no proof seeds are fetched from a separate endpoint game engine and seed system are DISCONNECTED — nonce verification — you can only verify nonces you’ve already played in a real system all outcomes are predetermined once the server seed is committed - they’re deterministic blocking future nonces suggests results don’t exist until you bet — summary — -client seed ignored by server -no cryptographic proof in bet responses -game engine and seed system DISCONNECTED -nonce verification restricted this isn’t provably fair it looks like provably fair UI on top of server side RNG MonkeyTilt should probably address this anyone can verify this themselves in 60 seconds - open the verifier, change the client seed, watch the result stay the same

CoinBets🔍

20,973 次观看 • 7 个月前

Implemented this credits system with Supabase x 🍋 A credit order fires a webhook that updates the database and also sets everything client side with Next.js cookies + server actions 🍪 Here it is end to end! 🚀 No sign-in, etc. required ⭐️

Implemented this credits system with Supabase x 🍋 A credit order fires a webhook that updates the database and also sets everything client side with Next.js cookies + server actions 🍪 Here it is end to end! 🚀 No sign-in, etc. required ⭐️

jhey ʕ•ᴥ•ʔ

54,049 次观看 • 2 年前

Finally. I shipped a side-project. Introducing inbrowser. Pluggable AI architecture totally in the browser. site: repo: @inbrowser/model: on-device w/ transformers.js & webgpu. Cloud model proxies and OpenRouter BYOK flows. @inbrowser/agent: pluggable client-side agent architecture @inbrowser/resumable: pick up and resume across refreshes @inbrowser/relay: when you need a server, syncs resumable jobs and picks up across network drops and backgrounded tabs.

Finally. I shipped a side-project. Introducing inbrowser. Pluggable AI architecture totally in the browser. site: repo: @inbrowser/model: on-device w/ transformers.js & webgpu. Cloud model proxies and OpenRouter BYOK flows. @inbrowser/agent: pluggable client-side agent architecture @inbrowser/resumable: pick up and resume across refreshes @inbrowser/relay: when you need a server, syncs resumable jobs and picks up across network drops and backgrounded tabs.

David East

18,794 次观看 • 3 个月前

🎞Unforgettable 6th Anniversary! Video Views Festival Part 2 🎞 Watch the videos featured in Parts 1 - 5, and leave a comment with your Server/Friend Code! A total of 10 lucky Knights will receive the 6th Anniversary special 'Keycap'! 💌 #TheSevenDeadlySins #7DS

🎞Unforgettable 6th Anniversary! Video Views Festival Part 2 🎞 Watch the videos featured in Parts 1 - 5, and leave a comment with your Server/Friend Code! A total of 10 lucky Knights will receive the 6th Anniversary special 'Keycap'! 💌 #TheSevenDeadlySins #7DS

The Seven Deadly Sins: Grand Cross

31,621 次观看 • 1 年前

New React framework: One. In this episode, I talk to One’s lead developer, Nate Wienert. What makes One special? - Do React and React native in the same project - SPA, static, or server modes on a per-file basis - Includes Tamagui, a web and mobile styling system - Soon will include Zero for smart sync between client and server Here's a short clip from our chat. Full video in next post.

New React framework: One. In this episode, I talk to One’s lead developer, Nate Wienert. What makes One special? - Do React and React native in the same project - SPA, static, or server modes on a per-file basis - Includes Tamagui, a web and mobile styling system - Soon will include Zero for smart sync between client and server Here's a short clip from our chat. Full video in next post.

Cory House

19,114 次观看 • 2 年前

BREAKING 🚨 🇬🇭: Lady in Russian Guy’s viral video shares her side of the story The lady in the in-video noted: "I am a real estate agent and had scheduled a meeting with a client at the mall, but the client did not show up despite my waiting for several minutes. While there, I was approached by a Russian man, and we had a brief conversation during which I mentioned that I work in real estate. He requested my contact details, which I shared… 1/2

BREAKING 🚨 🇬🇭: Lady in Russian Guy’s viral video shares her side of the story The lady in the in-video noted: "I am a real estate agent and had scheduled a meeting with a client at the mall, but the client did not show up despite my waiting for several minutes. While there, I was approached by a Russian man, and we had a brief conversation during which I mentioned that I work in real estate. He requested my contact details, which I shared… 1/2

WithAlvin 🇬🇭

942,191 次观看 • 8 个月前

This is a standard practice for almost all Tier-1 banking applications in Nigeria, and for some fintech applications I’ve previously performed pentests on. Client-side encryption isn’t a total waste, or a waste of compute, as some people have claimed, but rather a measure to protect against API tampering or API request/response manipulation between the client and the server when implemented properly. Even with HTTPS, attackers can capture a decrypted version of web or mobile API data in transit because the browser and the server establish a level of trust during the TLS handshake. Attackers can leverage this trust to capture & proxy already-decrypted traffic, tamper with it, and then forward it to the server. This allows them to override what the user interface or client is originally supposed to send and replace it with data of their choosing. That is why validation needs to be performed on both the client and the server side. To wrap up, encrypting API requests and responses makes it significantly harder for attackers to tamper with data, even if they capture the traffic, unless they have access to the encryption details (algorithm, encryption mode, key size, secret key, and initialization vector), assuming asymmetric encryption is used. In the demo below, you can see how I discovered additional parameters (balance, is_admin) in the API response, captured the registration API request, despite it being sent over HTTPS from the interface, added the discovered parameters, and successfully inflated my balance to 50 billion and also escalated my privileges to admin, and ultimately deleted the accounts of two live users/customers. In the second slide, I captured an API traffic of a bank app, and you can see how difficult the payloads are to read.

This is a standard practice for almost all Tier-1 banking applications in Nigeria, and for some fintech applications I’ve previously performed pentests on. Client-side encryption isn’t a total waste, or a waste of compute, as some people have claimed, but rather a measure to protect against API tampering or API request/response manipulation between the client and the server when implemented properly. Even with HTTPS, attackers can capture a decrypted version of web or mobile API data in transit because the browser and the server establish a level of trust during the TLS handshake. Attackers can leverage this trust to capture & proxy already-decrypted traffic, tamper with it, and then forward it to the server. This allows them to override what the user interface or client is originally supposed to send and replace it with data of their choosing. That is why validation needs to be performed on both the client and the server side. To wrap up, encrypting API requests and responses makes it significantly harder for attackers to tamper with data, even if they capture the traffic, unless they have access to the encryption details (algorithm, encryption mode, key size, secret key, and initialization vector), assuming asymmetric encryption is used. In the demo below, you can see how I discovered additional parameters (balance, is_admin) in the API response, captured the registration API request, despite it being sent over HTTPS from the interface, added the discovered parameters, and successfully inflated my balance to 50 billion and also escalated my privileges to admin, and ultimately deleted the accounts of two live users/customers. In the second slide, I captured an API traffic of a bank app, and you can see how difficult the payloads are to read.

Ghost St Badmus

218,042 次观看 • 10 个月前

Today we're launching Papermark Agents 🚀 An MCP server, API and CLI that let agents run your data room. ▪️Create a deal room from scratch ▪️Who viewed my pitch deck this week? ▪️Set up a buy-side M&A room in 30 seconds We're setting the data room standard!

Today we're launching Papermark Agents 🚀 An MCP server, API and CLI that let agents run your data room. ▪️Create a deal room from scratch ▪️Who viewed my pitch deck this week? ▪️Set up a buy-side M&A room in 30 seconds We're setting the data room standard!

Marc Seitz — oss/acc

37,449 次观看 • 3 个月前

🎞 [The Eminence in Shadow] New Collab Video Views Campaign Part 2 Watch the videos featured in Parts 1 - 5, and leave a comment with your Server/Friend Code! 30 Diamonds💎 will be given to a total of 25 lucky Knights! 💌 #TheSevenDeadlySins #7DS

🎞 [The Eminence in Shadow] New Collab Video Views Campaign Part 2 Watch the videos featured in Parts 1 - 5, and leave a comment with your Server/Friend Code! 30 Diamonds💎 will be given to a total of 25 lucky Knights! 💌 #TheSevenDeadlySins #7DS

The Seven Deadly Sins: Grand Cross

106,868 次观看 • 1 年前

🎞Unforgettable 6th Anniversary! Video Views Festival Part 1 🎞 Watch the videos featured in Parts 1 - 5, and leave a comment with your Server/Friend Code! A total of 10 lucky Knights will receive the 6th Anniversary special 'Keycap'! 💌 #TheSevenDeadlySins #7DS

🎞Unforgettable 6th Anniversary! Video Views Festival Part 1 🎞 Watch the videos featured in Parts 1 - 5, and leave a comment with your Server/Friend Code! A total of 10 lucky Knights will receive the 6th Anniversary special 'Keycap'! 💌 #TheSevenDeadlySins #7DS

The Seven Deadly Sins: Grand Cross

32,205 次观看 • 1 年前

0.32 has shipped, and it's a massive release from Rerun. There's a ton of cool new features, and I wanted to highlight 2 in particular 1. OSS Server streaming from disk 2. Dataset review I walk you through them in the video, so take a look. I'll have a much longer blog post next week about the entire pipeline. With 0.32, much of the foundation is set for a unified data layer for physical data, and I'll be getting into the details of it with all that I've built over the past year. This will cover 1. Raw Data Collection 2. Data Ingestion 3. Catalog Registration 4. Query and Review 5. Post Process 6. Training so lots to share

0.32 has shipped, and it's a massive release from Rerun. There's a ton of cool new features, and I wanted to highlight 2 in particular 1. OSS Server streaming from disk 2. Dataset review I walk you through them in the video, so take a look. I'll have a much longer blog post next week about the entire pipeline. With 0.32, much of the foundation is set for a unified data layer for physical data, and I'll be getting into the details of it with all that I've built over the past year. This will cover 1. Raw Data Collection 2. Data Ingestion 3. Catalog Registration 4. Query and Review 5. Post Process 6. Training so lots to share

Pablo Vela

11,264 次观看 • 5 个月前

BLIND SIDE SONNY! Tomorrow night 10/1 at 11:30pm EST, 8:30 PST we’ll be hanging out on YouTube to answer questions and watch the debut of the BSS video with you. Stay tuned tomorrow for links. Song is live everywhere tomorrow at 12am EST (Oct 2).

BLIND SIDE SONNY! Tomorrow night 10/1 at 11:30pm EST, 8:30 PST we’ll be hanging out on YouTube to answer questions and watch the debut of the BSS video with you. Stay tuned tomorrow for links. Song is live everywhere tomorrow at 12am EST (Oct 2).

Coheed and Cambria

31,993 次观看 • 2 年前

Here's my conversation with DHH. He is back for round 2! It was an epic fun 5 hour conversation about the future of programming, AI, Linux, and human civilization. It's here on X in full and is up everywhere else (see comment). Timestamps: 0:00 - Episode highlight 1:27 - Introduction 2:56 - Programming with AI agents 18:14 - How software will change 27:30 - AI impact on open source 37:21 - Building Omarchy Linux distro 47:05 - Vibe coding vs agentic engineering 1:00:06 - The end of manual programming 1:10:24 - Advice for programmers 1:22:30 - Surviving Internet Hate 1:31:46 - Programming setup for AI Agents 1:44:11 - Obsessing about speed 2:07:06 - Voice prompting vs typing 2:21:05 - Best AI coding models 2:37:55 - Best AI coding harnesses 2:50:57 - AI video generation and filmmaking 3:10:28 - Fatherhood 3:38:35 - Linux will win the desktop 3:49:51 - PewDiePie 3:59:24 - Future of programming 4:22:17 - Politics and immigration 4:53:54 - Longevity, over-optimization, and fear of death 5:05:38 - Eternal recurrence and future of human civization

Here's my conversation with DHH. He is back for round 2! It was an epic fun 5 hour conversation about the future of programming, AI, Linux, and human civilization. It's here on X in full and is up everywhere else (see comment). Timestamps: 0:00 - Episode highlight 1:27 - Introduction 2:56 - Programming with AI agents 18:14 - How software will change 27:30 - AI impact on open source 37:21 - Building Omarchy Linux distro 47:05 - Vibe coding vs agentic engineering 1:00:06 - The end of manual programming 1:10:24 - Advice for programmers 1:22:30 - Surviving Internet Hate 1:31:46 - Programming setup for AI Agents 1:44:11 - Obsessing about speed 2:07:06 - Voice prompting vs typing 2:21:05 - Best AI coding models 2:37:55 - Best AI coding harnesses 2:50:57 - AI video generation and filmmaking 3:10:28 - Fatherhood 3:38:35 - Linux will win the desktop 3:49:51 - PewDiePie 3:59:24 - Future of programming 4:22:17 - Politics and immigration 4:53:54 - Longevity, over-optimization, and fear of death 5:05:38 - Eternal recurrence and future of human civization

Lex Fridman

904,425 次观看 • 1 个月前

Introducing Open MCP Client 🪁 Chat with any MCP server in your own app, just grab a URL from . The team and I vibe coded with Cursor this weekend and built: 1. The first web-based MCP client (link👇) 2. An open-source client you can add into any app How it's built It uses CopilotKit🪁 for the client and interactivity layer, and connects to a 40 line LangGraph ReAct agent that coordinates MCP calls. Hosted on Vercel. Kudos to Suhas Deshpande and Tyler Slaton for hacking and thanks to Harrison Chase for pointers!

Introducing Open MCP Client 🪁 Chat with any MCP server in your own app, just grab a URL from . The team and I vibe coded with Cursor this weekend and built: 1. The first web-based MCP client (link👇) 2. An open-source client you can add into any app How it's built It uses CopilotKit🪁 for the client and interactivity layer, and connects to a 40 line LangGraph ReAct agent that coordinates MCP calls. Hosted on Vercel. Kudos to Suhas Deshpande and Tyler Slaton for hacking and thanks to Harrison Chase for pointers!

Atai Barkai

299,864 次观看 • 1 年前