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
At the analyst meeting today, I mentioned that one of our next priorities after Wayback support and deployment fixes is revisiting annotations and actually making them usable. In the short term, our current plan is OK (annotations are visible to you if you have annotation permissions and invisible otherwise), but will certainly be an issue if we start to host multiple teams or once things become more public open.
In the long run, we need to think through and answer questions about how someone can control the visibility of their annotations — are they personal, for a particular group/team (e.g. EDGI analysts), or public? (What other ways are there to think of and classify this?)
This issue is more a point for consideration and discussion, since in the short term, we are totally OK punting on it.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in seven days if no further activity occurs. If it should not be closed, please comment! Thank you for your contributions.
At the analyst meeting today, I mentioned that one of our next priorities after Wayback support and deployment fixes is revisiting annotations and actually making them usable. In the short term, our current plan is OK (annotations are visible to you if you have annotation permissions and invisible otherwise), but will certainly be an issue if we start to host multiple teams or once things become more public open.
In the long run, we need to think through and answer questions about how someone can control the visibility of their annotations — are they personal, for a particular group/team (e.g. EDGI analysts), or public? (What other ways are there to think of and classify this?)
This issue is more a point for consideration and discussion, since in the short term, we are totally OK punting on it.
The text was updated successfully, but these errors were encountered: