{ "server": "Hyperfy", "title": "Hyperfy Discord - 2026-01-23", "date": 1769126400, "stats": { "totalMessages": 101, "totalUsers": 24 }, "categories": [ { "channelId": "958209074045026327", "channelName": "βš‘β”‚general", "summary": "# Analysis of βš‘β”‚general Discord Chat\n\n## 1. Summary\nThe discussion centers around Hyperfy's transition from v1 to v2, with significant focus on improving onboarding and accessibility. Jin announced developing a v1 to v2 conversion pipeline, initially requiring Blender but later streamlined to direct conversion. This tool aims to help world owners migrate their content to v2. Several members highlighted the need for better onboarding resources, including starter templates with pre-installed apps from v1. Ash acknowledged these concerns, noting the challenge of balancing ease-of-use with user ownership of worlds. Jin also suggested improving developer experience through better documentation, including creating LLM-friendly documentation and making app repositories more accessible. The community discussed the importance of having v1 apps available in v2 to provide users with a foundation rather than starting with empty worlds. Jin requested that Ash upload a GitHub repository with reference apps to improve discoverability and LLM training capabilities.\n\n## 2. FAQ\nQ: What is the utility of the hyper token? (asked by Asik) A: Unanswered\nQ: What's the difference between v1 and v2, if hyperfy.io gets shutdown why would the token remains relevant? (asked by rando1337) A: Unanswered\nQ: Does v2 have draco / meshopt / EXT_mesh_gpu_instancing gltf extension support? (asked by jin) A: None of those! Ultra simple. Webp textures go a long way. (answered by ash)\n\n## 3. Help Interactions\nHelper: π•½π–”π–šπ–˜π–™π–†π–“ | Helpee: Cybermike | Context: Setting up a free server for a Hyperfy world | Resolution: Shared a YouTube tutorial link\nHelper: HypPrivakos - HyperWorld.Host | Helpee: Cybermike | Context: Alternative to self-hosting a world | Resolution: Offered to provide a world directly\nHelper: jin | Helpee: Multiple users | Context: Converting v1 worlds to v2 | Resolution: Created a batch converter tool that works directly without Blender\nHelper: jin | Helpee: Pete | Context: Converting worlds to v2 | Resolution: Offered to convert Pete's worlds personally\nHelper: untitled, xyz | Helpee: Community | Context: Explaining onboarding options | Resolution: Described GitHub and HyperWorld hosting paths for getting started\n\n## 4. Action Items\nTechnical: Create a GitHub repository with all v1 reference apps | Description: Upload apps from reference client to improve accessibility | Mentioned By: jin\nTechnical: Implement v1 to v2 world conversion tool | Description: Direct conversion without Blender step | Mentioned By: jin\nTechnical: Generate zip files of converted worlds for all world owners | Description: Package worlds and assets ready to launch with v2 | Mentioned By: jin\nDocumentation: Create LLM-friendly documentation | Description: Make a llms.txt file and add docstrings to code | Mentioned By: jin\nDocumentation: Improve discoverability of app repositories | Description: Create easy-to-find repo of different apps | Mentioned By: jin\nFeature: Bring back default v1 apps as pre-installed hyp apps in v2 | Description: Provide scaffolding for new users instead of empty worlds | Mentioned By: mrtzhckr\nFeature: Create a v2 homepage | Description: Help users understand what Hyperfy is and how to use it | Mentioned By: untitled, xyz\nFeature: Develop a starter pack with common v1 apps | Description: Give new users a foundation to build upon | Mentioned By: BallisticBanana", "messageCount": 71, "userCount": 23 }, { "channelId": "994775534733115412", "channelName": "πŸ’»β”‚developers", "summary": "# Analysis of πŸ’»β”‚developers Channel\n\n## 1. Summary\nThe discussion primarily focused on sprites.dev, a cloud VM service created by fly.io designed for AI agents but being repurposed for Hyperfy deployments. Ash reported successfully running Hyperfy on sprites.dev in just 3 minutes, noting it's easier to use than fly.io. Key advantages mentioned include hibernation when not in use (reducing costs), and potential cost-effectiveness for intermittent usage patterns typical of Hyperfy worlds. Ash is working on documentation and backup/restore functionality to enable local backups. The conversation also touched on a new webviews feature in development (PR #147) contributed by Saori. Additionally, there was a brief discussion about \"hyper scape,\" which was clarified to be a modified fork of Hyperfy.\n\n## 2. FAQ\nQ: What is sprites.dev? (asked by π•½π–”π–šπ–˜π–™π–†π–“) A: It's made by fly.io, meant for giving AI agents a VM in the cloud to work in, but it's easier to work with than fly.io (answered by ash)\nQ: Does the hyper scape thing Shaw's making have anything to do with hyperfy or just similar naming? (asked by general hyper) A: It's built off Hyperfy / It's a modified fork of Hyperfy (answered by π•½π–”π–šπ–˜π–™π–†π–“ and Jayzen)\n\n## 3. Help Interactions\nHelper: ash | Helpee: Channel members | Context: Sharing information about sprites.dev for Hyperfy deployment | Resolution: Provided initial insights and promised documentation\nHelper: π•½π–”π–šπ–˜π–™π–†π–“ and Jayzen | Helpee: general hyper | Context: Question about relationship between hyper scape and Hyperfy | Resolution: Clarified that hyper scape is a modified fork of Hyperfy\n\n## 4. Action Items\nType: Documentation | Description: Create documentation for using sprites.dev with Hyperfy | Mentioned By: ash\nType: Technical | Description: Implement backup/restore functionality for sprites.dev deployments | Mentioned By: ash\nType: Technical | Description: Complete webviews implementation (PR #147) | Mentioned By: ash", "messageCount": 21, "userCount": 5 }, { "channelId": "1326789867312775290", "channelName": "πŸͺ™β”‚hyper", "summary": "# Analysis of Discord Chat in \"πŸͺ™β”‚hyper\" Channel\n\n## 1. Summary\nThe chat segment is very brief and contains minimal technical content. The conversation primarily consists of casual banter about a \"shame cube\" gif being shared, with references to buying and selling (likely cryptocurrency or NFTs). There is a mention of someone creating actual shame cubes in Hyperfy (presumably a virtual platform). No substantive technical discussions, decisions, or problem-solving occurred in this limited chat excerpt.\n\n## 2. FAQ\nNo significant questions with meaningful responses were identified in this chat segment.\n\n## 3. Help Interactions\nNo significant help interactions were identified in this chat segment.\n\n## 4. Action Items\nNo clear action items were identified in this chat segment.\n\nThe chat appears to be primarily social in nature, with users sharing gifs and making jokes about a \"shame cube\" concept. There is a brief mention of someone updating a name, but without additional context, it's not possible to determine if this relates to any technical task or feature.", "messageCount": 8, "userCount": 3 }, { "channelId": "958214956426350652", "channelName": "πŸ“£β”‚announcements", "summary": "Type: Technical | Description: Download and preserve content from hyperfy.io before April 1st, 2026 | Mentioned By: ash", "messageCount": 1, "userCount": 1 } ] }