4 ms·
Maybe I'm missing something, but how can this be end-to-end encrypted when the password is optional, and there is no fragment in the shared URL? Update: Turns
by lxgr 6y ago
Maybe I'm missing something, but how can this be end-to-end encrypted when the password is optional, and there is no fragment in the shared URL?
Update: Turns out fragments are used for key sharing after all. This (in my opinion crucial to anyone aware about the difference between query parameters and fragments) bit is left out from the promotional video.
- nelsonenzo 6y agoWhat's a url fragment? How is it more secure?
- rakoo 6y agoURL fragments are the part after the hash symbol (#) like this: https://en.wikipedia.org/wiki/Donald_Trump#Books https://en.wikipedia.org/wiki/Donald_Trump#Books the original use case (still used today) is to be able to jump to the first DOM element with such an ID; typically title elements, such as the "Books" above. It is only used by the client, so is never sent to the server. Now with web applications, thanks to javascript, you can retrieve and use it. So now instead of using it as a locator inside of a page filled with content, you can use it as a string that you know isn't shared with the server: it's perfect for a secret key. You can send the receiver a link with that key, they will put it in their browser, receive the javascript from the server and use that javascript to decode content thanks to the key.
- pnt12 6y agoAs I understand it, a fragment is just read by the browser, a parameter is sent to the server. A common fragment is when you click some section of a website oagr and it changes the link to include #section-x, and if you bookmark it you browser will scroll to the right place automatically.