summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2010-01-26Use "Sign in with Twitter" auth pattern and official Twitter button for ↵Zach Copley
Twitter-based login. See: http://apiwiki.twitter.com/Sign-in-with-Twitter
2010-01-26Ask the user to set a password before disconnecting from TwitterZach Copley
2010-01-26- Twitter username wasn't getting stored in Foreign_user when linking ↵Zach Copley
Twitter account (fixed) - Updates to comments
2010-01-26Allow logging in using TwitterJulien C
Signed-off-by: Julien C <chaumond@gmail.com>
2010-01-26Merge branch '0.9.x' of git@gitorious.org:statusnet/mainline into 0.9.xSarven Capadisli
2010-01-26Setting the geo location cookie expire date far into the future: 2029 ;)Sarven Capadisli
2010-01-25Merge branch 'master' into 0.9.xEvan Prodromou
2010-01-25Offload inbox updates to a queue handler to speed up posting onlineEvan Prodromou
Moved much of the writing that happens when posting a notice to a new queuehandler, distribqueuehandler. This updates tags, groups, replies and inboxes at queue time (or at Web time, if queues are disabled). To make this work well, I had to break up the monolithic Notice::blowCaches() and make cache blowing happen closer to where data is updated. Squashed commit of the following: commit 5257626c62750ac4ac1db0ce2b71410c5711cfa3 Author: Evan Prodromou <evan@status.net> Date: Mon Jan 25 14:56:41 2010 -0500 slightly better handling of blowing tag memory cache commit 8a22a3cdf6ec28685da129a0313e7b2a0837c9ef Author: Evan Prodromou <evan@status.net> Date: Mon Jan 25 01:42:56 2010 -0500 change 'distribute' to 'distrib' so not too long for dbqueue commit 7a063315b0f7fad27cb6fbd2bdd74e253af83e4f Author: Evan Prodromou <evan@status.net> Date: Mon Jan 25 01:39:15 2010 -0500 change handle_notice() to handle() in distributqueuehandler commit 1a39ccd28b9994137d7bfd21bb4f230546938e77 Author: Evan Prodromou <evan@status.net> Date: Mon Jan 25 16:05:25 2010 -0500 error with queuemanager commit e6b3bb93f305cfd2de71a6340b8aa6fb890049b7 Author: Evan Prodromou <evan@status.net> Date: Mon Jan 25 01:11:34 2010 -0500 Blow memcache at different point rather than one big function for Notice class commit 94d557cdc016187d1d0647ae1794cd94d6fb8ac8 Author: Evan Prodromou <evan@status.net> Date: Mon Jan 25 00:48:44 2010 -0500 Blow memcache at different point rather than one big function for Notice class commit 1c781dd08c88a35dafc5c01230b4872fd6b95182 Author: Evan Prodromou <evan@status.net> Date: Wed Jan 20 08:54:18 2010 -0500 move broadcasting and distributing to new queuehandler commit da3e46d26b84e4f028f34a13fd2ee373e4c1b954 Author: Evan Prodromou <evan@status.net> Date: Wed Jan 20 08:53:12 2010 -0500 Move distribution of notices to new distribute queue handler
2010-01-25An update to geolocation cookie to use a single file and set theSarven Capadisli
expiry date to 30 days from now.
2010-01-25Fix presence notification on XMPP thread (now foreground, not background)Brion Vibber
2010-01-25Updated howto create a themeSarven Capadisli
2010-01-25Fix for PoweredByStatusNetPlugin to be localizable (was broken for ↵Brion Vibber
non-English word order) (Note the .po files will have to be added manually for now as we haven't set TranslateWiki up for plugins I think)
2010-01-24Use new StatusNetwork->serverName() to get full domain for wildcard config ↵Brion Vibber
until we rebuild queues to be based on nicknames. Fixes live bug with new *.status.net sites breaking queuedaemon.php
2010-01-24defaults for nickname and wildcardEvan Prodromou
2010-01-24save nickname and wildcard when setting up status networkEvan Prodromou
2010-01-24Merge branch '0.9.x' of git@gitorious.org:statusnet/mainline into 0.9.xEvan Prodromou
Conflicts: lib/stompqueuemanager.php
2010-01-24Merge branch 'master' into 0.9.xEvan Prodromou
Conflicts: lib/stompqueuemanager.php
2010-01-24set correct key types for User_flag_profileEvan Prodromou
2010-01-24add function doc comment to User_flag_profile::create()Evan Prodromou
2010-01-24Merge branch '0.9.x' of git@gitorious.org:statusnet/mainline into 0.9.xSarven Capadisli
2010-01-24Added version info for MobileProfile pluginSarven Capadisli
2010-01-24Merge commit 'refs/merge-requests/120' of ↵Brenda Wallace
git://gitorious.org/statusnet/mainline into 0.9.x
2010-01-23Use StartQueueDaemonIoManagers instead of removed StartIoManagerClasses eventCraig Andrews
2010-01-23Allow for instances as well as class names to be passed as queue handlers ↵Craig Andrews
and iomanagers.
2010-01-22StompQueueManager uses decode() to decode queued framesCraig Andrews
2010-01-22Merge branch 'testing' into 0.9.xBrion Vibber
2010-01-22Fix unqueuemanager for updated QueueHandler interfaceBrion Vibber
2010-01-22Consolidate PuSH publishing ping into a single POST for all feeds, and fix ↵Brion Vibber
server response (if any on failure) to go to log instead of stdout.
2010-01-22Fix unqueuemanager for updated QueueHandler interfaceBrion Vibber
2010-01-22Merge branch 'testing' of gitorious.org:statusnet/mainline into 0.9.xBrion Vibber
2010-01-22Fix for stuck queue messages: wrap processing in stomp transactions so our ↵Brion Vibber
lack of an ACK if PHP dies actually triggers redelivery. Previously, messages once delivered would just get stuck in the queue seemingly forever if they never got ACKed. Note this could lead to partial duplication, for instance if the OMB or Twitter queue handlers die after 1/2 of the outgoing sends. Recommendations: * catch exceptions more aggressively within queue handlers (so only PHP fatal errors are likely to kill in the middle) * for processing that involves sending to multiple clients, consider a second queue similar to the XMPP output, eg for OMB: - first queue gets delivery list and builds message data, enqueueing it for each target address - second queue can handle each individual outgoing message (and attempt redelivery etc separately) This would also protect better against a recurring error preventing delivery in the second part, and could spread out any slow sends over multiple threads.
2010-01-22XMPP queued output & initial retooling of DB queue manager to support ↵Brion Vibber
non-Notice objects. Queue handlers for XMPP individual & firehose output now send their XML stanzas to another output queue instead of connecting directly to the chat server. This lets us have as many general processing threads as we need, while all actual XMPP input and output go through a single daemon with a single connection open. This avoids problems with multiple connected resources: * multiple windows shown in some chat clients (psi, gajim, kopete) * extra load on server * incoming message delivery forwarding issues Database changes: * queue_item drops 'notice_id' in favor of a 'frame' blob. This is based on Craig Andrews' work branch to generalize queues to take any object, but conservatively leaving out the serialization for now. Table updater (preserves any existing queued items) in db/rc3to09.sql Code changes to watch out for: * Queue handlers should now define a handle() method instead of handle_notice() * QueueDaemon and XmppDaemon now share common i/o (IoMaster) and respawning thread management (RespawningDaemon) infrastructure. * The polling XmppConfirmManager has been dropped, as the message is queued directly when saving IM settings. * Enable $config['queue']['debug_memory'] to output current memory usage at each run through the event loop to watch for memory leaks To do: * Adapt XMPP i/o to component connection mode for multi-site support. * XMPP input can also be broken out to a queue, which would allow the actual notice save etc to be handled by general queue threads. * Make sure there are no problems with simply pushing serialized Notice objects to queues. * Find a way to improve interactive performance of the database-backed queue handler; polling is pretty painful to XMPP. * Possibly redo the way QueueHandlers are injected into a QueueManager. The grouping used to split out the XMPP output queue is a bit awkward. Conflicts: scripts/xmppdaemon.php
2010-01-22Fix for stuck queue messages: wrap processing in stomp transactions so our ↵Brion Vibber
lack of an ACK if PHP dies actually triggers redelivery. Previously, messages once delivered would just get stuck in the queue seemingly forever if they never got ACKed. Note this could lead to partial duplication, for instance if the OMB or Twitter queue handlers die after 1/2 of the outgoing sends. Recommendations: * catch exceptions more aggressively within queue handlers (so only PHP fatal errors are likely to kill in the middle) * for processing that involves sending to multiple clients, consider a second queue similar to the XMPP output, eg for OMB: - first queue gets delivery list and builds message data, enqueueing it for each target address - second queue can handle each individual outgoing message (and attempt redelivery etc separately) This would also protect better against a recurring error preventing delivery in the second part, and could spread out any slow sends over multiple threads.
2010-01-22Fixed innerHTML problem in IE7 and 8 for badge scriptSarven Capadisli
2010-01-22Merge branch '0.9.x' of git@gitorious.org:statusnet/mainline into 0.9.xEvan Prodromou
2010-01-22Merge branch 'testing' into 0.9.xEvan Prodromou
2010-01-22Merge branch 'master' into 0.9.xEvan Prodromou
2010-01-22Merge branch 'testing' of git@gitorious.org:statusnet/mainline into testingEvan Prodromou
2010-01-22do actual language negotiation for help docsEvan Prodromou
2010-01-22restructure doc.php for new useEvan Prodromou
2010-01-22action/doc.php is PHPCS cleanEvan Prodromou
2010-01-22Merge branch '0.9.x' of git@gitorious.org:statusnet/mainline into 0.9.xSarven Capadisli
2010-01-22Fixed innerHTML problem in IE7 and 8 for badge scriptSarven Capadisli
2010-01-22Fix unqueuemanager to work with new Queue layout pushed in ↵Eric Helgeson
0e852def6ae5aa529cca0aef1187152fb5a880be "* Queue handlers should now define a handle() method instead of handle_notice()" And Queue managers should call handle() :)
2010-01-22Memcached_DataObject unnecessarily require_once'd itselfEvan Prodromou
2010-01-22stupid mistake... let's not talk about this.Craig Andrews
2010-01-22Updated some references to the long gnone "isEnclosure" function to the new ↵Craig Andrews
"getEnclosure"
2010-01-21XMPP queued output & initial retooling of DB queue manager to support ↵Brion Vibber
non-Notice objects. Queue handlers for XMPP individual & firehose output now send their XML stanzas to another output queue instead of connecting directly to the chat server. This lets us have as many general processing threads as we need, while all actual XMPP input and output go through a single daemon with a single connection open. This avoids problems with multiple connected resources: * multiple windows shown in some chat clients (psi, gajim, kopete) * extra load on server * incoming message delivery forwarding issues Database changes: * queue_item drops 'notice_id' in favor of a 'frame' blob. This is based on Craig Andrews' work branch to generalize queues to take any object, but conservatively leaving out the serialization for now. Table updater (preserves any existing queued items) in db/rc3to09.sql Code changes to watch out for: * Queue handlers should now define a handle() method instead of handle_notice() * QueueDaemon and XmppDaemon now share common i/o (IoMaster) and respawning thread management (RespawningDaemon) infrastructure. * The polling XmppConfirmManager has been dropped, as the message is queued directly when saving IM settings. * Enable $config['queue']['debug_memory'] to output current memory usage at each run through the event loop to watch for memory leaks To do: * Adapt XMPP i/o to component connection mode for multi-site support. * XMPP input can also be broken out to a queue, which would allow the actual notice save etc to be handled by general queue threads. * Make sure there are no problems with simply pushing serialized Notice objects to queues. * Find a way to improve interactive performance of the database-backed queue handler; polling is pretty painful to XMPP. * Possibly redo the way QueueHandlers are injected into a QueueManager. The grouping used to split out the XMPP output queue is a bit awkward.
2010-01-21XMPP queued output & initial retooling of DB queue manager to support ↵Brion Vibber
non-Notice objects. Queue handlers for XMPP individual & firehose output now send their XML stanzas to another output queue instead of connecting directly to the chat server. This lets us have as many general processing threads as we need, while all actual XMPP input and output go through a single daemon with a single connection open. This avoids problems with multiple connected resources: * multiple windows shown in some chat clients (psi, gajim, kopete) * extra load on server * incoming message delivery forwarding issues Database changes: * queue_item drops 'notice_id' in favor of a 'frame' blob. This is based on Craig Andrews' work branch to generalize queues to take any object, but conservatively leaving out the serialization for now. Table updater (preserves any existing queued items) in db/rc3to09.sql Code changes to watch out for: * Queue handlers should now define a handle() method instead of handle_notice() * QueueDaemon and XmppDaemon now share common i/o (IoMaster) and respawning thread management (RespawningDaemon) infrastructure. * The polling XmppConfirmManager has been dropped, as the message is queued directly when saving IM settings. * Enable $config['queue']['debug_memory'] to output current memory usage at each run through the event loop to watch for memory leaks To do: * Adapt XMPP i/o to component connection mode for multi-site support. * XMPP input can also be broken out to a queue, which would allow the actual notice save etc to be handled by general queue threads. * Make sure there are no problems with simply pushing serialized Notice objects to queues. * Find a way to improve interactive performance of the database-backed queue handler; polling is pretty painful to XMPP. * Possibly redo the way QueueHandlers are injected into a QueueManager. The grouping used to split out the XMPP output queue is a bit awkward.
2010-01-21Merge branch 'testing' into 0.9.xBrion Vibber