HTTP Request
AndryGabry1
today while I was developing my world, I ran into a fairly serious problem (in my opinion), namely the impossibility of making an http request, especially considering that with the sdk2 in one way or another you could do this ...
So what I think is that it would be a very important feature to include, as it would allow you creators of worlds a greater creative capacity.
very important also because, despite the improvement brought by the sdk3, this can lead many world creators to still prefer the old sdk.
Log In
AndryGabry1
What I think is that it is perfectly possible.
Probably the reason they don't include it is because you would have to deal with possible misuse by malicious parties.
That said, in my opinion, it would be enough to implement similar mechanics:
- Warn the user that the world is making requests to unknown servers, possibly allowing them to enable or disable such requests.
- Give information regarding what is being requested from an external server: then the world developer would have to explain why it needs such requests and especially what happens/what data it sends during such a request.
- one could create a system of preauthorization of domains, going to create a system that would egg a check and in case ban such domains.
It sounds like a lot, but for a game that has been up for so many years, it shouldn't be much of a problem, plus the community world system where worlds are put in before they are officially approved would naturally dispose of worlds that cause crashes or the like.
Of course some other considerations would have to be made perhaps, and I would be open to discussing that with the developers.
Having said that, this feature is really important and would allow authors to give more leeway to their creativity
EEYORE＋․＋
I'm having the same concern. Author, is HTTP communication impossible?
AndryGabry1
EEYORE＋․＋: What I think is that it is perfectly possible.
Probably the reason they don't include it is because you would have to deal with possible misuse by malicious parties.
That said, in my opinion, it would be enough to implement similar mechanics:
- Warn the user that the world is making requests to unknown servers, possibly allowing them to enable or disable such requests.
- Give information regarding what is being requested from an external server: then the world developer would have to explain why it needs such requests and especially what happens/what data it sends during such a request.
- one could create a system of preauthorization of domains, going to create a system that would egg a check and in case ban such domains.
It sounds like a lot, but for a game that has been up for so many years, it shouldn't be much of a problem, plus the community world system where worlds are put in before they are officially approved would naturally dispose of worlds that cause crashes or the like.
Of course some other considerations would have to be made perhaps, and I would be open to discussing that with the developers.
Having said that, this feature is really important and would allow authors to give more leeway to their creativity
Jazzy Senpai
I see two major uses for this. Updating posters in worlds (in SDK 2 we use Panos to load textures over HTTP) and for sending inputs to remote applications (things like remote controlling OBS for festivals from inside VRChat, my VRC GBA project, etc etc etc) Ofcourse this could lead to data mining for analytics, but that's why we have the untrusted URLs checkbox right?