Age | Commit message (Collapse) | Author |
|
|
|
* Revert "Bump version to 1.4.4"
This reverts commit 1585b0c6cce6cebda3fdc8ba944aa2247e76d1be.
* Revert "Fix conversations (fixes #3869) (#3870)"
This reverts commit 15b43f555dcb06742c677d84c25d05774ef1bde2.
* Revert "Fix streaming server. Redis connection subscribe for each channel. (#3828)"
This reverts commit d8ec83280637e53ded67d4938a198cbeb9e8db05.
* Revert "Filter direct statuses in Status.as_home_timeline (#3842)"
This reverts commit bab5a18232a163b0c3c6a245f7f95d50d7022b36.
* Revert "Fix RemoteFollow behavior (#3868)"
This reverts commit a20cf3b64e93d764f1dfe88ecdb39f3fd4eefe03.
* Revert "Update fabricator for MediaAttachment to attach a file according to type (#3862)"
This reverts commit 356df7ae6b6edfc600fbc532f32fbc46314e00a0.
* Revert "Upgrade React Router (#3677)"
This reverts commit 8f03fdce7fa16fcaa829a40f395cefc85eb957d5.
* Revert "Do not call setState from unmounted component (#3853)"
This reverts commit 1fc6cb499742c1a872ad717a689c58a80aeb714d.
* Revert "Replace TextIconButton for SensitiveButton to IconButton (#3759)"
This reverts commit eb832e88f44d661a504a091defc051e052eb1252.
* Revert "Fix RTL detection on Ruby side (#3867)"
This reverts commit b16b69350eb4ded2e1011931433b51dac5e34b53.
* Revert "i18n: Fixed typo in Polish translation (#3864)"
This reverts commit da6fa029f66d50f38f2b6c85687994793f7766aa.
* Revert "Don't attach IntersectionObserver for wrapped statuses (#3863)"
This reverts commit 94ad0706f514e25c58c0a8f3201f96c1d1ccbbd8.
|
|
* Actually create conversations given explicit URIs
* Try to get the parent toot in before validation, to avoid creating a new conversation
|
|
The classes using Status.as_home_timeline, namely Feed and
PrecomputeFeedService are expected to filter direct statuses as
FanOutWriteService does, but their filtering were incomplete or missing.
This commit solves the problem by filtering direct statuses in
as_home_timeline as the other similar methods such as as_public_timeline
does.
|
|
* Invalid acct is an error. not "2 errors".
* Empty input should be different error from invalid acct
|
|
* chore(yarn): Remove react-router
* chore(yarn): Remove react-router-scroll
* chore(yarn): Remove history
* chore(yarn): Add react-router-dom
* chore: Remove usages of react-router-scroll
* refactor: Upgrade to react-router-web
* refactor: Use fork of react-router-scroll
This reverts commit 2ddea9a6c8d39fc64b7d0b587f3fbda7a45a7fa2.
* fix: Issues mentions in the PR feedback
|
|
Stop an executing task if the component already unmounted.
|
|
* Replace TextIconButton for SensitiveButton to IconButton
* line-height
|
|
This fixes below bugs:
* pipe characters being counted as RTL character
* only first word being checked
|
|
This fixes a bug that sometimes boosted statuses being hidden on scrolling.
Previously, we've attached IntersectionObserver twice for boosted statuses:
wrapper Status and wrapped Status. This will call intersection handler twice,
so this may results race condition...probably.
|
|
|
|
|
|
|
|
There was no link for visitors to follow to see the about page.
|
|
* Bring Toot button in line with counter
Both should use stringz I guess
* Use grapheme_length for character count
|
|
|
|
|
|
Rename Activitypub to ActivityPub
|
|
* Debounce autosuggestions
* Remove duplicate import
|
|
|
|
|
|
* Whitelist allowed classes for federated statuses
Allowed classes are currently:
- Any microformats class (h/p/u/dt/e-*)
- the classes mention, hashtag, ellipses and invisible.
this last one is somewhat suspect, but Mastodon currently uses it to render hidden link text.
resolved #3790
* Fix code style
|
|
|
|
|
|
FetchRemoteAccountService (#3642)
|
|
ancestors/descendants even if the viewer is anonymous (#3752)
|
|
|
|
mergeDeep also merges columns, but it should be replaced simply.
So in the new function, first apply mergeDeep except columns, and set default columns if columns unset.
|
|
account before removing content for quicker feedback to end-users
|
|
|
|
* Make Pubsubhubbub::DistributionWorker handle both single stream entry
arguments, as well as arrays of stream entries
* Add BatchedRemoveStatusService, make SuspendAccountService use it
* Improve method names
* Add test
* Add more tests
* Use PuSH payloads of 100 to have a clear mapping of
1000 input statuses -> 10 PuSH payloads
It was nice while it lasted
|
|
* Add form for account deletion
* If avatar or header are gone from source, remove them
* Add option to have SuspendAccountService remove user record, add tests
* Exclude suspended accounts from search
|
|
* Fix #2619 - When redis feed is empty, fall back to database
* Use redis value to return feed from database only while RegenerationWorker
hasn't finished running
* Fix specs
* Replace usage of reject!
|
|
|
|
joinmastodon.org (#3725)
|
|
|
|
|
|
* i18n: minor fix in Polish translation
* i18n
|
|
* Unread indicator was invisible behind column header, adjusted
* Unread indicator now a CSS pseudo-element
* Adjust flex
|
|
* Update Russian translation (pin)
|
|
follow up #3564
|
|
* Re-add clear notifications button
* remove connect() in column_settings
* one line
* remove unused props
|
|
|
|
TagManager.local_url? was sometimes called with an URI with a nil host,
leading to a crash in TagManager.local_url?. This fixes moves the
already-existing uri.host.blank? check in front to avoid this case.
|
|
of delete Salmon (#3672)
* Fix removal of status sending the original status to mentioned users instead
of delete Salmon, add test
* Create remove_status_service_spec.rb
|
|
* Move ancestors/descendants out of timelines reducer
* Refactor timelines reducer
All types of timelines now have a flat structure and use the same
reducer functions and actions
* Reintroduce some missing behaviours
* Fix wrong import in reports
* Fix includes typo
* Fix issue related to "next" pagination in timelines and notifications
* Fix bug with timeline's initial state, expandNotifications
|
|
```
DEPRECATION WARNING: The behavior of `attribute_changed?` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_change_to_attribute?` instead. (called from block in <class:Account> at /Users/rene/Workspace/personal/ruby/mastodon/app/models/account.rb:60)
DEPRECATION WARNING: The behavior of `attribute_changed?` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_change_to_attribute?` instead. (called from block in <class:Account> at /Users/rene/Workspace/personal/ruby/mastodon/app/models/account.rb:60)
DEPRECATION WARNING: The behavior of `attribute_changed?` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_change_to_attribute?` instead. (called from block in <class:Account> at /Users/rene/Workspace/personal/ruby/mastodon/app/models/account.rb:60)
DEPRECATION WARNING: The behavior of `attribute_changed?` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_change_to_attribute?` instead. (called from block in <class:Account> at /Users/rene/Workspace/personal/ruby/mastodon/app/models/account.rb:61)
DEPRECATION WARNING: The behavior of `attribute_changed?` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_change_to_attribute?` instead. (called from block in <class:Account> at /Users/rene/Workspace/personal/ruby/mastodon/app/models/account.rb:62)
DEPRECATION WARNING: The behavior of `attribute_changed?` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_change_to_attribute?` instead. (called from block in <class:Account> at /Users/rene/Workspace/personal/ruby/mastodon/app/models/account.rb:63)
```
Here's PR describing changes to Dirty API https://github.com/rails/rails/pull/25337
|
|
* Localize date in digest
* Cover NotificationMailer more
|
|
|
|
|