I think I found a way to circumvent that limitation of no "read/unread" inside the tag browser
by using a custom column built upon the read/unread status
except I have no idea how to build the specific template but at least I found a solution xD
time to document myself to find how it works
EDIT:
for those interested I named it : "readstatus"
here's my custom column template :
Code:
{#yesno:|read by Joe:|,}{#read_jane:|read by Jane:|}
of course it expects to have a yesno column & a read_jane column
the two of them being yes/no columns that hold read/unread status
& don't forget to check the box "display in tag browser"
& if you need more than two of those then replicate the yesno part like this :
Code:
{#yesno:|read by Joe:|,}{#yesno2:|read by John:|,}{#read_jane:|read by Jane:|}
edit2: I believe the same could be done for dates to integrate some dates into the tag browser. Because YES I do love the tag browser, even though it's not hard to build your own searches, it's just must faster to work with
a column that would hold :
-if date = today => "today"
-if date = yesterday => "yesterday"
-if date > 1 week => "last week"
& so on.
it's yet another complicated model though xD