mastodon - Plural Café fork of Mastodon/Glitch Social

Age	Commit message (Collapse)	Author
2023-03-21	Refactoring relations_map (#24195)	Takeshi Umeda

2022-11-10	Remove dead code and refactor status threading code (#20357)	Claire
	* Remove dead code * Remove unneeded/broken parameters and refactor descendant computation
2021-01-10	Optimize map { ... }.compact calls (#15513)	luigi
	* Optimize map { ... }.compact using Enumerable#filter_map, supported since Ruby 2.7 * Add poyfill for Enumerable#filter_map
2020-01-11	Refactor StatusThreadingConcern (#9626)	ysksn
	* Remove #filter_from_context? * Create scope Status.with_accounts Retrieving AR objects should be their model's scope
2019-02-28	Improved remote thread fetching (#10106)	ThibG
	* Fetch up to 5 replies when discovering a new remote status This is used for resolving threads downwards. The originating server must add a “replies” attributes with such replies for it to be useful. * Add some tests for ActivityPub::FetchRepliesWorker * Add specs for ActivityPub::FetchRepliesService * Serialize up to 5 public self-replies for ActivityPub notes * Add specs for ActivityPub::NoteSerializer * Move exponential backoff logic to a worker concern * Fetch first page of paginated collections when fetching thread replies * Add specs for paginated collections in replies * Move Note replies serialization to a first CollectionPage The collection isn't actually paginable yet as it has no id nor a `next` field. This may come in another PR. * Use pluck(:uri) instead of map(&:uri) to improve performances * Fix fetching replies when they are in a CollectionPage
2018-11-24	Sort self-replies to the top of descendants (#9320)	Eugen Rochko
	Fix #6463
2018-11-23	Revert "Sort self-replies to the top of the thread (#9296)" (#9335)	Eugen Rochko
	This reverts commit 074960bb0fa59664c0ae1a35ef80301f5033700d. Fix #9315
2018-11-16	Sort self-replies to the top of the thread (#9296)	Eugen Rochko
	Fix #6463
2018-06-04	Fix context performance by partially reverting #7083 (#7734)	nightpool
	* Fix context performance by partially reverting #7083 * Fix code style issue * fix off-by-1 error in thread limits * code style fix
2018-05-13	Fix nil error in StatusFilter (#7470)	Eugen Rochko
	Fix #7462
2018-05-03	Fix n+1 queries in StatusThreadingConcern (#7321)	Eugen Rochko

2018-04-23	Paginate descendant statuses in public page (#7148)	Akihiko Odaki

2018-04-11	Paginate ancestor statuses in public page (#7102)	Akihiko Odaki
	This also limits the statuses returned by API, but pagination is not implemented in Web API yet. I still expect it brings user experience better than making a user wait to fetch all ancestor statuses and flooding the column with them.
2018-04-09	Exclude status itself from context query (#7083)	Akihiko Odaki
	ancestor_statuses and descendant_statuses used to include the root status itself, but the behavior is confusing because the root status is not an ancestor nor descendant.
2017-06-05	Introduce StatusThreadingConcern (#3490)	Matt Jankowski
	* Add a StatusFilter class to identify visibility of statuses by accounts * Extract StatusThreadingConcern from Status * Clarify purpose of checking for nil account