There are many myths in circulation regarding Resonite. This page presents a growing list of myths and explanations on why they are false, with links to other resources that indicate why.
Myths
Resonite supports NFTs and cryptocurrency
We don't.
Resonite is purposefully hard, difficult or complex on purpose
It's not; it just isn't finished.
We have a full roadmap of UI changes and other features that will improve the user experience and make things easier to use.
Resonite is restrictive on purpose
We support all groups, identities and communities. You are always welcome on Resonite as long as the Guidelines are respected. The guidelines do not restrict or discriminate against any users.
Resonite is open-source
It isn't.
Resonite is for only Furries
That isn't true; furries do make a large proportion of our community but it is not ALL of our community. Scroll through the tweets under the hash tag #Resonite to see a wide variety of avatars and communities.
Resonite only has one developer
Nope, the Resonite Team has a full list. It is true that our main developer created a lot of Resonite, but they still have other team members help!
Resonite is only for creators
That's not correct, while our UI is kinda complex right now, it is NOT just for creators. You can hang out and chat, play games, and do whatever you'd like. It's up to you; you don't need to be a creator to use or enjoy Resonite.
Resonite bans users who submit negative reviews of it
That's not correct, we only ban users who violate our Guidelines.
Resonite bans users who report security issues
If users do not follow the security and reporting policy, this may happen; provided this is followed, we will not.
You need to buy Dynamic Bones for Resonite
No, You don't.
Resonite uses its own Dynamic Bones implementation which is different from both Dynamic Bones(The original Unity asset) and PhysBones(The VRC version). Our version is free.
This person works for Resonite and they are "bad" in some way.
We've had some false reports that "bad" individuals work for our team, these are factually inaccurate and you can see a full list of Team members on our wiki.
Users in sessions you're in have access to your hard drive
They don't.
Your hard drive is only accessible by yourself via dedicated UIs that other users cannot see or interact with. If you find something that concerns you then please report it.
You don't care about security
We do, we have a full security reporting policy and reports are handled as quickly as possible depending on their urgency.
Resonite is single-threaded
Multiple parts of Resonite are multi-threaded.
More are planned to be multi-threaded in the future.
Resonite doesn't have Collections/Component access because it would allow malicious actions
While this is true, it doesn't present the whole picture. We don't avoid implementing features to avoid malicious activity, instead we design these features to avoid those. When talking about these features it is important to present the whole picture or it makes the Resonite Team look like "baddies" who are purposefully denying you access to features. Resonite isn't, its a little more complicated than that.
When it comes to both of these features, the reasons they don't exist are because:
- Resonite isn't finished yet.
- Resonite has a large roadmap that takes a lot of time to complete.
- These features need to be implemented correctly or there will be:
- Performance Issues
- Future Proofing Issues
- Backwards compatibility issues
- Potential for Malicious activity
So while you're correct, please try to represent the full picture.
Where to get the Truth?
If you're looking to get the truth about anything Resonite-related, then your best bet is to go right to the source:
- Announcements
- Twitter for our Resonite Team and Our Twitter
- Here this wiki!
See Also
- Limitations - A list of commonly discussed Resonite Limitations