Whenever the user inputs an email, we will save it locally in that domain for prefill later and other reasons.

When a user subscribes via email (and no account), we save that locally as well, so the subscribe button goes away.

The vault signup will validate the email in the notify service- SOMEHOW, this detail is not yet solved.

When the email is validated, the "anonymous" subscriptions for that email will be upgraded to full notif subscriptions.

All local peer subscriptions are determined by combining:

• Contacts

• Enable email notifications

On the "join" and "comment" workflow, we will automatically create a contact for the site. This blank/simple contact means "I am a member of this site"

On the "follow" workflow,, we will create a contact for the account you are following, with some metadata which indicates "I am only following this account, I am not subscribed to their site"

Followers and Follows appear inside the profile. The profile URL should be created with the following:

• domain.com/:profile which is the profile for that site account

• anydomain.com/hm/<ACCOUNT_ID>/:profile

• The :profile URL has different sections/tabs

  • :profile - shows the main feed of activity

  • :profile/follows - shows who this account is following

  • :profile/following - shows who is following this account

  • :profile/membership - shows what sites this account has joined

When logging in, you are immediately redirected to h.m

When "creating account" we collect your email before the redirect

When redirecting back:

• We create the contact for following or joining, depending on the workflow

• We publish the comment (if you were creating a comment)

I believe join and subscribe are fully decoupled?

• You can join without subscribing

• You can subscribe without joining

• If you are logged in, your "subscribe" will be attached to your account.

• The "subscription" is managed by the notification server of your account, it is not public

More implementation notes incoming...