-
-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CLI client #55
Comments
Hi @cupcakearmy thanks for this great peace of code! One question, do I understand you correctly that it is already possible to use the api? I was looking for this feature but did not found anything. An API which could be use for automated generation of messages would be interesting eg for delivering credentials etc. during automated server or user management etc. |
Hey there. So the "API" works, but as the server is not aware of encryption, it does not help much. It's basically a glorified string key value store. |
understood. But wouldn't it be worth spending the frontend an api? I would be not more than 2 endpoints, one for encryption, one for version? |
You mean the german "spendieren"? |
yes sorry. I mean because the frontend is taking care about the encryption etc. the functions are already there. What is needed is an api endpoint from the frontend which uses the functions of the frontend to generate the messages, and return the url for further usage. |
Maybe lets chat on discord :) https://discord.com/invite/nuby6RnxZt |
Some have asked about the possibility of using cryptgeon from the cli.
(#54 and https://discord.com/channels/252403122348097536/912714340157755482/1016073982757322863)
However while the app already uses Rest and using the endpoints is not an issue, encryption is handled by design in the front end, therefore the server is agnostic about the contents of the data, wether it's encrypted or not.
Goals:
Anyone interested: leave feedback and comments below so we can do something together here :)
The text was updated successfully, but these errors were encountered: