Commit graph

285 commits

Author SHA1 Message Date
friendica
c6d07feff5 This is long overdue - use a symblic constant NULL_DATE instead of the easily mis-typed sequence '0000-00-00 00:00:00' 2014-09-08 20:35:15 -07:00
friendica
1102499c71 realm detection logic reversed 2014-09-04 16:09:52 -07:00
friendica
2d0ad0625a sql error in profile_activity 2014-08-31 16:24:05 -07:00
friendica
8a62b824f9 lots of little Diaspora issues 2014-08-28 21:49:13 -07:00
friendica
6a42d6fe3b works one way sort of - now to go the other way - which will require fixing a whole slew of FIXMEs 2014-08-26 18:58:48 -07:00
friendica
eb8f194419 sort out some anomalies 2014-08-25 21:42:46 -07:00
friendica
9196c9eef0 We really can't do this without a hubloc. I was hoping we could, but notifier is setup to take hublocs, not xchans. 2014-08-22 21:37:08 -07:00
friendica
69d3e5468d provide the site blacklist everywhere it is needed 2014-08-21 21:07:32 -07:00
friendica
4a76925787 some more work on realms 2014-08-17 19:06:56 -07:00
friendica
82eb265a20 add collections widget to connections page - and some more work on realms 2014-08-17 17:48:41 -07:00
friendica
20bdcb037f provide backend storage and declaration of directory realm 2014-08-16 16:10:35 -07:00
zottel
d57fe0765c don't block "public" messages with authenticated scope 2014-08-15 21:36:24 +02:00
friendica
802a5c2946 zot logging to figure out why we occasionally don't have an address on xchan_import - I suspect we don't have anything useful at all. 2014-08-12 20:46:33 -07:00
friendica
ad1472abf0 got the logic reversed on that one 2014-08-07 18:58:33 -07:00
friendica
f412f6a654 over-ride the private flag if we received a post that isn't completely public, but they didn't set the private flag. 2014-08-07 17:49:57 -07:00
friendica
2cff122d6f public scope delivery issues 2014-08-06 21:16:24 -07:00
friendica
8da548344b clone sync of "unfriend" actions 2014-08-05 17:47:17 -07:00
friendica
5a5190f2ff add an encoding type to formatted zot communication structures so that we can later add alternate encodings. 2014-07-24 15:55:01 -07:00
friendica
9e988afa1f ensure that we don't have permission settings issues due to version skew across sites. 2014-07-17 20:59:58 -07:00
friendica
437b0cb16e collection sync issue 2014-07-17 15:53:07 -07:00
friendica
feb23fc9bc collection sync 2014-07-16 21:18:28 -07:00
friendica
01491e7d61 limit fields to what we require 2014-07-14 21:52:20 -07:00
friendica
c398d556b3 index collection sync info by hash rather than id 2014-07-14 21:49:48 -07:00
friendica
1accf82bd1 clean up more code duplication 2014-07-14 21:21:24 -07:00
friendica
5ad76c4d0c the sending side of clone syncing of collection/privacy_group information. The receiving side is not yet implemented. 2014-07-14 02:37:41 -07:00
friendica
b2abc51929 much better fix to problem yesterday of updates with the wrong ud_addr 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.
2014-06-30 21:17:19 -07:00
friendica
f64f84b5e9 control chars crept in. 2014-06-30 03:52:20 -07:00
friendica
71e8643bf6 ensure we have a unique guid for each address if one is generated. 2014-06-30 03:38:12 -07:00
friendica
4e8d10e269 update the update records for all addresses attached to this channel, not just the primary. 2014-06-30 03:34:37 -07:00
Alexandre Hannud Abdo
b20887995a Implements a new permission level PERMS_PENDING
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.
2014-06-19 15:13:32 -03:00
friendica
5c8359f976 note work still remaining 2014-06-17 17:36:41 -07:00
friendica
dafd3a9e43 sync profiles to nomadic clones 2014-06-17 17:34:51 -07:00
friendica
78609e9363 send new connection notification even if auto-perms are set 2014-06-12 17:31:42 -07:00
friendica
4fa3b420ab duplicate birthday events showing up 2014-06-04 21:02:57 -07:00
friendica
2386bc4d00 bring back birthdays 2014-06-02 17:49:19 -07:00
friendica
9b5eabf108 Merge branch 'master' into newevent
Conflicts:
	include/zot.php
2014-05-29 16:14:10 -07:00
friendica
2a6d7b6a07 cleanup dead directory entries. This was a real b#tch, so keep your eye out 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. 2014-05-28 21:42:46 -07:00
friendica
2f5bd7e1b3 add activity_received hook 2014-05-13 20:58:55 -07:00
friendica
1a4c99ec02 fix events until the new event subscription mechanism goes in, as shared events have been broken 2014-05-07 22:28:19 -07:00
friendica
a00103b7df better event management 2014-05-07 22:23:43 -07:00
friendica
e22e94cd97 ok *now* shred works with alternate config files 2014-05-07 20:31:21 -07:00
friendica
769b0f6bc9 Often somebody will join the matrix with a dodgy cert and we'll sort that 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. 2014-04-13 18:30:06 -07:00
friendica
e64ec31a9d add the message-id to delivery reports. This _could_ allow an enterprising 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). 2014-04-10 22:17:35 -07:00
friendica
bf1f18e172 Include the entire original item when notifying other channels of deletions 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. 2014-04-10 16:14:19 -07:00
friendica
74029a9ee9 this should be better - "xchan deleted" state on remote sites only follows 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. 2014-04-07 16:10:43 -07:00
friendica
7e160a7b04 undo one of yesterday's changes - if a channel was deleted we want to mark 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. 2014-04-07 13:13:00 -07:00
friendica
10167fdf51 prevent follows of and notifications to deceased channels 2014-04-07 02:55:00 -07:00
friendica
1108eaaed0 source routing stuff 2014-03-29 21:53:50 -07:00
friendica
a6d8668a5f try and sort out the item delete mess 2014-03-27 20:28:48 -07:00
friendica
8594d069a1 new connection notification 2014-03-27 18:03:19 -07:00