You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is currently tricky to keep up with comments across multiple editgroups.
My personal preference is to avoid setting up setting emails as a notification. Partially this is to avoid having email addresses associated with editor identities and stored in any way in our databases, because it is a privacy risk. And having email delivered reliably is unfortunately a behavior that either requires constant maintenance or paying for a third party service.
As a partial solution, I propose that we have per-editor notification pages. These wouldn't require a login to access, though it might be hard to discover URLs if not logged in.fatcat_web would generate the page via multiple API calls. To start with, the editgroup history and comment/annotation history of the current editor would be queried, for the last ~20 of each. Then, for each editgroup that has been interacted with, all the editgroups and annotations on each will be fetched. Then all the editgroup state changes (submissions, merges) and annotations will be sorted in to a single list and displayed. This endpoint can have HTML, JSON, and RSS formats, to make it easy to keep up.
A downside with this approach is that if an old editgroup (not in the recent 20 or whatever) has a new annotation, that annotation might be missed.
The text was updated successfully, but these errors were encountered:
It is currently tricky to keep up with comments across multiple editgroups.
My personal preference is to avoid setting up setting emails as a notification. Partially this is to avoid having email addresses associated with editor identities and stored in any way in our databases, because it is a privacy risk. And having email delivered reliably is unfortunately a behavior that either requires constant maintenance or paying for a third party service.
As a partial solution, I propose that we have per-editor notification pages. These wouldn't require a login to access, though it might be hard to discover URLs if not logged in.
fatcat_web
would generate the page via multiple API calls. To start with, the editgroup history and comment/annotation history of the current editor would be queried, for the last ~20 of each. Then, for each editgroup that has been interacted with, all the editgroups and annotations on each will be fetched. Then all the editgroup state changes (submissions, merges) and annotations will be sorted in to a single list and displayed. This endpoint can have HTML, JSON, and RSS formats, to make it easy to keep up.A downside with this approach is that if an old editgroup (not in the recent 20 or whatever) has a new annotation, that annotation might be missed.
The text was updated successfully, but these errors were encountered: