| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | When checking permissions ignore checking site "Block Public" settings in ↵ | zotlabs | 2018-07-30 | 1 | -3/+3 |
| | | | | | cases where site permissions aren't applicable | ||||
| * | issue syncing pageflags | zotlabs | 2018-07-04 | 1 | -8/+5 |
| | | |||||
| * | hubzilla issue #1169 | zotlabs | 2018-05-10 | 1 | -0/+5 |
| | | |||||
| * | update zot.php to fix php warning invalid argument supplied for foreach() | Mario Vavti | 2018-04-23 | 1 | -16/+18 |
| | | | | | - this is taken from pr #1085 which was against wrong branch | ||||
| * | Active channels information is a bit imprecise. Provide a higher accuracy ↵ | zotlabs | 2018-04-16 | 1 | -0/+11 |
| | | | | | method. This will require a transition period | ||||
| * | use profile_store_lowlevel() when importing profile structures to ensure all ↵ | zotlabs | 2018-04-05 | 1 | -4/+7 |
| | | | | | non-null fields are present | ||||
| * | slight change in mail privacy implementation. If you initiate a private mail ↵ | zotlabs | 2018-03-22 | 1 | -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 accepted | zotlabs | 2018-03-06 | 1 | -7/+10 |
| | | |||||
| * | Update composer autoload cache. | Klaus Weidenbach | 2018-03-01 | 1 | -4/+6 |
| | | |||||
| * | move dreport from zot to lib | zotlabs | 2018-02-21 | 1 | -4/+4 |
| | | |||||
| * | move Zotlabs\Zot\Verify to Zotlabs\Lib\Verify as part of the z6 re-org | zotlabs | 2018-02-21 | 1 | -2/+2 |
| | | |||||
| * | move the zot6 delivery to zot_fetch where it makes more sense. Exhaustively ↵ | zotlabs | 2018-02-20 | 1 | -1/+6 |
| | | | | | hand tested. | ||||
| * | zot6 delivery cleanup | zotlabs | 2018-02-20 | 1 | -50/+49 |
| | | |||||
| * | OAEP padding mismatch on some newer encryption methods | zotlabs | 2018-02-19 | 1 | -3/+0 |
| | | |||||
| * | more logging | zotlabs | 2018-02-19 | 1 | -0/+1 |
| | | |||||
| * | add logging | zotlabs | 2018-02-19 | 1 | -0/+2 |
| | | |||||
| * | cosmetic | zotlabs | 2018-02-08 | 1 | -2/+1 |
| | | |||||
| * | turn the logs down again | zotlabs | 2018-02-08 | 1 | -2/+1 |
| | | |||||
| * | zot6 testing | zotlabs | 2018-02-08 | 1 | -4/+8 |
| | | |||||
| * | z6 testing | zotlabs | 2018-02-08 | 1 | -0/+2 |
| | | |||||
| * | encrypt the httpsig for zot6 transport | zotlabs | 2018-02-07 | 1 | -2/+4 |
| | | |||||
| * | compatibility: fallback to legacy zot if OWA succeeds but no data['msg'] is ↵ | zotlabs | 2018-02-07 | 1 | -1/+1 |
| | | | | | present | ||||
| * | zot6 delivery work | zotlabs | 2018-02-07 | 1 | -3/+3 |
| | | |||||
| * | more zot6 delivery work | zotlabs | 2018-02-07 | 1 | -1/+85 |
| | | |||||
| * | initial z6 delivery | zotlabs | 2018-01-16 | 1 | -27/+23 |
| | | |||||
| * | z6 deliver | zotlabs | 2018-01-16 | 1 | -8/+71 |
| | | |||||
| * | this should finish up hubzilla issue #113 | zotlabs | 2017-12-31 | 1 | -0/+9 |
| | | |||||
| * | sql compliance issue | zotlabs | 2017-12-10 | 1 | -1/+1 |
| | | |||||
| * | default profile assign | zotlabs | 2017-11-24 | 1 | -0/+2 |
| | | |||||
| * | use logger | zotlabs | 2017-11-08 | 1 | -2/+1 |
| | | |||||
| * | :bulb: Improving Doxygen documentation. | Klaus Weidenbach | 2017-11-03 | 1 | -193/+292 |
| | | | | | | Fix some Doxygen parsing errors. Improve hooks documentation. | ||||
| * | put deferred queue logic every place we create a delivery process (except ↵ | zotlabs | 2017-11-02 | 1 | -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 set | zotlabs | 2017-11-01 | 1 | -0/+10 |
| | | |||||
| * | do not send message_list responses to dead sites (this delivery method ↵ | zotlabs | 2017-11-01 | 1 | -1/+1 |
| | | | | | bypassed the notifier) | ||||
| * | Maria's profile photo issue, please push to master. | zotlabs | 2017-11-01 | 1 | -0/+4 |
| | | |||||
| * | wrong key | zotlabs | 2017-10-22 | 1 | -4/+2 |
| | | |||||
| * | regression in zot site info after zot6 work | zotlabs | 2017-10-16 | 1 | -4/+6 |
| | | |||||
| * | typo | zotlabs | 2017-10-11 | 1 | -1/+2 |
| | | |||||
| * | for federated forums we need to keep track of what protocols are available ↵ | zotlabs | 2017-10-10 | 1 | -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 stuff | zotlabs | 2017-09-25 | 1 | -9/+5 |
| | | |||||
| * | zot_site_info - always sign the site block with the site private key | zotlabs | 2017-09-25 | 1 | -4/+4 |
| | | |||||
| * | tagging changes - provides ability to mention a forum by using !forumname as ↵ | zotlabs | 2017-09-24 | 1 | -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. | ||||
| * | encrypt delivery reports. This will cause a bit of consternation because ↵ | zotlabs | 2017-09-21 | 1 | -3/+20 |
| | | | | | this is not backward compatible and older sites will see some incorrect delivery reports from newer sites until the next upgrade; as their systems will not know how to read the ecnrypted final reports. | ||||
| * | make wiki page mimetype default to wiki mimetype (this was the original ↵ | zotlabs | 2017-09-13 | 1 | -1/+3 |
| | | | | | intent but the wrong variable was used) | ||||
| * | more zot6 | zotlabs | 2017-09-13 | 1 | -0/+1 |
| | | |||||
| * | Zot6: some things that need to be done ahead of time so we can turbocharge ↵ | zotlabs | 2017-09-13 | 1 | -11/+35 |
| | | | | | the delivery engine and split off site records from channel records. | ||||
| * | avoid a security patch and resultant compatibility issues; instead restrict ↵ | zotlabs | 2017-09-05 | 1 | -2/+1 |
| | | | | | the input characters we accept in token verification strings to hex digits. This will all be changing in the coming weeks/months anyway. | ||||
| * | validate the security context | zotlabs | 2017-09-03 | 1 | -0/+1 |
| | | |||||
| * | lognoise: don't log sync packet contents if there are no clones to receive them | zotlabs | 2017-08-23 | 1 | -2/+3 |
| | | |||||
| * | consolidate disable_discover_tab config if it was not yet set to either 1 or ↵ | git-marijus | 2017-08-06 | 1 | -1/+3 |
| | | | | | 0 in DB | ||||
 |
index : volse-hubzilla.git | |
| Volse Hubzilla -- soft fork of main Hubzilla core for Volse | Harald Eilertsen |
| aboutsummaryrefslogtreecommitdiffstats |