and use Obfuscated text or normal text and enter the encoded text here than its ready now u can set this for api/secret/token anything it will automatically call the actual text which you have encoded using our service.
thank you for your contribution…
however somehow I’m not sure if I understand, when exactly I could use the extension …
could you explain a little bit more in detail and provide an example, when exactly the use of the extension would make sense…
Thank you
But one has to send their secret key in plain unencrypted text across the net with a get request to a third party web site, who can access this secret key, in order to get it encoded …
If I hash my Secret or API or URL inside my app… it’s not gonna be a secure practice but if I hash it using my server codes which can only be decoded by this extension - make the process more secure and safe…
what exactly is the extension about? hashing or encryption?
see the difference here
There is a fundamental difference between Hashing and Encryption algorithms, see this stackoverflow answer: Hashing is one way. You can not get your data/string from a hash code. Encryption is 2 way - you can decrypt again the encrypted string if you have the key with you.
and here you are talking about decoding/encoding…
everything in this thread is a bix mix of everything… encryption/decryption, hash, encoding/decoding…
in short you can explain as;
The server script simply convert your key/API/Url into the Key which can be then decoded only by using this extension…
Also as i haven’t relesed this opensource so i don’t think, there is a need to explain about the backend. As i already siad you key/secrect/api/url is not gonna be stored on server it’ll simply get converted to a key taht my extension can simply convert it back to actual data.
Only for mister Taifun!!
On server [ When You Generate Key]:
the script 1st hash your key{data} using a custom pattern and set of hashing.
Now this hashed data is then encoded to add an extra layer of security. [ Basically it appears like a B64 string, So may be you are confused due to this. ]
To be honest your extension of encryption is super awesome. but if we encrypt that inside our app, then it won’t make any sense.
So here i have splited the security system into 2 set client and server… were you conert your data/key/api/url etc into a key which my server generates… and then you put it inot your apk… and here you use my extension which then converts back that key into the data/api/url/key etc into actual data
So if your api key is ABCDE00123
it’ll convert this data into a key
Now you keep this data into your server as key/api/url/secret etc
and use the key into the apk were before you make request to your server key/api/url etc it’ll get converted back into the actual data [ i.e : ABCDE00123 ]
: Unlock Key
it will automatically call the actual text which you have encoded using our service. 
