aboutsummaryrefslogtreecommitdiffstats
path: root/include/zot.php
Commit message (Collapse)AuthorAgeFilesLines
...
* need to figure out what's causing thisfriendica2013-09-121-0/+6
|
* so public_recips and allowed_public_recips is working so much better than ↵friendica2013-09-121-4/+12
| | | | before, but was still not quite right. We seem to be getting all the right results for top-level posts now, but comments aren't getting through on channels for which we've allowed them to send us their stream, but not comment on our posts. The reason is we were seeing if they could comment - and we only need to do that if we own the post. If they own the post, we only need to check if they can send us their stream.
* Merge pull request #129 from MicMee/masterfriendica2013-09-121-1/+2
|\ | | | | to flag failed auth attempts in db table hubloc as hubloc_receive_error
| * delete logger line; was the wrong place.Michael Meer2013-09-111-1/+0
| |
| * flag failed auth attempts in DB table hublocMichael Meer2013-09-111-1/+3
| |
* | assuming this doesn't blow up the internet like the last fix - this is a ↵friendica2013-09-111-1/+1
|/ | | | very old bug that's been reported time and time again and nobody every bothered to debug or even report it somewhere where we could monitor it. It's buried somewhere in my stream, but basically is "things don't work right if you've got 'everybody in my address book' permissions" on "can send me their channel stream and posts". I think this is Michelle's problem and anybody else who has en empty matrix after making lots of connections.
* well that really stuffed things up...friendica2013-09-101-2/+2
|
* provide detailed error to remote site for the myriad of things that can go ↵friendica2013-09-101-4/+8
| | | | wrong inside item_store(), !! this changes the return of item_store !!
* just a typoMichael Meer2013-09-091-1/+1
|
* some alteration to the way directory sync was originally supposed to work. ↵friendica2013-09-091-25/+14
| | | | I'm making this up as I go and not exactly certain where to go next but it makes more sense now and I think the basic idea will actually work. I'll just have to keep making it up until it does work.
* make sure new contacts who are not yet in the address book are sync'd across ↵friendica2013-09-081-0/+14
| | | | clone instances
* public site list (will take a few days to populate, assuming folks have ↵friendica2013-09-051-3/+16
| | | | updated their site access policy which old sites do not have)
* update hubloc_timestampsfriendica2013-08-271-5/+14
|
* clone sync was trying to update xchan info in the abook loop.friendica2013-08-261-1/+1
|
* more cleanup from the mess yesterday - you might have a look for xchan_addr ↵friendica2013-08-261-0/+3
| | | | and hubloc_addr with slashes in them and fix them - especially getting rid of ip addresses and the /channel/xyz in the addr fields
* try to fix bad addresses that got into the networkfriendica2013-08-251-0/+3
|
* Try to ensure full paths don't leak into xchan_addr and hubloc_addrfriendica2013-08-251-1/+1
|
* possible fix for mention tags not posting to mentioned forum (when send ↵friendica2013-08-221-3/+25
| | | | stream permission is blocked)
* add detailed logging to public recips - find out why some public recipients ↵friendica2013-08-221-0/+3
| | | | are getting bypassed (David Benfells' problem with tagging groups, etc.)
* implement premium channel discoveryfriendica2013-08-211-5/+14
|
* don't import any hubloc that doesn't have a sitekey. Eventually we should ↵friendica2013-08-111-2/+7
| | | | also verify that it is a valid key, as we've already seen one case where one character got mangled and messed up communication.
* convert all stored json calls to json_decode_plus()friendica2013-08-061-2/+2
|
* yhis should fix the privacy leak - as well as non-private replies to private ↵friendica2013-08-011-0/+1
| | | | posts
* fix some privacy leakage in logsfriendica2013-07-311-14/+0
|
* fix bug #84, make imported messages from your clones show up on your wallfriendica2013-07-291-0/+12
|
* encrypt private messages on disk - there are still a couple of places where ↵friendica2013-07-281-6/+17
| | | | the text is leaked in the logs during processing.
* add gz to access denied files to block rotated logs from public accessfriendica2013-07-261-1/+2
|
* the rest of the heavy lifting on clone sync - now we're down to some log ↵friendica2013-07-251-1/+82
| | | | messages and a whole lot of testing
* build_sync_packet was looking at stale channel info - load it fresh from the DB.friendica2013-07-251-1/+8
|
* log the sync packets locally at LOGGER_DATA levelfriendica2013-07-251-0/+2
|
* more work on clone syncfriendica2013-07-251-0/+101
|
* fix media uploads in api (specifically friendica for android)friendica2013-07-251-34/+0
|
* start saving site infofriendica2013-07-231-4/+88
|
* make zot_finger more bulletprooffriendica2013-07-211-0/+5
|
* improve logging zot_fingerfriendica2013-07-211-1/+1
|
* improvements in delivery loggingfriendica2013-07-211-8/+8
|
* validate input to import_xchan(), as we don't consistently check it prior to ↵friendica2013-07-181-0/+7
| | | | entering this function
* add channel_name to delivery logs because it is a bit more useful than an ↵friendica2013-07-151-10/+10
| | | | xchan_hash
* more diagnosticsfriendica2013-07-151-2/+2
|
* more error checkingfriendica2013-07-141-3/+7
|
* more logging on hubloc import - figure out why it did not get stored.friendica2013-07-141-1/+2
|
* more work on bug #59 - hope this doesn't hork everything. Also some tweaking ↵friendica2013-07-081-1/+1
| | | | of the theme for the new radius control, which produced some surprising results when expert mode was toggled.
* really, truly fix the age missing in directory bugfriendica2013-07-021-1/+0
|
* missing commafriendica2013-07-021-1/+1
|
* age was not syncing to the directoryfriendica2013-07-021-1/+4
|
* issue #65friendica2013-07-011-0/+66
|
* add age to directory profile - requires updating on each birthday and that ↵friendica2013-06-301-0/+1
| | | | part is still missing
* more work on channel syncfriendica2013-06-261-0/+8
|
* make manual image scaling work - even if auto scaling kicks in.friendica2013-06-231-1/+1
|
* hopefully this won't screw up everything - if it does, revert. Otherwise ↵friendica2013-06-161-1/+3
| | | | this should work at delivery time to check tag deliveries and bounce the message before it's stored if the channel doesn't allow you to post and you aren't allowed to tag deliver either. Previously this was handled after the post was already stored so you needed posting permission as well as tag deliver permission to get past the checks.