Depreciated builds connecting to server and posting #72
Comments
Wouldn't it be possible for the Cloudlink Server to send a message containing a version number, and have the client check to see if it is an older build? |
I have an idea. |
More or less CLTLS, a project yet to be implemented. Keep it simple for now, we'll just do a number check. |
CLTLS can be utilized in a special way, sorta. |
Please contact me in Discord as we still have to discuss CLTLS. |
I can try, but I can't for too long. |
Nevermind! I can't. Sorry! I'll just try this weekend. |
ok. |
Because of improvements to CloudLink and the addition of Trusted Access, we can simply assign a unique key for a new build of Meower and put that key into the compiled HTML page, without sharing the key in public access source code. For every new build, we destroy the old keys, which will prevent older builds of Meower from gaining trust on the server. |
@MikeDev101 what would happen with meowerplus, would we get our own keys? |
keys will be provided when needed |
Fixed as of latest build, with both trust keys and IP blocking |
Discussed in https://github.com/meower-media-co/Meower/discussions/70
Originally posted by TermOfficial November 24, 2021
This could potentially cause meower to be a train wreck if we make a bug in a previous release and let the old releases connect to the server. If the bug was severe and did something bad, the server is a goner.
The text was updated successfully, but these errors were encountered: