SJRK-20: Discuss authorship management

Metadata

Source
SJRK-20
Type
Epic
Priority
Blocker
Status
Open
Resolution
N/A
Assignee
N/A
Reporter
Gregor Moss
Created
2017-10-31T15:42:31.863-0400
Updated
2020-12-13T21:12:54.958-0500
Versions
N/A
Fixed Versions
  1. 1.0
Component
  1. Storytelling Tool Server
  2. Storytelling Tool UI

Description

Discuss, broadly, how we'll handle story authorship

We want people to be able to:

  • Write their stories
  • come back to them later and edit them
  • make a story public
  • make a story private

Will include discussions of a possible user account management system

  • maintaining our own user management system
  • allowing 3rd-party authentication schemes
  • providing a token that the user can use in the future to go back and edit their story

Consider complexity and security

Comments

  • Alan Harnum commented 2017-11-09T16:11:02.057-0500

    Possibilities:

    • allow the user to generate an authorship token that they will keep track of in order to manage their story or stories. one token per 'author' (users might want to have more than one persona that they could have separate tokens for)
    • tokens should be cryptographically random and secure (i.e. non-predictable), and not exposed to the general user-base
    • show the user the stories that 'belong' to them
    • allow them to access an editing interface to adjust the story content, privacy, or other aspects of it

  • Alan Harnum commented 2017-11-09T16:12:41.922-0500

    If we decide to implement user account management, we should consider third-party authentication systems like Google, Facebook, OAuth, etc