Support for user profiles

[jrokeach]

Support for user profiles and metadata.
Fields:

• Position (ENUM)
• Company (Verification via email?)
• Location (City, State/Province, Country)
• Certifications
• ASN(s) or PeeringDB Org

[KeatonSK]

I'll work that into my build and then push it once you push your latest build.

[jrokeach]

We need to discuss how this is going to work. The info in the issue so far is very sparse.

…

On Thu, Mar 12, 2020, 11:20 AM Keaton (SK) ***@***.***> wrote: I'll work that into my build and then push it once you push your latest build. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#8 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIG2WOZYE24GOSAWYUV2ELRHD4U5ANCNFSM4LGL532Q> .

[1Ludwig]

First of all, what kind of features do we want to enable (now and in the future)?
Then with what kind of info would we need to make that happen?

[jrokeach]

To start, let's enable collecting and viewing the data. Privacy controls are probably a next option. I'd like to prompt users for the information when they accept the rules, but not mandate that they fill it out. If we can group this by postal code, we may be able to do things like automatically spawn channels once a certain number of users are on the server from that area. For example, the bot could notice that the server just had the 15th user join in the area of New York City. Let's spawn a channel just for these users, create a group, and assign all users to that group. Obviously this is very forward thinking but just an example of something we could do. Probably the easiest way to do this is postal code. I thought about doing the same thing with company, but I don't want to do that because that may lead to more posting of company confidential information on Discord, which is simply a bad thing. However, on the subject of companies, it might be feasible to build roles based on company. I want the company to be in the format of domain name, so that we can have a means of validating if we later want to provide validation. Finally, the same applies to certifications - I'd like to be able to validate those via ingestion of verification emails in the future, but for the time being allow people to just assign whatever certs they want to themselves (off of a standard list of common networking certs).

…

-----Original Message----- From: Ludwig Nilsson <[email protected]> Reply-To: networking-discord/network-ranger < [email protected]> To: networking-discord/network-ranger < [email protected]> Cc: Jason Rokeach <[email protected]>, Assign < [email protected]> Subject: Re: [networking-discord/network-ranger] Support for user profiles (#8) Date: Thu, 12 Mar 2020 08:56:37 -0700 First of all, what kind of features do we want to enable (now and in the future)? Then with what kind of info would we need to make that happen? — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub, or unsubscribe. [ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": " #8 (comment) ", "url": " #8 (comment) ", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

[jrokeach]

Also should include ASN(s)

[jrokeach]

Company portion complete - using roles instead of a DB.

[jrokeach]

Started laying groundwork for this in #58