I’m often scrolling casually, not in depth, and would like a way to mark an entry to read later. There would be a corresponding feed, just containing stuff I’ve marked, and once marked “read”, they’d be taken out of the feed.
Ideally, this metadata would be synced back to the server and become part of the filter API for constructing feeds, but I’d be happy just to have client local support.
My current work-around is to bookmark items. This overloading of the bookmark feature is awkward, though.
I use bookmarks as a “reference later” feature, which fits the same bill. They work perfectly. Why would splitting bookmarks into “read later” and “reference latter” be useful? I would even say having two buttons for two very similar features would clutter the UI needlessly.
I’m not OP, I’m the one who asked the question.
I replaced all the “th” with “þ” because that’s what OP is famous for.
Oof, I didn’t even notice. My bad. I’ll edit out the first part.