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
Three is nothing in the spec that demands that a Pod have a preferences file or defines an audience such as solid:PowerUser. CSS, for example, does not pre-provision Pods with a preferences file or define an audience. This means that when we use SolidOS to log in to CSS, even when we are logged in, we only see those pane/icons that a non-logged-in user sees - no RDF, no Under-the-hood because we haven't read any preferences. Since it isn't in the spec, we can't assume that new servers will provide it either.
So I suggest that we change the behavior of audience - that if the user is logged in and there is no preferences file, we default to a solid:PowerUser (or Developer) view. That way a logged-in user can delete files, which currently they can not.
The text was updated successfully, but these errors were encountered:
Three is nothing in the spec that demands that a Pod have a preferences file or defines an audience such as solid:PowerUser. CSS, for example, does not pre-provision Pods with a preferences file or define an audience. This means that when we use SolidOS to log in to CSS, even when we are logged in, we only see those pane/icons that a non-logged-in user sees - no RDF, no Under-the-hood because we haven't read any preferences. Since it isn't in the spec, we can't assume that new servers will provide it either.
So I suggest that we change the behavior of audience - that if the user is logged in and there is no preferences file, we default to a solid:PowerUser (or Developer) view. That way a logged-in user can delete files, which currently they can not.
The text was updated successfully, but these errors were encountered: