We are inconsistent with our usage of email and id. We were not disciplined, thinking that a service should use email since it's a much simpler identifier for humans, but for systems, it's more optimal to reference a human id, and an identity service can resolve that to get email.
We were thinking of building an ecosystem where the email is the reference, however, in a future world with the flowy ecosystem, we will wish that we had a flowy.llink system human identification system instead of building our system atop the idea of email addresses.
Email addresses are less performant as indexes, inconsistent size, non-unique (dot and other characters don't count in email addresses) and people may want to change their account email address later. And to accommodate that, we would not want to have all sorts of asynchronous events to migrate all associated data.
We are inconsistent with our usage of email and id. We were not disciplined, thinking that a service should use email since it's a much simpler identifier for humans, but for systems, it's more optimal to reference a human id, and an identity service can resolve that to get email.
We were thinking of building an ecosystem where the email is the reference, however, in a future world with the flowy ecosystem, we will wish that we had a flowy.llink system human identification system instead of building our system atop the idea of email addresses.
Email addresses are less performant as indexes, inconsistent size, non-unique (dot and other characters don't count in email addresses) and people may want to change their account email address later. And to accommodate that, we would not want to have all sorts of asynchronous events to migrate all associated data.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
We are inconsistent with our usage of email and id. We were not disciplined, thinking that a service should use email since it's a much simpler identifier for humans, but for systems, it's more optimal to reference a human id, and an identity service can resolve that to get email.
We were thinking of building an ecosystem where the email is the reference, however, in a future world with the flowy ecosystem, we will wish that we had a flowy.llink system human identification system instead of building our system atop the idea of email addresses.
Email addresses are less performant as indexes, inconsistent size, non-unique (dot and other characters don't count in email addresses) and people may want to change their account email address later. And to accommodate that, we would not want to have all sorts of asynchronous events to migrate all associated data.