My current way of keeping up with journals is based on using an online RSS reader. This is, I would assume, a pretty common way of keeping up to date. ChemBrows offers several advantages, perhaps most importantly the machine learning estimation of individualized article "hotness". However, being a program you run on your own computer, it also has some disadvantages, specifically that your database (including the machine learning model, which papers you've read or not, which are stored as read later, which you like, etc) cannot be (or so it seems) transferred between computers.
I think a great improvement for ChemBrows would be the ability to store everything in a single database file, that can be synchronized between computers using e.g. dropbox or syncthing. Then, your "journal reading" would be kept in a single file, sort of like many of us keep our bibliographies in a single .bib file. You could use chembrows on multiple computers, too.
My current way of keeping up with journals is based on using an online RSS reader. This is, I would assume, a pretty common way of keeping up to date. ChemBrows offers several advantages, perhaps most importantly the machine learning estimation of individualized article "hotness". However, being a program you run on your own computer, it also has some disadvantages, specifically that your database (including the machine learning model, which papers you've read or not, which are stored as read later, which you like, etc) cannot be (or so it seems) transferred between computers.
I think a great improvement for ChemBrows would be the ability to store everything in a single database file, that can be synchronized between computers using e.g. dropbox or syncthing. Then, your "journal reading" would be kept in a single file, sort of like many of us keep our bibliographies in a single .bib file. You could use chembrows on multiple computers, too.
Are there any plans for such an improvement?