rugk

> have to handle the start of the execution of our logic differently, as we have to ensure all files got loaded. Well… this is exactly a problem that ES6...

As for the simplest change: Could not you re-create the old pastes? I.e. copy the text and paste it into a new paste?

Marking this as blocked now, because we can likely not fix it easily without shipping yet another fallback library… BTW, switching to GCM all the time back seemed to have...

It is likely not writable, that's why this error happens. However, the error can be prevented, and as you see there is already a PR for it.

No `data` is writable, but not the parent directory (so the webroot). And this is completely fine as PrivateBin usually does not need to write there…

Thanks for your suggestion. You can send us a [PR](https://help.github.com/articles/creating-a-pull-request/) for that. Just edit PrivateBin's [bootstrap CSS file](https://github.com/PrivateBin/PrivateBin/blob/master/css/bootstrap/privatebin.css#L77).

You do not need to get deep into that at all, and you can easily edit the file online at GitHub e.g. So it is really easy and fast to...

No, you did not do anything wrong with the PR. It works all right. We are just reviewing it, and may request some changes and so on. You can just...

Reproduced this. Okay so reopning this, because I do see the real issue here is not that Edge is not supported, but that our error handling is not smart enough...

### Likely problem Legacy Edge implements some Web Crypto APIs, just [misses PBKDF2 support](https://github.com/PrivateBin/PrivateBin/issues/468#issuecomment-516299300). ## Technical solution * detect whether we have PBKDF2 support? * better: detect whether the browser...