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

extension/indexers: ensure less 'span' in visited marks #365

Open
karlicoss opened this issue Jan 29, 2023 · 2 comments
Open

extension/indexers: ensure less 'span' in visited marks #365

karlicoss opened this issue Jan 29, 2023 · 2 comments
Labels
backend Related to indexing/serving enhancement New feature or request frontend Related to browser extension

Comments

@karlicoss
Copy link
Owner

for @karlicoss a good example is this page https://github.com/settings/billing

image

One thing that would be nice is to make google takout visit 'boring' -- that can be achieved by removing contexts in promnesia indexer (for simple visits they only contain the domain name) https://github.com/karlicoss/promnesia/blob/master/src/promnesia/sources/takeout.py#L39

Another is perhaps adding an option to hide "boring" visits completely, or even better to hide certain sources. Maybe ideally with a javascript-based hook to start with

@karlicoss karlicoss added enhancement New feature or request backend Related to indexing/serving frontend Related to browser extension labels Jan 29, 2023
karlicoss added a commit that referenced this issue Jan 31, 2023
this makes it less spammy when showing visited marks/in the sidebar
they mostly should be treated like 'boring' link visits

see #365
@karlicoss
Copy link
Owner Author

after:
image

still could benefit from excluding them from the visited marks UI I guess but it's quite a bit better

karlicoss added a commit that referenced this issue Jan 31, 2023
this makes it less spammy when showing visited marks/in the sidebar
they mostly should be treated like 'boring' link visits

see #365
@AnweshGangula
Copy link
Contributor

Just sharing a related concern I'm facing:

The context in below screenshot renders the HTML text from Logseq

I have raised a related issue with contexts in search.html in #430

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Related to indexing/serving enhancement New feature or request frontend Related to browser extension
Projects
None yet
Development

No branches or pull requests

2 participants