I really dislike it when companies use a new extension like "github.community" instead of a subdomain like "community.github.com" because there is no real way to know if the site is a phishing attempt or not. Getting people used to accept going to another site seems very bad for security. Especially when there are already domains like http://github.co (notice the .CO instead of .COM) that don't belong to the trademark owner.
GitHub Community Forum
11–20 of 46 posts
Re: GitHub Community Forum
#12Earlier quoted context omitted.
The registrant details in the whois are GitHub’s, and the name servers match. Seems likely to be genuine.
I hope so, clicking on 'sign in' logged me into my github account with no further action. Does anyone know how they did that?
You're probably already logged in on the main Github.com domain.
You were redirected from the community domain to the main domain to log in. Once there, the system saw you were already logged in and redirected you back to the community site with some proper tokens in the url to identify you.
Re: GitHub Community Forum
#13I really dislike it when companies use a new extension like "github.community" instead of a subdomain like "community.github.com" because there is no real way to know if the site is a phishing attempt or not. Getting people used to accept going to another site seems very bad for security. Especially when there are already domains like http://github.co (notice the .CO instead of .COM) that don't belong to the trademar…
My UK bank recently started using nationwide.nationwide-service.co.uk as an origin for e-mails.
I had to check WHOIS and contact them to ensure it was valid, it just sounded so phishy.
Given that previously nationwide.co.uk was used and trusted, I wonder what internal discussions led to selecting that new domain and why. And what advocates for the end-users spoke up and said "whoa dudes that's just confusing".
Re: GitHub Community Forum
#14I looked at this for a while, but I'm not sure I understand what is going on here. Is this a Stackoverflow competitor or just some sort of watercooler to talk about Github in general? Feels a little bit random to me.
Agreed. There was never a time when using GitHub that I thought "man, I wish there was an official forum where I could ask something about GitHub".
Re: GitHub Community Forum
#15They made an announcement on their blog for this community a few weeks ago [1]. However, it's true it's been quite a silent announcement. No banners on the site, no links...
[1] https://github.com/blog/2457-connect-with-developers-around-...
Re: GitHub Community Forum
#16I really dislike it when companies use a new extension like "github.community" instead of a subdomain like "community.github.com" because there is no real way to know if the site is a phishing attempt or not. Getting people used to accept going to another site seems very bad for security. Especially when there are already domains like http://github.co (notice the .CO instead of .COM) that don't belong to the trademar…
My UK bank recently started using nationwide.nationwide-service.co.uk as an origin for e-mails. I had to check WHOIS and contact them to ensure it was valid, it just sounded so phishy. Given that previously nationwide.co.uk was used and trusted, I wonder what internal discussions led to selecting that new domain and why. And what advocates for the end-users spoke up and said "whoa dudes that's just confusing".
It's fairly common for companies to send automated e-mails from a separate domain to try to mitigate the impact of spam filters. ceo@company.com doesn't want her e-mails to be marked as spam just because some marketing e-mails are being sent from noreply@company.com.
Re: GitHub Community Forum
#17I really dislike it when companies use a new extension like "github.community" instead of a subdomain like "community.github.com" because there is no real way to know if the site is a phishing attempt or not. Getting people used to accept going to another site seems very bad for security. Especially when there are already domains like http://github.co (notice the .CO instead of .COM) that don't belong to the trademar…
My UK bank recently started using nationwide.nationwide-service.co.uk as an origin for e-mails. I had to check WHOIS and contact them to ensure it was valid, it just sounded so phishy. Given that previously nationwide.co.uk was used and trusted, I wonder what internal discussions led to selecting that new domain and why. And what advocates for the end-users spoke up and said "whoa dudes that's just confusing".
I wonder if this has caught on because the business want's to move fast with new email campaigns and such, but their IT people forbid them from getting a new subdomain?
I wouldn't be surprised if in some organisations it's easier to register a new domain than to get any changes made to the "mothership" domain.
Re: GitHub Community Forum
#18Ehhhh, so, like. GitHub is big on open source stuff, supposedly. Love that they went with lithium stuff instead of some of the more open source solutions that could've used the manpower from GitHub.
Interestingly, one of the "new subcommunities" (linked in the footer) seems to be Discourse: https://education.github.community/
And the Atom discussion area is too (but that's been up for a while): https://discuss.atom.io/
Re: GitHub Community Forum
#19I really dislike it when companies use a new extension like "github.community" instead of a subdomain like "community.github.com" because there is no real way to know if the site is a phishing attempt or not. Getting people used to accept going to another site seems very bad for security. Especially when there are already domains like http://github.co (notice the .CO instead of .COM) that don't belong to the trademar…
You think that's bad, look at PayPal. They talk big about phishing prevention but use a bunch of random domain names including paypal-community.com and other obscure stuff.
Re: GitHub Community Forum
#20I really dislike it when companies use a new extension like "github.community" instead of a subdomain like "community.github.com" because there is no real way to know if the site is a phishing attempt or not. Getting people used to accept going to another site seems very bad for security. Especially when there are already domains like http://github.co (notice the .CO instead of .COM) that don't belong to the trademar…
Also from an SEO perspective, they could have bumped their domain authority even further by using the same domain - they now need to grow this new domain from square 1, and it's going to be hard, even for a large company like Github.