aboutsummaryrefslogtreecommitdiffstats
path: root/doc/html/item_8php.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc/html/item_8php.html')
-rw-r--r--doc/html/item_8php.html1
1 files changed, 1 insertions, 0 deletions
diff --git a/doc/html/item_8php.html b/doc/html/item_8php.html
index 34bd42f97..31e88a3fd 100644
--- a/doc/html/item_8php.html
+++ b/doc/html/item_8php.html
@@ -367,6 +367,7 @@ Functions</h2></td></tr>
<p>Is this a reply to something?</p>
<p>fix naked links by passing through a callback to see if this is a red site (already known to us) which will get a zrl, otherwise link with url</p>
<p>When a photo was uploaded into the message using the (profile wall) ajax uploader, The permissions are initially set to disallow anybody but the owner from seeing it. This is because the permissions may not yet have been set for the post. If it's private, the photo permissions should be set appropriately. But we didn't know the final permissions on the post until now. So now we'll look for links of uploaded photos and attachments that are in the post and set them to the same permissions as the post itself.</p>
+<p>If the post was end-to-end encrypted we can't find images and attachments in the body, use our media_str input instead which only contains these elements - but only do this when encrypted content exists because the photo/attachment may have been removed from the post and we should keep it private. If it's encrypted we have no way of knowing so we'll set the permissions regardless and realise that the media may not be referenced in the post.</p>
<p>Fold multi-line [code] sequences</p>
<p>Look for any tags and linkify them</p>