-
Notifications
You must be signed in to change notification settings - Fork 547
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
[request] mark bookmarks read #247
Comments
This would be a really helpful feature, especially when shiori is used as a read-it-later client. |
I agree that this would be a good feature. As an interim workaround, I use this url as my default start page: The link above lists bookmarks with no tag (i.e. unread). Once I have read an article, I give it a tag (e.g. Read), and it disappears from the list. |
@thejdev I like that idea a lot. To remix it if you set this URL is your home it filters out the tag #read and shows all others. This works really well for me because I use tagging for many other things http:https://YourShioriServer/?search=-tag%3Aread#home I wish shiori did filtering in real time though. That's the downside I see, you need to refresh the page for any new tagged articles to be filtered out. |
Hi guys. I'm your new Shiori maintainer. This feature is a high priority for me. Specifically, I want to add support for read, starred and—possibly—archived status. Right now, I'm thinking of something along the lines that @thejdev suggests: basically just using tags, but treating certain tags (e.g. There's some "infrastructural" stuff that needs doing first, though. |
First of all, thanks for reviving the project, appreciate it. If I can suggest something here, start easy with the change. Maybe just one special tag for starters like |
What makes you say it would be simpler? I think the main difference is whether you think a "read later" list should be opt-in (add I'm more inclined to the former (tag as Existing users have probably read most of the articles they're interested in by this point, and they may not even want to use the feature. That's a better fit with the opt-in |
Honestly - it doesn't matter. 99% of my bookmarks are read and stored "just in case" (it's a knowledge base for me). I think it's a matter of default tagging. If everything is |
Exactly. That's why I prefer "tag Of course, it's simple enough to automatically add any tag to items on database migration or when importing/adding. So, it's really a question of opt-in vs opt-out, and currently I'm quite strongly inclined towards opt-in. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
... and move them out of sight. archive them, hide them, etc. but keep them available and searchable in case I need to come back to them one day. Just don't show them in a default view.
The text was updated successfully, but these errors were encountered: