RSSNext / RSSNext/Folo

Feature Proposal: Discover feeds for each Inbox entries

Open
#805 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
39k
Forks
2.1k
Avg merge
1d 4h
Merged PRs (30d)
10

Description

Clear and concise description of the problem

The inbox usually acts like a to-do list. I typically take two actions on an inbox entry:

  • Read it and do nothing
  • Read it and subscribe to the site
Suggested solution
Lazy Discovery - Discover on Action

Add a button to the content view of each inbox entry that has a URL.

When the button is clicked, it should open a modal or popover suggesting related feeds for the user to follow.

Alternative
Eager Discovery - Discovery on Retrieved

Discover related feeds, either synchronously or asynchronously, when the backend retrieves an inbox entry with URL.

Add a button to the content view of each inbox entry that has related feeds not currently followed by the user.

(Optional) Include a highlight effect on the button if it's the user's first time seeing the feed.

Clicking the button will display a popover to help users follow the feed.

Additional context

I'm building a Chrome extension to send readable pages to Follow's Inbox. https://github.com/xc2/follow-it-later.

The feature mentioned in this issue would help users subscribe to sites later in Follow.

Without this feature, I'd have to call the discover endpoint in the extension and add subscribe URLs to the content field of each entry sent to Follow.

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named. Start by locating the inbox content view and the discover endpoint referenced in the proposal, then determine how either lazy or eager discovery fits the existing flow; done means eligible entries expose related feeds and users can follow them through the proposed modal or popover.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
backend, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.