Don't base64 encode data
jimmywarting opened this issue · 3 comments
When seeding add an array of files instead
torrent.seed([file, file2, file3])
and instead of rendering a big image as base64 use createObjectURL
I think we wouldn't be able to store images on sessionStorage that way.
Think about reloading the browser, recovering and re-rendering all images and then create a torrent you can share.
Do you store base64 data in sessionStorage? Jesus... there are better storage out there such as indexedDB, localForage makes that easy for you to store blobs with a easy localstorage like with promises
sure you can use whatever data storage you like and base64 encode it, but base64 data takes up ~3x more data. I think at least the torrents should not be base64 encoded, what if you would like to download the torrent using webtorrent-desktop? you would get a weird base64 string back.