2010-09-16 04:18:01 +09:00
|
|
|
<?php
|
2020-09-15 22:59:27 +09:00
|
|
|
// This file is part of GNU social - https://www.gnu.org/software/social
|
|
|
|
//
|
|
|
|
// GNU social is free software: you can redistribute it and/or modify
|
|
|
|
// it under the terms of the GNU Affero General Public License as published by
|
|
|
|
// the Free Software Foundation, either version 3 of the License, or
|
|
|
|
// (at your option) any later version.
|
|
|
|
//
|
|
|
|
// GNU social is distributed in the hope that it will be useful,
|
|
|
|
// but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
// GNU Affero General Public License for more details.
|
|
|
|
//
|
|
|
|
// You should have received a copy of the GNU Affero General Public License
|
|
|
|
// along with GNU social. If not, see <http://www.gnu.org/licenses/>.
|
|
|
|
|
2010-09-16 04:18:01 +09:00
|
|
|
/*
|
2020-09-15 22:59:27 +09:00
|
|
|
* Class for activity streams
|
2010-09-16 04:18:01 +09:00
|
|
|
*
|
2020-09-15 22:59:27 +09:00
|
|
|
* @package GNUsocial
|
|
|
|
* @copyright 2010 StatusNet, Inc.
|
|
|
|
* @license https://www.gnu.org/licenses/agpl.html GNU AGPL v3 or later
|
2010-09-16 04:18:01 +09:00
|
|
|
*/
|
|
|
|
|
2020-09-15 22:59:27 +09:00
|
|
|
defined('GNUSOCIAL') || die();
|
|
|
|
|
2010-09-16 04:18:01 +09:00
|
|
|
/**
|
|
|
|
* Class for activity streams
|
|
|
|
*
|
2014-06-27 20:58:35 +09:00
|
|
|
* Includes objects like notices, subscriptions and from plugins.
|
2010-09-16 04:18:01 +09:00
|
|
|
*
|
|
|
|
* We extend atomusernoticefeed since it does some nice setup for us.
|
|
|
|
*
|
2020-09-15 22:59:27 +09:00
|
|
|
* @package GNUsocial
|
|
|
|
* @copyright 2010 StatusNet, Inc.
|
|
|
|
* @license https://www.gnu.org/licenses/agpl.html GNU AGPL v3 or later
|
2010-09-16 04:18:01 +09:00
|
|
|
*/
|
|
|
|
class UserActivityStream extends AtomUserNoticeFeed
|
|
|
|
{
|
2011-01-03 08:22:12 +09:00
|
|
|
public $activities = array();
|
2014-06-27 20:58:35 +09:00
|
|
|
public $after = null;
|
2011-01-03 08:22:12 +09:00
|
|
|
|
Scalability work on user backup stream generation.
UserActivityStream -- used to create a full activity stream including subscriptions, favorites, notices, etc -- normally buffers everything into memory at once. This is infeasible for accounts with long histories of serious usage; it can take tens of seconds just to pull all records from the database, and working with them all in memory is very likely to hit resource limits.
This commit adds an alternate mode for this class which avoids pulling notices until during the actual output. Instead of pre-sorting and buffering all the notices, empty spaces between the other activities are filled in with notices as we're making output. This means more smaller queries spread out during operations, and less stuff kept in memory.
Callers (backupaccount action, and backupuser.php) which can stream their output pass an $outputMode param of UserActivityStream::OUTPUT_RAW, and during getString() it'll send straight to output as well as slurping the notices in this extra funky fashion.
Other callers will let it default to the OUTPUT_STRING mode, which keeps the previous behavior.
There should be a better way to do this, swapping out the stringer output for raw output more consitently.
2011-02-26 04:04:57 +09:00
|
|
|
const OUTPUT_STRING = 1;
|
|
|
|
const OUTPUT_RAW = 2;
|
|
|
|
public $outputMode = self::OUTPUT_STRING;
|
|
|
|
|
|
|
|
/**
|
|
|
|
*
|
|
|
|
* @param User $user
|
2020-09-15 22:59:27 +09:00
|
|
|
* @param bool $indent
|
|
|
|
* @param bool $outputMode: UserActivityStream::OUTPUT_STRING to return a string,
|
|
|
|
* or UserActivityStream::OUTPUT_RAW to go to raw output.
|
|
|
|
* Raw output mode will attempt to stream, keeping less
|
|
|
|
* data in memory but will leave $this->activities incomplete.
|
Scalability work on user backup stream generation.
UserActivityStream -- used to create a full activity stream including subscriptions, favorites, notices, etc -- normally buffers everything into memory at once. This is infeasible for accounts with long histories of serious usage; it can take tens of seconds just to pull all records from the database, and working with them all in memory is very likely to hit resource limits.
This commit adds an alternate mode for this class which avoids pulling notices until during the actual output. Instead of pre-sorting and buffering all the notices, empty spaces between the other activities are filled in with notices as we're making output. This means more smaller queries spread out during operations, and less stuff kept in memory.
Callers (backupaccount action, and backupuser.php) which can stream their output pass an $outputMode param of UserActivityStream::OUTPUT_RAW, and during getString() it'll send straight to output as well as slurping the notices in this extra funky fashion.
Other callers will let it default to the OUTPUT_STRING mode, which keeps the previous behavior.
There should be a better way to do this, swapping out the stringer output for raw output more consitently.
2011-02-26 04:04:57 +09:00
|
|
|
*/
|
2020-09-15 22:59:27 +09:00
|
|
|
public function __construct(
|
|
|
|
$user,
|
|
|
|
$indent = true,
|
|
|
|
$outputMode = UserActivityStream::OUTPUT_STRING,
|
|
|
|
$after = null
|
|
|
|
) {
|
2010-09-16 04:18:01 +09:00
|
|
|
parent::__construct($user, null, $indent);
|
|
|
|
|
Scalability work on user backup stream generation.
UserActivityStream -- used to create a full activity stream including subscriptions, favorites, notices, etc -- normally buffers everything into memory at once. This is infeasible for accounts with long histories of serious usage; it can take tens of seconds just to pull all records from the database, and working with them all in memory is very likely to hit resource limits.
This commit adds an alternate mode for this class which avoids pulling notices until during the actual output. Instead of pre-sorting and buffering all the notices, empty spaces between the other activities are filled in with notices as we're making output. This means more smaller queries spread out during operations, and less stuff kept in memory.
Callers (backupaccount action, and backupuser.php) which can stream their output pass an $outputMode param of UserActivityStream::OUTPUT_RAW, and during getString() it'll send straight to output as well as slurping the notices in this extra funky fashion.
Other callers will let it default to the OUTPUT_STRING mode, which keeps the previous behavior.
There should be a better way to do this, swapping out the stringer output for raw output more consitently.
2011-02-26 04:04:57 +09:00
|
|
|
$this->outputMode = $outputMode;
|
2013-06-29 20:49:43 +09:00
|
|
|
|
Scalability work on user backup stream generation.
UserActivityStream -- used to create a full activity stream including subscriptions, favorites, notices, etc -- normally buffers everything into memory at once. This is infeasible for accounts with long histories of serious usage; it can take tens of seconds just to pull all records from the database, and working with them all in memory is very likely to hit resource limits.
This commit adds an alternate mode for this class which avoids pulling notices until during the actual output. Instead of pre-sorting and buffering all the notices, empty spaces between the other activities are filled in with notices as we're making output. This means more smaller queries spread out during operations, and less stuff kept in memory.
Callers (backupaccount action, and backupuser.php) which can stream their output pass an $outputMode param of UserActivityStream::OUTPUT_RAW, and during getString() it'll send straight to output as well as slurping the notices in this extra funky fashion.
Other callers will let it default to the OUTPUT_STRING mode, which keeps the previous behavior.
There should be a better way to do this, swapping out the stringer output for raw output more consitently.
2011-02-26 04:04:57 +09:00
|
|
|
if ($this->outputMode == self::OUTPUT_STRING) {
|
|
|
|
// String buffering? Grab all the notices now.
|
|
|
|
$notices = $this->getNotices();
|
|
|
|
} elseif ($this->outputMode == self::OUTPUT_RAW) {
|
|
|
|
// Raw output... need to restructure from the stringer init.
|
|
|
|
$this->xw = new XMLWriter();
|
|
|
|
$this->xw->openURI('php://output');
|
2020-09-15 22:59:27 +09:00
|
|
|
if (is_null($indent)) {
|
Scalability work on user backup stream generation.
UserActivityStream -- used to create a full activity stream including subscriptions, favorites, notices, etc -- normally buffers everything into memory at once. This is infeasible for accounts with long histories of serious usage; it can take tens of seconds just to pull all records from the database, and working with them all in memory is very likely to hit resource limits.
This commit adds an alternate mode for this class which avoids pulling notices until during the actual output. Instead of pre-sorting and buffering all the notices, empty spaces between the other activities are filled in with notices as we're making output. This means more smaller queries spread out during operations, and less stuff kept in memory.
Callers (backupaccount action, and backupuser.php) which can stream their output pass an $outputMode param of UserActivityStream::OUTPUT_RAW, and during getString() it'll send straight to output as well as slurping the notices in this extra funky fashion.
Other callers will let it default to the OUTPUT_STRING mode, which keeps the previous behavior.
There should be a better way to do this, swapping out the stringer output for raw output more consitently.
2011-02-26 04:04:57 +09:00
|
|
|
$indent = common_config('site', 'indent');
|
|
|
|
}
|
|
|
|
$this->xw->setIndent($indent);
|
|
|
|
|
|
|
|
// We'll fetch notices later.
|
|
|
|
$notices = array();
|
|
|
|
} else {
|
|
|
|
throw new Exception('Invalid outputMode provided to ' . __METHOD__);
|
|
|
|
}
|
|
|
|
|
2013-06-29 20:49:43 +09:00
|
|
|
$this->after = $after;
|
|
|
|
|
Scalability work on user backup stream generation.
UserActivityStream -- used to create a full activity stream including subscriptions, favorites, notices, etc -- normally buffers everything into memory at once. This is infeasible for accounts with long histories of serious usage; it can take tens of seconds just to pull all records from the database, and working with them all in memory is very likely to hit resource limits.
This commit adds an alternate mode for this class which avoids pulling notices until during the actual output. Instead of pre-sorting and buffering all the notices, empty spaces between the other activities are filled in with notices as we're making output. This means more smaller queries spread out during operations, and less stuff kept in memory.
Callers (backupaccount action, and backupuser.php) which can stream their output pass an $outputMode param of UserActivityStream::OUTPUT_RAW, and during getString() it'll send straight to output as well as slurping the notices in this extra funky fashion.
Other callers will let it default to the OUTPUT_STRING mode, which keeps the previous behavior.
There should be a better way to do this, swapping out the stringer output for raw output more consitently.
2011-02-26 04:04:57 +09:00
|
|
|
// Assume that everything but notices is feasible
|
|
|
|
// to pull at once and work with in memory...
|
2013-05-24 04:02:30 +09:00
|
|
|
|
2010-09-16 04:18:01 +09:00
|
|
|
$subscriptions = $this->getSubscriptions();
|
|
|
|
$subscribers = $this->getSubscribers();
|
|
|
|
$groups = $this->getGroups();
|
|
|
|
|
2014-11-08 00:08:16 +09:00
|
|
|
$objs = array_merge($subscriptions, $subscribers, $groups, $notices);
|
2014-06-27 20:58:35 +09:00
|
|
|
|
|
|
|
Event::handle('AppendUserActivityStreamObjects', array($this, &$objs));
|
2010-09-16 04:18:01 +09:00
|
|
|
|
2013-05-25 02:50:24 +09:00
|
|
|
$subscriptions = null;
|
|
|
|
$subscribers = null;
|
|
|
|
$groups = null;
|
|
|
|
|
|
|
|
unset($subscriptions);
|
|
|
|
unset($subscribers);
|
|
|
|
unset($groups);
|
|
|
|
|
2010-09-16 04:18:01 +09:00
|
|
|
// Sort by create date
|
|
|
|
|
|
|
|
usort($objs, 'UserActivityStream::compareObject');
|
|
|
|
|
Scalability work on user backup stream generation.
UserActivityStream -- used to create a full activity stream including subscriptions, favorites, notices, etc -- normally buffers everything into memory at once. This is infeasible for accounts with long histories of serious usage; it can take tens of seconds just to pull all records from the database, and working with them all in memory is very likely to hit resource limits.
This commit adds an alternate mode for this class which avoids pulling notices until during the actual output. Instead of pre-sorting and buffering all the notices, empty spaces between the other activities are filled in with notices as we're making output. This means more smaller queries spread out during operations, and less stuff kept in memory.
Callers (backupaccount action, and backupuser.php) which can stream their output pass an $outputMode param of UserActivityStream::OUTPUT_RAW, and during getString() it'll send straight to output as well as slurping the notices in this extra funky fashion.
Other callers will let it default to the OUTPUT_STRING mode, which keeps the previous behavior.
There should be a better way to do this, swapping out the stringer output for raw output more consitently.
2011-02-26 04:04:57 +09:00
|
|
|
// We'll keep these around for later, and interleave them into
|
|
|
|
// the output stream with the user's notices.
|
2013-05-25 02:50:24 +09:00
|
|
|
|
|
|
|
$this->objs = $objs;
|
2011-01-03 08:22:12 +09:00
|
|
|
}
|
2011-01-29 08:33:13 +09:00
|
|
|
|
Scalability work on user backup stream generation.
UserActivityStream -- used to create a full activity stream including subscriptions, favorites, notices, etc -- normally buffers everything into memory at once. This is infeasible for accounts with long histories of serious usage; it can take tens of seconds just to pull all records from the database, and working with them all in memory is very likely to hit resource limits.
This commit adds an alternate mode for this class which avoids pulling notices until during the actual output. Instead of pre-sorting and buffering all the notices, empty spaces between the other activities are filled in with notices as we're making output. This means more smaller queries spread out during operations, and less stuff kept in memory.
Callers (backupaccount action, and backupuser.php) which can stream their output pass an $outputMode param of UserActivityStream::OUTPUT_RAW, and during getString() it'll send straight to output as well as slurping the notices in this extra funky fashion.
Other callers will let it default to the OUTPUT_STRING mode, which keeps the previous behavior.
There should be a better way to do this, swapping out the stringer output for raw output more consitently.
2011-02-26 04:04:57 +09:00
|
|
|
/**
|
2014-06-27 20:58:35 +09:00
|
|
|
* Interleave the pre-sorted objects with the user's
|
Scalability work on user backup stream generation.
UserActivityStream -- used to create a full activity stream including subscriptions, favorites, notices, etc -- normally buffers everything into memory at once. This is infeasible for accounts with long histories of serious usage; it can take tens of seconds just to pull all records from the database, and working with them all in memory is very likely to hit resource limits.
This commit adds an alternate mode for this class which avoids pulling notices until during the actual output. Instead of pre-sorting and buffering all the notices, empty spaces between the other activities are filled in with notices as we're making output. This means more smaller queries spread out during operations, and less stuff kept in memory.
Callers (backupaccount action, and backupuser.php) which can stream their output pass an $outputMode param of UserActivityStream::OUTPUT_RAW, and during getString() it'll send straight to output as well as slurping the notices in this extra funky fashion.
Other callers will let it default to the OUTPUT_STRING mode, which keeps the previous behavior.
There should be a better way to do this, swapping out the stringer output for raw output more consitently.
2011-02-26 04:04:57 +09:00
|
|
|
* notices, all in reverse chron order.
|
|
|
|
*/
|
2020-09-15 22:59:27 +09:00
|
|
|
public function renderEntries($format = Feed::ATOM, $handle = null)
|
2011-01-03 08:22:12 +09:00
|
|
|
{
|
2013-05-30 05:45:52 +09:00
|
|
|
$haveOne = false;
|
|
|
|
|
Scalability work on user backup stream generation.
UserActivityStream -- used to create a full activity stream including subscriptions, favorites, notices, etc -- normally buffers everything into memory at once. This is infeasible for accounts with long histories of serious usage; it can take tens of seconds just to pull all records from the database, and working with them all in memory is very likely to hit resource limits.
This commit adds an alternate mode for this class which avoids pulling notices until during the actual output. Instead of pre-sorting and buffering all the notices, empty spaces between the other activities are filled in with notices as we're making output. This means more smaller queries spread out during operations, and less stuff kept in memory.
Callers (backupaccount action, and backupuser.php) which can stream their output pass an $outputMode param of UserActivityStream::OUTPUT_RAW, and during getString() it'll send straight to output as well as slurping the notices in this extra funky fashion.
Other callers will let it default to the OUTPUT_STRING mode, which keeps the previous behavior.
There should be a better way to do this, swapping out the stringer output for raw output more consitently.
2011-02-26 04:04:57 +09:00
|
|
|
$end = time() + 1;
|
2013-05-25 02:50:24 +09:00
|
|
|
foreach ($this->objs as $obj) {
|
2016-02-03 09:04:14 +09:00
|
|
|
set_time_limit(10);
|
|
|
|
|
2013-05-25 02:50:24 +09:00
|
|
|
try {
|
|
|
|
$act = $obj->asActivity();
|
|
|
|
} catch (Exception $e) {
|
|
|
|
common_log(LOG_ERR, $e->getMessage());
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
|
Scalability work on user backup stream generation.
UserActivityStream -- used to create a full activity stream including subscriptions, favorites, notices, etc -- normally buffers everything into memory at once. This is infeasible for accounts with long histories of serious usage; it can take tens of seconds just to pull all records from the database, and working with them all in memory is very likely to hit resource limits.
This commit adds an alternate mode for this class which avoids pulling notices until during the actual output. Instead of pre-sorting and buffering all the notices, empty spaces between the other activities are filled in with notices as we're making output. This means more smaller queries spread out during operations, and less stuff kept in memory.
Callers (backupaccount action, and backupuser.php) which can stream their output pass an $outputMode param of UserActivityStream::OUTPUT_RAW, and during getString() it'll send straight to output as well as slurping the notices in this extra funky fashion.
Other callers will let it default to the OUTPUT_STRING mode, which keeps the previous behavior.
There should be a better way to do this, swapping out the stringer output for raw output more consitently.
2011-02-26 04:04:57 +09:00
|
|
|
$start = $act->time;
|
|
|
|
|
|
|
|
if ($this->outputMode == self::OUTPUT_RAW && $start != $end) {
|
|
|
|
// In raw mode, we haven't pre-fetched notices.
|
|
|
|
// Grab the chunks of notices between other activities.
|
2013-05-25 02:50:24 +09:00
|
|
|
try {
|
|
|
|
$notices = $this->getNoticesBetween($start, $end);
|
|
|
|
foreach ($notices as $noticeAct) {
|
|
|
|
try {
|
2015-02-13 19:41:21 +09:00
|
|
|
$nact = $noticeAct->asActivity($this->user->getProfile());
|
2013-05-25 02:50:24 +09:00
|
|
|
if ($format == Feed::ATOM) {
|
|
|
|
$nact->outputTo($this, false, false);
|
|
|
|
} else {
|
2013-05-30 05:45:52 +09:00
|
|
|
if ($haveOne) {
|
|
|
|
fwrite($handle, ",");
|
|
|
|
}
|
2013-05-25 02:50:24 +09:00
|
|
|
fwrite($handle, json_encode($nact->asArray()));
|
2013-05-30 05:45:52 +09:00
|
|
|
$haveOne = true;
|
2013-05-25 02:50:24 +09:00
|
|
|
}
|
|
|
|
} catch (Exception $e) {
|
|
|
|
common_log(LOG_ERR, $e->getMessage());
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
$nact = null;
|
|
|
|
unset($nact);
|
2013-05-24 04:02:30 +09:00
|
|
|
}
|
2013-05-25 02:50:24 +09:00
|
|
|
} catch (Exception $e) {
|
|
|
|
common_log(LOG_ERR, $e->getMessage());
|
Scalability work on user backup stream generation.
UserActivityStream -- used to create a full activity stream including subscriptions, favorites, notices, etc -- normally buffers everything into memory at once. This is infeasible for accounts with long histories of serious usage; it can take tens of seconds just to pull all records from the database, and working with them all in memory is very likely to hit resource limits.
This commit adds an alternate mode for this class which avoids pulling notices until during the actual output. Instead of pre-sorting and buffering all the notices, empty spaces between the other activities are filled in with notices as we're making output. This means more smaller queries spread out during operations, and less stuff kept in memory.
Callers (backupaccount action, and backupuser.php) which can stream their output pass an $outputMode param of UserActivityStream::OUTPUT_RAW, and during getString() it'll send straight to output as well as slurping the notices in this extra funky fashion.
Other callers will let it default to the OUTPUT_STRING mode, which keeps the previous behavior.
There should be a better way to do this, swapping out the stringer output for raw output more consitently.
2011-02-26 04:04:57 +09:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2013-05-25 02:50:24 +09:00
|
|
|
$notices = null;
|
|
|
|
unset($notices);
|
|
|
|
|
|
|
|
try {
|
|
|
|
if ($format == Feed::ATOM) {
|
|
|
|
// Only show the author sub-element if it's different from default user
|
2014-04-28 21:08:42 +09:00
|
|
|
$act->outputTo($this, false, ($act->actor->id != $this->user->getUri()));
|
2013-05-25 02:50:24 +09:00
|
|
|
} else {
|
2013-05-30 05:45:52 +09:00
|
|
|
if ($haveOne) {
|
|
|
|
fwrite($handle, ",");
|
|
|
|
}
|
2013-05-25 02:50:24 +09:00
|
|
|
fwrite($handle, json_encode($act->asArray()));
|
2013-05-30 05:45:52 +09:00
|
|
|
$haveOne = true;
|
2013-05-25 02:50:24 +09:00
|
|
|
}
|
|
|
|
} catch (Exception $e) {
|
|
|
|
common_log(LOG_ERR, $e->getMessage());
|
|
|
|
}
|
|
|
|
|
|
|
|
$act = null;
|
|
|
|
unset($act);
|
Scalability work on user backup stream generation.
UserActivityStream -- used to create a full activity stream including subscriptions, favorites, notices, etc -- normally buffers everything into memory at once. This is infeasible for accounts with long histories of serious usage; it can take tens of seconds just to pull all records from the database, and working with them all in memory is very likely to hit resource limits.
This commit adds an alternate mode for this class which avoids pulling notices until during the actual output. Instead of pre-sorting and buffering all the notices, empty spaces between the other activities are filled in with notices as we're making output. This means more smaller queries spread out during operations, and less stuff kept in memory.
Callers (backupaccount action, and backupuser.php) which can stream their output pass an $outputMode param of UserActivityStream::OUTPUT_RAW, and during getString() it'll send straight to output as well as slurping the notices in this extra funky fashion.
Other callers will let it default to the OUTPUT_STRING mode, which keeps the previous behavior.
There should be a better way to do this, swapping out the stringer output for raw output more consitently.
2011-02-26 04:04:57 +09:00
|
|
|
|
|
|
|
$end = $start;
|
|
|
|
}
|
|
|
|
|
|
|
|
if ($this->outputMode == self::OUTPUT_RAW) {
|
|
|
|
// Grab anything after the last pre-sorted activity.
|
2013-05-25 02:50:24 +09:00
|
|
|
try {
|
2013-06-29 20:49:43 +09:00
|
|
|
if (!empty($this->after)) {
|
|
|
|
$notices = $this->getNoticesBetween($this->after, $end);
|
|
|
|
} else {
|
|
|
|
$notices = $this->getNoticesBetween(0, $end);
|
|
|
|
}
|
2013-05-25 02:50:24 +09:00
|
|
|
foreach ($notices as $noticeAct) {
|
|
|
|
try {
|
2015-02-13 19:55:37 +09:00
|
|
|
$nact = $noticeAct->asActivity($this->user->getProfile());
|
2013-05-25 02:50:24 +09:00
|
|
|
if ($format == Feed::ATOM) {
|
|
|
|
$nact->outputTo($this, false, false);
|
|
|
|
} else {
|
2013-05-30 05:45:52 +09:00
|
|
|
if ($haveOne) {
|
|
|
|
fwrite($handle, ",");
|
|
|
|
}
|
2013-05-25 02:50:24 +09:00
|
|
|
fwrite($handle, json_encode($nact->asArray()));
|
2013-05-30 05:45:52 +09:00
|
|
|
$haveOne = true;
|
2013-05-25 02:50:24 +09:00
|
|
|
}
|
|
|
|
} catch (Exception $e) {
|
|
|
|
common_log(LOG_ERR, $e->getMessage());
|
|
|
|
continue;
|
|
|
|
}
|
2013-05-24 04:02:30 +09:00
|
|
|
}
|
2013-05-25 02:50:24 +09:00
|
|
|
} catch (Exception $e) {
|
|
|
|
common_log(LOG_ERR, $e->getMessage());
|
Scalability work on user backup stream generation.
UserActivityStream -- used to create a full activity stream including subscriptions, favorites, notices, etc -- normally buffers everything into memory at once. This is infeasible for accounts with long histories of serious usage; it can take tens of seconds just to pull all records from the database, and working with them all in memory is very likely to hit resource limits.
This commit adds an alternate mode for this class which avoids pulling notices until during the actual output. Instead of pre-sorting and buffering all the notices, empty spaces between the other activities are filled in with notices as we're making output. This means more smaller queries spread out during operations, and less stuff kept in memory.
Callers (backupaccount action, and backupuser.php) which can stream their output pass an $outputMode param of UserActivityStream::OUTPUT_RAW, and during getString() it'll send straight to output as well as slurping the notices in this extra funky fashion.
Other callers will let it default to the OUTPUT_STRING mode, which keeps the previous behavior.
There should be a better way to do this, swapping out the stringer output for raw output more consitently.
2011-02-26 04:04:57 +09:00
|
|
|
}
|
2010-09-16 04:18:01 +09:00
|
|
|
}
|
2013-06-03 03:38:00 +09:00
|
|
|
|
2013-06-29 20:49:43 +09:00
|
|
|
if (empty($this->after) || strtotime($this->user->created) > $this->after) {
|
|
|
|
// We always add the registration activity at the end, even if
|
|
|
|
// they have older activities (from restored backups) in their stream.
|
2013-06-03 03:38:00 +09:00
|
|
|
|
2013-06-29 20:49:43 +09:00
|
|
|
try {
|
|
|
|
$ract = $this->user->registrationActivity();
|
|
|
|
if ($format == Feed::ATOM) {
|
|
|
|
$ract->outputTo($this, false, false);
|
|
|
|
} else {
|
|
|
|
if ($haveOne) {
|
|
|
|
fwrite($handle, ",");
|
|
|
|
}
|
|
|
|
fwrite($handle, json_encode($ract->asArray()));
|
|
|
|
$haveOne = true;
|
2013-06-03 03:38:00 +09:00
|
|
|
}
|
2013-06-29 20:49:43 +09:00
|
|
|
} catch (Exception $e) {
|
|
|
|
common_log(LOG_ERR, $e->getMessage());
|
2013-06-03 03:38:00 +09:00
|
|
|
}
|
|
|
|
}
|
2010-09-16 04:18:01 +09:00
|
|
|
}
|
|
|
|
|
2020-09-15 22:59:27 +09:00
|
|
|
public function compareObject($a, $b)
|
2010-09-16 04:18:01 +09:00
|
|
|
{
|
|
|
|
$ac = strtotime((empty($a->created)) ? $a->modified : $a->created);
|
|
|
|
$bc = strtotime((empty($b->created)) ? $b->modified : $b->created);
|
|
|
|
|
|
|
|
return (($ac == $bc) ? 0 : (($ac < $bc) ? 1 : -1));
|
|
|
|
}
|
|
|
|
|
2020-09-15 22:59:27 +09:00
|
|
|
public function getSubscriptions()
|
2010-09-16 04:18:01 +09:00
|
|
|
{
|
|
|
|
$subs = array();
|
|
|
|
|
|
|
|
$sub = new Subscription();
|
|
|
|
|
|
|
|
$sub->subscriber = $this->user->id;
|
|
|
|
|
2013-06-29 20:49:43 +09:00
|
|
|
if (!empty($this->after)) {
|
|
|
|
$sub->whereAdd("created > '" . common_sql_date($this->after) . "'");
|
|
|
|
}
|
|
|
|
|
2010-09-16 04:18:01 +09:00
|
|
|
if ($sub->find()) {
|
|
|
|
while ($sub->fetch()) {
|
|
|
|
if ($sub->subscribed != $this->user->id) {
|
|
|
|
$subs[] = clone($sub);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return $subs;
|
|
|
|
}
|
|
|
|
|
2020-09-15 22:59:27 +09:00
|
|
|
public function getSubscribers()
|
2010-09-16 04:18:01 +09:00
|
|
|
{
|
|
|
|
$subs = array();
|
|
|
|
|
|
|
|
$sub = new Subscription();
|
|
|
|
|
|
|
|
$sub->subscribed = $this->user->id;
|
|
|
|
|
2013-06-29 20:49:43 +09:00
|
|
|
if (!empty($this->after)) {
|
|
|
|
$sub->whereAdd("created > '" . common_sql_date($this->after) . "'");
|
|
|
|
}
|
|
|
|
|
2010-09-16 04:18:01 +09:00
|
|
|
if ($sub->find()) {
|
|
|
|
while ($sub->fetch()) {
|
|
|
|
if ($sub->subscriber != $this->user->id) {
|
|
|
|
$subs[] = clone($sub);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return $subs;
|
|
|
|
}
|
|
|
|
|
Scalability work on user backup stream generation.
UserActivityStream -- used to create a full activity stream including subscriptions, favorites, notices, etc -- normally buffers everything into memory at once. This is infeasible for accounts with long histories of serious usage; it can take tens of seconds just to pull all records from the database, and working with them all in memory is very likely to hit resource limits.
This commit adds an alternate mode for this class which avoids pulling notices until during the actual output. Instead of pre-sorting and buffering all the notices, empty spaces between the other activities are filled in with notices as we're making output. This means more smaller queries spread out during operations, and less stuff kept in memory.
Callers (backupaccount action, and backupuser.php) which can stream their output pass an $outputMode param of UserActivityStream::OUTPUT_RAW, and during getString() it'll send straight to output as well as slurping the notices in this extra funky fashion.
Other callers will let it default to the OUTPUT_STRING mode, which keeps the previous behavior.
There should be a better way to do this, swapping out the stringer output for raw output more consitently.
2011-02-26 04:04:57 +09:00
|
|
|
/**
|
|
|
|
*
|
|
|
|
* @param int $start unix timestamp for earliest
|
|
|
|
* @param int $end unix timestamp for latest
|
|
|
|
* @return array of Notice objects
|
|
|
|
*/
|
2020-09-15 22:59:27 +09:00
|
|
|
public function getNoticesBetween($start = 0, $end = 0)
|
2010-09-16 04:18:01 +09:00
|
|
|
{
|
2020-09-15 22:59:27 +09:00
|
|
|
$notices = [];
|
2010-09-16 04:18:01 +09:00
|
|
|
|
|
|
|
$notice = new Notice();
|
|
|
|
|
|
|
|
$notice->profile_id = $this->user->id;
|
|
|
|
|
2013-06-29 20:49:43 +09:00
|
|
|
// Only stuff after $this->after
|
|
|
|
|
|
|
|
if (!empty($this->after)) {
|
|
|
|
if ($start) {
|
|
|
|
$start = max($start, $this->after);
|
|
|
|
}
|
|
|
|
if ($end) {
|
|
|
|
$end = max($end, $this->after);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
Scalability work on user backup stream generation.
UserActivityStream -- used to create a full activity stream including subscriptions, favorites, notices, etc -- normally buffers everything into memory at once. This is infeasible for accounts with long histories of serious usage; it can take tens of seconds just to pull all records from the database, and working with them all in memory is very likely to hit resource limits.
This commit adds an alternate mode for this class which avoids pulling notices until during the actual output. Instead of pre-sorting and buffering all the notices, empty spaces between the other activities are filled in with notices as we're making output. This means more smaller queries spread out during operations, and less stuff kept in memory.
Callers (backupaccount action, and backupuser.php) which can stream their output pass an $outputMode param of UserActivityStream::OUTPUT_RAW, and during getString() it'll send straight to output as well as slurping the notices in this extra funky fashion.
Other callers will let it default to the OUTPUT_STRING mode, which keeps the previous behavior.
There should be a better way to do this, swapping out the stringer output for raw output more consitently.
2011-02-26 04:04:57 +09:00
|
|
|
if ($start) {
|
|
|
|
$tsstart = common_sql_date($start);
|
|
|
|
$notice->whereAdd("created >= '$tsstart'");
|
|
|
|
}
|
|
|
|
if ($end) {
|
|
|
|
$tsend = common_sql_date($end);
|
|
|
|
$notice->whereAdd("created < '$tsend'");
|
|
|
|
}
|
|
|
|
|
2020-09-15 22:59:27 +09:00
|
|
|
$notice->orderBy('created DESC, id DESC');
|
Scalability work on user backup stream generation.
UserActivityStream -- used to create a full activity stream including subscriptions, favorites, notices, etc -- normally buffers everything into memory at once. This is infeasible for accounts with long histories of serious usage; it can take tens of seconds just to pull all records from the database, and working with them all in memory is very likely to hit resource limits.
This commit adds an alternate mode for this class which avoids pulling notices until during the actual output. Instead of pre-sorting and buffering all the notices, empty spaces between the other activities are filled in with notices as we're making output. This means more smaller queries spread out during operations, and less stuff kept in memory.
Callers (backupaccount action, and backupuser.php) which can stream their output pass an $outputMode param of UserActivityStream::OUTPUT_RAW, and during getString() it'll send straight to output as well as slurping the notices in this extra funky fashion.
Other callers will let it default to the OUTPUT_STRING mode, which keeps the previous behavior.
There should be a better way to do this, swapping out the stringer output for raw output more consitently.
2011-02-26 04:04:57 +09:00
|
|
|
|
2010-09-16 04:18:01 +09:00
|
|
|
if ($notice->find()) {
|
|
|
|
while ($notice->fetch()) {
|
|
|
|
$notices[] = clone($notice);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return $notices;
|
|
|
|
}
|
|
|
|
|
2020-09-15 22:59:27 +09:00
|
|
|
public function getNotices()
|
Scalability work on user backup stream generation.
UserActivityStream -- used to create a full activity stream including subscriptions, favorites, notices, etc -- normally buffers everything into memory at once. This is infeasible for accounts with long histories of serious usage; it can take tens of seconds just to pull all records from the database, and working with them all in memory is very likely to hit resource limits.
This commit adds an alternate mode for this class which avoids pulling notices until during the actual output. Instead of pre-sorting and buffering all the notices, empty spaces between the other activities are filled in with notices as we're making output. This means more smaller queries spread out during operations, and less stuff kept in memory.
Callers (backupaccount action, and backupuser.php) which can stream their output pass an $outputMode param of UserActivityStream::OUTPUT_RAW, and during getString() it'll send straight to output as well as slurping the notices in this extra funky fashion.
Other callers will let it default to the OUTPUT_STRING mode, which keeps the previous behavior.
There should be a better way to do this, swapping out the stringer output for raw output more consitently.
2011-02-26 04:04:57 +09:00
|
|
|
{
|
2013-06-29 20:49:43 +09:00
|
|
|
if (!empty($this->after)) {
|
|
|
|
return $this->getNoticesBetween($this->after);
|
|
|
|
} else {
|
|
|
|
return $this->getNoticesBetween();
|
|
|
|
}
|
Scalability work on user backup stream generation.
UserActivityStream -- used to create a full activity stream including subscriptions, favorites, notices, etc -- normally buffers everything into memory at once. This is infeasible for accounts with long histories of serious usage; it can take tens of seconds just to pull all records from the database, and working with them all in memory is very likely to hit resource limits.
This commit adds an alternate mode for this class which avoids pulling notices until during the actual output. Instead of pre-sorting and buffering all the notices, empty spaces between the other activities are filled in with notices as we're making output. This means more smaller queries spread out during operations, and less stuff kept in memory.
Callers (backupaccount action, and backupuser.php) which can stream their output pass an $outputMode param of UserActivityStream::OUTPUT_RAW, and during getString() it'll send straight to output as well as slurping the notices in this extra funky fashion.
Other callers will let it default to the OUTPUT_STRING mode, which keeps the previous behavior.
There should be a better way to do this, swapping out the stringer output for raw output more consitently.
2011-02-26 04:04:57 +09:00
|
|
|
}
|
|
|
|
|
2020-09-15 22:59:27 +09:00
|
|
|
public function getGroups()
|
2010-09-16 04:18:01 +09:00
|
|
|
{
|
|
|
|
$groups = array();
|
|
|
|
|
|
|
|
$gm = new Group_member();
|
|
|
|
|
|
|
|
$gm->profile_id = $this->user->id;
|
|
|
|
|
2013-06-29 20:49:43 +09:00
|
|
|
if (!empty($this->after)) {
|
|
|
|
$gm->whereAdd("created > '" . common_sql_date($this->after) . "'");
|
|
|
|
}
|
|
|
|
|
2010-09-16 04:18:01 +09:00
|
|
|
if ($gm->find()) {
|
|
|
|
while ($gm->fetch()) {
|
|
|
|
$groups[] = clone($gm);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return $groups;
|
|
|
|
}
|
2013-05-25 02:50:24 +09:00
|
|
|
|
2020-09-15 22:59:27 +09:00
|
|
|
public function createdAfter($item)
|
|
|
|
{
|
2013-06-29 20:49:43 +09:00
|
|
|
$created = strtotime((empty($item->created)) ? $item->modified : $item->created);
|
|
|
|
return ($created >= $this->after);
|
2013-06-09 06:53:47 +09:00
|
|
|
}
|
|
|
|
|
2020-09-15 22:59:27 +09:00
|
|
|
public function writeJSON($handle)
|
2013-05-25 02:50:24 +09:00
|
|
|
{
|
2019-08-23 21:36:02 +09:00
|
|
|
require_once INSTALLDIR . '/lib/activitystreams/activitystreamjsondocument.php';
|
2013-05-25 02:50:24 +09:00
|
|
|
fwrite($handle, '{"items": [');
|
|
|
|
$this->renderEntries(Feed::JSON, $handle);
|
2013-05-30 06:03:08 +09:00
|
|
|
fwrite($handle, ']}');
|
2013-05-25 02:50:24 +09:00
|
|
|
}
|
2010-09-16 04:18:01 +09:00
|
|
|
}
|