Folo icon indicating copy to clipboard operation
Folo copied to clipboard

Add chronological (oldest to newest) sorting option for content feeds

Open forkmax opened this issue 1 year ago โ€ข 1 comments

Clear and concise description of the problem

Description

Currently, Follow displays content in reverse chronological order (newest to oldest) across all feed types including articles, Twitter posts, and Weibo posts. While this is common for social media platforms, it can sometimes disrupt the natural reading flow, especially in the following scenarios:

Current Issues:

  • When reading Twitter threads, we often see replies before the original post, making it difficult to understand the context
  • For article series or sequential content, newer posts appear first, forcing readers to scroll down to find the beginning
  • Following story developments or news updates becomes challenging as we need to read backwards

Feature Request: I suggest adding a sorting toggle button that allows users to switch between:

  • Newest to oldest (current default)
  • Oldest to newest (chronological)

Benefits:

  • Improved reading experience for sequential content
  • Better context understanding for Twitter conversations
  • More natural content consumption flow
  • Enhanced user control over content organization

Suggested solution

Suggested Implementation: A simple toggle button in the feed view that:

  • Persists user preference per feed type
  • Can be set globally or per subscription
  • Maintains the current default (newest first) while giving users the option to switch

This feature would significantly enhance the reading experience on Follow, especially for users who prefer to consume content in its natural chronological progression.

Alternative

No response

Additional context

No response

Validations

  • [X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

forkmax avatar Oct 24 '24 06:10 forkmax

ๅŒ้œ€ๆฑ‚

geekhuashan avatar Oct 28 '24 06:10 geekhuashan

Bot detected the issue body's language is not English, translate it automatically. ๐Ÿ‘ฏ๐Ÿ‘ญ๐Ÿป๐Ÿง‘โ€๐Ÿคโ€๐Ÿง‘๐Ÿ‘ซ๐Ÿง‘๐Ÿฟโ€๐Ÿคโ€๐Ÿง‘๐Ÿป๐Ÿ‘ฉ๐Ÿพโ€๐Ÿคโ€๐Ÿ‘จ๐Ÿฟ๐Ÿ‘ฌ๐Ÿฟ


Same requirement

github-actions[bot] avatar Oct 28 '24 06:10 github-actions[bot]

Bot detected the issue body's language is not English, translate it automatically. ๐Ÿ‘ฏ๐Ÿ‘ญ๐Ÿป๐Ÿง‘โ€๐Ÿคโ€๐Ÿง‘๐Ÿ‘ซ๐Ÿง‘๐Ÿฟโ€๐Ÿคโ€๐Ÿง‘๐Ÿป๐Ÿ‘ฉ๐Ÿพโ€๐Ÿคโ€๐Ÿ‘จ๐Ÿฟ๐Ÿ‘ฌ๐Ÿฟ


Same requirement

github-actions[bot] avatar Oct 28 '24 13:10 github-actions[bot]

Duplicate of #425

TonyRL avatar Oct 28 '24 13:10 TonyRL

Thank you very much for your suggestion, let us track this issue there

hyoban avatar Oct 28 '24 14:10 hyoban

่ฟ™ไธชๅŠŸ่ƒฝ้œ€ๆฑ‚็œŸ็š„ๅพˆๆ™ฎ้ๅ•Š๏ผŒไธบไป€ไนˆๅฐฑๆ˜ฏไธๅŠ ๅ‘ข๏ผŒnot planned๏ผŒ็ญ‰ไบ†่ฟ™ไนˆไน…๏ผŒๅบ”่ฏฅไนŸไธ้šพๅงใ€‚

geekhuashan avatar Mar 14 '25 07:03 geekhuashan

Bot detected the issue body's language is not English, translate it automatically. ๐Ÿ‘ฏ๐Ÿ‘ญ๐Ÿป๐Ÿง‘โ€๐Ÿคโ€๐Ÿง‘๐Ÿ‘ซ๐Ÿง‘๐Ÿฟโ€๐Ÿคโ€๐Ÿง‘๐Ÿป๐Ÿ‘ฉ๐Ÿพโ€๐Ÿคโ€๐Ÿ‘จ๐Ÿฟ๐Ÿ‘ฌ๐Ÿฟ


This function requirement is really common, why just not add it? Not planned. It shouldn't be difficult after waiting for so long.

github-actions[bot] avatar Mar 14 '25 07:03 github-actions[bot]