mastodon - Plural Café fork of Mastodon/Glitch Social

Age	Commit message (Collapse)	Author
2019-07-06	Remove Salmon and PubSubHubbub (#11205)	Eugen Rochko
	* Remove Salmon and PubSubHubbub endpoints * Add error when trying to follow OStatus accounts * Fix new accounts not being created in ResolveAccountService
2018-01-05	Fix PuSH workers (#6200)	ThibG

2017-09-24	Suppress backtrace when failed to communicate with a remote instance (#5076)	Daigo 3 Dango

2017-09-14	Revert unique retry job (#4937)	abcang
	* Revert "Enable UniqueRetryJobMiddleware even when called from sidekiq worker (#4836)" This reverts commit 6859d4c0289e767955aac3f345074220fe200604. * Revert "Do not execute the job with the same arguments as the retry job (#4814)" This reverts commit be7ffa2d7539d5a1946a3933cb9d242b9fac0ddc.
2017-09-05	Do not execute the job with the same arguments as the retry job (#4814)	abcang

2017-07-28	When PuSH subscribe attempts are exhausted, unsubscribe (#4422)	Eugen Rochko

2017-07-27	Add callback_url/acct information for Sidekiq PuSH workers Exception. (#4281)	Clworld
	* Add destination informations to exception on SubscribeWorker and DeliveryWorker. * Simplify delivery error message. * Prevent changing Exception type... * fix typo.
2017-07-10	Limit total subscribe retries to 10, but space them out more (#4142)	Eugen Rochko
	Since there is little point in retrying so often when a service is down or does not exist anymore. Subscriptions are renewed 1 day before they should expire, so retrying in 30 minutes, then 2 hours, then 12 hours is fine. If even after that, the remote server does not work, there is little sense in retrying more often than once a day Also, uniqueness of the job should ensure that failed retries will not result in multiple retries for the same endpoint when the next resubscription cycle comes
2017-05-06	Fix Scheduler::SubscriptionsScheduler (#2834)	Eugen Rochko
	* Fix Scheduler::SubscriptionsScheduler, add worker test for it * Change production log level of Sidekiq to "warn" instead of "info"
2017-05-05	More robust PuSH subscription refreshes (#2799)	Eugen Rochko
	* Fix #2473 - Use sidekiq scheduler to refresh PuSH subscriptions instead of cron Fix an issue where / in domain would raise exception in TagManager#normalize_domain PuSH subscriptions refresh done in a round-robin way to avoid hammering a single server's hub in sequence. Correct handling of failures/retries through Sidekiq (see also #2613). Optimize Account#with_followers scope. Also, since subscriptions are now delegated to Sidekiq jobs, an uncaught exception will not stop the entire refreshing operation halfway through Fix #2702 - Correct user agent header on outgoing http requests * Add test for SubscribeService * Extract #expiring_accounts into method * Make mastodon:push:refresh no-op * Queues are now defined in sidekiq.yml * Queues are now in sidekiq.yml