Hi all,
I work on a project called Peergos.
Can think of it as a global filesystem where people have total control over their data.
Has some nice properties like P2P connectivity, E2E encryption, fine grained access control strong meta-data protection (And self-hostable).
Project
Recently I added the ability to build Apps. I thought TiddlyWiki would be a good App to install.
It took all of about 10 code line changes to get it working in development. I made slight edits to put.js and http.js to handle sending binary data.
But I did need to amend the CSP of the Peergos Appās sandbox to allow āunsafe-evalā. Iām not keen on making that change.
A question for the Developers:
Has this CSP issue come up before. Has there been any discussion on a workaround or proposed long-term solution?
Perhaps integrate a WASM compiled JS engine (like Quick.js) in combination with using āwasm-unsafe-evalā?