forked from matrix/element-web
update README
Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
This commit is contained in:
parent
b7ed7a1dd7
commit
22d0d1029e
|
@ -52,15 +52,6 @@ We have put some coarse mitigations into place to try to protect against this
|
||||||
situation, but it's still not good practice to do it in the first place. See
|
situation, but it's still not good practice to do it in the first place. See
|
||||||
https://github.com/vector-im/riot-web/issues/1977 for more details.
|
https://github.com/vector-im/riot-web/issues/1977 for more details.
|
||||||
|
|
||||||
The same applies for end-to-end encrypted content, but since this is decrypted
|
|
||||||
on the client, Riot needs a way to supply the decrypted content from a separate
|
|
||||||
origin to the one Riot is hosted on. This currently done with a 'cross origin
|
|
||||||
renderer' which is a small piece of javascript hosted on a different domain.
|
|
||||||
To avoid all Riot installs needing one of these to be set up, riot.im hosts
|
|
||||||
one on usercontent.riot.im which is used by default.
|
|
||||||
https://github.com/vector-im/riot-web/issues/6173 tracks progress on replacing
|
|
||||||
this with something better.
|
|
||||||
|
|
||||||
Building From Source
|
Building From Source
|
||||||
====================
|
====================
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue