From 090ce0c5bfad5f5242bc80d8aeb80a5b9735aed7 Mon Sep 17 00:00:00 2001 From: Golda Velez Date: Thu, 24 Sep 2020 19:31:15 +0000 Subject: [PATCH] Update design/preexisting/protocols/peergos.md --- protocols/peergos.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/protocols/peergos.md b/protocols/peergos.md index 4d6e49a..e6d9579 100644 --- a/protocols/peergos.md +++ b/protocols/peergos.md @@ -50,10 +50,11 @@ Peergos was developed by the [core team](https://peergos.org/about) on a [self-f Peergos is a private and access controlled layer on top of IPFS which can be used to build applications. Other than the Peergos reference implementation client which allows users to store and share private files, there are a few demo [applications](https://peergos.org/posts/applications), including a read-only viewer for PDF files, and an editor for text or code. -The goal of allowing people to deploy apps on Peergos that are viewable from the browser is currently limited by [sandboxing constraints](https://kevodwyer.github.io/sandbox/) within browsers. +The goal of allowing people to deploy apps on Peergos that are viewable from the browser is currently limited by [sandboxing constraints](https://kevodwyer.github.io/sandbox/) within browsers. [COOP/COEP](https://web.dev/why-coop-coep/) increase the security of in-browser applications. ### Links - [Peergos](https://peergos.org/) - [Peergos book](https://book.peergos.org) - [Source code](https://github.com/peergos/peergos) +- [COOP and COEP Explainer](https://docs.google.com/document/d/1zDlfvfTJ_9e8Jdc8ehuV4zMEu9ySMCiTGMS9y0GU92k/edit)