aboutsummaryrefslogtreecommitdiffstats
path: root/include/zot.php
Commit message (Collapse)AuthorAgeFilesLines
...
| * use common msg_drop functionMax Kostikov2018-09-151-25/+3
| |
| * formattingMax Kostikov2018-09-151-1/+1
| |
| * Save combined view on calling first message in threadMax Kostikov2018-09-151-0/+20
| |
* | do not sync the channel_moved fieldzotlabs2018-09-161-7/+7
|/
* Corrected resubmit of fixes to Authors unable to comment on posts they ↵M.Dent2018-09-041-7/+22
| | | | authored when owned by others.
* Revert "Fix: Authors unable to comment on posts they authored when under ↵Mario Vavti2018-09-031-15/+2
| | | | | | | | owned by others in certain circumstances." This reverts commit e2824f925964fbfe160255de6e733b4c2de3cecb. Reverting because it breaks forum mentions.
* Fix: Authors unable to comment on posts they authored when under owned by ↵M.Dent2018-09-011-2/+15
| | | | others in certain circumstances.
* Add dreport_process hookM.Dent2018-08-291-0/+1
|
* When checking permissions ignore checking site "Block Public" settings in ↵zotlabs2018-07-301-3/+3
| | | | cases where site permissions aren't applicable
* issue syncing pageflagszotlabs2018-07-041-8/+5
|
* hubzilla issue #1169zotlabs2018-05-101-0/+5
|
* update zot.php to fix php warning invalid argument supplied for foreach()Mario Vavti2018-04-231-16/+18
| | | | - this is taken from pr #1085 which was against wrong branch
* Active channels information is a bit imprecise. Provide a higher accuracy ↵zotlabs2018-04-161-0/+11
| | | | method. This will require a transition period
* use profile_store_lowlevel() when importing profile structures to ensure all ↵zotlabs2018-04-051-4/+7
| | | | non-null fields are present
* slight change in mail privacy implementation. If you initiate a private mail ↵zotlabs2018-03-221-4/+22
| | | | conversation and they respond, accept the reply. You can't hide behind your permissions or lack thereof. Often this will be accidental. If you truly want to block them from replying and your permissions otherwise would not allow them to reply, delete the conversation.
* don't add pending connections to the default privacy group until acceptedzotlabs2018-03-061-7/+10
|
* Update composer autoload cache.Klaus Weidenbach2018-03-011-4/+6
|
* move dreport from zot to libzotlabs2018-02-211-4/+4
|
* move Zotlabs\Zot\Verify to Zotlabs\Lib\Verify as part of the z6 re-orgzotlabs2018-02-211-2/+2
|
* move the zot6 delivery to zot_fetch where it makes more sense. Exhaustively ↵zotlabs2018-02-201-1/+6
| | | | hand tested.
* zot6 delivery cleanupzotlabs2018-02-201-50/+49
|
* OAEP padding mismatch on some newer encryption methodszotlabs2018-02-191-3/+0
|
* more loggingzotlabs2018-02-191-0/+1
|
* add loggingzotlabs2018-02-191-0/+2
|
* cosmeticzotlabs2018-02-081-2/+1
|
* turn the logs down againzotlabs2018-02-081-2/+1
|
* zot6 testingzotlabs2018-02-081-4/+8
|
* z6 testingzotlabs2018-02-081-0/+2
|
* encrypt the httpsig for zot6 transportzotlabs2018-02-071-2/+4
|
* compatibility: fallback to legacy zot if OWA succeeds but no data['msg'] is ↵zotlabs2018-02-071-1/+1
| | | | present
* zot6 delivery workzotlabs2018-02-071-3/+3
|
* more zot6 delivery workzotlabs2018-02-071-1/+85
|
* initial z6 deliveryzotlabs2018-01-161-27/+23
|
* z6 deliverzotlabs2018-01-161-8/+71
|
* this should finish up hubzilla issue #113zotlabs2017-12-311-0/+9
|
* sql compliance issuezotlabs2017-12-101-1/+1
|
* default profile assignzotlabs2017-11-241-0/+2
|
* use loggerzotlabs2017-11-081-2/+1
|
* :bulb: Improving Doxygen documentation.Klaus Weidenbach2017-11-031-193/+292
| | | | | Fix some Doxygen parsing errors. Improve hooks documentation.
* put deferred queue logic every place we create a delivery process (except ↵zotlabs2017-11-021-0/+17
| | | | for protocol 'friend requests' which aren't likely to swamp the delivery system). Remove it from the queue_delivery function which was too late to do anything.
* don't perform zot_refresh on dead sites unless $force is setzotlabs2017-11-011-0/+10
|
* do not send message_list responses to dead sites (this delivery method ↵zotlabs2017-11-011-1/+1
| | | | bypassed the notifier)
* Maria's profile photo issue, please push to master.zotlabs2017-11-011-0/+4
|
* wrong keyzotlabs2017-10-221-4/+2
|
* regression in zot site info after zot6 workzotlabs2017-10-161-4/+6
|
* typozotlabs2017-10-111-1/+2
|
* for federated forums we need to keep track of what protocols are available ↵zotlabs2017-10-101-0/+16
| | | | to red/hubzilla channels to determine which posts need to be mangled for transport to individual networks - based on what networks the author can communicate with. We probably need this for all xchans and hublocs but at some point it becomes increasingly difficult to scrape this information and map out a compatibility matrix. It's also doubtful anybody will use this system because we basically have to forge comments between network sites involving different protocols and this is going to look like crap to anybody that isn't on red/Hubzilla. Eventually they have to fix their protocols for this to work correctly, but nobody seems to believe me that their networks are basically anti-federation, so we need something like this to highlight their walled garden specifications and the resulting federation problems in a form they can't really argue with.
* more zot6 basic stuffzotlabs2017-09-251-9/+5
|
* zot_site_info - always sign the site block with the site private keyzotlabs2017-09-251-4/+4
|
* tagging changes - provides ability to mention a forum by using !forumname as ↵zotlabs2017-09-241-1/+1
| | | | well as the traditional red style (@forumname+). This should probably not be advertised on a wide scale until after a critical mass of sites have updated to a version containing these changes. This adds yet another option type to the ACL module which probably needs refactoring soon since it is turning into option type spaghetti.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-28 22:51:44 +0000