{
  "server": "Hyperfy",
  "title": "Hyperfy Discord - 2025-06-22",
  "date": 1750550400,
  "stats": {
    "totalMessages": 103,
    "totalUsers": 20
  },
  "categories": [
    {
      "channelId": "994775534733115412",
      "channelName": "💻│developers",
      "summary": "# Discord Chat Analysis for 💻│developers\n\n## 1. Summary:\nThe discussion primarily focused on inventory systems and app contexts in a 3D environment. Ashxn proposed a concept where apps could have different contexts - either \"being placed in the world\" or \"being held by a player.\" This would allow items like fishing rods to behave differently based on context. The team debated the merits of implementing a standardized inventory system versus maintaining flexibility for developers. Some argued that a conventional approach would improve UX but might limit creativity, while others suggested providing core functionality with an option to disable it. There was also discussion about transparency issues and light leaking problems in the rendering pipeline, specifically in the \"89 world\" project. The render-pipeline branch was intended to fix transparency ordering issues, but some problems persisted, possibly related to flipped normals affecting light leaking through meshes.\n\n## 2. FAQ:\nQ: Who designed the first room? (asked by Ashxn) A: 0mka mentioned \"home and 89\" (answered by 0mka)\nQ: Is an inventory system broadly applicable to a 3D immersive experience? (asked by maximus) A: Ashxn agreed with concerns but suggested a minimal backpack button approach with disable option (answered by Ashxn)\nQ: What branch/version is the \"89 world\" running on? (asked by Ashxn) A: It's on the dev branch (answered by ~/drdoge.eth and 0mka)\nQ: What is the \"light leak\" issue? (asked by Ashxn) A: It refers to sun leaking through mesh in a cookie cutter style, possibly not working due to flipped normals (answered by ᲼~/^b0gie-(.*)$/)\n\n## 3. Help Interactions:\nHelper: hiroP | Helpee: Ashxn | Context: Discussing inventory system implementation approach | Resolution: Suggested using engine functionality with reference implementation that developers could use or customize\nHelper: 0mka | Helpee: Ashxn | Context: Ashxn couldn't find items/wearables in the 89 world | Resolution: Explained Ashxn only saw the dock and needed to set their name\nHelper: ᲼~/^b0gie-(.*)$/ | Helpee: Ashxn | Context: Explaining why dev branch was used for 89 world instead of render-pipeline | Resolution: Clarified it was due to light leak functionality not working\n\n## 4. Action Items:\nType: Technical | Description: Fix transparency issues in the render pipeline | Mentioned By: Ashxn\nType: Technical | Description: Investigate and fix light leak functionality in render-pipeline branch | Mentioned By: ᲼~/^b0gie-(.*)$/\nType: Technical | Description: Merge transparency fixes from render-pipeline branch into dev branch | Mentioned By: Ashxn\nType: Feature | Description: Implement app contexts system (world placement vs. player held) | Mentioned By: Ashxn\nType: Feature | Description: Create standard hooks/events for backpack/inventory system | Mentioned By: Shiffty\nType: Feature | Description: Develop a \"standard item\" implementation for interoperability | Mentioned By: Shiffty",
      "messageCount": 46,
      "userCount": 7
    },
    {
      "channelId": "958209074045026327",
      "channelName": "⚡│general",
      "summary": "# Discord Chat Analysis\n\n## 1. Summary\nThe chat primarily revolves around issues with deploying Hyperfy worlds to online servers. A user named \"ovo\" reported that assets which worked perfectly in local testing appeared as red cubes when deployed to their online server. The discussion suggests this might be related to file size limits, with assets between 20MB and 90MB being affected. ovo mentioned changing the file limit in the environment variables but still experienced issues. There was also a brief discussion about the Hyperfy documentation URL changing from hyperfy.how to docs.hyperfy.xyz, causing confusion for some users. HypPrivakos, who runs a hosting service called HyperWorld.Host, offered assistance with troubleshooting the deployment issues. The conversation highlights common challenges in deploying 3D worlds and the importance of proper documentation access.\n\n## 2. FAQ\nQ: I can test my world locally and it runs perfectly, but every time i deploy the world to the online server, some uploaded assets turn into red cubes. How can this be fixed? (asked by ovo) A: That may mean either your local world or the server world versions are mismatched (answered by ᲼~/^b0gie-(.*)$/)\nQ: How big is the assets? (asked by HypPrivakos - HyperWorld.Host) A: Red cubes appeared randomly from 20M to 90M. I changed the file limit in the env. (answered by ovo)\nQ: Hyperfy.how is down.. any alternative? (asked by CheddarQueso 🧀) A: https://docs.hyperfy.xyz/ (answered by HypPrivakos - HyperWorld.Host)\n\n## 3. Help Interactions\nHelper: HypPrivakos - HyperWorld.Host | Helpee: ovo | Context: Assets appearing as red cubes when deployed to online server | Resolution: Offered to help troubleshoot if provided with world name and problematic file details\nHelper: HypPrivakos - HyperWorld.Host | Helpee: CheddarQueso 🧀 | Context: Needed alternative to hyperfy.how for documentation | Resolution: Provided the correct docs URL (docs.hyperfy.xyz)\nHelper: ᲼~/^b0gie-(.*)$/ | Helpee: ovo | Context: Assets appearing as red cubes when deployed | Resolution: Offered to help when available and suggested version mismatch as possible cause\n\n## 4. Action Items\nTechnical: Investigate why assets between 20-90MB appear as red cubes when deployed to online servers | Mentioned By: ovo\nTechnical: Review server stability issues reported by users | Mentioned By: ovo\nDocumentation: Update references from hyperfy.how to docs.hyperfy.xyz across all materials | Mentioned By: maximus\nDocumentation: Make another announcement about the docs URL change | Mentioned By: ᲼~/^b0gie-(.*)$/\nDocumentation: Resolve confusion between documentation title and URL | Mentioned By: hiroP",
      "messageCount": 33,
      "userCount": 9
    },
    {
      "channelId": "1326789867312775290",
      "channelName": "🪙│hyper",
      "summary": "# Analysis of Discord Chat in 🪙│hyper Channel\n\n## 1. Summary\nThe chat primarily revolves around concerns about the HYPER token's management and performance. Community members express worry about the token's declining value and perceived lack of management strategy. Several users request more active token management, including market making, a clear tokenomics plan, and a visible roadmap. The discussion highlights tension between long-term project development and short-term token performance.\n\nA notable perspective shared is comparing HYPER to the REKT token approach, where value derives from brand recognition rather than direct utility or revenue sharing. Some community members suggest that token value should naturally follow project success rather than being artificially supported. There's an underlying concern about vesting schedules and token unlocks potentially impacting price further.\n\nThe conversation reveals a community seeking reassurance about the token's role in the ecosystem while project representatives maintain focus on technology development over token price management.\n\n## 2. FAQ\nQ: What do you think about concerns regarding lack of token management? (asked by simk) A: I can't give financial advice. Founders have 15% vesting over three years. If you understand our tech and platform economics, you can make your own judgment calls. (answered by Ashxn)\nQ: When will there be token buy backs to bring incentive? (asked by MUDBONE) A: Unanswered\n\n## 3. Help Interactions\nHelper: Rick | Helpee: johan | Context: Sharing perspective on token utility approach | Resolution: Rick shared a tweet about REKT's approach to tokens as brand coins, which johan expanded upon to explain how tokens can derive value from project success rather than direct utility\n\n## 4. Action Items\nTechnical: None explicitly mentioned in the chat\nDocumentation: Create and publish tokenomics action plan and roadmap | Description: Develop visible short and long-term roadmap showing token's role in ecosystem | Mentioned By: simk\nFeature: Implement token buybacks | Description: Consider token buybacks as incentive mechanism | Mentioned By: MUDBONE",
      "messageCount": 14,
      "userCount": 9
    },
    {
      "channelId": "1022421054582423562",
      "channelName": "🐞│issues",
      "summary": "# Analysis of 🐞│issues Channel\n\n## 1. Summary\nThe chat segment covers a few technical issues related to model rendering and LiveKit errors. One user reported that some models only work on local servers but appear as red boxes when uploaded to online servers, even becoming red boxes for the uploader after refreshing. Another discussion briefly touched on triggers working in VR, with confirmation that they should work. Finally, there was a discussion about a LiveKit error message that incorrectly warns about including API secrets in web client bundles. This was identified as a false error caused by LiveKit's code incorrectly detecting the environment - it checks for a 'document' global variable to determine if it's running on a client, but the application uses Node.js with ponyfills for the document global, triggering the false warning. The error was reported to LiveKit but received no response.\n\n## 2. FAQ\nQ: Why do some models only work on local server but show as red boxes on online servers? (asked by Coinexpert) A: Unspecified, ash offered to investigate if the app was shared (answered by ash)\nQ: Do triggers work in VR? (asked by Enryt) A: Should work in VR, would test and update if needed (answered by 0mka)\nQ: Why is LiveKit throwing an API secret error? (asked by 0mka) A: It's a false error because LiveKit incorrectly detects environment by checking for 'document' global (answered by ash)\n\n## 3. Help Interactions\nHelper: ash | Helpee: Coinexpert | Context: Models appearing as red boxes on online servers | Resolution: Offered to investigate if app was shared\nHelper: 0mka | Helpee: Enryt | Context: Question about triggers working in VR | Resolution: Confirmed they should work and offered to test\nHelper: ash | Helpee: 0mka | Context: LiveKit error about API secret in web client bundle | Resolution: Explained it's a false error due to LiveKit's environment detection logic\n\n## 4. Action Items\nTechnical: Investigate models appearing as red boxes on online servers | Description: Debug why models work locally but not when uploaded | Mentioned By: Coinexpert\nTechnical: Test triggers in VR | Description: Verify functionality and update if needed | Mentioned By: 0mka\nTechnical: Find way to suppress false LiveKit error | Description: Error is \"annoying af\" but currently unavoidable | Mentioned By: ash",
      "messageCount": 10,
      "userCount": 4
    }
  ]
}