2016-11-15 17:56:29 +02:00
|
|
|
# frozen_string_literal: true
|
2023-02-20 07:58:28 +02:00
|
|
|
|
2017-05-02 03:14:47 +03:00
|
|
|
# == Schema Information
|
|
|
|
#
|
|
|
|
# Table name: follows
|
|
|
|
#
|
2018-04-23 12:29:17 +03:00
|
|
|
# id :bigint(8) not null, primary key
|
2017-05-02 03:14:47 +03:00
|
|
|
# created_at :datetime not null
|
|
|
|
# updated_at :datetime not null
|
2018-04-23 12:29:17 +03:00
|
|
|
# account_id :bigint(8) not null
|
|
|
|
# target_account_id :bigint(8) not null
|
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 16:00:35 +02:00
|
|
|
# show_reblogs :boolean default(TRUE), not null
|
2018-05-04 22:14:34 +03:00
|
|
|
# uri :string
|
2020-09-18 18:26:45 +03:00
|
|
|
# notify :boolean default(FALSE), not null
|
2022-09-21 00:51:21 +03:00
|
|
|
# languages :string is an Array
|
2017-05-02 03:14:47 +03:00
|
|
|
#
|
2016-11-15 17:56:29 +02:00
|
|
|
|
2016-08-17 18:56:23 +03:00
|
|
|
class Follow < ApplicationRecord
|
2016-11-09 18:48:44 +02:00
|
|
|
include Paginable
|
2018-02-18 04:14:46 +02:00
|
|
|
include RelationshipCacheable
|
2020-03-08 16:17:39 +02:00
|
|
|
include RateLimitable
|
2020-12-27 00:52:46 +02:00
|
|
|
include FollowLimitable
|
2020-03-08 16:17:39 +02:00
|
|
|
|
|
|
|
rate_limit by: :account, family: :follows
|
2016-03-25 03:13:30 +02:00
|
|
|
|
2018-11-19 01:43:52 +02:00
|
|
|
belongs_to :account
|
|
|
|
belongs_to :target_account, class_name: 'Account'
|
2016-02-22 17:00:20 +02:00
|
|
|
|
2016-11-21 15:59:13 +02:00
|
|
|
has_one :notification, as: :activity, dependent: :destroy
|
|
|
|
|
2016-02-23 20:17:37 +02:00
|
|
|
validates :account_id, uniqueness: { scope: :target_account_id }
|
2022-09-21 00:51:21 +03:00
|
|
|
validates :languages, language: true
|
2017-05-23 14:12:19 +03:00
|
|
|
|
|
|
|
scope :recent, -> { reorder(id: :desc) }
|
2018-05-04 22:14:34 +03:00
|
|
|
|
|
|
|
def local?
|
|
|
|
false # Force uri_for to use uri attribute
|
|
|
|
end
|
|
|
|
|
2018-08-17 17:24:56 +03:00
|
|
|
def revoke_request!
|
2022-09-21 00:51:21 +03:00
|
|
|
FollowRequest.create!(account: account, target_account: target_account, show_reblogs: show_reblogs, notify: notify, languages: languages, uri: uri)
|
2018-08-17 17:24:56 +03:00
|
|
|
destroy!
|
|
|
|
end
|
|
|
|
|
2018-05-04 22:14:34 +03:00
|
|
|
before_validation :set_uri, only: :create
|
2018-11-19 01:43:52 +02:00
|
|
|
after_create :increment_cache_counters
|
Add follower synchronization mechanism (#14510)
* Add support for followers synchronization on the receiving end
Check the `collectionSynchronization` attribute on `Create` and `Announce`
activities and synchronize followers from provided collection if possible.
* Add tests for followers synchronization on the receiving end
* Add support for follower synchronization on the sender's end
* Add tests for the sending end
* Switch from AS attributes to HTTP header
Replace the custom `collectionSynchronization` ActivityStreams attribute by
an HTTP header (`X-AS-Collection-Synchronization`) with the same syntax as
the `Signature` header and the following fields:
- `collectionId` to specify which collection to synchronize
- `digest` for the SHA256 hex-digest of the list of followers known on the
receiving instance (where “receiving instance” is determined by accounts
sharing the same host name for their ActivityPub actor `id`)
- `url` of a collection that should be fetched by the instance actor
Internally, move away from the webfinger-based `domain` attribute and use
account `uri` prefix to group accounts.
* Add environment variable to disable followers synchronization
Since the whole mechanism relies on some new preconditions that, in some
extremely rare cases, might not be met, add an environment variable
(DISABLE_FOLLOWERS_SYNCHRONIZATION) to disable the mechanism altogether and
avoid followers being incorrectly removed.
The current conditions are:
1. all managed accounts' actor `id` and inbox URL have the same URI scheme and
netloc.
2. all accounts whose actor `id` or inbox URL share the same URI scheme and
netloc as a managed account must be managed by the same Mastodon instance
as well.
As far as Mastodon is concerned, breaking those preconditions require extensive
configuration changes in the reverse proxy and might also cause other issues.
Therefore, this environment variable provides a way out for people with highly
unusual configurations, and can be safely ignored for the overwhelming majority
of Mastodon administrators.
* Only set follower synchronization header on non-public statuses
This is to avoid unnecessary computations and allow Follow-related
activities to be handled by the usual codepath instead of going through
the synchronization mechanism (otherwise, any Follow/Undo/Accept activity
would trigger the synchronization mechanism even if processing the activity
itself would be enough to re-introduce synchronization)
* Change how ActivityPub::SynchronizeFollowersService handles follow requests
If the remote lists a local follower which we only know has sent a follow
request, consider the follow request as accepted instead of sending an Undo.
* Integrate review feeback
- rename X-AS-Collection-Synchronization to Collection-Synchronization
- various minor refactoring and code style changes
* Only select required fields when computing followers_hash
* Use actor URI rather than webfinger domain in synchronization endpoint
* Change hash computation to be a XOR of individual hashes
Makes it much easier to be memory-efficient, and avoid sorting discrepancy issues.
* Marginally improve followers_hash computation speed
* Further improve hash computation performances by using pluck_each
2020-10-21 19:04:09 +03:00
|
|
|
after_create :invalidate_hash_cache
|
2018-08-09 16:24:29 +03:00
|
|
|
after_destroy :remove_endorsements
|
2018-11-19 01:43:52 +02:00
|
|
|
after_destroy :decrement_cache_counters
|
Add follower synchronization mechanism (#14510)
* Add support for followers synchronization on the receiving end
Check the `collectionSynchronization` attribute on `Create` and `Announce`
activities and synchronize followers from provided collection if possible.
* Add tests for followers synchronization on the receiving end
* Add support for follower synchronization on the sender's end
* Add tests for the sending end
* Switch from AS attributes to HTTP header
Replace the custom `collectionSynchronization` ActivityStreams attribute by
an HTTP header (`X-AS-Collection-Synchronization`) with the same syntax as
the `Signature` header and the following fields:
- `collectionId` to specify which collection to synchronize
- `digest` for the SHA256 hex-digest of the list of followers known on the
receiving instance (where “receiving instance” is determined by accounts
sharing the same host name for their ActivityPub actor `id`)
- `url` of a collection that should be fetched by the instance actor
Internally, move away from the webfinger-based `domain` attribute and use
account `uri` prefix to group accounts.
* Add environment variable to disable followers synchronization
Since the whole mechanism relies on some new preconditions that, in some
extremely rare cases, might not be met, add an environment variable
(DISABLE_FOLLOWERS_SYNCHRONIZATION) to disable the mechanism altogether and
avoid followers being incorrectly removed.
The current conditions are:
1. all managed accounts' actor `id` and inbox URL have the same URI scheme and
netloc.
2. all accounts whose actor `id` or inbox URL share the same URI scheme and
netloc as a managed account must be managed by the same Mastodon instance
as well.
As far as Mastodon is concerned, breaking those preconditions require extensive
configuration changes in the reverse proxy and might also cause other issues.
Therefore, this environment variable provides a way out for people with highly
unusual configurations, and can be safely ignored for the overwhelming majority
of Mastodon administrators.
* Only set follower synchronization header on non-public statuses
This is to avoid unnecessary computations and allow Follow-related
activities to be handled by the usual codepath instead of going through
the synchronization mechanism (otherwise, any Follow/Undo/Accept activity
would trigger the synchronization mechanism even if processing the activity
itself would be enough to re-introduce synchronization)
* Change how ActivityPub::SynchronizeFollowersService handles follow requests
If the remote lists a local follower which we only know has sent a follow
request, consider the follow request as accepted instead of sending an Undo.
* Integrate review feeback
- rename X-AS-Collection-Synchronization to Collection-Synchronization
- various minor refactoring and code style changes
* Only select required fields when computing followers_hash
* Use actor URI rather than webfinger domain in synchronization endpoint
* Change hash computation to be a XOR of individual hashes
Makes it much easier to be memory-efficient, and avoid sorting discrepancy issues.
* Marginally improve followers_hash computation speed
* Further improve hash computation performances by using pluck_each
2020-10-21 19:04:09 +03:00
|
|
|
after_destroy :invalidate_hash_cache
|
2018-05-04 22:14:34 +03:00
|
|
|
|
|
|
|
private
|
|
|
|
|
|
|
|
def set_uri
|
|
|
|
self.uri = ActivityPub::TagManager.instance.generate_uri_for(self) if uri.nil?
|
|
|
|
end
|
2018-08-09 16:24:29 +03:00
|
|
|
|
|
|
|
def remove_endorsements
|
|
|
|
AccountPin.where(target_account_id: target_account_id, account_id: account_id).delete_all
|
|
|
|
end
|
2018-11-19 01:43:52 +02:00
|
|
|
|
|
|
|
def increment_cache_counters
|
|
|
|
account&.increment_count!(:following_count)
|
|
|
|
target_account&.increment_count!(:followers_count)
|
|
|
|
end
|
|
|
|
|
|
|
|
def decrement_cache_counters
|
|
|
|
account&.decrement_count!(:following_count)
|
|
|
|
target_account&.decrement_count!(:followers_count)
|
|
|
|
end
|
Add follower synchronization mechanism (#14510)
* Add support for followers synchronization on the receiving end
Check the `collectionSynchronization` attribute on `Create` and `Announce`
activities and synchronize followers from provided collection if possible.
* Add tests for followers synchronization on the receiving end
* Add support for follower synchronization on the sender's end
* Add tests for the sending end
* Switch from AS attributes to HTTP header
Replace the custom `collectionSynchronization` ActivityStreams attribute by
an HTTP header (`X-AS-Collection-Synchronization`) with the same syntax as
the `Signature` header and the following fields:
- `collectionId` to specify which collection to synchronize
- `digest` for the SHA256 hex-digest of the list of followers known on the
receiving instance (where “receiving instance” is determined by accounts
sharing the same host name for their ActivityPub actor `id`)
- `url` of a collection that should be fetched by the instance actor
Internally, move away from the webfinger-based `domain` attribute and use
account `uri` prefix to group accounts.
* Add environment variable to disable followers synchronization
Since the whole mechanism relies on some new preconditions that, in some
extremely rare cases, might not be met, add an environment variable
(DISABLE_FOLLOWERS_SYNCHRONIZATION) to disable the mechanism altogether and
avoid followers being incorrectly removed.
The current conditions are:
1. all managed accounts' actor `id` and inbox URL have the same URI scheme and
netloc.
2. all accounts whose actor `id` or inbox URL share the same URI scheme and
netloc as a managed account must be managed by the same Mastodon instance
as well.
As far as Mastodon is concerned, breaking those preconditions require extensive
configuration changes in the reverse proxy and might also cause other issues.
Therefore, this environment variable provides a way out for people with highly
unusual configurations, and can be safely ignored for the overwhelming majority
of Mastodon administrators.
* Only set follower synchronization header on non-public statuses
This is to avoid unnecessary computations and allow Follow-related
activities to be handled by the usual codepath instead of going through
the synchronization mechanism (otherwise, any Follow/Undo/Accept activity
would trigger the synchronization mechanism even if processing the activity
itself would be enough to re-introduce synchronization)
* Change how ActivityPub::SynchronizeFollowersService handles follow requests
If the remote lists a local follower which we only know has sent a follow
request, consider the follow request as accepted instead of sending an Undo.
* Integrate review feeback
- rename X-AS-Collection-Synchronization to Collection-Synchronization
- various minor refactoring and code style changes
* Only select required fields when computing followers_hash
* Use actor URI rather than webfinger domain in synchronization endpoint
* Change hash computation to be a XOR of individual hashes
Makes it much easier to be memory-efficient, and avoid sorting discrepancy issues.
* Marginally improve followers_hash computation speed
* Further improve hash computation performances by using pluck_each
2020-10-21 19:04:09 +03:00
|
|
|
|
|
|
|
def invalidate_hash_cache
|
|
|
|
return if account.local? && target_account.local?
|
|
|
|
|
|
|
|
Rails.cache.delete("followers_hash:#{target_account_id}:#{account.synchronization_uri_prefix}")
|
|
|
|
end
|
2016-02-22 17:00:20 +02:00
|
|
|
end
|