* 2. We may be the target or other side of the conversation to scenario 1, and will
* interact with that process on our own user's behalf.
*
- * @see PDF with dfrn specs: https://github.com/friendica/friendica/blob/master/spec/dfrn2.pdf
+ * @see PDF with dfrn specs: https://github.com/friendica/friendica/blob/stable/spec/dfrn2.pdf
* You also find a graphic which describes the confirmation process at
- * https://github.com/friendica/friendica/blob/master/spec/dfrn2_contact_confirmation.png
+ * https://github.com/friendica/friendica/blob/stable/spec/dfrn2_contact_confirmation.png
*/
use Friendica\App;
$params['page'] = 2;
}
- Logger::log('Confirm: posting data to ' . $dfrn_confirm . ': ' . print_r($params, true), Logger::DATA);
+ Logger::debug('Confirm: posting data', ['confirm' => $dfrn_confirm, 'parameter' => $params]);
/*
*
$forum = (($page == 1) ? 1 : 0);
$prv = (($page == 2) ? 1 : 0);
- Logger::log('dfrn_confirm: requestee contacted: ' . $node);
+ Logger::notice('requestee contacted', ['node' => $node]);
- Logger::log('dfrn_confirm: request: POST=' . print_r($_POST, true), Logger::DATA);
+ Logger::debug('request', ['POST' => $_POST]);
// If $aes_key is set, both of these items require unpacking from the hex transport encoding.