 |
The Hubzilla
|
|
The Hubzilla
|
Public Member Functions | |
| post () | |
| get () | |
| item_check_service_class ($channel_id, $iswebpage) | |
 Public Member Functions inherited from Zotlabs\Web\Controller | |
| init () | |
| post () | |
| get () | |
This is the POST destination for most all locally posted text stuff. This function handles status, wall-to-wall status, local comments, and remote coments that are posted on this site (as opposed to being delivered in a feed). Also processed here are posts and comments coming through the statusnet/twitter API. All of these become an "item" which is our basic unit of information. Posts that originate externally or do not fall into the above posting categories go through item_store() instead of this function.
| Zotlabs\Module\Item::get | ( | ) |
| Zotlabs\Module\Item::item_check_service_class | ( | $channel_id, | |
| $iswebpage | |||
| ) |
Referenced by Zotlabs\Module\Item\post().
| Zotlabs\Module\Item::post | ( | ) |
Is this a reply to something?
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.
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.
