{ "server": "Hyperfy", "title": "Hyperfy Discord - 2025-11-29", "date": 1764374400, "stats": { "totalMessages": 25, "totalUsers": 9 }, "categories": [ { "channelId": "994775534733115412", "channelName": "💻│developers", "summary": "# Discord Chat Analysis for 💻│developers\n\n## 1. Summary\nThe discussion focused on licensing implications for the Hyperfy v2 engine, which uses GPL-3. Ash clarified that while the engine's code falls under GPL-3 requirements (meaning modifications to the engine must remain open-source), apps added via the UI interface are not subject to the same license restrictions. Ash explained that GPL-3 is designed to ensure that significant improvements to the codebase benefit the entire community, not just individual forkers. The license serves primarily to prevent profit-making from forked versions with substantial improvements that should have been contributed back to the main repository. Ash noted they would only enforce these rights in cases where someone was making significant profit from a fork with valuable improvements, and expressed openness to incorporating good features developed by the community.\n\n## 2. FAQ\nQ: When someone mods this engine, the result has to stay open-source, right? However, Apps which can be added via the UI interface, those can remain closed-source, if required? (asked by Ozymandias) A: Under GPL 3, which Hyperfy v2 engine is, that seems correct. (answered by HypPrivakos - HyperWorld.Host) / license doesn't apply to apps, those aren't part of the codebase the license is for. (answered by ash)\nQ: What's the main reason for using GPL-3 license? (implied question) A: The main reason it has this license is to deter people from making profit off a fork that has nice improvements that should have been PR'd back into our repo. (answered by ash)\n\n## 3. Help Interactions\nHelper: HypPrivakos - HyperWorld.Host | Helpee: Ozymandias | Context: Clarification about GPL-3 license implications for engine mods vs. apps | Resolution: Confirmed that engine mods must remain open-source while apps can be closed-source\nHelper: ash | Helpee: Ozymandias | Context: Detailed explanation of GPL-3 license implications | Resolution: Provided comprehensive explanation of license purpose, enforcement philosophy, and application to different components\n\n## 4. Action Items\nDocumentation: Create clear documentation about licensing implications for engine modifications vs. apps | Mentioned By: Implied from discussion\nDocumentation: Explain GPL-3 enforcement philosophy for the project | Mentioned By: ash", "messageCount": 10, "userCount": 3 }, { "channelId": "958209074045026327", "channelName": "⚡│general", "summary": "# Analysis of Discord Chat in \"⚡│general\"\n\n## 1. Summary\nThe chat segment is extremely brief, containing only two messages. User \"emotionull\" asks about workflows for coding on Hyperfy, and user \".hyp shaman\" responds with a simple command suggestion of `/create`. There is no substantial technical discussion or problem-solving evident in this limited exchange.\n\n## 2. FAQ\nQ: What's everyone's workflow when trying to vibe code on top of hyperfy? (asked by emotionull) A: `/create` (answered by .hyp shaman)\n\n## 3. Help Interactions\nHelper: .hyp shaman | Helpee: emotionull | Context: Asking about workflow for coding on Hyperfy | Resolution: Suggested using the `/create` command\n\n## 4. Action Items\nNo specific action items were identified in this brief exchange.", "messageCount": 2, "userCount": 2 }, { "channelId": "1330373197203505185", "channelName": "🤖│agents", "summary": "The chat segment is extremely brief with only three messages. A user named Fibelius inquired about examples of live agents in .xyz worlds or .hyp environments, specifically referencing an example created by drdoge. Fibelius also attempted to reach out to another user. Later, Agent12 responded suggesting that a specific user (identified by ID 297290503181959169) would be the best resource for finding a running agent.", "messageCount": 3, "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 concrete solution was reached during this conversation, though .hyp shaman suggested trying to run it locally first and referenced a beginner's video by Roustan.\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 seen Roustan's helpful video for beginners? (asked by .hyp shaman) A: CarTarL indicated they need a hosted version, not a local setup.\n\n## 3. Help Interactions:\nHelper: .hyp shaman | Helpee: CarTarL | Context: User struggling with Hyperfy setup on DigitalOcean | Resolution: Suggested trying local setup first and watching Roustan's beginner video, but solution wasn't implemented as user needed hosted version.\nHelper: Shiffty | Helpee: CarTarL | Context: User reported spam/scam attempt | Resolution: 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 guides | Description: Provide clearer instructions for setting up Hyperfy on cloud platforms 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 } ] }