10000 Should we allow anonymous users to save projects? · Issue #604 · stevekrouse/WoofJS · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Should we allow anonymous users to save projects? #604
Open
@hallpell

Description

@hallpell

We're currently somewhat inconsistent on allowing users that aren't logged in to save a project. If they click on the 'Save' button, it will prompt them to create an account/log in before saving their project. But if they instead try to open the project in full screen, it by-passes that check and immediately asks them for a project name and saves their project. Various thoughts on this:

  • I think it's good to allow anonymous users to use the full-screen functionality (though am not dead-set on this)
    • Without looking into the code in detail, it shouldn't be too hard to prompt for account creation when we attempt to full-screen from an anonymous session.
  • The way our projects/firebase are structured require a project to be saved to get a full-screen view, and this structure is unlikely to change (large data migration scares me without a very compelling reason).
  • I'd like to be able to cull projects created by anonymous users after some amount of time (a couple hours is probably fine, but it could be much longer; days-weeks is fine), partially to limit excess data storage and partially to free-up project names.
    • I'm not sure where something like this would live; having permission to delete projects is spooky (and doubly-so deleting projects you don't own [because they have no owner]).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0