Appreciate the staggered responses, @Yewnyx. I guess breaking it up was necessary to fit the mental gymnastics in. So let’s address this one incision at a time:
1. Prefabs and Compile Time:
You went on about prefabs not existing at compile time, shaders not being decompilable, and Unity behaving differently in builds. I appreciate the Unity lecture, but none of that changes the reality that the content itself is still flagged with recognizable identifiers—identifiers that file-checking could absolutely parse before it’s even considered for upload. We’re not talking about decompiling shaders; we’re talking about recognizing known prefabs. This isn’t cutting-edge tech; it’s basic file validation.
2. Ineffective Code Gating Systems:
You claim that every code-gating system is “foundationally and fundamentally bad.” Funny, because Resonite—significantly smaller and with fewer resources—somehow manages to implement content gating that works. So, what’s VRChat’s excuse with its larger budget and broader reach? You talk about it being “ineffective,” yet it’s demonstrably more effective than doing nothing at all—which is what VRChat seems content with.
3. Users Are the Problem and the Solution:
The audacity of blaming users for the platform’s lack of moderation is impressive. Imagine any other platform responding to security concerns by saying, “Well, maybe the users are the real issue.” It’s called accountability. Platforms are responsible for their own moderation policies. Passing the blame to users is both lazy and a blatant attempt to divert from the core issue: VRChat’s hands-off approach.
4. “Treating This Like a Job” and “You’re Just One Person”:
I’m a paying subscriber to VRC+. That’s money going directly to the platform to, I assume, support its growth and safety. Don’t try to diminish community effort with the “You’re just one person” argument. One person can and has sparked change before. And by the way, if I’m just one insignificant voice, it’s interesting how much you feel the need to respond to every point I make.
5. “Read the Documentation”:
This is my favorite. Documentation that conveniently talks about vague plans with no visible outcome. Do you really believe tossing around devblogs that go nowhere is the same as progress? Because last I checked, actual results are measured by improvements in user safety—not by well-worded promises.
Let me make this clear, @Yewnyx—I’m not here to sip VRChat’s Kool-Aid and sing songs of patience. I’m here to expose the cracks, push for solutions, and make sure VRChat cannot ignore them. If that makes you uncomfortable, perhaps it’s time to ask why demanding better for the community bothers you so much. Or is it just easier to settle for mediocrity and call it “realism”?