{ "server": "Hyperfy", "title": "Hyperfy Discord - 2025-11-30", "date": 1764460800, "stats": { "totalMessages": 121, "totalUsers": 12 }, "categories": [ { "channelId": "1330373197203505185", "channelName": "🀖│agents", "summary": "# Discord Chat Analysis for \"🀖│agents\" Channel\n\n## 1. Summary\nThe chat segment contains a brief discussion about AI agents in virtual worlds, specifically focusing on examples of live agents in .xyz worlds or .hyp environments. Fibelius inquires about examples like one created by drdoge months ago, expressing interest in agentic AI beyond simple applications like trading, shooting games, or basic emoji reactions. They criticize what they perceive as the community's focus on development details and simplistic NPC behaviors. In response, .hyp shaman clarifies the distinction between basic NPCs in play.hyperfy and more advanced agent implementations like \"Eliza in hyperfy,\" which allows characters to interact with the platform in more sophisticated ways, offering to answer further questions about this technology.\n\n## 2. FAQ\nQ: Does anyone know some .xyz worlds or .hyp examples with live agents? (asked by Fibelius) A: Agent12 suggested that @297290503181959169 would probably be the best bet for a Running Agent.\nQ: Is the agent example made by drdoge some months ago still live? (asked by Fibelius) A: Unanswered\n\n## 3. Help Interactions\nHelper: .hyp shaman | Helpee: Fibelius | Context: Confusion between basic NPCs and more advanced agents in hyperfy | Resolution: Clarified the distinction between simple NPCs in play.hyperfy and more advanced \"Eliza in hyperfy\" implementation, offering further assistance.\n\n## 4. Action Items\nFeature: Explore more sophisticated AI agents beyond basic NPCs in virtual worlds | Description: Development of agents that go beyond simple behaviors like trading, shooting, or emoji reactions | Mentioned By: Fibelius\nDocumentation: Clarify the differences between NPCs and advanced agents in hyperfy | Description: Explain capabilities of \"Eliza in hyperfy\" versus basic NPCs | Mentioned By: .hyp shaman", "messageCount": 6, "userCount": 3 }, { "channelId": "958209074045026327", "channelName": "⚡│general", "summary": "The chat segment is extremely brief with minimal technical content. There appears to be a brief question about a system called \"V1\" being down, which was responded to with confirmation that it was working for at least one user. The chat also includes a command \"/create\" and brief comments about \"Lore\" and a map. No substantial technical discussions, decisions, or problem-solving occurred in this limited exchange.", "messageCount": 5, "userCount": 3 }, { "channelId": "994775534733115412", "channelName": "💻│developers", "summary": "# Analysis of 💻│developers Channel\n\n## 1. Summary\nThe discussion primarily focused on licensing concerns related to Hyperfy's GPLv3 license and its implications for app development. Ozymandias raised questions about whether apps built on Hyperfy would be subject to GPLv3 requirements, expressing concern about protecting trade secrets while contributing to the platform. HypPrivakos and ash clarified that apps are separate from the codebase and not subject to the license, comparing it to how Windows apps can be proprietary despite running on Windows. 3rdEyeVisuals provided detailed explanations about GPL licensing, noting that while selling GPL software is permitted, source code must be provided. The conversation explored the \"SaaS loophole\" where GPL only triggers when distributing software, not when running services. A key technical solution discussed was keeping proprietary logic on the backend server while only sending minimal UI and rendering code to the browser, thus protecting trade secrets while complying with licensing requirements. Ozymandias mentioned creating a PR and an issue for tracking code changes, acknowledging Hyperfy's issue template.\n\n## 2. FAQ\nQ: Does the GPLv3 license apply to apps built on Hyperfy? (asked by Ozymandias) A: No, apps are not part of the codebase, so the license doesn't apply to them. (answered by ash and HypPrivakos)\nQ: Can you sell GPL software? (implied by Ozymandias) A: Yes, you can sell GPL software at any price, but you must provide source code, include the GPL license, and allow recipients the same freedoms. (answered by 3rdEyeVisuals)\nQ: Does GPLv3 require sharing code when running it as a service? (implied in discussion) A: No, GPLv3 only triggers when you distribute the software, not when running it as a service. (answered by 3rdEyeVisuals)\nQ: When a scene app interacts with Hyperfy engine, does it create a \"single derivative work\" under GPL? (asked by Ozymandias) A: Unanswered definitively, though ash maintained apps can be proprietary and monetized.\nQ: How can developers protect their proprietary code while using Hyperfy? (implied by Ozymandias) A: Keep logic on the backend server and only send minimal UI and rendering code to the browser. (answered by 3rdEyeVisuals)\n\n## 3. Help Interactions\nHelper: 3rdEyeVisuals | Helpee: Ozymandias | Context: Explaining GPL licensing implications for app development | Resolution: Provided detailed explanation of GPL misconceptions and suggested keeping proprietary code on backend servers.\nHelper: ash | Helpee: Ozymandias | Context: Clarifying whether GPLv3 applies to apps | Resolution: Confirmed apps can be entirely proprietary and monetized as they're separate from the engine.\nHelper: HypPrivakos | Helpee: Ozymandias | Context: Explaining relationship between apps and codebase | Resolution: Clarified that apps use the Hyperfy engine but don't directly use code from its codebase.\nHelper: 3rdEyeVisuals | Helpee: Ozymandias | Context: Demonstrating backend code approach | Resolution: Shared code example showing how to keep logic on backend while only rendering in browser.\n\n## 4. Action Items\nType: Technical | Description: Create backend services for apps to keep proprietary logic server-side | Mentioned By: 3rdEyeVisuals\nType: Technical | Description: Implement fetch operations from private backend with minimal UI in browser | Mentioned By: 3rdEyeVisuals\nType: Documentation | Description: Clarify licensing implications for apps built on Hyperfy | Mentioned By: Ozymandias\nType: Technical | Description: Create PR for added features to enhance Apps environment capabilities | Mentioned By: Ozymandias\nType: Documentation | Description: Elaborate on how Hyperscape handles licensing with Hyperfy fork | Mentioned By: 3rdEyeVisuals", "messageCount": 98, "userCount": 4 }, { "channelId": "1326789867312775290", "channelName": "🪙│hyper", "summary": "No technical discussions, decisions, or problem-solving occurred in this chat segment. The only interaction was a user (QMA) using a command \"$hyperfy\" to which a bot (Rick) responded with price information about the HYPER/SOL trading pair on Solana, showing a market cap of 690K with a -7.4% price change and providing a link to Dexscreener.", "messageCount": 2, "userCount": 2 }, { "channelId": "1022421054582423562", "channelName": "🐞│issues", "summary": "# Analysis of 🐞│issues Channel\n\n## 1. Summary:\nThe chat segment shows a user (CarTarL) experiencing difficulties setting up a Hyperfy world on a DigitalOcean droplet. They encountered a build error related to esbuild service being stopped on Node.js v22.11.0. The user mentioned that the process used to be simpler in the past with NFT integration. During the conversation, CarTarL also had to deal with a spam/scam attempt from another user trying to redirect them to an external server. No resolution to the technical issue was reached within this chat segment, though another user (.hyp shaman) asked if they had tried running it locally or watched Roustan's beginner guide video.\n\n## 2. FAQ:\nQ: How can I fix the esbuild error when setting up Hyperfy on a DigitalOcean droplet? (asked by CarTarL) A: Unanswered\nQ: Have you managed to get it working locally or watched Roustan's beginner guide? (asked by .hyp shaman) A: CarTarL indicated they need a hosted version, not local, and have been following the DigitalOcean docs.\n\n## 3. Help Interactions:\nHelper: .hyp shaman | Helpee: CarTarL | Context: User struggling with Hyperfy setup on DigitalOcean | Resolution: Suggested trying locally first and watching a beginner guide video, but no final resolution achieved.\nHelper: Shiffty | Helpee: CarTarL | Context: User reported someone trying to redirect them to an external server for \"support\" | Resolution: Shiffty confirmed the problematic user was banned (\"Hammered\").\n\n## 4. Action Items:\nTechnical: Investigate esbuild service stopping during build process on Node.js v22.11.0 | Description: Fix build error when deploying Hyperfy on DigitalOcean | Mentioned By: CarTarL\nDocumentation: Update deployment documentation | Description: Clarify current setup process for hosted environments like DigitalOcean | Mentioned By: CarTarL\nTechnical: Review compatibility with Node.js v22.11.0 | Description: Address deprecation warning for fs.Stats constructor | Mentioned By: CarTarL", "messageCount": 10, "userCount": 4 } ] }