Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature discusion: Block list. Usage and Design #85

Open
Endle opened this issue Nov 28, 2022 · 1 comment
Open

Feature discusion: Block list. Usage and Design #85

Endle opened this issue Nov 28, 2022 · 1 comment

Comments

@Endle
Copy link
Owner

Endle commented Nov 28, 2022

Is your feature request related to a problem? Please describe.
I assume some people may have some pages for outdated, useless, or even ready-to-delete texts. For example, I have a page called GTD/Archived. It is a very long page, and it could appear in fireSeqSearch hits very frequently.

Describe the solution you'd like
I'd like to add a BlockList feature.

Additional context
However, I have several potential approaches to it, and I'm still in doubt.

  1. Create a blocklist.txt, and te server would load it
  2. Add an option in the web extension
  3. Add a tag in some pages of logseq, and they'll be ignored
  4. etc...

Please share your thoughts on this feature.

Note: Only English and Chinese posts are allowed in the issues section. English is preferred.
请使用英文或中文发 issue.

@Endle
Copy link
Owner Author

Endle commented Jul 8, 2023

I added an option for zotero items #122

Now sure if it's needed to block other pages

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant