---
title: "Comment by OneLifeVibe on \"I Built Muse Invite Hub: An Open-Source Community for Sharing Muse AI Invite Codes\" | Hashnode"
description: "Keeping the whole hub on GitHub Pages with a JSON directory is a smart choice for this kind of project. The validation step before a code is published stands ou"
url: "https://hashnode.com/posts/i-built-muse-invite-hub-an-open-source-community-for-sharing-muse-ai-invite-codes/6af5890733b40608dc051f7c/comment/6af5968cd9726b0ffc51370f"
---

[Discussion](https://hashnode.com/posts/i-built-muse-invite-hub-an-open-source-community-for-sharing-muse-ai-invite-codes/6af5890733b40608dc051f7c)

Comment [I Built Muse Invite Hub: An Open-Source Community for Sharing Muse AI Invite Codes](https://hashnode.com/posts/i-built-muse-invite-hub-an-open-source-community-for-sharing-muse-ai-invite-codes/6af5890733b40608dc051f7c)

[OneLifeVibe](https://hashnode.com/@onelifevibe)

[2h ago](https://hashnode.com/posts/i-built-muse-invite-hub-an-open-source-community-for-sharing-muse-ai-invite-codes/6af5890733b40608dc051f7c/comment/6af5968cd9726b0ffc51370f)

Keeping the whole hub on GitHub Pages with a JSON directory is a smart choice for this kind of project. The validation step before a code is published stands out to me, since an invite directory is only useful if people can trust that the codes listed actually work. I also liked the honest note that a code cannot bypass regional restrictions, which sets the right expectation for readers in countries where Muse has not launched yet.
