5 ms·

One thing that could be improved with this is to have an option for a human readable/typeable link. I wanted to quickly transfer a file from my desktop to my ph

One thing that could be improved with this is to have an option for a human readable/typeable link. I wanted to quickly transfer a file from my desktop to my phone. Used Send and realized I didn't want to type that cryptographic URL. I ran the Send link through Typer.in (specializing in hand-typed urls) and it worked as I initially expected. However, it would be nice if Send had this functionality by default.

cdancette 9y ago
The private key is in the url, and mozilla says explicitly that they don't know this private key. They could shorten the url but then they would have the private key.
konart 9y ago
Well, if you use Firefox on your phone you can leave tab openned on your desktop and choose this tab on your phone. Or, if you are a Telegram user - you can send the link you yourself. You can also use you mail inbox.
dublinben 9y ago
You could have also just generated a QR code of the URL and scanned it with your phone, if you didn't want to send it electronically. I'm sure they expect users to just email these links to their recipient.
jwcacces 9y ago
Typer.in stores the link you give it, and returns a human readable lookup link. The whole point of Send is that the link includes the secret key to decrypt your file. Whoever you give that secret to, including Typer.in can get the file. The Send link must include the secret key, because no one else should get it, and that key must be of sufficient length to protect your file. Thus human-readable-izing it could do nothing to decrease its complexity and would just result in a huge string of words that were just as much as a pain to type in.
- indiv0 9y ago
  At least at the moment, downloading the file once removes it from Mozilla's servers. So in the event typer.in used the URL you provided to download the file, you would know as the file would no longer be accessible.
SubiculumCode 9y ago
Yes. My workflow is to get the link from Firefox Send (which I love btw), email the link, open email on other device, click link. There are I suppose two use-cases. 1) To send to yourself. 2) To send to others. The second use-case, is fine under the current workflow, but the first use-case the workflow is annoying. If using Firefox Sync, perhaps the link could be synced over, maybe?

cdancette 9y ago

The private key is in the url, and mozilla says explicitly that they don't know this private key. They could shorten the url but then they would have the private key.

konart 9y ago

Well, if you use Firefox on your phone you can leave tab openned on your desktop and choose this tab on your phone. Or, if you are a Telegram user - you can send the link you yourself. You can also use you mail inbox.

dublinben 9y ago

You could have also just generated a QR code of the URL and scanned it with your phone, if you didn't want to send it electronically. I'm sure they expect users to just email these links to their recipient.

jwcacces 9y ago

Typer.in stores the link you give it, and returns a human readable lookup link. The whole point of Send is that the link includes the secret key to decrypt your file. Whoever you give that secret to, including Typer.in can get the file. The Send link must include the secret key, because no one else should get it, and that key must be of sufficient length to protect your file. Thus human-readable-izing it could do nothing to decrease its complexity and would just result in a huge string of words that were just as much as a pain to type in.

indiv0 9y ago
At least at the moment, downloading the file once removes it from Mozilla's servers. So in the event typer.in used the URL you provided to download the file, you would know as the file would no longer be accessible.

SubiculumCode 9y ago

Yes. My workflow is to get the link from Firefox Send (which I love btw), email the link, open email on other device, click link. There are I suppose two use-cases. 1) To send to yourself. 2) To send to others. The second use-case, is fine under the current workflow, but the first use-case the workflow is annoying. If using Firefox Sync, perhaps the link could be synced over, maybe?