Video wird geladen...

Video konnte nicht geladen werden

Beim Laden dieses Videos ist ein Problem aufgetreten. Dies könnte an einem vorübergehenden Netzwerkproblem liegen oder das Video ist möglicherweise nicht verfügbar.

New Expo example: graphQL server and client with ✨automatic type generation✨! 🧘‍♀️ GraphQL Yoga - server 💜 URQL - client 🎉 gql.tada - type generation ☁️ EAS Hosting - for API & web deployments

Kadi Kraman 💚

14,592 subscribers

17,470 Aufrufe • vor 1 Jahr •via X (Twitter)

Wissenschaft & Technologie Bildung Kunst

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

I just added a Hono example and guide for Supabase Auth 🔥 It uses Hono with Vite ⚡ & React to demo Supabase Auth working across client and server using cookies 🍪😋 Shoutout to Aditya for the Hono/JSX + Vite example I built upon 🫶 Code below 👇

I just added a Hono example and guide for Supabase Auth 🔥 It uses Hono with Vite ⚡ & React to demo Supabase Auth working across client and server using cookies 🍪😋 Shoutout to Aditya for the Hono/JSX + Vite example I built upon 🫶 Code below 👇

Thor 雷神 ⚡️

12,082 Aufrufe • vor 1 Jahr

React tip: "use client" misconceptions (2/5) 🚫 "You cannot nest Server Components inside Client Components because "use client" turns everything into Client Components." ✅ We can pass the rendered result of Server Components to Client Components as props. Simple example: (Server Component) (Client Component) (Server Component) is designed for the client. It needs to instantly open and close when clicked. is designed for the server. It uses packages that don't work in the browser and needs to fetch data close to where it's stored without exposing credentials. So, how can we nest a component that uses server APIs inside a component that uses client APIs... without using `import`? React props to the rescue! --- (0:00) 1-4: Reminder: Importing code forms a module dependency graph. Adding dependencies to a server or client bundle. (0:23) 5-6: Reminder: Using components eventually forms a rendered component tree. (0:37) 9: Oh no! We get an error when trying to `import` a client API (useState) into a server module. (0:44) 10: We know the trick by now: Add "use client" to mark `2.js` as a client entry point. This moves the module to the client bundle and allows us to use client APIs like `useState.` (0:51) 11: But we get a new error! "use client" moved all imported dependencies into the client bundle, including our ORM package, which doesn't work in the browser. (0:59) 13: Let's refactor without changing our rendered component hierarchy. First, we move the `Cart` import to the parent file that imports `Modal`. This moves `Cart` outside the "use client" boundary and consequently the client bundle. (1:11) 15: Then, we pass down the rendered result of `Cart` as a prop to `Modal`. This allows `Cart` to be entirely rendered on the server as a Server Component before being passed down. `Modal` has no knowledge of what the `cart` prop is. Its only responsibility is placing whatever it receives into the `{cart}` slot. (1:15) 16: Finally, it's common to use the special `children` prop for a component's primary content. The key insight is that we were able to use props to retain our desired component hierarchy even though we changed our module dependency graph.

React tip: "use client" misconceptions (2/5) 🚫 "You cannot nest Server Components inside Client Components because "use client" turns everything into Client Components." ✅ We can pass the rendered result of Server Components to Client Components as props. Simple example: (Server Component) (Client Component) (Server Component) is designed for the client. It needs to instantly open and close when clicked. is designed for the server. It uses packages that don't work in the browser and needs to fetch data close to where it's stored without exposing credentials. So, how can we nest a component that uses server APIs inside a component that uses client APIs... without using `import`? React props to the rescue! --- (0:00) 1-4: Reminder: Importing code forms a module dependency graph. Adding dependencies to a server or client bundle. (0:23) 5-6: Reminder: Using components eventually forms a rendered component tree. (0:37) 9: Oh no! We get an error when trying to `import` a client API (useState) into a server module. (0:44) 10: We know the trick by now: Add "use client" to mark `2.js` as a client entry point. This moves the module to the client bundle and allows us to use client APIs like `useState.` (0:51) 11: But we get a new error! "use client" moved all imported dependencies into the client bundle, including our ORM package, which doesn't work in the browser. (0:59) 13: Let's refactor without changing our rendered component hierarchy. First, we move the `Cart` import to the parent file that imports `Modal`. This moves `Cart` outside the "use client" boundary and consequently the client bundle. (1:11) 15: Then, we pass down the rendered result of `Cart` as a prop to `Modal`. This allows `Cart` to be entirely rendered on the server as a Server Component before being passed down. `Modal` has no knowledge of what the `cart` prop is. Its only responsibility is placing whatever it receives into the `{cart}` slot. (1:15) 16: Finally, it's common to use the special `children` prop for a component's primary content. The key insight is that we were able to use props to retain our desired component hierarchy even though we changed our module dependency graph.

Delba

43,989 Aufrufe • vor 2 Jahren

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 Aufrufe • vor 1 Jahr

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

217,252 Aufrufe • vor 7 Monaten

JWT in 60 Seconds 👇 What is JWT ? JWT = JSON Web Token A compact, URL-safe token used for: - Authentication - Authorization - Secure API communication - Identity sharing between services It is digitally signed, so it can be verified and trusted. 🟢 Why JWT exists Typical flow without JWT: User → Application → Database (Session Store) - Server stores sessions - Requires memory/storage - Hard to scale in microservices - More infrastructure complexity - Needs sticky sessions behind Load Balancer - This doesn’t scale well in distributed systems. 🟢 JWT comes into the picture - JWT is stateless authentication. New flow: User → Application → JWT → Client → API - No session stored on server - Token carries user identity & claims - Server only verifies signature - Perfect for scalable systems. 🟢 Complete JWT request flow 1️⃣ User logs in with credentials 2️⃣ Server validates user 3️⃣ Server generates JWT (Header + Payload + Signature) 4️⃣ Client stores JWT (usually in browser/app) 5️⃣ Client sends JWT in Authorization header 6️⃣ Server verifies signature 7️⃣ If valid → Access granted No database lookup for session needed. 🟢 Where JWT is used in real systems? - REST APIs - Microservices authentication - OAuth2 / SSO - API Gateways - Kubernetes dashboards - CI/CD tools - Mobile & SPA applications - Almost every modern cloud-native app uses JWT. 🟢 JWT in DevOps & System Design : As a DevOps engineer, JWT knowledge is used in: - Designing stateless applications - Scaling apps behind Load Balancers - Implementing API security - Working with IAM & OAuth providers - Securing microservices communication - Reducing session storage dependency Stateless auth = Better scalability + Simpler infrastructure Thanks for reading. Happy Learning !

JWT in 60 Seconds 👇 What is JWT ? JWT = JSON Web Token A compact, URL-safe token used for: - Authentication - Authorization - Secure API communication - Identity sharing between services It is digitally signed, so it can be verified and trusted. 🟢 Why JWT exists Typical flow without JWT: User → Application → Database (Session Store) - Server stores sessions - Requires memory/storage - Hard to scale in microservices - More infrastructure complexity - Needs sticky sessions behind Load Balancer - This doesn’t scale well in distributed systems. 🟢 JWT comes into the picture - JWT is stateless authentication. New flow: User → Application → JWT → Client → API - No session stored on server - Token carries user identity & claims - Server only verifies signature - Perfect for scalable systems. 🟢 Complete JWT request flow 1️⃣ User logs in with credentials 2️⃣ Server validates user 3️⃣ Server generates JWT (Header + Payload + Signature) 4️⃣ Client stores JWT (usually in browser/app) 5️⃣ Client sends JWT in Authorization header 6️⃣ Server verifies signature 7️⃣ If valid → Access granted No database lookup for session needed. 🟢 Where JWT is used in real systems? - REST APIs - Microservices authentication - OAuth2 / SSO - API Gateways - Kubernetes dashboards - CI/CD tools - Mobile & SPA applications - Almost every modern cloud-native app uses JWT. 🟢 JWT in DevOps & System Design : As a DevOps engineer, JWT knowledge is used in: - Designing stateless applications - Scaling apps behind Load Balancers - Implementing API security - Working with IAM & OAuth providers - Securing microservices communication - Reducing session storage dependency Stateless auth = Better scalability + Simpler infrastructure Thanks for reading. Happy Learning !

Nandkishor

27,790 Aufrufe • vor 4 Monaten

🚀 AG2 v0.11.1 is live! 🖥️ AG-UI Message Streaming – Real-time agent responses in your AG-UI frontends with new event-based streaming architecture. 🌊 A2A Streaming – Full streaming support for Agent-to-Agent communication! LLM text streaming now flows through A2A for real-time responses from remote agents, both server and client-side. 📡 OpenAI – Get more out of OpenAI's latest Responses API with stateful conversations, built-in tools (web search, image gen, apply_patch), reasoning model support, and enhanced cost tracking. Docs: 🛠️🪲 Bug fixes and maintenance #AG2 #AI #MultiAgentSystems #AIAgents #OpenSource #AGUI

🚀 AG2 v0.11.1 is live! 🖥️ AG-UI Message Streaming – Real-time agent responses in your AG-UI frontends with new event-based streaming architecture. 🌊 A2A Streaming – Full streaming support for Agent-to-Agent communication! LLM text streaming now flows through A2A for real-time responses from remote agents, both server and client-side. 📡 OpenAI – Get more out of OpenAI's latest Responses API with stateful conversations, built-in tools (web search, image gen, apply_patch), reasoning model support, and enhanced cost tracking. Docs: 🛠️🪲 Bug fixes and maintenance #AG2 #AI #MultiAgentSystems #AIAgents #OpenSource #AGUI

AG2

17,513 Aufrufe • vor 5 Monaten

Bring Bitcoin and Lightning Network capabilities to your favorite LLM client through the new ZBD ZBD MCP Server 🎉 Useful for creating all kinds of workflows and automations with your favorite MCP-compatible hosts such as Anthropic's Claude or Cursor Check the comment below on how to set it up for yourself, and begin using natural language to send and receive global Bitcoin payments at the speed of the internet 🌎

Bring Bitcoin and Lightning Network capabilities to your favorite LLM client through the new ZBD ZBD MCP Server 🎉 Useful for creating all kinds of workflows and automations with your favorite MCP-compatible hosts such as Anthropic's Claude or Cursor Check the comment below on how to set it up for yourself, and begin using natural language to send and receive global Bitcoin payments at the speed of the internet 🌎

André Neves

12,766 Aufrufe • vor 1 Jahr

✨ A new chapter begins! Announcing… 📃 Docs by Hashnode. Developer documentation shouldn't be an afterthought — it should feel like a natural part of your brand. That’s why we built a brand new documentation tool. The content engine for your API docs and product guides. Create and scale docs as dynamic as your code. Built for teams needing full control and customization — without the heavy lifting. ✦ Headless mode powered by GraphQL APIs or ✦ Hosted version with custom domains with… ✦ Best in class visual editing powered by MDX ✦ Collaborative editing and review comments ✦ AI-powered search and AI-assisted writing ✦ Automatic API references from OpenAPI specs ✦ Built in Analytics ✦ Versioning ✦ Advanced member roles and contributors and more. Experience the best developer docs product on the internet. GA Fall 2024. Available in public beta today. Sign up. 🚀

Hashnode

279,929 Aufrufe • vor 1 Jahr

🚨 They are available! 🚨 Our new 3rd generation Advance server lineup is now available in the Gravelines, Roubaix, Limburg, and Vint Hill data centers. They will deliver unmatched performance for your web projects, applications, as well as virtualization and containerization workloads. Equipped with AMD #EPYC 4004 processors, these servers offer efficiency, durability, and a compelling performance-to-price ratio, allowing you to leverage our sovereign #cloud. ☁🔐 🔹 Optimal Performance: Equipped with AMD EPYC 4004 processors 🔹 DDR5 ECC Memory: Up to 5200 MHz 🔹 2x25 Gbps network interface for unparalleled stability (public and private) More regions will be available to deploy these new references in the following weeks.🌍 👉Discover and configure your new Advance 3rd generation here :

🚨 They are available! 🚨 Our new 3rd generation Advance server lineup is now available in the Gravelines, Roubaix, Limburg, and Vint Hill data centers. They will deliver unmatched performance for your web projects, applications, as well as virtualization and containerization workloads. Equipped with AMD #EPYC 4004 processors, these servers offer efficiency, durability, and a compelling performance-to-price ratio, allowing you to leverage our sovereign #cloud. ☁🔐 🔹 Optimal Performance: Equipped with AMD EPYC 4004 processors 🔹 DDR5 ECC Memory: Up to 5200 MHz 🔹 2x25 Gbps network interface for unparalleled stability (public and private) More regions will be available to deploy these new references in the following weeks.🌍 👉Discover and configure your new Advance 3rd generation here :

OVHcloud

10,325 Aufrufe • vor 2 Jahren

We're rolling out Phase #1 of mod loading on Lunar Client with the release of Server Modpacks ✨ We are starting off with a curated modpack for Hoplite, featuring numerous mods sourced directly from Modrinth. Simply go to the 'versions' page on the launcher to play with the modpack. We will be working with more servers to create bespoke modpacks for each one of them. If you are a server owner and want your own modpack, reach out to us via email at servers@lunarclient.com Phase #2 of mod loading will allow you to use a wide range of Fabric mods sourced from Modrinth on Lunar, independent of modpacks. Coming soon... 👀

We're rolling out Phase #1 of mod loading on Lunar Client with the release of Server Modpacks ✨ We are starting off with a curated modpack for Hoplite, featuring numerous mods sourced directly from Modrinth. Simply go to the 'versions' page on the launcher to play with the modpack. We will be working with more servers to create bespoke modpacks for each one of them. If you are a server owner and want your own modpack, reach out to us via email at [email protected] Phase #2 of mod loading will allow you to use a wide range of Fabric mods sourced from Modrinth on Lunar, independent of modpacks. Coming soon... 👀

Lunar Client

70,521 Aufrufe • vor 2 Jahren

New Video Tutorial - Deploying a personal merchant AI agent with payment processing on EigenCompute @eigenlayer ⚡️ • Zero to live with HTTP endpoint in 10 minutes • Sell arbitrary items, receive payments, all via X402 • Natural language API • Easily extendable to any commerce use case • Includes full codebase for both client and merchant (server) EigenCompute lets you deploy apps which generate proof of exactly what code is executing. Users can verify your app’s behavior cryptographically, not just trusting the developer or the company. So you get smart contract-like guarantees like transparency and verifiability, but with the programmability and performance of Web2 infrastructure. You containerize your app with Docker, and it runs in secure enclaves called TEEs that generate these proofs.

New Video Tutorial - Deploying a personal merchant AI agent with payment processing on EigenCompute @eigenlayer ⚡️ • Zero to live with HTTP endpoint in 10 minutes • Sell arbitrary items, receive payments, all via X402 • Natural language API • Easily extendable to any commerce use case • Includes full codebase for both client and merchant (server) EigenCompute lets you deploy apps which generate proof of exactly what code is executing. Users can verify your app’s behavior cryptographically, not just trusting the developer or the company. So you get smart contract-like guarantees like transparency and verifiability, but with the programmability and performance of Web2 infrastructure. You containerize your app with Docker, and it runs in secure enclaves called TEEs that generate these proofs.

nader dabit

41,295 Aufrufe • vor 9 Monaten

🚀 Exciting News! We're thrilled to announce the launch of Qwen Chat ( ) – your new go-to Web UI for interacting with Qwen models! 🌟 💬 Chat effortlessly with our flagship model Qwen2.5-Plus , explore vision-language capabilities with Qwen2-VL-Max , and dive into reasoning models like QwQ and QVQ, code with coding expert Qwen2.5-Coder-32B-Instruct, etc. ✨ Key Features: * Choose & compare multiple models in one interface * Upload documents & get answers based on them * Preview mode with HTML support * Upload images for visual understanding 🌟 Coming Soon: Web search, image generation, voice mode, and more! 🔗 Ready to experience the future? Start to chat with Qwen today 💬 Feel free to send us your feedback and suggestions!

🚀 Exciting News! We're thrilled to announce the launch of Qwen Chat ( ) – your new go-to Web UI for interacting with Qwen models! 🌟 💬 Chat effortlessly with our flagship model Qwen2.5-Plus , explore vision-language capabilities with Qwen2-VL-Max , and dive into reasoning models like QwQ and QVQ, code with coding expert Qwen2.5-Coder-32B-Instruct, etc. ✨ Key Features: * Choose & compare multiple models in one interface * Upload documents & get answers based on them * Preview mode with HTML support * Upload images for visual understanding 🌟 Coming Soon: Web search, image generation, voice mode, and more! 🔗 Ready to experience the future? Start to chat with Qwen today 💬 Feel free to send us your feedback and suggestions!

Qwen

215,137 Aufrufe • vor 1 Jahr

This Chinese guy created agents in Claude Code for MCP servers and single-handedly serves 6 marketing agencies a month from one iPhone, earning $5,000 from each. Inside he runs a pipeline of 7 agents on Claude Sonnet 4.6 that every Monday pulls a scan of the tech stack from a selected agency, develops an MCP server for its ad accounts, and over the course of a week brings it to production code ready to connect to Claude Desktop. No DevOps, no senior developer, no project manager. Just a Mac Mini in a work corner, an iPhone in the pocket, and a single API key. And traditional dev shops keep 5 people on project rates for the same contract, while his entire P&L is tokens, dirt-cheap hosting on Cloudflare, and Calendly. 7 agents run under a shared orchestrator-router and burn about 5 million tokens a day, which in the API bill comes out to $540 a month. The Mac Mini itself sits at home and keeps the entire orchestrator running 24/7, and from the iPhone the owner connects to it through a secure remote terminal and sees the output of any session right on the smartphone screen, wherever he happens to be. His starting system prompt looks like this: "you run a solo shop for custom MCP servers for marketing agencies. you hand out read-only tasks to 6 sub-agents and own all commits and shipping yourself. sub-agents: // Hunter (finds marketing agencies of 15 to 60 people that have no MCP access to Google Ads, Meta Ads, TikTok Ads, and HubSpot) // Mapper (pulls their tech stack, identifies 3 to 5 integration pains, and simultaneously writes the technical spec for the server: which tools, resources, and prompts to export through MCP, which auth flow and rate limit) // Coder (generates an MCP server in Python through the MCP SDK, deploys 8 to 15 tools for ad accounts and CRM) // Validator (connects the server to Claude Desktop, runs real client API keys in a sandbox, and checks for compliance with the MCP spec) // Shipper (writes a README, integration guide, deployment manual, packages the server, and hosts it on Cloudflare Workers or pushes to the GitHub of the client) // Mobile (always online on the iPhone, books demo calls in Calendly, picks up hot fixes, and confirms contracts through a secure remote terminal to the Mac Mini). only 1 owner agent works on 1 contract, no overlaps. you pull the owner out of observation mode only when a deal goes above $7,500 or the test coverage of the server drops below 85%." This prompt gives the system an understanding of its role and the limits of intervention from the very first line. It knows it is supposed to find agencies on its own. It knows it is supposed to bring every MCP server to production on its own. It knows it connects the live owner only on large deals or when the tests do not converge. → The pipeline runs without breaks, day or night → Hunter goes through about 130 marketing agencies on LinkedIn and Clutch per day → Mapper rolls out 4 audit reports with the tech stack and a final spec for each → Coder writes 1 to 2 MCP servers per week in Python with 8 to 15 tools → Validator validates every server through Claude Desktop with real client API keys → Shipper rolls out the full documentation package and pushes the finished product to Cloudflare Workers or the GitHub of the client And only when a contract breaks $7,500 or test coverage drops below 85% does the orchestrator pull the owner from whatever he is doing. And when the owner at that moment is behind the wheel or at a meeting in a coworking space, the Mobile agent in his iPhone picks up 1 contract in progress: confirms a meeting with the agency CMO in Calendly, opens a live demo of the MCP server through a secure terminal to the Mac Mini, and writes the test result to the shared state. The owner just swipes "approve" and in 15 minutes joins the Zoom demo. The fresh system log from last Wednesday looks like this: "hunter report: 132 agencies checked on LinkedIn and Clutch, 19 without MCP integrations, 8 with active requests for AI tooling in job posts, 4 with an open Q4 budget. passing to mapper." "coder: MCP server for Northwave Performance Marketing built in Python, 11 tools for Google Ads, Meta Ads, and GA4, 320 lines of code. exported to /Users/dev/mcp-shop/clients/northwave/server.py. validator connecting to Claude Desktop." "validator: 11 tools passed validation through Claude Desktop, test coverage 92%, average latency 380 ms. passing to shipper." "eval flag: contract with Pacific Reach Agency at $8,200 exceeds the approved limit of $7,500. sending for manual review." In his work setup there is no cloud server, no external team, and not even a separate office. At home sits a Mac Mini with a sandbox at /Users/dev/mcp-shop, on top runs an MCP router with a single API key to Claude, and the same key is forwarded to a secure terminal on the iPhone. Out of everything I have seen this year, this is the cleanest solo shop for custom MCP servers for marketing agencies: $540 a month on the API, about $30,000 into the account, and between them 7 system prompts, 1 Mac Mini in a work corner, and 1 iPhone that never leaves the pocket.

This Chinese guy created agents in Claude Code for MCP servers and single-handedly serves 6 marketing agencies a month from one iPhone, earning $5,000 from each. Inside he runs a pipeline of 7 agents on Claude Sonnet 4.6 that every Monday pulls a scan of the tech stack from a selected agency, develops an MCP server for its ad accounts, and over the course of a week brings it to production code ready to connect to Claude Desktop. No DevOps, no senior developer, no project manager. Just a Mac Mini in a work corner, an iPhone in the pocket, and a single API key. And traditional dev shops keep 5 people on project rates for the same contract, while his entire P&L is tokens, dirt-cheap hosting on Cloudflare, and Calendly. 7 agents run under a shared orchestrator-router and burn about 5 million tokens a day, which in the API bill comes out to $540 a month. The Mac Mini itself sits at home and keeps the entire orchestrator running 24/7, and from the iPhone the owner connects to it through a secure remote terminal and sees the output of any session right on the smartphone screen, wherever he happens to be. His starting system prompt looks like this: "you run a solo shop for custom MCP servers for marketing agencies. you hand out read-only tasks to 6 sub-agents and own all commits and shipping yourself. sub-agents: // Hunter (finds marketing agencies of 15 to 60 people that have no MCP access to Google Ads, Meta Ads, TikTok Ads, and HubSpot) // Mapper (pulls their tech stack, identifies 3 to 5 integration pains, and simultaneously writes the technical spec for the server: which tools, resources, and prompts to export through MCP, which auth flow and rate limit) // Coder (generates an MCP server in Python through the MCP SDK, deploys 8 to 15 tools for ad accounts and CRM) // Validator (connects the server to Claude Desktop, runs real client API keys in a sandbox, and checks for compliance with the MCP spec) // Shipper (writes a README, integration guide, deployment manual, packages the server, and hosts it on Cloudflare Workers or pushes to the GitHub of the client) // Mobile (always online on the iPhone, books demo calls in Calendly, picks up hot fixes, and confirms contracts through a secure remote terminal to the Mac Mini). only 1 owner agent works on 1 contract, no overlaps. you pull the owner out of observation mode only when a deal goes above $7,500 or the test coverage of the server drops below 85%." This prompt gives the system an understanding of its role and the limits of intervention from the very first line. It knows it is supposed to find agencies on its own. It knows it is supposed to bring every MCP server to production on its own. It knows it connects the live owner only on large deals or when the tests do not converge. → The pipeline runs without breaks, day or night → Hunter goes through about 130 marketing agencies on LinkedIn and Clutch per day → Mapper rolls out 4 audit reports with the tech stack and a final spec for each → Coder writes 1 to 2 MCP servers per week in Python with 8 to 15 tools → Validator validates every server through Claude Desktop with real client API keys → Shipper rolls out the full documentation package and pushes the finished product to Cloudflare Workers or the GitHub of the client And only when a contract breaks $7,500 or test coverage drops below 85% does the orchestrator pull the owner from whatever he is doing. And when the owner at that moment is behind the wheel or at a meeting in a coworking space, the Mobile agent in his iPhone picks up 1 contract in progress: confirms a meeting with the agency CMO in Calendly, opens a live demo of the MCP server through a secure terminal to the Mac Mini, and writes the test result to the shared state. The owner just swipes "approve" and in 15 minutes joins the Zoom demo. The fresh system log from last Wednesday looks like this: "hunter report: 132 agencies checked on LinkedIn and Clutch, 19 without MCP integrations, 8 with active requests for AI tooling in job posts, 4 with an open Q4 budget. passing to mapper." "coder: MCP server for Northwave Performance Marketing built in Python, 11 tools for Google Ads, Meta Ads, and GA4, 320 lines of code. exported to /Users/dev/mcp-shop/clients/northwave/server.py. validator connecting to Claude Desktop." "validator: 11 tools passed validation through Claude Desktop, test coverage 92%, average latency 380 ms. passing to shipper." "eval flag: contract with Pacific Reach Agency at $8,200 exceeds the approved limit of $7,500. sending for manual review." In his work setup there is no cloud server, no external team, and not even a separate office. At home sits a Mac Mini with a sandbox at /Users/dev/mcp-shop, on top runs an MCP router with a single API key to Claude, and the same key is forwarded to a secure terminal on the iPhone. Out of everything I have seen this year, this is the cleanest solo shop for custom MCP servers for marketing agencies: $540 a month on the API, about $30,000 into the account, and between them 7 system prompts, 1 Mac Mini in a work corner, and 1 iPhone that never leaves the pocket.

Blaze

55,926 Aufrufe • vor 2 Monaten

We’re excited to officially launch LlamaParse, the first genAI-native document parsing solution. Not only is it better at parsing out images/tables/charts 📊📈 than virtually every other parser, it is now steerable through natural language instructions - output the document in whatever format you desire! It is also the only parsing solution that seamlessly allows you to build accurate RAG over complex documents, free of hallucinations 🔥 We launched it in private preview a few weeks ago and hit 2k users, 1M total PDF pages parsed. And now it’s better than ever. LlamaParse contains the following killer features: ✅ SOTA table/chart extraction ✅ Seamless integration with LlamaIndex 🦙 advanced RAG/agents ✅✨ Natural language Parsing Instructions ✅✨JSON mode and image extraction ✅✨Support for ~10 document types (.pdf, .pptx, .docx, .xml) and more Our pricing is simple: 1k free per day, and additional pages at 0.3c a page, or $3 for 1k pages. If you want advanced document RAG and/or private deployments, come get in touch with us to chat about LlamaCloud. Check out our full blog post here: LlamaParse client repo: Signup at 🦙☁️: Come talk to us:

We’re excited to officially launch LlamaParse, the first genAI-native document parsing solution. Not only is it better at parsing out images/tables/charts 📊📈 than virtually every other parser, it is now steerable through natural language instructions - output the document in whatever format you desire! It is also the only parsing solution that seamlessly allows you to build accurate RAG over complex documents, free of hallucinations 🔥 We launched it in private preview a few weeks ago and hit 2k users, 1M total PDF pages parsed. And now it’s better than ever. LlamaParse contains the following killer features: ✅ SOTA table/chart extraction ✅ Seamless integration with LlamaIndex 🦙 advanced RAG/agents ✅✨ Natural language Parsing Instructions ✅✨JSON mode and image extraction ✅✨Support for ~10 document types (.pdf, .pptx, .docx, .xml) and more Our pricing is simple: 1k free per day, and additional pages at 0.3c a page, or $3 for 1k pages. If you want advanced document RAG and/or private deployments, come get in touch with us to chat about LlamaCloud. Check out our full blog post here: LlamaParse client repo: Signup at 🦙☁️: Come talk to us:

LlamaIndex 🦙

143,136 Aufrufe • vor 2 Jahren

✨ I made a new thing today: 📑 Whenever I need to quickly copy paste a raw JSON data dump from my app and view it I'd always use json . parser . online . fr but it seems unmaintained, keeps going down, doesn't have HTTPS, and other JSON viewers are full of spyware/malware/tracking scripts So I made this today with a lot of help from ChatGPT to solve it for me and everyone else: visualizes raw JSON data for you, and does it 100% on the client without sending any data to the server But it also secretly supports a lot of other data formats like XML, PHP serialized data, hexadecimal, base64 encoded data, and even binary! And it also works well on mobile! Another one of my little hack projects :D If you want me to add other data types, let me know and I'll add them

✨ I made a new thing today: 📑 Whenever I need to quickly copy paste a raw JSON data dump from my app and view it I'd always use json . parser . online . fr but it seems unmaintained, keeps going down, doesn't have HTTPS, and other JSON viewers are full of spyware/malware/tracking scripts So I made this today with a lot of help from ChatGPT to solve it for me and everyone else: visualizes raw JSON data for you, and does it 100% on the client without sending any data to the server But it also secretly supports a lot of other data formats like XML, PHP serialized data, hexadecimal, base64 encoded data, and even binary! And it also works well on mobile! Another one of my little hack projects :D If you want me to add other data types, let me know and I'll add them

@levelsio

882,659 Aufrufe • vor 1 Jahr

Make your CLI 10x more powerful with custom subagents! Mistral Vibe is an open-source coding agent that runs in your terminal. Most terminal agents give you one assistant that does everything. With Vibe, you can build custom subagents for targeted tasks like deploy scripts, PR reviews, and test generation, then invoke them on demand. Here's how it works: Each subagent runs independently and handles its job without cluttering your main workflow. You might have one for PR reviews, another for testing, and another for deployment. The agent also has full access to your codebase. It scans your project structure and Git status automatically, so it understands context across multiple files, not just the one you're editing. Key capabilities: • Web search and fetching - query and fetch content from the web mid-session for documentation, or API references. • Multi-choice clarifications - when your instruction is ambiguous, Vibe prompts with options instead of guessing. You pick the right path before it acts. • Full skills support - slash commands for preconfigured workflows, custom subagents for specialized tasks, and extensibility through the Agent Skills standard. Vibe works in your terminal or connects to VS Code, JetBrains, and Zed through the Agent Client Protocol. Mistral Vibe is available through Le Chat Pro and Team plans. It's 100% open source Link to Mistral Vibe in the comments!

Make your CLI 10x more powerful with custom subagents! Mistral Vibe is an open-source coding agent that runs in your terminal. Most terminal agents give you one assistant that does everything. With Vibe, you can build custom subagents for targeted tasks like deploy scripts, PR reviews, and test generation, then invoke them on demand. Here's how it works: Each subagent runs independently and handles its job without cluttering your main workflow. You might have one for PR reviews, another for testing, and another for deployment. The agent also has full access to your codebase. It scans your project structure and Git status automatically, so it understands context across multiple files, not just the one you're editing. Key capabilities: • Web search and fetching - query and fetch content from the web mid-session for documentation, or API references. • Multi-choice clarifications - when your instruction is ambiguous, Vibe prompts with options instead of guessing. You pick the right path before it acts. • Full skills support - slash commands for preconfigured workflows, custom subagents for specialized tasks, and extensibility through the Agent Skills standard. Vibe works in your terminal or connects to VS Code, JetBrains, and Zed through the Agent Client Protocol. Mistral Vibe is available through Le Chat Pro and Team plans. It's 100% open source Link to Mistral Vibe in the comments!

Sumanth

10,483 Aufrufe • vor 4 Monaten

for better understanding of how bitcoin works, i decided to build a fork called TETSUO. bitcoin uses secp256k1 ECDSA with SHA256/RIPEMD160 hashing for addresses and transaction signing. TETSUO maintains that exact same cryptographic foundation, we inherit decades of security research. but we optimized the transaction format: - sequence numbers set to 0xffffffff for full script compatibility - SIGHASH_ALL appended to the signing preimage before hashing (not after) - proper little-endian encoding throughout this meant rebuilding the entire signing pipeline. started by forking the bitcoin-core codebase, then built a complete TypeScript wallet SDK on top. implemented BIP39 mnemonic generation, UTXO selection, fee estimation, all the stuff wallets need. the critical part: client-side signing only. your private keys never touch any server. transaction is built locally, signed locally, broadcast to network. open source: (the node) (the SDK) (block explorer) understanding bitcoin meant understanding every layer of the protocol.

for better understanding of how bitcoin works, i decided to build a fork called TETSUO. bitcoin uses secp256k1 ECDSA with SHA256/RIPEMD160 hashing for addresses and transaction signing. TETSUO maintains that exact same cryptographic foundation, we inherit decades of security research. but we optimized the transaction format: - sequence numbers set to 0xffffffff for full script compatibility - SIGHASH_ALL appended to the signing preimage before hashing (not after) - proper little-endian encoding throughout this meant rebuilding the entire signing pipeline. started by forking the bitcoin-core codebase, then built a complete TypeScript wallet SDK on top. implemented BIP39 mnemonic generation, UTXO selection, fee estimation, all the stuff wallets need. the critical part: client-side signing only. your private keys never touch any server. transaction is built locally, signed locally, broadcast to network. open source: (the node) (the SDK) (block explorer) understanding bitcoin meant understanding every layer of the protocol.

acidburn

80,862 Aufrufe • vor 6 Monaten

✨ 7 years after I set up a Quake III server, I have it running again, but now in the web browser, much easier 😊 👉 👈 Back in 2019 we'd play a fork of Quake III called OpenArena in a Bali villa with Daniel Lockyer Marc Köhlbrugge @dannypostmaa Lenny Dos Santos 🚀 Guilherme Rizzo Andrey Azimov Sean and other ppl But it broke after a new Mac update and they never really fixed it, it kinda sucked because it was actually the only game we could just load with friends online and play death match a bit and then continue your day Luckily Luka built Q3JS which successfully compiles ioquake3 to WebAssembly and now it works in the browser To make it extra simple, I've set up a Q3JS server and frontend for you to use at which loads you straight into the game A big problem is that most of the times, nobody's playing, so I've also added Web Notifications, which notifies you if enough human players join, so you can join a match. And I've added a daily match at 8 PM GMT every day which everyone also gets notified when it starts If you want more servers and maps etc, you can check out Luka's own HAPPY FRAGGING

✨ 7 years after I set up a Quake III server, I have it running again, but now in the web browser, much easier 😊 👉 👈 Back in 2019 we'd play a fork of Quake III called OpenArena in a Bali villa with Daniel Lockyer Marc Köhlbrugge @dannypostmaa Lenny Dos Santos 🚀 Guilherme Rizzo Andrey Azimov Sean and other ppl But it broke after a new Mac update and they never really fixed it, it kinda sucked because it was actually the only game we could just load with friends online and play death match a bit and then continue your day Luckily Luka built Q3JS which successfully compiles ioquake3 to WebAssembly and now it works in the browser To make it extra simple, I've set up a Q3JS server and frontend for you to use at which loads you straight into the game A big problem is that most of the times, nobody's playing, so I've also added Web Notifications, which notifies you if enough human players join, so you can join a match. And I've added a daily match at 8 PM GMT every day which everyone also gets notified when it starts If you want more servers and maps etc, you can check out Luka's own HAPPY FRAGGING

@levelsio

300,382 Aufrufe • vor 4 Monaten

Announcing Gemini 2.5 Flash Image! (Nano Banana) from Google DeepMind. This model brings you state of the art image generation! Here's 7m of demos. Today marks a leap forward in AI-powered image creativity with the launch of stronger native image generation and editing in Gemini 2.5 Flash. Here's what's new: 👤 Consistent character design: Maintain a character's identity across multiple images, changing their outfits, poses, and scenes without losing their core look. 🎨 Creative composition: Seamlessly merge elements from up to three different images into a single, cohesive masterpiece. The potential for surrealist art and unique compositions is endless. ✍️ Targeted edits with natural language: Go beyond the prompt. You can now make highly specific edits like "change the background," "restore this faded photo," or "edit the character's outfit" with simple commands. ✨ Design & identity adaptation: Apply a specific style, texture, or pattern from one image to another, unlocking new possibilities for fashion, product design, and architectural visualization. I've put together a ~7-minute video demo to walk you through these features and show just how powerful they are in action. We can't wait to see what you all create! Try the model out in Google AI Studio, Gemini app or the Gemini API.

Announcing Gemini 2.5 Flash Image! (Nano Banana) from Google DeepMind. This model brings you state of the art image generation! Here's 7m of demos. Today marks a leap forward in AI-powered image creativity with the launch of stronger native image generation and editing in Gemini 2.5 Flash. Here's what's new: 👤 Consistent character design: Maintain a character's identity across multiple images, changing their outfits, poses, and scenes without losing their core look. 🎨 Creative composition: Seamlessly merge elements from up to three different images into a single, cohesive masterpiece. The potential for surrealist art and unique compositions is endless. ✍️ Targeted edits with natural language: Go beyond the prompt. You can now make highly specific edits like "change the background," "restore this faded photo," or "edit the character's outfit" with simple commands. ✨ Design & identity adaptation: Apply a specific style, texture, or pattern from one image to another, unlocking new possibilities for fashion, product design, and architectural visualization. I've put together a ~7-minute video demo to walk you through these features and show just how powerful they are in action. We can't wait to see what you all create! Try the model out in Google AI Studio, Gemini app or the Gemini API.

Addy Osmani

159,059 Aufrufe • vor 10 Monaten

The very first Agentic Oracle is now live! Developers, create your own prediction markets with our CLI powered by the Agentic Oracle in minutes: Updated GitHub: Updated documentation: Core Features: Oracle System: - AI-powered permissionless oracle with autonomous research agents - TLS verification and SHA-256 hashing for data integrity - IPFS proof storage for immutable audit trails - Multi-source consensus and cross-verification - Cryptographic verification of all data sources Prediction Markets: - Binary (Yes/No) and multi-outcome market support - On-chain settlement with stake-weighted governance - Order book markets with limit/market orders - Automated Market Maker (AMM) integration - Dynamic outcome slot pricing SDK Package (sora-oracle): - TypeScript SDK with full type safety - Wallet client integration (ethers.js) - Market creation and management APIs - Order placement and position tracking - Real-time orderbook queries CLI Tools (sora-oracle-cli): - create-prediction: Deploy new prediction contracts - create-market: Create binary markets with oracle scheduling - list-predictions: Query indexed contracts - config: Manage settings (auto-populated except privateKey) Smart Contracts: - 24 production-grade contracts on BSC Mainnet - OpenZeppelin v5 security (ReentrancyGuard, access control) - UUPS upgradeable proxy pattern - Pausable mechanisms and input validation Payments & Credits: - HTTP 402 micropayments via S402Facilitator - USDC on BNB Chain support - 10x parallel transaction speedup with MultiWalletS402Pool - API credit system with tiered pricing

The very first Agentic Oracle is now live! Developers, create your own prediction markets with our CLI powered by the Agentic Oracle in minutes: Updated GitHub: Updated documentation: Core Features: Oracle System: - AI-powered permissionless oracle with autonomous research agents - TLS verification and SHA-256 hashing for data integrity - IPFS proof storage for immutable audit trails - Multi-source consensus and cross-verification - Cryptographic verification of all data sources Prediction Markets: - Binary (Yes/No) and multi-outcome market support - On-chain settlement with stake-weighted governance - Order book markets with limit/market orders - Automated Market Maker (AMM) integration - Dynamic outcome slot pricing SDK Package (sora-oracle): - TypeScript SDK with full type safety - Wallet client integration (ethers.js) - Market creation and management APIs - Order placement and position tracking - Real-time orderbook queries CLI Tools (sora-oracle-cli): - create-prediction: Deploy new prediction contracts - create-market: Create binary markets with oracle scheduling - list-predictions: Query indexed contracts - config: Manage settings (auto-populated except privateKey) Smart Contracts: - 24 production-grade contracts on BSC Mainnet - OpenZeppelin v5 security (ReentrancyGuard, access control) - UUPS upgradeable proxy pattern - Pausable mechanisms and input validation Payments & Credits: - HTTP 402 micropayments via S402Facilitator - USDC on BNB Chain support - 10x parallel transaction speedup with MultiWalletS402Pool - API credit system with tiered pricing

Sora 🔶

120,425 Aufrufe • vor 7 Monaten