|
|
|
|
# frozen_string_literal: true
|
|
|
|
|
|
|
|
|
|
source 'https://rubygems.org'
|
|
|
|
|
ruby '>= 2.7.0', '< 3.3.0'
|
|
|
|
|
|
|
|
|
|
gem 'pkg-config', '~> 1.5'
|
|
|
|
|
|
|
|
|
|
gem 'puma', '~> 6.1'
|
|
|
|
|
gem 'rails', '~> 6.1.7'
|
|
|
|
|
gem 'sprockets', '~> 3.7.2'
|
|
|
|
|
gem 'thor', '~> 1.2'
|
|
|
|
|
gem 'rack', '~> 2.2.6'
|
|
|
|
|
|
|
|
|
|
gem 'haml-rails', '~>2.0'
|
|
|
|
|
gem 'pg', '~> 1.4'
|
|
|
|
|
gem 'makara', '~> 0.5'
|
|
|
|
|
gem 'pghero'
|
|
|
|
|
gem 'dotenv-rails', '~> 2.8'
|
|
|
|
|
|
|
|
|
|
gem 'aws-sdk-s3', '~> 1.119', require: false
|
|
|
|
|
gem 'fog-core', '<= 2.4.0'
|
|
|
|
|
gem 'fog-openstack', '~> 0.3', require: false
|
|
|
|
|
gem 'kt-paperclip', '~> 7.1', github: 'kreeti/kt-paperclip', ref: '11abf222dc31bff71160a1d138b445214f434b2b'
|
|
|
|
|
gem 'blurhash', '~> 0.1'
|
|
|
|
|
|
|
|
|
|
gem 'active_model_serializers', '~> 0.10'
|
|
|
|
|
gem 'addressable', '~> 2.8'
|
|
|
|
|
gem 'bootsnap', '~> 1.16.0', require: false
|
|
|
|
|
gem 'browser'
|
|
|
|
|
gem 'charlock_holmes', '~> 0.7.7'
|
|
|
|
|
gem 'chewy', '~> 7.2'
|
|
|
|
|
gem 'devise', '~> 4.9'
|
|
|
|
|
gem 'devise-two-factor', '~> 4.0'
|
|
|
|
|
|
|
|
|
|
group :pam_authentication, optional: true do
|
|
|
|
|
gem 'devise_pam_authenticatable2', '~> 9.2'
|
|
|
|
|
end
|
|
|
|
|
|
|
|
|
|
gem 'net-ldap', '~> 0.17'
|
|
|
|
|
gem 'omniauth-cas', '~> 2.0'
|
|
|
|
|
gem 'omniauth-saml', '~> 1.10'
|
|
|
|
|
gem 'omniauth_openid_connect', '~> 0.6.0'
|
|
|
|
|
gem 'omniauth', '~> 1.9'
|
|
|
|
|
gem 'omniauth-rails_csrf_protection', '~> 0.1'
|
|
|
|
|
|
|
|
|
|
gem 'color_diff', '~> 0.1'
|
|
|
|
|
gem 'discard', '~> 1.2'
|
|
|
|
|
gem 'doorkeeper', '~> 5.6'
|
|
|
|
|
gem 'ed25519', '~> 1.3'
|
|
|
|
|
gem 'fast_blank', '~> 1.0'
|
|
|
|
|
gem 'fastimage'
|
|
|
|
|
gem 'hiredis', '~> 0.6'
|
|
|
|
|
gem 'redis-namespace', '~> 1.10'
|
|
|
|
|
gem 'htmlentities', '~> 4.3'
|
|
|
|
|
gem 'http', '~> 5.1'
|
|
|
|
|
gem 'http_accept_language', '~> 2.1'
|
|
|
|
|
gem 'httplog', '~> 1.6.2'
|
|
|
|
|
gem 'idn-ruby', require: 'idn'
|
|
|
|
|
gem 'kaminari', '~> 1.2'
|
|
|
|
|
gem 'link_header', '~> 0.0'
|
|
|
|
|
gem 'mime-types', '~> 3.4.1', require: 'mime/types/columnar'
|
|
|
|
|
gem 'nokogiri', '~> 1.14'
|
|
|
|
|
gem 'nsa', '~> 0.2'
|
|
|
|
|
gem 'oj', '~> 3.14'
|
|
|
|
|
gem 'ox', '~> 2.14'
|
|
|
|
|
gem 'parslet'
|
|
|
|
|
gem 'posix-spawn'
|
|
|
|
|
gem 'public_suffix', '~> 5.0'
|
|
|
|
|
gem 'pundit', '~> 2.3'
|
|
|
|
|
gem 'premailer-rails'
|
|
|
|
|
gem 'rack-attack', '~> 6.6'
|
|
|
|
|
gem 'rack-cors', '~> 1.1', require: 'rack/cors'
|
|
|
|
|
gem 'rails-i18n', '~> 6.0'
|
|
|
|
|
gem 'rails-settings-cached', '~> 0.6', git: 'https://github.com/mastodon/rails-settings-cached.git', branch: 'v0.6.6-aliases-true'
|
|
|
|
|
gem 'redcarpet', '~> 3.6'
|
|
|
|
|
gem 'redis', '~> 4.5', require: ['redis', 'redis/connection/hiredis']
|
|
|
|
|
gem 'mario-redis-lock', '~> 1.2', require: 'redis_lock'
|
|
|
|
|
gem 'rqrcode', '~> 2.1'
|
|
|
|
|
gem 'ruby-progressbar', '~> 1.11'
|
|
|
|
|
gem 'sanitize', '~> 6.0'
|
|
|
|
|
gem 'scenic', '~> 1.7'
|
|
|
|
|
gem 'sidekiq', '~> 6.5'
|
|
|
|
|
gem 'sidekiq-scheduler', '~> 5.0'
|
|
|
|
|
gem 'sidekiq-unique-jobs', '~> 7.1'
|
|
|
|
|
gem 'sidekiq-bulk', '~> 0.2.0'
|
|
|
|
|
gem 'simple-navigation', '~> 4.4'
|
|
|
|
|
gem 'simple_form', '~> 5.2'
|
|
|
|
|
gem 'sprockets-rails', '~> 3.4', require: 'sprockets/railtie'
|
|
|
|
|
gem 'stoplight', '~> 3.0.1'
|
|
|
|
|
gem 'strong_migrations', '~> 0.7'
|
|
|
|
|
gem 'tty-prompt', '~> 0.23', require: false
|
|
|
|
|
gem 'twitter-text', '~> 3.1.0'
|
|
|
|
|
gem 'tzinfo-data', '~> 1.2022'
|
|
|
|
|
gem 'webpacker', '~> 5.4'
|
|
|
|
|
gem 'webpush', github: 'ClearlyClaire/webpush', ref: 'f14a4d52e201128b1b00245d11b6de80d6cfdcd9'
|
|
|
|
|
gem 'webauthn', '~> 3.0'
|
|
|
|
|
|
|
|
|
|
gem 'json-ld'
|
|
|
|
|
gem 'json-ld-preloaded', '~> 3.2'
|
|
|
|
|
gem 'rdf-normalize', '~> 0.5'
|
|
|
|
|
|
|
|
|
|
group :development, :test do
|
|
|
|
|
gem 'fabrication', '~> 2.30'
|
|
|
|
|
gem 'fuubar', '~> 2.5'
|
|
|
|
|
gem 'i18n-tasks', '~> 1.0', require: false
|
|
|
|
|
gem 'rspec-rails', '~> 6.0'
|
|
|
|
|
gem 'rspec_chunked', '~> 0.6'
|
linting: RuboCop update, config fixes (#20574)
* fix(rubocop): update gems and add performance and rspec
fix(rubocop): update gems and add performance and rspec
- update present rubocop gems
- add rubocop-rspec and rubocop-performance gems
- move rubocop gems to gem group :development, :test in order to
make linting in a github action that runs with RAILS_ENV=test possible
* feat(rubocop): disable some annoyance RSpec cops
To mee these prooved to be more annoying than helpful.
If not agreed, they can be enabled any time.
* fix(rubocop): do not ignore spec/**/*
Because rubocop-rspec should lint the specs as well, and they
deserve to be readable in general. It is relevant code, after all.
* fix(rubocop): change ignore db/**/* to db/schema.rb
because rails cops do some lints for migrations.
E.g. reversable migrations linting and more.
* fix(rubocop): tune rules configs
Bunch of commits squashed:
fix(rubocop): enable Layout/LineLength cop
Because this project has code with line lenghts > 500 chars.
This is not good practice at all, so I strongly suggest to
change the practice in the future.
But allow heredoc, URI and comments to still be long lines
and make the default Max: 120 explicit, by repeating it in the
config. To me this max length seems reasonable. Perhaps
a bit more could be ok for some. But > 500 chars in one line
Seems to be way too long IMHO.
fix(rubocop): Metrics/CyclomaticComplexity Max to 12
The default is 7, perhaps quite strict. But 25 is too loose,
the rule becomes pointless like that.
fix(rubocop): AllCops ruby version, cacheing and more info
- fix the target ruby version from 2.5 to 3.0
- have the cop error messages to be more informative and helpful
- enable cacheing in /tmp
fix(rubocop): Metrics/AbcSize to 34 from 115
Rubocops default is 17. If the rule is at 115 is becomes
pointless.
fix(rubocop): Metrics/BlockLength improvements
- instead of ignoring tasks completely, ignore only the
long blocks that are specific to tasks (task, namespace)
- ignore also concern specific block methods (included, class_methods)
fix(rubocop): Metrics/ClassLength count heredoc array as one line
fix(rubocop): Metrics/MethodLength Max to 25
- the default is 10, but 65 is too loose, so perhaps 25?
fix(rubocop): Metrics/ModuleLength array and heredoc count as one
fix(rubocop): Metrics/PerceivedComplexity to 16 from 25
Rubocops default is 8, so how about only doubling that, instead
of > than tripple it?
fix(rubocop): enable Style/RedundantAssignment
Because I think that this rule would never really hurt,
but improve code quality and readability.
fix(rubocop): enable Style/RescueStandardError
I think everyone that ever had to debug what this can bring
will hopefully agree that this rule totally makes sense.
In the super rare exeptions where this is totally needed,
it can be excluded by disabling comment in that place.
fix(rubocop): Metrics/ParameterLists add explicit defaults and some excludes
2 years ago
|
|
|
gem 'rubocop-performance', require: false
|
|
|
|
|
gem 'rubocop-rails', require: false
|
|
|
|
|
gem 'rubocop-rspec', require: false
|
|
|
|
|
gem 'rubocop', require: false
|
|
|
|
|
end
|
|
|
|
|
|
|
|
|
|
group :production, :test do
|
|
|
|
|
gem 'private_address_check', '~> 0.5'
|
|
|
|
|
end
|
|
|
|
|
|
|
|
|
|
group :test do
|
|
|
|
|
gem 'capybara', '~> 3.38'
|
|
|
|
|
gem 'faker', '~> 3.1'
|
|
|
|
|
gem 'json-schema', '~> 3.0'
|
|
|
|
|
gem 'rack-test', '~> 2.0'
|
|
|
|
|
gem 'rails-controller-testing', '~> 1.0'
|
|
|
|
|
gem 'rspec_junit_formatter', '~> 0.6'
|
|
|
|
|
gem 'rspec-sidekiq', '~> 3.1'
|
|
|
|
|
gem 'simplecov', '~> 0.22', require: false
|
|
|
|
|
gem 'webmock', '~> 3.18'
|
|
|
|
|
end
|
|
|
|
|
|
|
|
|
|
group :development do
|
|
|
|
|
gem 'active_record_query_trace', '~> 1.8'
|
|
|
|
|
gem 'annotate', '~> 3.2'
|
|
|
|
|
gem 'better_errors', '~> 2.9'
|
|
|
|
|
gem 'binding_of_caller', '~> 1.0'
|
|
|
|
|
gem 'bullet', '~> 7.0'
|
|
|
|
|
gem 'letter_opener', '~> 1.8'
|
|
|
|
|
gem 'letter_opener_web', '~> 2.0'
|
|
|
|
|
gem 'memory_profiler'
|
|
|
|
|
gem 'brakeman', '~> 5.4', require: false
|
|
|
|
|
gem 'bundler-audit', '~> 0.9', require: false
|
|
|
|
|
|
|
|
|
|
gem 'capistrano', '~> 3.17'
|
|
|
|
|
gem 'capistrano-rails', '~> 1.6'
|
|
|
|
|
gem 'capistrano-rbenv', '~> 2.2'
|
|
|
|
|
gem 'capistrano-yarn', '~> 2.0'
|
|
|
|
|
|
|
|
|
|
gem 'stackprof'
|
|
|
|
|
end
|
|
|
|
|
|
|
|
|
|
group :production do
|
|
|
|
|
gem 'lograge', '~> 0.12'
|
|
|
|
|
end
|
|
|
|
|
|
|
|
|
|
gem 'concurrent-ruby', require: false
|
|
|
|
|
gem 'connection_pool', require: false
|
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
4 years ago
|
|
|
gem 'xorcist', '~> 1.1'
|
Revamp post filtering system (#18058)
* Add model for custom filter keywords
* Use CustomFilterKeyword internally
Does not change the API
* Fix /filters/edit and /filters/new
* Add migration tests
* Remove whole_word column from custom_filters (covered by custom_filter_keywords)
* Redesign /filters
Instead of a list, present a card that displays more information and handles
multiple keywords per filter.
* Redesign /filters/new and /filters/edit to add and remove keywords
This adds a new gem dependency: cocoon, as well as a npm dependency:
cocoon-js-vanilla. Those are used to easily populate and remove form fields
from the user interface when manipulating multiple keyword filters at once.
* Add /api/v2/filters to edit filter with multiple keywords
Entities:
- `Filter`: `id`, `title`, `filter_action` (either `hide` or `warn`), `context`
`keywords`
- `FilterKeyword`: `id`, `keyword`, `whole_word`
API endpoits:
- `GET /api/v2/filters` to list filters (including keywords)
- `POST /api/v2/filters` to create a new filter
`keywords_attributes` can also be passed to create keywords in one request
- `GET /api/v2/filters/:id` to read a particular filter
- `PUT /api/v2/filters/:id` to update a new filter
`keywords_attributes` can also be passed to edit, delete or add keywords in
one request
- `DELETE /api/v2/filters/:id` to delete a particular filter
- `GET /api/v2/filters/:id/keywords` to list keywords for a filter
- `POST /api/v2/filters/:filter_id/keywords/:id` to add a new keyword to a
filter
- `GET /api/v2/filter_keywords/:id` to read a particular keyword
- `PUT /api/v2/filter_keywords/:id` to edit a particular keyword
- `DELETE /api/v2/filter_keywords/:id` to delete a particular keyword
* Change from `irreversible` boolean to `action` enum
* Remove irrelevent `irreversible_must_be_within_context` check
* Fix /filters/new and /filters/edit with update for filter_action
* Fix Rubocop/Codeclimate complaining about task names
* Refactor FeedManager#phrase_filtered?
This moves regexp building and filter caching to the `CustomFilter` class.
This does not change the functional behavior yet, but this changes how the
cache is built, doing per-custom_filter regexps so that filters can be matched
independently, while still offering caching.
* Perform server-side filtering and output result in REST API
* Fix numerous filters_changed events being sent when editing multiple keywords at once
* Add some tests
* Use the new API in the WebUI
- use client-side logic for filters we have fetched rules for.
This is so that filter changes can be retroactively applied without
reloading the UI.
- use server-side logic for filters we haven't fetched rules for yet
(e.g. network error, or initial timeline loading)
* Minor optimizations and refactoring
* Perform server-side filtering on the streaming server
* Change the wording of filter action labels
* Fix issues pointed out by linter
* Change design of “Show anyway” link in accordence to review comments
* Drop “irreversible” filtering behavior
* Move /api/v2/filter_keywords to /api/v1/filters/keywords
* Rename `filter_results` attribute to `filtered`
* Rename REST::LegacyFilterSerializer to REST::V1::FilterSerializer
* Fix systemChannelId value in streaming server
* Simplify code by removing client-side filtering code
The simplifcation comes at a cost though: filters aren't retroactively
applied anymore.
2 years ago
|
|
|
gem 'cocoon', '~> 1.2'
|
|
|
|
|
|
|
|
|
|
gem 'net-http', '~> 0.3.2'
|
