#vrc #vrchat #api #rest

yanked onlivfe_net

Network connection handling of onlivfe

0.0.0-alpha.0 Mar 4, 2023

#5 in #vrchat-api

Used in onlivfe_wrapper


331 lines


The network interaction parts of onlivfe.

API considerations

serde by default fails at deserializing the whole response if even a single part is unexpected. Which is why we should generally allow data to just be missing, and use serde_with's VecSkipError and DefaultOnError.

Beyond that, we should try to respect the platforms that we interact with, and generally follow rate limits and/or wishes of said platforms developers, up to a reasonable extent. However, as our application is meant for interoperability, which some platforms may not like, thus we must not bow down to any singular platform too much either.


Network connection handling of onlivfe.

Very WIP.


~1M SLoC