Meower can't connect on TurboWarp about meower-vanilla HOT 12 CLOSED

Did you setup a local Meower server? https://github.com/meower-media-co/Meower-server#readme

from meower-vanilla.

Do I have to?

from meower-vanilla.

For security purposes, the publically available source code of Meower doesn't have a valid security key to gain trust on the Meower server. To demo the source code, you will need to be running a local meower server.

from meower-vanilla.

Speaking of trusted access, you can already find the security key with a bit of searching in the project.json of the meower.org release of meower, which you can find pretty easily too.

from meower-vanilla.

Speaking of trusted access, you can already find the security key with a bit of searching in the project.json of the meower.org release of meower, which you can find pretty easily too.

That is true, we plan on obfuscating this through custom JS provided through Github secrets, but this is still in the planning stages.

from meower-vanilla.

That is true, we plan on obfuscating this through custom JS provided through Github secrets, but this is still in the planning stages.

What about some other way of implementing trusted access, like with CORS? Ofc people would still be able to bypass it but it will be a slight bit harder and plus you can combine it with other types of security. (BTW, also how would custom JS be providable by github secrets?)

from meower-vanilla.

That is true, we plan on obfuscating this through custom JS provided through Github secrets, but this is still in the planning stages.

What about some other way of implementing trusted access, like with CORS? Ofc people would still be able to bypass it but it will be a slight bit harder and plus you can combine it with other types of security. (BTW, also how would custom JS be providable by github secrets?)

something @wgyt mentioned in dizzycord. Idk how they planned it would work. more r&d needed.

from meower-vanilla.

What about some other way of implementing trusted access, like with CORS? Ofc people would still be able to bypass it but it will be a slight bit harder and plus you can combine it with other types of security. (BTW, also how would custom JS be providable by github secrets?)

something @wgyt mentioned in dizzycord. Idk how they planned it would work. more r&d needed.

that was an idea for new pipeline, but i realized its a PITA to do new pipeline with built in packager, so we would need to build the html file ourselves and pushing it, making the custom JS idea pointless when we can just add the key manually

from meower-vanilla.

Also there's still the way of just opening your developer console, going to network and watching the WebSocket connection.

from meower-vanilla.

meower is now a key of the meower server, can be fixed by changing the server to connect to to server.meower.org.

from meower-vanilla.

from meower-vanilla.

Did you setup a local Meower server? https://github.com/meower-media-co/Meower-server#readme

Half a month later, I figured it out.

from meower-vanilla.