Skip to content
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

Implementing API for upload of text/file through terminals #352

Closed
3 tasks done
driftywinds opened this issue Nov 26, 2024 · 2 comments
Closed
3 tasks done

Implementing API for upload of text/file through terminals #352

driftywinds opened this issue Nov 26, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@driftywinds
Copy link

driftywinds commented Nov 26, 2024

What type of request is this?

New feature idea

Clear and concise description of the feature you are proposing

I checked the docs and there doesn't seemed to be an API that lets people upload text or files straight from the terminal, meaning that people would HAVE to use the UI to do their bidding. Implementing a cURL compatible API would allow for not only terminals to interact with instances without UI but also give potential for apps on the different platforms.

Additional context

This project reminded me of transfer.sh, except its even more secure, but it only lacked this aspect in my opinion so I thought I should maybe try suggesting it as a feature. Please correct me if I'm wrong and this already exists.

Validations

  • Check the feature is not already implemented in the project.
  • Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
  • Check that the feature is technically feasible and aligns with the project's goals.
@driftywinds driftywinds added the enhancement New feature or request label Nov 26, 2024
@Zoobdude
Copy link
Contributor

Enclosed uses end to end encryption which means that the payload is encrypted on the device before being sent over the internet and only decrypted on the recipients device. Unfortunately, although it increases security, this means it's not possible to just expose an API endpoint, which is why the CLI client and NPM package exist to provide the tools needed to prepare and encrypt the file before sending.

Although you might ask what difference does it make encrypting it on the device before sending if HTTPS is secure already? This is because the server would still store your note in an unencrypted state. This is the difference between securing data in transit and data at rest.

Hope this explains why this wouldn't be possible, but thank you for the suggestion!

@driftywinds
Copy link
Author

Thank you for explaining, makes sense!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants