2016-11-19 18:33:02 -05:00
|
|
|
# frozen_string_literal: true
|
|
|
|
|
|
|
|
class NotifyService < BaseService
|
|
|
|
def call(recipient, activity)
|
|
|
|
@recipient = recipient
|
|
|
|
@activity = activity
|
|
|
|
@notification = Notification.new(account: @recipient, activity: @activity)
|
|
|
|
|
2017-04-16 12:04:05 -04:00
|
|
|
return if recipient.user.nil? || blocked?
|
2016-11-19 18:33:02 -05:00
|
|
|
|
|
|
|
create_notification
|
|
|
|
send_email if email_enabled?
|
2016-11-22 11:32:51 -05:00
|
|
|
rescue ActiveRecord::RecordInvalid
|
|
|
|
return
|
2016-11-19 18:33:02 -05:00
|
|
|
end
|
|
|
|
|
|
|
|
private
|
|
|
|
|
2016-11-21 04:37:34 -05:00
|
|
|
def blocked_mention?
|
2017-04-04 13:21:37 -04:00
|
|
|
FeedManager.instance.filter?(:mentions, @notification.mention.status, @recipient.id)
|
2016-11-21 04:37:34 -05:00
|
|
|
end
|
|
|
|
|
|
|
|
def blocked_favourite?
|
2017-07-22 10:36:36 -04:00
|
|
|
false
|
2016-11-21 04:37:34 -05:00
|
|
|
end
|
|
|
|
|
|
|
|
def blocked_follow?
|
|
|
|
false
|
|
|
|
end
|
|
|
|
|
|
|
|
def blocked_reblog?
|
Allow hiding of reblogs from followed users (#5762)
* Allow hiding of reblogs from followed users
This adds a new entry to the account menu to allow users to hide
future reblogs from a user (and then if they've done that, to show
future reblogs instead).
This does not remove or add historical reblogs from/to the user's
timeline; it only affects new statuses.
The API for this operates by sending a "reblogs" key to the follow
endpoint. If this is sent when starting a new follow, it will be
respected from the beginning of the follow relationship (even if
the follow request must be approved by the followee). If this is
sent when a follow relationship already exists, it will simply
update the existing follow relationship. As with the notification
muting, this will now return an object ({reblogs: [true|false]}) or
false for each follow relationship when requesting relationship
information for an account. This should cause few issues due to an
object being truthy in many languages, but some modifications may
need to be made in pickier languages.
Database changes: adds a show_reblogs column (default true,
non-nullable) to the follows and follow_requests tables. Because
these are non-nullable, we use the existing MigrationHelpers to
perform this change without locking those tables, although the
tables are likely to be small anyway.
Tests included.
See also <https://github.com/glitch-soc/mastodon/pull/212>.
* Rubocop fixes
* Code review changes
* Test fixes
This patchset closes #648 and resolves #3271.
* Rubocop fix
* Revert reblogs defaulting in argument, fix tests
It turns out we needed this for the same reason we needed it in muting:
if nil gets passed in somehow (most usually by an API client not passing
any value), we need to detect and handle it.
We could specify a default in the parameter and then also catch nil, but
there's no great reason to duplicate the default value.
2017-11-28 09:00:35 -05:00
|
|
|
@recipient.muting_reblogs?(@notification.from_account)
|
2016-11-21 04:37:34 -05:00
|
|
|
end
|
|
|
|
|
2016-12-26 15:52:03 -05:00
|
|
|
def blocked_follow_request?
|
|
|
|
false
|
|
|
|
end
|
|
|
|
|
2017-11-14 15:12:57 -05:00
|
|
|
def following_sender?
|
|
|
|
return @following_sender if defined?(@following_sender)
|
|
|
|
@following_sender = @recipient.following?(@notification.from_account) || @recipient.requested?(@notification.from_account)
|
|
|
|
end
|
|
|
|
|
|
|
|
def optional_non_follower?
|
|
|
|
@recipient.user.settings.interactions['must_be_follower'] && !@notification.from_account.following?(@recipient)
|
|
|
|
end
|
|
|
|
|
|
|
|
def optional_non_following?
|
|
|
|
@recipient.user.settings.interactions['must_be_following'] && !following_sender?
|
|
|
|
end
|
|
|
|
|
|
|
|
def direct_message?
|
|
|
|
@notification.type == :mention && @notification.target_status.direct_visibility?
|
|
|
|
end
|
|
|
|
|
|
|
|
def response_to_recipient?
|
|
|
|
@notification.target_status.in_reply_to_account_id == @recipient.id
|
|
|
|
end
|
|
|
|
|
|
|
|
def optional_non_following_and_direct?
|
|
|
|
direct_message? &&
|
|
|
|
@recipient.user.settings.interactions['must_be_following_dm'] &&
|
|
|
|
!following_sender? &&
|
|
|
|
!response_to_recipient?
|
|
|
|
end
|
|
|
|
|
|
|
|
def hellbanned?
|
|
|
|
@notification.from_account.silenced? && !following_sender?
|
|
|
|
end
|
|
|
|
|
|
|
|
def from_self?
|
|
|
|
@recipient.id == @notification.from_account.id
|
|
|
|
end
|
|
|
|
|
|
|
|
def domain_blocking?
|
|
|
|
@recipient.domain_blocking?(@notification.from_account.domain) && !following_sender?
|
|
|
|
end
|
|
|
|
|
2016-11-19 18:33:02 -05:00
|
|
|
def blocked?
|
2017-11-14 15:12:57 -05:00
|
|
|
blocked = @recipient.suspended? # Skip if the recipient account is suspended anyway
|
|
|
|
blocked ||= from_self? # Skip for interactions with self
|
|
|
|
blocked ||= domain_blocking? # Skip for domain blocked accounts
|
|
|
|
blocked ||= @recipient.blocking?(@notification.from_account) # Skip for blocked accounts
|
2017-11-14 21:56:41 -05:00
|
|
|
blocked ||= @recipient.muting_notifications?(@notification.from_account)
|
2017-11-14 15:12:57 -05:00
|
|
|
blocked ||= hellbanned? # Hellban
|
|
|
|
blocked ||= optional_non_follower? # Options
|
|
|
|
blocked ||= optional_non_following? # Options
|
|
|
|
blocked ||= optional_non_following_and_direct? # Options
|
Feature conversations muting (#3017)
* Add <ostatus:conversation /> tag to Atom input/output
Only uses ref attribute (not href) because href would be
the alternate link that's always included also.
Creates new conversation for every non-reply status. Carries
over conversation for every reply. Keeps remote URIs verbatim,
generates local URIs on the fly like the rest of them.
* Conversation muting - prevents notifications that reference a conversation
(including replies, favourites, reblogs) from being created. API endpoints
/api/v1/statuses/:id/mute and /api/v1/statuses/:id/unmute
Currently no way to tell when a status/conversation is muted, so the web UI
only has a "disable notifications" button, doesn't work as a toggle
* Display "Dismiss notifications" on all statuses in notifications column, not just own
* Add "muted" as a boolean attribute on statuses JSON
For now always false on contained reblogs, since it's only relevant for
statuses returned from the notifications endpoint, which are not nested
Remove "Disable notifications" from detailed status view, since it's
only relevant in the notifications column
* Up max class length
* Remove pending test for conversation mute
* Add tests, clean up
* Rename to "mute conversation" and "unmute conversation"
* Raise validation error when trying to mute/unmute status without conversation
2017-05-14 21:04:13 -04:00
|
|
|
blocked ||= conversation_muted?
|
2017-11-14 15:12:57 -05:00
|
|
|
blocked ||= send("blocked_#{@notification.type}?") # Type-dependent filters
|
2016-11-19 18:33:02 -05:00
|
|
|
blocked
|
|
|
|
end
|
|
|
|
|
Feature conversations muting (#3017)
* Add <ostatus:conversation /> tag to Atom input/output
Only uses ref attribute (not href) because href would be
the alternate link that's always included also.
Creates new conversation for every non-reply status. Carries
over conversation for every reply. Keeps remote URIs verbatim,
generates local URIs on the fly like the rest of them.
* Conversation muting - prevents notifications that reference a conversation
(including replies, favourites, reblogs) from being created. API endpoints
/api/v1/statuses/:id/mute and /api/v1/statuses/:id/unmute
Currently no way to tell when a status/conversation is muted, so the web UI
only has a "disable notifications" button, doesn't work as a toggle
* Display "Dismiss notifications" on all statuses in notifications column, not just own
* Add "muted" as a boolean attribute on statuses JSON
For now always false on contained reblogs, since it's only relevant for
statuses returned from the notifications endpoint, which are not nested
Remove "Disable notifications" from detailed status view, since it's
only relevant in the notifications column
* Up max class length
* Remove pending test for conversation mute
* Add tests, clean up
* Rename to "mute conversation" and "unmute conversation"
* Raise validation error when trying to mute/unmute status without conversation
2017-05-14 21:04:13 -04:00
|
|
|
def conversation_muted?
|
|
|
|
if @notification.target_status
|
|
|
|
@recipient.muting_conversation?(@notification.target_status.conversation)
|
|
|
|
else
|
|
|
|
false
|
|
|
|
end
|
|
|
|
end
|
|
|
|
|
2016-11-19 18:33:02 -05:00
|
|
|
def create_notification
|
|
|
|
@notification.save!
|
2016-12-26 15:52:03 -05:00
|
|
|
return unless @notification.browserable?
|
2017-07-06 22:02:06 -04:00
|
|
|
Redis.current.publish("timeline:#{@recipient.id}", Oj.dump(event: :notification, payload: InlineRenderer.render(@notification, @recipient, :notification)))
|
2017-07-13 16:15:32 -04:00
|
|
|
send_push_notifications
|
|
|
|
end
|
|
|
|
|
|
|
|
def send_push_notifications
|
2017-07-19 16:37:52 -04:00
|
|
|
# HACK: Can be caused by quickly unfavouriting a status, since creating
|
|
|
|
# a favourite and creating a notification are not wrapped in a transaction.
|
|
|
|
return if @notification.activity.nil?
|
|
|
|
|
|
|
|
sessions_with_subscriptions = @recipient.user.session_activations.where.not(web_push_subscription: nil)
|
|
|
|
sessions_with_subscriptions_ids = sessions_with_subscriptions.select { |session| session.web_push_subscription.pushable? @notification }.map(&:id)
|
2017-07-18 10:25:40 -04:00
|
|
|
|
|
|
|
WebPushNotificationWorker.push_bulk(sessions_with_subscriptions_ids) do |session_activation_id|
|
|
|
|
[session_activation_id, @notification.id]
|
|
|
|
end
|
2016-11-19 18:33:02 -05:00
|
|
|
end
|
|
|
|
|
|
|
|
def send_email
|
2017-05-06 17:06:52 -04:00
|
|
|
NotificationMailer.public_send(@notification.type, @recipient, @notification).deliver_later
|
2016-11-19 18:33:02 -05:00
|
|
|
end
|
|
|
|
|
|
|
|
def email_enabled?
|
2017-05-06 17:06:52 -04:00
|
|
|
@recipient.user.settings.notification_emails[@notification.type.to_s]
|
2016-11-19 18:33:02 -05:00
|
|
|
end
|
|
|
|
end
|