about summary refs log tree commit diff
path: root/app/workers
AgeCommit message (Collapse)Author
2019-08-18use default sidekiq options for `LogWorker`multiple creatures
2019-08-18use default sidekiq options for `DomainBlockWorker`multiple creatures
2019-08-09transparancy log - automatically add a content warning if there are admin ↵multiple creatures
comments; support a custom `subject`
2019-08-09janitor - add db & media pruning jobmultiple creatures
2019-08-08admin transparancy log - support markdownmultiple creatures
2019-08-08janitor - option to export `activityrelay` configmultiple creatures
2019-08-08janitor - make sure values excludes are dedupedmultiple creatures
2019-08-07add distributability check to reblog workermultiple creatures
2019-08-07add option to automatically space out boosts over configurable random intervalsmultiple creatures
2019-08-05janitor can now write suspended domains to whatever JANITOR_BLOCKLIST_OUTPUT ↵multiple creatures
is set to so they can be imported elsewhere (e.g., `nginx`)
2019-08-03move `Scheduler::JanitorScheduler::admin_account` to ↵multiple creatures
`ModerationHelper::janitor_account`
2019-08-03respect 'don't @ me' requestsmultiple creatures
2019-08-03`domain_exists` -> `domain_exists?`multiple creatures
2019-08-03rename `BangtagHelper` to `ModerationHelper`multiple creatures
2019-08-03skip importing dead domainsmultiple creatures
2019-08-03`monsterpit-janitor` is now built in as a sidekiq job (with better code)multiple creatures
2019-07-31ability to add domain moderation notes, edit existing domain policies ↵multiple creatures
in-place, and process asynchronously
2019-07-30revert to `text/plain` for transparancy loggermultiple creatures
2019-07-29add plain-text console formatting optionmultiple creatures
2019-07-29fix delayed roars mentions bug, increase delay to 1 minute, include local ↵multiple creatures
only prop
2019-07-29optional delayed publishing of roars for proofreadingmultiple creatures
2019-07-26make sure self-destructing roar worker exits successfullymultiple creatures
2019-07-26process self-destructing roars asynchronouslymultiple creatures
2019-07-26split federation & moderation logs into different subscopes + make scope tag ↵multiple creatures
prefix configurable
2019-07-24logger should not generate link cards or mentions for entriesmultiple creatures
2019-07-24transparancy - log use of admin related method calls & activitypub ↵multiple creatures
auto-rejections to a logger account
2019-07-24revert the current unfinished chat implementationmultiple creatures
2019-07-23add self-destructing roars & `live`/`lifespan` bangtagsmultiple creatures
2019-07-15local visibility scope, chat scope+tags, unlisted tagsmultiple creatures
2019-07-15make blocking domains actually block the accountsmultiple creatures
2019-05-21Drop remaining OStatus and PuSH code, as well as related database items.multiple creatures
2019-05-21Drop OStatus support. Fix some of the Rspec tests.multiple creatures
2019-05-04Merge branch 'master' into glitch-soc/merge-upstreamThibaut Girka
Conflicts: - app/models/media_attachment.rb
2019-05-03Do not retry processing ActivityPub jobs raising validation errors (#10614)ThibG
* Do not retry processing ActivityPub jobs raising validation errors Jobs yielding validation errors most probably won't ever be accepted, so it makes sense not to clutter the queues with retries. * Lower RecordInvalid error reporting to debug log level * Remove trailing whitespace
2019-04-08Merge branch 'master' into glitch-soc/merge-upstreamThibaut Girka
Conflicts: - config/locales/pl.yml Conflict caused by new upstream string too close to glitch-specific “flavour” string. Took both strings.
2019-04-08Export and import show_reblogs together with following list (#10495)ThibG
* Refactor imports * Export show_reblogs when exporting list of followed users * Add support for importing show_reblogs with following collection * Fix tests
2019-04-04Merge branch 'master' into glitch-soc/merge-upstreamThibaut Girka
Conflicts: - app/controllers/following_accounts_controller.rb Conflicts were due to glitch-soc's theming system. - app/javascript/packs/public.js Some code has been change upstream, but it has been moved to app/javascript/core/settings.js in glitch-soc. Applied the changes there.
2019-04-03Export and import `hide_notifications` alongside user mutes (#10335)ThibG
* Export hide_notifications along with user mutes * Import hide_notifications along with muted users list * Add headers for CSV exports
2019-03-28Merge branch 'master' into glitch-soc/merge-upstreamThibaut Girka
Conflicts: - app/workers/activitypub/distribute_poll_update_worker.rb - config/locales/pl.yml
2019-03-28Rename :poll to :preloadable_poll and :owned_poll to :poll on Status (#10401)Eugen Rochko
Also, fix some n+1 queries Resolve #10365
2019-03-16Merge branch 'master' into glitch-soc/merge-upstreamThibaut Girka
Conflicts: - app/services/remove_status_service.rb Conflict because we still handle the direct timeline. Took upstream changes, with that one extra function call. - config/locales/ca.yml Conflict because theme names were updated. Decided to *keep* the theme names even if they are useless to avoid future conflicts. - config/locales/oc.yml Decided to *keep* the theme names even if they are useless to avoid future conflicts. - config/locales/pl.yml Decided to *keep* the theme names even if they are useless to avoid future conflicts.
2019-03-16Avoid race condition when streaming deleted statuses (#10280)ThibG
* Avoid race condition when streaming deleted statuses * Move redis lock to DistributionWorker to avoid extra Redis value
2019-03-14Merge branch 'master' into glitch-soc/merge-upstreamThibaut Girka
Conflicts: - app/views/admin/settings/edit.html.haml: Conflict due to how the theming settings change.
2019-03-14Fix wrong method used in PollExpirationNotifyWorker (#10265)Eugen Rochko
2019-03-13Merge branch 'master' into glitch-soc/merge-upstreamThibaut Girka
Conflicts: - app/controllers/about_controller.rb - app/controllers/tags_controller.rb - app/views/about/show.html.haml - spec/views/about/show.html.haml_spec.rb
2019-03-12Fix poll update handler calling method was that was not available (#10246)Eugen Rochko
* Fix poll update handler calling method was that was not available Fix regression from #10209 * Refactor VoteService * Refactor ActivityPub::DistributePollUpdateWorker and optimize it * Fix typo * Fix typo
2019-03-11Do not leak instance-local polls to remote followersThibaut Girka
2019-03-11Support pushing and receiving updates to poll tallies (#10209)ThibG
* Process incoming poll tallies update * Send Update on poll vote * Do not send Updates for a poll more often than once every 3 minutes * Include voters in people to notify of results update * Schedule closing poll worker on poll creation * Add new notification type for ending polls * Add front-end support for ended poll notifications * Fix UpdatePollSerializer * Fix Updates not being triggered by local votes * Fix tests failure * Fix web push notifications for closing polls * Minor cleanup * Notify voters of both remote and local polls when those close * Fix delivery of poll updates to mentioned accounts and voters
2019-03-05Do not error out on unsalvageable errors in FetchRepliesService (#10175)ThibG
* Do not error out on unsalvageable errors in FetchRepliesService Fixes #10152 * Fix FetchRepliesWorker erroring out on deleted statuses
2019-02-28Improved remote thread fetching (#10106)ThibG
* Fetch up to 5 replies when discovering a new remote status This is used for resolving threads downwards. The originating server must add a “replies” attributes with such replies for it to be useful. * Add some tests for ActivityPub::FetchRepliesWorker * Add specs for ActivityPub::FetchRepliesService * Serialize up to 5 public self-replies for ActivityPub notes * Add specs for ActivityPub::NoteSerializer * Move exponential backoff logic to a worker concern * Fetch first page of paginated collections when fetching thread replies * Add specs for paginated collections in replies * Move Note replies serialization to a first CollectionPage The collection isn't actually paginable yet as it has no id nor a `next` field. This may come in another PR. * Use pluck(:uri) instead of map(&:uri) to improve performances * Fix fetching replies when they are in a CollectionPage