aboutsummaryrefslogtreecommitdiffstats
path: root/doc/channels.bb
diff options
context:
space:
mode:
authorfriendica <info@friendica.com>2014-09-02 21:11:09 -0700
committerfriendica <info@friendica.com>2014-09-02 21:11:09 -0700
commit7001f41d3d021f1e7fb87cc3c628739bc5362d2a (patch)
treeadbf388ff45ea8702174f9ae14b6e046e50a22ac /doc/channels.bb
parentc7decf70a2d11dc2e208a508a0e7503139ab18c9 (diff)
downloadvolse-hubzilla-7001f41d3d021f1e7fb87cc3c628739bc5362d2a.tar.gz
volse-hubzilla-7001f41d3d021f1e7fb87cc3c628739bc5362d2a.tar.bz2
volse-hubzilla-7001f41d3d021f1e7fb87cc3c628739bc5362d2a.zip
provide a config option to prevent wall uploads (photos and files) from being set to the same ACL as the containing post, and instead are uploaded with public visibility (no ACL). This is to prevent folks on other networks from seeing prohibited signs for things uploaded into a private conversation. It is primarily useful when posting to collections that have mixed folks from red and other networks and an otherwise public (typical) profile. Consequently, these uploads will match your chosen default visibility for photos and storage and not that of the containing conversation item (and is only useful if the default visibility is public). This choice must be explained adequately because it represents a complex series of tradeoffs and side effects. It will reduce complaints from other networks about blocked content, but essentially forces you to use another method (dav or the photos page) if you wish to upload protected files/media.
Diffstat (limited to 'doc/channels.bb')
0 files changed, 0 insertions, 0 deletions