The chrome extension currently does not know who the user is. Add something to figure this out once they have logged in. We may need an endpoint on fluidinfo.com that gives the username of an authenticated request, or we may extract the username from the content of the dashboard page, or something.
Once we again have this information we can make it possible to follow things directly (if we want) and what the user sees in popus can be personalized again (due to per-user following not anon following).
The chrome extension currently does not know who the user is. Add something to figure this out once they have logged in. We may need an endpoint on fluidinfo.com that gives the username of an authenticated request, or we may extract the username from the content of the dashboard page, or something.
Once we again have this information we can make it possible to follow things directly (if we want) and what the user sees in popus can be personalized again (due to per-user following not anon following).