Add a blocking option when right-clicking on a subscribed feed
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start by tracing the subscribed-feed right-click menu and the existing automation feature. Confirm how a subscription source is represented for blocking, then define the menu action and blocking category or view; done means users can temporarily block and unblock subscribed feeds without unsubscribing.
Written by the indexing model from the issue text.
Description
Clear and concise description of the problem
Sometimes, we just want to temporarily block multiple feeds for a short period of time, but we don't want to unsubscribe. The existing automation feature may enable blocking, but they are not convenient. It would be more convenient if there were an option to (un)block on the menu of the subscribed feed when right-clicking.
Suggested solution
- The blocking option in the right-click menu can be set to quickly create an automated rule for blocking based on this subscription source
- Add a category or view specifically for blocking
Alternative
No response
Additional context
No response
Validations
- Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
- This issue is valid
- Dominant language
- TypeScript
- Stars
- 39.3k
- Forks
- 2.2k
- Avg merge
- 9h 14m
- Merged PRs (30d)
- 16
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from RSSNext/Folo
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
bug platform: desktop
Difficulty 4/5 3-5 days Newbie friendliness 48/100
RSSNext/Folo#5139 · 1 comment ·
Maintainers usually reply within 1 day
-
bug need info platform: desktop
Difficulty 4/5 3-5 days Newbie friendliness 35/100
RSSNext/Folo#5055 · 2 comments ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 50/100
RSSNext/Folo#5054 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
RSSNext/Folo#5053 · 1 comment ·
Maintainers usually reply within 1 day
Similar issues
-
Update project links after the repository renamesPossibly taken @JonathanTSilva claimed this today. Openai-generated priority: p2 size: xs type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
JonathanTSilva/jts-website#119 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
promplate/code-review#158 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
[Docs] CONTRIBUTING points the Backend Remake milestone at a branch that does not existPossibly taken @franpts2 claimed this today. Opendocs
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 3 days
-
Split up selector calls in favourites/index?Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day