lemon24

Rough order of things, based on what blocks what: * [x] decide how to store flag change timestamps * [x] find a way to model "not read, but I don't...

I don't know what other combinations mean, but this is enough to show "not read, but I don't care" == read and not important and important_changed is not None. Using...

Regarding how we store timestamps: We could do it with entry metadata (#253), but that's not implemented yet, and using it in queries would be a pain. It makes more...

The minimal API: ```python # Reader mark_as_read(...) # use the real "now", backwards compatible mark_as_read(..., now: Optional[datetime]) # use a custom "now"; mainly for plug-ins # TODO: find a better...

To do (for storing stuff): * [x] migration * [x] Entry attribute (will break some tests) * [x] set attribute in mark_as_... * [x] expose modified argument in mark_as_... *...

We're mostly done with the "store modified" part. The UX for "don't care" needs a bit of work, though... In 4278939 (and 59004b3) I had to make the "unimportant"/"unread" buttons...

Spent about 12 hours on this until now.

Some conclusions from playing with the Atom feed below: * xml.sax.SAXParseException "undefined entity" is survivable. * "mismatched tag" is *not*; we get all the good entries, and then the broken...

Here's a script that covers exactly my use case: ```python import sys import re from reader import make_reader, Content, FeedNotFoundError from reader.plugins.entry_dedupe import _normalize def dup_feed(reader, src, dst, label=None): src_feed...

Basic support means import/export. This can/should be built on top of Reader. "Advanced" support probably means importing feeds from a URL regularly. Ideally, Reader should be aware of these (so...