Page MenuHomePhabricator

Unknown User Interface
Open, NormalPublic


That was a big selling point for me in Plag, you could just browse without an account (but you needed one to post

Move the sign in page to the menu, make the entire bottom navbar the home button, add a 3rd endorsement option navigates to home without the login page
Its do-able

count anonymous users as views
(not endorsements)

The client would create an anonymous user account. Were we would save what the user did to each card, and when they register we convert that temporary account to a real account and apply endorsement

let the api remember a token like for registered users and also send that token on registration
cookies / local storage

Event Timeline

WyldBot created this task.May 13 2018, 5:49 PM
Info-Screen changed the visibility from "All Users" to "Public (No Login Required)".May 14 2018, 10:37 PM
Info-Screen triaged this task as Normal priority.May 16 2018, 12:17 AM
Info-Screen moved this task from Backlog to Account on the Server API board.May 24 2018, 3:14 PM
CLOVIS added a subscriber: CLOVIS.Nov 18 2018, 6:22 PM

So when you open the app for the first time:

  1. you get a choice: "create account" / "log-in" / "browse anonymously"
  2. if you choose the third option, the lib registers you, for example with /anonymous/register which returns a token
  3. you can browse your cards ? comment anonymously ? post anonymously ?
  4. in your bio, there's a "register" button, which sends a request to /anonymous/convert, then you can continue using the app with the same token ?

Wait, is this for the Client (web) or app?
And IMO the anonymous token should not be a token but a username/password combo that's only usable on /anonymous endpoints, and you don't register an anonymous account but change the username and password to a new one.

Just for now I would say web, our current apps still need loads of work, and this is far far future

Wait, is this for the Client (web) or app?

Ultimately, for both

And IMO the anonymous token should not be a token but a username/password combo [...]

Well the point is to *not* require a username/password combo