gildas-lormeau / gildas-lormeau/SingleFile

Auto-settings rule based on "category"

Open
#994 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature request
Dominant language
JavaScript
Stars
22.4k
Forks
1.4k
Avg merge
1h 32m
Merged PRs (30d)
5

Description

Discussed in https://github.com/gildas-lormeau/SingleFile/discussions/986

Originally posted by thecheesemo June 23, 2022
I have been using SingleFile extensively to manually save pages for later reference. I do this mainly for archiving purposes and because i have a bad memory. I've since realized that I always want to save every news article I read. So, I've started to define Auto-settings rules with a specific SingleFile profile for each url of news sites i visit, This profile auto saves pages, and that works fine. However, like most people on the web now, i don't go to just one news source, I get most of my news from link aggregators like google news and reddit. I have to manually add each news website's top level domain (TLD) to the Auto-settings rule with my news autosave profile.

Could it be possible to create an option in the Auto-settings that would let you define a profile based on the "category" of the TDL?

I don't even know if there exists such a list that can be referenced, or how one would go about making one other then a manual process. But if such a list does exist, or can be created easily enough, that would be a pretty great feature.

Contributor guide

No contributing guide indexed for this repository

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

Start with issue #994 and the linked discussion #986 to understand the requested category-based Auto-settings behavior. Determine whether a maintained category or TLD source is available and clarify the expected matching rules and settings UI before identifying implementation entry points. Done should include an agreed category definition and a testable profile-selection behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.