ๆญฃๅœจๅŠ ่ฝฝ่ง†้ข‘...

่ง†้ข‘ๅŠ ่ฝฝๅคฑ่ดฅ

Your AI stack just stopped being closed. ๐Ÿ”“ TanStack AI now speaks AG-UI client-to-server. - The same client hits any AG-UI server. - Any AG-UI client hits a TanStack server. Zero breaking changes. Migration guide in the tweet below ๐Ÿ‘‡

79,086 ๆฌก่ง‚็œ‹ โ€ข 1 ไธชๆœˆๅ‰ โ€ขvia X (Twitter)

0 ๆก่ฏ„่ฎบ

ๆš‚ๆ— ่ฏ„่ฎบ

ๅŽŸๅง‹ๅธ–ๅญ็š„่ฏ„่ฎบๅฐ†ๆ˜พ็คบๅœจ่ฟ™้‡Œ

็›ธๅ…ณ่ง†้ข‘

We are witnessing a fundamental shift in how software is built. Over the decades, UI was static and predictable. But AI is changing the fundamental nature of the interface. We are moving away from fixed UI and toward a new standard: Generative UI. Generative UI lets agents participate in the UI, not just the conversation. Itโ€™s a dynamic participant in the user experience. Depending on the complexity of your app, Generative UI generally falls into three categories: 1. Static (AG-UI): UI is chosen from a fixed set of hand-built components 2. Open-Ended (MCP Apps): agent sends arbitrary content like raw HTML or iframes for total flexibility. 3. Declarative (A2UI): agent and frontend communicate via a structured UI spec for dynamic widgets and forms. The AG-UI Protocol by CopilotKit is the real breakthrough. AG-UI acts as the universal transport layer. It provides the integrations and middleware for every Gen-UI spec, making it trivial to bring dynamic components into your existing app. CopilotKit provides the go-to ecosystem for building agentic applications and is the React client of AG-UI. It is designed to be deeply integrated, allowing developers to bring their own frameworks or protocols to the table. Play around with different types of Generative UI here โ†’ Check out the video attached to see Generative UI in action. Appreciate the CopilotKit team for collaborating with me on this deep dive.

Pratham

33,920 ๆฌก่ง‚็œ‹ โ€ข 5 ไธชๆœˆๅ‰

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 ๆฌก่ง‚็œ‹ โ€ข 3 ไธชๆœˆๅ‰