Bluevia accounts are going to be generated automatically from the handsets. They will be in the form of an email address; a big hash ending with something like "@id.bluevia.com" (you can assume it's that for now). Since these user accounts are automatically built, they aren't valid email addresses and there isn't a valid name, homepage, etc. This bug is to: - Add a method to the user object to identify if an account is from bluevia (just check if it ends with that string and return yes/no). - Remove the "signed in as" text in the footer - Remove any links to their account detail page or the account editing page - Make sure going to the URL of the above two pages does not allow someone to edit their account - Modify any code that emails users (grep for the code) and make sure we aren't emailing these fake accounts. Some areas use a special function for emailing so we can check our whitelist first and we can add to that function. Others email directly. - Check around our pages and make sure their display_name isn't used anywhere else. If it is, remove it. Spec: bottom of https://docs.google.com/document/d/13CZqSbOdf_W7Wb-r7cLFLA_XwdDNVT8T9LMLpul4iYs/edit

Kicking to the week after so we can do this after the new designs land

On hold, pending updates to the payment plan. Likely a wontfix

Is this still a valid bug? BlueVia is no longer our target for basecamp.

This is no longer valid. New details are here: https://wiki.mozilla.org/Apps/ID_and_Payments See bug 794634 for the new way we are working with Persona accounts/emails.