starred/shiori

Fork 0

mirror of https://github.com/go-shiori/shiori.git synced 2026-04-25 06:25:54 +03:00

[GH-ISSUE #247] [request] mark bookmarks read #183

New issue

Closed

opened 2026-02-25 23:33:38 +03:00 by kerem · 8 comments

kerem commented

2026-02-25 23:33:38 +03:00

Owner

Originally created by @microcreators on GitHub (May 5, 2020).
Original GitHub issue: https://github.com/go-shiori/shiori/issues/247

... 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.

Originally created by @microcreators on GitHub (May 5, 2020). Original GitHub issue: https://github.com/go-shiori/shiori/issues/247 ... 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.

kerem

2026-02-25 23:33:38 +03:00

closed this issue
added the
type:enhancement

component:frontend

component:backend
labels

kerem commented

2026-02-25 23:33:38 +03:00

Author

Owner

@michaelx commented on GitHub (Jun 1, 2020):

This would be a really helpful feature, especially when shiori is used as a read-it-later client.

@michaelx commented on GitHub (Jun 1, 2020): This would be a really helpful feature, especially when shiori is used as a read-it-later client.

kerem commented

2026-02-25 23:33:38 +03:00

Author

Owner

@thejdev commented on GitHub (Jun 5, 2020):

I agree that this would be a good feature.

As an interim workaround, I use this url as my default start page:
https://shiori-server/?search=-tag%3A*#home

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 commented on GitHub (Jun 5, 2020): I agree that this would be a good feature. As an interim workaround, I use this url as my default start page: https://shiori-server/?search=-tag%3A*#home 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.

kerem commented

2026-02-25 23:33:38 +03:00

Author

Owner

@8bitgentleman commented on GitHub (Jun 5, 2020):

@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://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.

@8bitgentleman commented on GitHub (Jun 5, 2020): @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://YourShioriServer/?search=-tag%3Aread#home](http://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.

kerem commented

2026-02-25 23:33:38 +03:00

Author

Owner

@deanishe commented on GitHub (Aug 6, 2020):

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. unread, starred) specially in the UI.

There's some "infrastructural" stuff that needs doing first, though.

@deanishe commented on GitHub (Aug 6, 2020): 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. `unread`, `starred`) specially in the UI. There's some "infrastructural" stuff that needs doing first, though.

kerem commented

2026-02-25 23:33:38 +03:00

Author

Owner

@microcreators commented on GitHub (Aug 8, 2020):

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 read? I think I'd be simpler to add this vs. having everything else tagged as unread.

@microcreators commented on GitHub (Aug 8, 2020): 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 `read`? I think I'd be simpler to add this vs. having everything else tagged as `unread`.

kerem commented

2026-02-25 23:33:38 +03:00

Author

Owner

@deanishe commented on GitHub (Aug 8, 2020):

I think I'd be simpler to add this vs. having everything else tagged as unread.

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 unread) or opt-out (add read).

I'm more inclined to the former (tag as unread to add to "read later" list) because I don't want an update to automatically shunt everybody's entire list of existing bookmarks (and any new ones they add/import) into their new "read later" list (because they aren't tagged as read).

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 unread model.

@deanishe commented on GitHub (Aug 8, 2020): > I think I'd be simpler to add this vs. having everything else tagged as unread. 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 `unread`) or opt-out (add `read`). I'm more inclined to the former (tag as `unread` to add to "read later" list) because I don't want an update to automatically shunt everybody's entire list of existing bookmarks (and any new ones they add/import) into their new "read later" list (because they aren't tagged as `read`). 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 `unread` model.

kerem commented

2026-02-25 23:33:38 +03:00

Author

Owner

@microcreators commented on GitHub (Aug 8, 2020):

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 unread by default, there will be (a lot of) manual work to hide what's no longer fresh.

@microcreators commented on GitHub (Aug 8, 2020): 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 `unread` by default, there will be (a lot of) manual work to hide what's no longer fresh.

kerem commented

2026-02-25 23:33:38 +03:00

Author

Owner

@deanishe commented on GitHub (Aug 8, 2020):

If everything is unread by default, there will be (a lot of) manual work to hide what's no longer fresh.

Exactly. That's why I prefer "tag unread to add to read-later list".

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.

@deanishe commented on GitHub (Aug 8, 2020): > If everything is unread by default, there will be (a lot of) manual work to hide what's no longer fresh. Exactly. That's why I prefer "tag `unread` to add to read-later list". 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.