| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | zot logging to figure out why we occasionally don't have an address on ↵ | friendica | 2014-08-12 | 1 | -0/+4 |
| | | | | | xchan_import - I suspect we don't have anything useful at all. | ||||
| * | got the logic reversed on that one | friendica | 2014-08-07 | 1 | -1/+1 |
| | | |||||
| * | over-ride the private flag if we received a post that isn't completely ↵ | friendica | 2014-08-07 | 1 | -1/+13 |
| | | | | | public, but they didn't set the private flag. | ||||
| * | public scope delivery issues | friendica | 2014-08-06 | 1 | -3/+11 |
| | | |||||
| * | clone sync of "unfriend" actions | friendica | 2014-08-05 | 1 | -0/+15 |
| | | |||||
| * | add an encoding type to formatted zot communication structures so that we ↵ | friendica | 2014-07-24 | 1 | -5/+1 |
| | | | | | can later add alternate encodings. | ||||
| * | ensure that we don't have permission settings issues due to version skew ↵ | friendica | 2014-07-17 | 1 | -1/+1 |
| | | | | | across sites. | ||||
| * | collection sync issue | friendica | 2014-07-17 | 1 | -0/+25 |
| | | |||||
| * | collection sync | friendica | 2014-07-16 | 1 | -0/+114 |
| | | |||||
| * | limit fields to what we require | friendica | 2014-07-14 | 1 | -1/+1 |
| | | |||||
| * | index collection sync info by hash rather than id | friendica | 2014-07-14 | 1 | -1/+1 |
| | | |||||
| * | clean up more code duplication | friendica | 2014-07-14 | 1 | -6/+20 |
| | | |||||
| * | the sending side of clone syncing of collection/privacy_group information. ↵ | friendica | 2014-07-14 | 1 | -1/+15 |
| | | | | | The receiving side is not yet implemented. | ||||
| * | much better fix to problem yesterday of updates with the wrong ud_addr ↵ | friendica | 2014-06-30 | 1 | -23/+16 |
| | | | | | | | getting updated. Now we'll pass in the update table row to import_xchan so we know exactly which ud_addr applies. We still need ud_flags passed in separately. | ||||
| * | control chars crept in. | friendica | 2014-06-30 | 1 | -1/+1 |
| | | |||||
| * | ensure we have a unique guid for each address if one is generated. | friendica | 2014-06-30 | 1 | -1/+1 |
| | | |||||
| * | update the update records for all addresses attached to this channel, not ↵ | friendica | 2014-06-30 | 1 | -7/+19 |
| | | | | | just the primary. | ||||
| * | Implements a new permission level PERMS_PENDING | Alexandre Hannud Abdo | 2014-06-19 | 1 | -11/+15 |
| | | | | | | | | | | | | | | | | | With this a user can allow some action to any user which connects to them, even before they've connected back. Ref. https://mobiliza.org.br/display/478d9e71eaf55748dc646d3990651d6d34cfb7db5c38360538ec730ca3ccf908@zothub.com Also some code cleanup and an alternative logic for handling notifications of permission changes in zot.php. This assumes that private posts are still restricted to people in your addressbook. Regardless of your global permissions, a pending channel won't get private posts, even if the post only has a deny clause not matching the pending channel. | ||||
| * | note work still remaining | friendica | 2014-06-17 | 1 | -0/+1 |
| | | |||||
| * | sync profiles to nomadic clones | friendica | 2014-06-17 | 1 | -0/+39 |
| | | |||||
| * | send new connection notification even if auto-perms are set | friendica | 2014-06-12 | 1 | -1/+1 |
| | | |||||
| * | duplicate birthday events showing up | friendica | 2014-06-04 | 1 | -0/+7 |
| | | |||||
| * | bring back birthdays | friendica | 2014-06-02 | 1 | -2/+11 |
| | | |||||
| * | Merge branch 'master' into newevent | friendica | 2014-05-29 | 1 | -1/+21 |
| |\ | | | | | | | | | Conflicts: include/zot.php | ||||
| | * | cleanup dead directory entries. This was a real b#tch, so keep your eye out ↵ | friendica | 2014-05-28 | 1 | -0/+18 |
| | | | | | | | | | for issues - which you shouldn't see until next weekend when this is scheduled to run. We're only setting flags, so if anything goes wrong we should be able to recover without too much pain. | ||||
| | * | add activity_received hook | friendica | 2014-05-13 | 1 | -0/+3 |
| | | | |||||
| | * | fix events until the new event subscription mechanism goes in, as shared ↵ | friendica | 2014-05-07 | 1 | -1/+1 |
| | | | | | | | | | events have been broken | ||||
| * | | better event management | friendica | 2014-05-07 | 1 | -30/+0 |
| |/ | |||||
| * | ok *now* shred works with alternate config files | friendica | 2014-05-07 | 1 | -0/+4 |
| | | |||||
| * | Often somebody will join the matrix with a dodgy cert and we'll sort that ↵ | friendica | 2014-04-13 | 1 | -11/+25 |
| | | | | | out but their profile photo will remain rainbow man (or the site default). However the photo_date has been updated so we won't try again. This checkin looks for such a failure and leaves the photo_date alone if the photo import failed. | ||||
| * | add the message-id to delivery reports. This _could_ allow an enterprising ↵ | friendica | 2014-04-10 | 1 | -14/+14 |
| | | | | | developer to collect the delivery reports for a given post and store them in a DB table so that the sender could track and verify where a message had been sent on a web page and verify the success or failure of those attempts without requiring admin access. (To be fair this would also need an extra flag which hasn't yet been implemented to indicate that a channel created a second delivery chain of the message). | ||||
| * | Include the entire original item when notifying other channels of deletions ↵ | friendica | 2014-04-10 | 1 | -1/+1 |
| | | | | | as it contains important routing and scope information. Previously we were only sending a couple of critical fields like the message-id, flags, and creation date. The thinking was that it is deleted, let's not resend the deleted contents anywhere. But in order to route this through the same path the original post took we really need the entire original post with all of its baggage attached. | ||||
| * | this should be better - "xchan deleted" state on remote sites only follows ↵ | friendica | 2014-04-07 | 1 | -9/+6 |
| | | | | | the xchan_flags and not the channel_pageflags; XCHAN_FLAGS_DELETED should only be set if the channel is to be removed from the entire network. As mentioned in a previous commit, channel_pageflags could be set to PAGE_REMOVED but still leave living clones on other sites. | ||||
| * | undo one of yesterday's changes - if a channel was deleted we want to mark ↵ | friendica | 2014-04-07 | 1 | -6/+6 |
| | | | | | the hubloc deleted - but not the xchan. The channel might be alive at another hubloc. We should only mark the xchan deleted when removing a channel from the entire network - e.g. there are no hubs left to service it. | ||||
| * | prevent follows of and notifications to deceased channels | friendica | 2014-04-07 | 1 | -0/+9 |
| | | |||||
| * | source routing stuff | friendica | 2014-03-29 | 1 | -0/+3 |
| | | |||||
| * | try and sort out the item delete mess | friendica | 2014-03-27 | 1 | -3/+3 |
| | | |||||
| * | new connection notification | friendica | 2014-03-27 | 1 | -0/+9 |
| | | |||||
| * | more work on firehose | friendica | 2014-03-26 | 1 | -5/+7 |
| | | |||||
| * | this should improve queue performance dramatically. | friendica | 2014-03-24 | 1 | -1/+2 |
| | | |||||
| * | create_sys_channel during setup bypasses our check when creating the first ↵ | friendica | 2014-03-23 | 1 | -0/+2 |
| | | | | | account that there is a site keypair. Esnure that a site keypair is created before any sys channels are created. | ||||
| * | found what I believe is the root cause of issue #230, but don't yet have a ↵ | friendica | 2014-03-20 | 1 | -13/+21 |
| | | | | | workable solution. This one is hard. | ||||
| * | increase log info to track down source of ownership failures | friendica | 2014-03-20 | 1 | -1/+1 |
| | | |||||
| * | cleanup | friendica | 2014-03-18 | 1 | -12/+19 |
| | | |||||
| * | bring friends back | friendica | 2014-03-06 | 1 | -10/+10 |
| | | |||||
| * | change flags for one-way connections from hidden to unconnected so we can ↵ | friendica | 2014-03-04 | 1 | -5/+10 |
| | | | | | still use hidden for - well hiding connections | ||||
| * | directory sync issues | friendica | 2014-03-03 | 1 | -8/+8 |
| | | |||||
| * | some anomolies found when viewing connections in various cases. | friendica | 2014-03-02 | 1 | -0/+21 |
| | | |||||
| * | minor stuff, some doco, auth cleanup, and make "unknown" more translateable ↵ | friendica | 2014-02-22 | 1 | -4/+0 |
| | | | | | by context. | ||||
| * | fix login weirdness for accounts that need to be approved | friendica | 2014-02-20 | 1 | -5/+0 |
| | | |||||
 |
index : volse-hubzilla.git | |
| Volse Hubzilla -- soft fork of main Hubzilla core for Volse | Harald Eilertsen |
| aboutsummaryrefslogtreecommitdiffstats |