about summary refs log tree commit diff
path: root/app
AgeCommit message (Collapse)Author
2020-11-01Federate follower-only posts with strict audienceFire Demon
2020-11-01Federate public scope as unlisted unless tags are presentFire Demon
2020-10-31Ignore case of username confirmationFire Demon
2020-10-31Do not cache web app custom CSSFire Demon
2020-10-31Add lowercase modeFire Demon
2020-10-29Display an error if registration was rejected due to spamFire Demon
2020-10-28Make push notifications optionalFire Demon
2020-10-28Merge remote-tracking branch 'upstream/master' into devFire Demon
2020-10-28Do not deliver deletes to servers which a user has had no contactFire Demon
2020-10-28If a user adds a hard mute, it no longer cause a defederationFire Demon
2020-10-28Fix IP blocks in admin panelThibaut Girka
It was broken due to discrepancies between upstream and glitch-soc's theming system.
2020-10-27Add option to hide notification markersThibaut Girka
2020-10-26Add local setting for pop-in player positionThibaut Girka
2020-10-26Add setting to disable the pop-in playerThibaut Girka
2020-10-26Respect glitch-soc's reply counter setting in the pop-in playerThibaut Girka
2020-10-26[Glitch] Fix regressions in icon buttons in web UIEugen Rochko
Port a549415868fe23e0afaf258c17afafac117d0163 to glitch-soc Signed-off-by: Thibaut Girka <thib@sitedethib.com>
2020-10-26[Glitch] Add pop-out player for audio/video in web UIEugen Rochko
port d88a79b4566869ede24958fbff946e357bbb3cb9 to glitch-soc Signed-off-by: Thibaut Girka <thib@sitedethib.com>
2020-10-26[Glitch] Fix follow request notificationsThibG
Port 3678b10823a691256ad63c1c4df8dc659dfc3bc0 to glitch-soc Signed-off-by: Thibaut Girka <thib@sitedethib.com>
2020-10-26Merge branch 'master' into glitch-soc/merge-upstreamThibaut Girka
Conflicts: - `app/services/process_mentions_service.rb`: glitch-soc local-only handling, ported upstream changes
2020-10-26Fix follow request notifications (#15048)ThibG
2020-10-24Allow 12 weeks to pass between last sign-in before verifying accountFire Demon
2020-10-23Fix followers synchronization mechanism not being triggered on mentions (#15026)ThibG
e.g. if someone on an instance that previously had followers gets mentioned in a private toot, before this PR, they would not receive a Collection-Synchronization header and may show the toot to the former followers in addition to the mentioned person.
2020-10-23Fix account processing failing because of large collections (#15027)ThibG
Fixes #15025
2020-10-22Fix spellingFire Demon
2020-10-22Show boosts of followed authors in homeFire Demon
2020-10-22Use mentioned account IDs rather than the mention IDs themselves!Fire Demon
2020-10-22Update schemaFire Demon
2020-10-22Merge remote-tracking branch 'upstream/master' into merge-glitchFire Demon
2020-10-21Pluck status IDs instead of using select()Fire Demon
2020-10-21When a local user blocks another account, also defederate interactions ↵Fire Demon
between them
2020-10-21Reciprocate incoming blocksFire Demon
2020-10-21Limit unpublishing to local postsFire Demon
2020-10-21When unpublishing, defederate post before setting it local-onlyFire Demon
2020-10-21[Glitch] Fix strings that could not be translatedmayaeh
Port fb5f3be18f50eb5657479196e29d13a905c43ac8 to glitch-soc Signed-off-by: Thibaut Girka <thib@sitedethib.com>
2020-10-21[Glitch] Change how missing desktop notifications permission is displayedEugen Rochko
Port a69ca294738dbe22bacaf9f1fc5a551d99797b35 to glitch-soc Signed-off-by: Thibaut Girka <thib@sitedethib.com>
2020-10-21Move columns-related CSS rules into the appropriate filesThibaut Girka
2020-10-21[Glitch] Fix browser notification permission request logicThibG
Port f54ca3d08e068af07a5b7a8b139e7658b3236db8 to glitch-soc Signed-off-by: Thibaut Girka <thib@sitedethib.com>
2020-10-21[Glitch] Add duration parameter to muting.OSAMU SATO
Port 96761752eccfc0d239974a24e0cc2d74c6aee7ac to glitch-soc Signed-off-by: Thibaut Girka <thib@sitedethib.com>
2020-10-21[Glitch] Change how CDN_HOST is passed down to make assets build reproducibleThibG
Port 4c45b43cb8a3d902c130729d36d559ec9de23d3e to glitch-soc Signed-off-by: Thibaut Girka <thib@sitedethib.com>
2020-10-21[Glitch] Fix unread notification marker not updating when mounting columnThibG
Port dac3e362fd5c3d1be9e5d89149049a7eb2c6bbc4 to glitch-soc Signed-off-by: Thibaut Girka <thib@sitedethib.com>
2020-10-21[Glitch] Ignore alt-key hotkeys in text fieldsThibG
Port 63770d3aac1611155213e4c903424849cc254519 to glitch-soc Signed-off-by: Thibaut Girka <thib@sitedethib.com>
2020-10-21[Glitch] Fix mark as read in notifications to be saved immediatelyTakeshi Umeda
Port bec8b12bb52a57b54b66899b2650a5611d9bd561 to glitch-soc Signed-off-by: Thibaut Girka <thib@sitedethib.com>
2020-10-21[Glitch] Fix bell button causing a brief “Cancel follow request” on ↵ThibG
locked accounts Port 82951920f7321fefbdf0628cbb70f2f490f7b716 to glitch-soc Signed-off-by: Thibaut Girka <thib@sitedethib.com>
2020-10-21Merge branch 'master' into glitch-soc/merge-upstreamThibaut Girka
Conflicts: - `.github/dependabot.yml`: Updated upstream, we deleted it to not be flooded by Depandabot. Kept deleted. - `Gemfile.lock`: Puma updated on both sides, went for the most recent version. - `app/controllers/api/v1/mutes_controller.rb`: Upstream updated the serializer to support timed mutes, while glitch-soc added a custom API ages ago to get information that is already available elsewhere. Dropped the glitch-soc-specific API, went with upstream changes. - `app/javascript/core/admin.js`: Conflict due to changing how assets are loaded. Went with upstream. - `app/javascript/packs/public.js`: Conflict due to changing how assets are loaded. Went with upstream. - `app/models/mute.rb`: 🤷 - `app/models/user.rb`: New user setting added upstream while we have glitch-soc-specific user settings. Added upstream's user setting. - `config/settings.yml`: Upstream added a new user setting close to a user setting we had changed the defaults for. Added the new upstream setting. - `package.json`: Upstream dependency updated “too close” to a glitch-soc-specific dependency. No real conflict. Updated the dependency.
2020-10-21Add follower synchronization mechanism (#14510)ThibG
* 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-21Rename Fediverse timeline to the TavernFire Demon
2020-10-21Merge remote-tracking branch 'upstream/master' into devFire Demon
2020-10-21When a local user blocks a server, ask the server to remove their dataFire Demon
2020-10-21Make receiving boosts from Tavern timeline in home feed opt-in; always ↵Fire Demon
aggregate boosts
2020-10-20Removed disabling comments for Style/MethodMissingSuper (#15014)abcang
* Removed disabling comments for Style/MethodMissingSuper * Update rubocop for codeclimate
generated by cgit-pink (git 2.37.1) at 2024-11-09 23:29:12 +0000