You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want our own global ban system, but solely relying on a remote command execute system can cause some issues like banlist desync and over populating.
So what if, instead, we make a standard configurable HTTP API for authenticating users when joining.
Joining server might become slower because server need to send request to a http server, but this way we can offload ASN/VPN banning and global ban to a web server.
We are definitely keeping the old ban system for local bans and for hosters who don't want to setup a authentication server.
And we still need the remote command system for banning a players after they have joined.
The text was updated successfully, but these errors were encountered:
TsFreddie
changed the title
[feat][RFC] HTTP Authenticate API
[feat][RFC] HTTP/Websockets Authentication API
Aug 28, 2021
We want our own global ban system, but solely relying on a remote command execute system can cause some issues like banlist desync and over populating.
So what if, instead, we make a standard configurable HTTP API for authenticating users when joining.
Joining server might become slower because server need to send request to a http server, but this way we can offload ASN/VPN banning and global ban to a web server.
We are definitely keeping the old ban system for local bans and for hosters who don't want to setup a authentication server.
And we still need the remote command system for banning a players after they have joined.
The text was updated successfully, but these errors were encountered: