[DavidTC]

If it sounds strange to you, Reading List did not start out with any sync capability at all, it was just about the ability to maintain orderable lists of books.

That sounds strange to me. Barring the word 'orderable', I don't see what advantage that has over tags or making a custom column. (In fact, I don't quite understand how the books are orderable, they do not seem to such to me.)

I understand this didn't start out as a sync plugin, but it honestly baffles as to what else it is supposed to be.

In terms of implementing it, it would need some thought. Currently the plugin is all about manually adding items to lists, with menu items to support this with actions such as Add, Edit, Remove. What relevance do they have for a list that is being automatically populated? Do we just make such actions not apply to a tag driven list, so all you can do is "View" it? Probably the simplest approach.

Doesn't Reading List already add and remove tags when you take them on and off the list? I don't see why that part need change at all.

Then there is the question of custom columns - I support doing stuff with custom columns or tags, so you should be able to do custom column driven lists as well.

I don't see why why you're _not_ just using a custom column as the actual defining feature of the list.

These seems be one of those very strange ways in which plugins seem unwilling to interact with each other. I don't understand this concept of storing 'toggles' anywhere but as a tag, or a custom column if people don't want to make it a 'tag' per se.

If that happens, people can make stuff that happens in one plugin apply to another. But instead, the stuff get 'marked:', which is apparently some secret thing no one else is allowed to know about. I can't add it to the tag browser, I can't add it as a column, it's just somehow 'marked:' where I can search for it if I happen to know what it is (Or have a button that provides the search), but that's it.

Then there are other issues around device syncing. If the list is populated on demand (which it would have to be), then that means when you plugin/sync to your device it needs to do a query behind the scenes to figure out what books if any are on the list. So there are potentially some performance implications.

I don't know anything about the plugin API, so I don't know, but it's possible that you can put a hook on metadata changes, and just whenever a book changes tags, you quickly check it.