Intra-affiliation and inter-affiliation postings management

Abstract

Techniques for managing intra-affiliation and inter-affiliation postings are described. Disclosed are techniques for receiving a posting from an account, the account being associated with an affiliation and an account parameter, transmitting one or more affiliation-specific parameters associated with the affiliation to the account, receiving a posting parameter from the account, the posting parameter being selected from one or more affiliation-specific parameters, determining a level of relevancy of the posting to a receiving account based on the posting parameter, the account parameter, and a receiving account parameter, the receiving account being associated with the receiving account parameter, generating an order of postings based on the level of relevancy, and transmitting the order of postings to the receiving account. One or more postings may be displayed at the receiving account based on the order.

1 . A non-transitory computer readable medium comprising instructions, which when executed by one or more hardware processors, cause performance of operations comprising:
 presenting a first interface that requests an email address of a user, without requesting an affiliation of the user;   receiving the email address entered via the first interface by the user;   identifying a domain name corresponding to the email address;   identifying a library storing associations between (a) a plurality of domain names and (b) a plurality of affiliations;   determining that the domain name corresponding to the email address is associated with a particular affiliation, of the plurality of affiliations, based on the library storing associations between (a) the plurality of domain names and (b) the plurality of affiliations; and   storing the particular affiliation in association with a user account for the user.   
     
     
         2 . The medium of  claim 1 , wherein the operations further comprise:
 identifying a set of one or more affiliation-specific parameters associated with the particular affiliation; and   causing display of the set of affiliation-specific parameters at a second interface.   
     
     
         3 . The medium of  claim 2 , wherein the operations further comprise:
 receiving a selection of a particular affiliation-specific parameter, from the set of affiliation-specific parameters, via the second interface by the user; and   storing the particular affiliation-specific parameter in association with the user account.   
     
     
         4 . The medium of  claim 1 , wherein the operations further comprise:
 transmitting an affiliation-specific parameter, associated with the particular affiliation, to the client device associated with the user.   
     
     
         5 . The medium of  claim 1 , wherein the operations further comprise:
 transmitting a posting, whose relevancy to the user is determined based on the particular affiliation, to a client device associated with the user.   
     
     
         6 . The medium of  claim 1 , wherein the particular affiliation comprises at least one of: a school, a college, a university, a company, an organization, a club, a league, and a team. 
     
     
         7 . The medium of  claim 1 , wherein the particular affiliation is identified as being associated with the user without the user entering a name of the particular affiliation via the first interface. 
     
     
         8 . The medium of  claim 1 , wherein the email address is received as part of a user registration process. 
     
     
         9 . The medium of  claim 1 , wherein the operations further comprise: generating a user account for the user. 
     
     
         10 . The medium of  claim 1 , wherein the operations further comprise: receiving a posting from the user. 
     
     
         11 . The medium of  claim 1 , wherein the operations further comprise:
 determining a level of relevancy of a posting to the user based on the particular affiliation; and   causing display of the posting based on the level of relevancy at a second interface.   
     
     
         12 . The medium of  claim 1 , wherein the operations further comprise: transmitting an email message to the email address, the email message including data configured to authenticate the email address. 
     
     
         13 . A method, comprising:
 presenting a first interface that requests an email address of a user, without requesting an affiliation of the user;   receiving the email address entered via the first interface by the user;   identifying a domain name corresponding to the email address;   identifying a library storing associations between (a) a plurality of domain names and (b) a plurality of affiliations;   determining that the domain name corresponding to the email address is associated with a particular affiliation, of the plurality of affiliations, based on the library storing associations between (a) the plurality of domain names and (b) the plurality of affiliations; and   storing the particular affiliation in association with a user account for the user.   
     
     
         14 . The method of  claim 13 , further comprising:
 identifying a set of one or more affiliation-specific parameters associated with the particular affiliation; and   causing display of the set of affiliation-specific parameters at a second interface.   
     
     
         15 . The method of  claim 14 , further comprising:
 receiving a selection of a particular affiliation-specific parameter, from the set of affiliation-specific parameters, via the second interface by the user; and   storing the particular affiliation-specific parameter in association with the user account.   
     
     
         16 . The method of  claim 13 , further comprising:
 transmitting an affiliation-specific parameter, associated with the particular affiliation, to the client device associated with the user.   
     
     
         17 . A system, comprising:
 at least one device including a hardware processor; and   the system being configured to perform operations comprising:   presenting a first interface that requests an email address of a user, without requesting an affiliation of the user;   receiving the email address entered via the first interface by the user;   identifying a domain name corresponding to the email address;   identifying a library storing associations between (a) a plurality of domain names and (b) a plurality of affiliations;   determining that the domain name corresponding to the email address is associated with a particular affiliation, of the plurality of affiliations, based on the library storing associations between (a) the plurality of domain names and (b) the plurality of affiliations; and   storing the particular affiliation in association with a user account for the user.   
     
     
         18 . The system of  claim 17 , wherein the operations further comprise:
 identifying a set of one or more affiliation-specific parameters associated with the particular affiliation; and   causing display of the set of affiliation-specific parameters at a second interface.   
     
     
         19 . The system of  claim 18 , wherein the operations further comprise:
 receiving a selection of a particular affiliation-specific parameter, from the set of affiliation-specific parameters, via the second interface by the user; and   storing the particular affiliation-specific parameter in association with the user account.   
     
     
         20 . The system of  claim 17 , wherein the operations further comprise:
 transmitting an affiliation-specific parameter, associated with the particular affiliation, to the client device associated with the user.