# Hyperfy Discord - 2026-02-03

## Overall Discussion Highlights

### Hyperfy v1 to v2 Migration
- Jin documented remaining apps that need migration from v1 to v2, creating issues and organizing them into milestones
- Approximately 90% of entities are covered in the migration plan
- Apps being migrated include hyperfy-terrain (296 uses), hyperfy-command (265), hyperfy-shifter (211), and many others

### Platform Philosophy & Approach
- Strong emphasis on content exportability as a minimum requirement for web3 platforms
- Jin advocated for a "File>App mindset" and digital preservation through open platforms
- Discussion on the fragility of cloud services (including arweave and IPFS) with promotion of local-first approaches
- PabloFM from Numinia shared comparative screenshots showing Hyperfy's achievements despite having fewer resources than competitors
- Community members appreciated Hyperfy's "lean, agile and open source" approach, seeing it as advantageous in the AI era

### Community Projects
- User "cru" announced "molt.space", an open-source fork of Hyperfy, inviting developers to contribute, fork, or remix the code

### Technical Issues
- A security issue was reported where Chrome flags a site as "not secure" while other browsers (Safari, MS Edge, Brave) don't show the warning
- Site administrator mentioned they had fixed a similar flag last week but Chrome flagged it again

## Key Questions & Answers

**Q: What apps remain to be migrated from v1 to v2?**  
**A:** Various apps including hyperfy-terrain, hyperfy-command, hyperfy-shifter, hyperfy-alert, hyperfy-attachable, and many others with usage counts ranging from 296 to 31, plus custom content (answered by jin)

## Community Help & Collaboration

- **Migration Planning**: Jin helped the community by creating issues for all remaining apps that need migration and organizing them into milestones for better tracking
- **Browser Compatibility**: Multiple users tested a website across different browsers to help identify that a security warning was specific to Chrome rather than a universal issue

## Action Items

### Technical
- Complete migration of remaining v1 to v2 apps, starting with most frequently used ones (Mentioned by: jin)
- Implement content export functionality for better user data ownership (Mentioned by: jin)
- Check out and potentially contribute to the molt.space GitHub repository (Hyperfy fork) (Mentioned by: cru)
- Resolve Chrome security warning issue on website (Mentioned by: site administrator)

### Documentation
- Create announcement about v1 platform shutdown with timeline and transition plan (Mentioned by: jin)

### Feature
- Adopt "File>App mindset" for digital preservation that prioritizes user ownership of content and open standards (Mentioned by: jin)
- Implement local-first approaches for content storage as the most private, fast, and decentralized solution (Mentioned by: jin)