Default REALM and SOLO Mode Implementation This proposal is now in status: PASSED. Voting Results: * Yes 81% 7,758,097 VP (168 votes) * No 14% 1,437,464 VP (7 votes) * Abstain 5% 504,177 VP (7 votes)

Hello, @mazafaka, It is nice to see you involved on this discussion :slight_smile:. Initially, I shared the same concern as you, but I have since come to understand the importance of this change for Decentraland. I would like to add my 2 cents here, which may prove valuable to others as well. Here is my perspective on the proposal (please note that these opinions are my own): * One of Decentraland's primary objectives is to attract new users and increase the Monthly Active Users (MAU) count. I believe we can all agree on the significance of this goal. * Within the DAO, we often discuss realms, servers, and nodes. However, for "regular" users who are not involved in the DAO or interested in the technical aspects of Decentraland's infrastructure, we need to shift our perspective and consider them as newcomers. Building an open metaverse should not be limited to technical individuals. It appears that this might be the current situation, where users need to learn several things before fully enjoying Decentraland. * Given the above, should users really need to be concerned about realms, nodes, and servers when accessing play.decentraland.org? Or should we strive to make these technical details transparent, allowing users to focus solely on connecting with their friends in the metaverse? We should minimize cognitive complexity, such as questions like "where are you?" or "why can't I see you?" Our aim is to facilitate connections among people: "Come to coordinates X, Y, and you will find all of us." I understand that this might seem like a significant change, but once I framed it in these terms, it became clear to me. We must prioritize the user experience to attract a larger user base. Regarding the main concern about decentralization, it won't be a single node going forward. All existing nodes will remain in place and continue to be essential for the proposed changes to function effectively. The following assumptions outline how this proposal maintains decentralization (again, this is my point of view): 1. User data will continue to be replicated: By replicating user data across multiple nodes, we ensure redundancy and prevent single points of failure. This approach aligns with the decentralized nature of the network. 2. User data will still be validated by all the nodes: In a decentralized system, it is crucial to have multiple nodes validate user data. This validation process helps achieve consensus and enhances the integrity of the data. 3. Decentraland will still rely on all nodes for smooth operation: Each node plays a crucial role in processing and delivering content to users. The continued involvement of all nodes is vital for the system to function seamlessly, highlighting the decentralized nature of Decentraland. 4. The change: User communications will no longer be reliant on the specific node they are connected to: With this proposed change, the responsibility of determining user interactions will no longer rest with individual nodes. Instead, the focus will shift towards content delivery (*niceeee*). Users will have the freedom to connect with others without being constrained by a specific node, enhancing the decentralized nature of the platform. I strongly think that by shifting the responsibility of user interactions away from individual nodes, we further promote decentralization and empower users to connect with others freely within the metaverse. **(Off-note: even when the nodes are not currently handling these user communications they act as a boundary, this is what I mean)** Thanks for reading!

Congratulations! Looks like someone has finished the python scripting course! :clap: "Realm" doesn't necessarily refer to just one server; it might be implemented with one or more servers. As stated in the proposal, it's a bundle of services that can be scalable in case of overload, and it could also consist of multiple servers in different regions. The main focus of this proposal should be on decoupling the Content service from the Comms service and facilitating people connecting with each other. The code is open source, allowing anyone to start a new Comms service. Furthermore, anyone can run a Comms service without the need to host a Content service, utilizing the current Catalyst network. In case of failure, there will be multiple Comms services available, giving users the freedom to switch between them. I see someone who is genuinely interested in the progress of the platform and not their own interest posting a proposal. I see someone doing something to get people to connect with each other, which is the final goal, posting a proposal. Ignorants & arrogants commenting on proposals?

Please, use the word "server" next time. With this idea you can only overload the "default" realm at some point. Saw nothing about latency and regions on this proposal. You know what network latency is, and why there are few realms? Newbs posting proposals?

Default doesn't mean centralization, please read the full proposal and the white paper and then respectfully comment if you have a concern.

Default realm = centralization :) Voting NO on this piece of ****