Ehhhh, 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.
It links a great deal to Github on its homepage, yet none of the Github links mention it or link back to it. My first impression was that someone was trying to bootstrap a forum by looking to look official.
I suppose it's just not launched yet. Else you'd at least expect a blog post.
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.
github.community isn't. It sends you to github.com regardless, since their login is there. github.com sees you're already logged in, and redirects back, passing auth.
Most OAuth providers have a flag for first party clients which allows them to bypass the usual authorization dance and just bounce you straight back to the origin.
Man, the design of this is so unpolished that I actually find it a bit stressful to look at. The lack of grid adherence, the strange hierarchy of font sizes, it doesn't seem up to Github's normal high standards of clean and sensible design choices. But then I guess it's new and they'll refine it.
Yeah it's incredibly weird how unfinished this seems.
Look at the navigation hierarchy. There are two nav background colors, but you can barely see the difference (even on a new MBP). The search input blends into the nav background, and not in a stylistic way, it seems completely on accident.
The "Community Forum" logo type looks off brand.
The iconography illustration in the masthead was mailed in. It's just the same two icons copy pasted.
The card layout at the bottom seems very un-github as well. They are typically very good at handling large amounts of text and information, but those cards are really hard to read. They bounce around from center-aligned lists (usually a bad idea) to nested columns.
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.
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.
Not sure why you're being downvoted, that's likely the reason. Employee email addresses will be sent with @nationwide.co.uk and even if the communication in this case was important, enough people will mark it as spam. Using a second domain helps keeping the domain clean.
And I take it using a separate subdomain wont work either? I.E. if you send mail from hi@marketing.example.com it will still hurt frank@example.com so they need to get a different domain?
It depends on how spam filters are configured, but yes, subdomains can harm root domain's reputations. However, it's generally seen as OK to use subdomains to mitigate reputations being spread to the main domain. As long as you have your records in order to show what's going on, using a subdomain is usually OK.[1]
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.
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.
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.
They 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...
I'll take this as an opportunity to shill my GitHub replacement: https://meta.sr.ht/
If you're a pessimist like me you've kept a mental list of demerits (like this weird forum) that add up to a picture of a slowly dying platform. Join mine instead and postpone the cold grip of death!
I wouldn't be so sure of GitHub if I were you. How long has it been the biggest player? It wasn't so long ago SourceForge was dominant and look what happened to it. GitHub is beholden to their investors, and it will make decisions that benefit them at the expense of their users. Services like Pinboard thrive as some random dude on the internet. I use a business model that doesn't have the same risks to longevity that GitHub does.
Yeah, but SourceForge wasn't exactly supplanted by a random guy with a dodgy-looking domain.
Crucially, there's no imperative to leave a platform just because it might be slowly dying. If it does what you need it to do, and do it well, the effort to switch is unlikely to be worth it. SourceForge is still around, and still (strangely enough) servicing some projects -- it's not like anyone got left behind because they failed to see that SF was "slowly dying" in time.
Well, I'm not exactly a random guy. I have a lot of involvement in open source out there plain to see, and sr.ht itself is open source so you can just run it yourself.
>Crucially, there's no imperative to leave a platform just because it might be slowly dying. If it does what you need it to do, and do it well, the effort to switch is unlikely to be worth it. SourceForge is still around, and still (strangely enough) servicing some projects -- it's not like anyone got left behind because they failed to see that SF was "slowly dying" in time.
SF has also been injecting adware into software hosted on it. You stay behind at the expense of everyone around you.
And honestly - it's a lot easier, at least for me, to trust a person whose name and email address I know than a faceless company with interests that don't align with mine.
45 comments
[ 3.3 ms ] story [ 96.0 ms ] threadIs this a Stackoverflow competitor or just some sort of watercooler to talk about Github in general?
Feels a little bit random to me.
And the Atom discussion area is too (but that's been up for a while): https://discuss.atom.io/
I wonder what was their experience with Discourse like.
I suppose it's just not launched yet. Else you'd at least expect a blog post.
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.
Look at the navigation hierarchy. There are two nav background colors, but you can barely see the difference (even on a new MBP). The search input blends into the nav background, and not in a stylistic way, it seems completely on accident.
The "Community Forum" logo type looks off brand.
The iconography illustration in the masthead was mailed in. It's just the same two icons copy pasted.
The card layout at the bottom seems very un-github as well. They are typically very good at handling large amounts of text and information, but those cards are really hard to read. They bounce around from center-aligned lists (usually a bad idea) to nested columns.
I will say the community search is nice.
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".
[1]: http://www.magillreport.com/Spamhaus-Provides-Answers-Part-F...
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.
[0]: https://www.mxsasha.eu/blog/2014/03/04/definitive-guide-to-c...
[1] https://github.com/blog/2457-connect-with-developers-around-...
If you're a pessimist like me you've kept a mental list of demerits (like this weird forum) that add up to a picture of a slowly dying platform. Join mine instead and postpone the cold grip of death!
Crucially, there's no imperative to leave a platform just because it might be slowly dying. If it does what you need it to do, and do it well, the effort to switch is unlikely to be worth it. SourceForge is still around, and still (strangely enough) servicing some projects -- it's not like anyone got left behind because they failed to see that SF was "slowly dying" in time.
>Crucially, there's no imperative to leave a platform just because it might be slowly dying. If it does what you need it to do, and do it well, the effort to switch is unlikely to be worth it. SourceForge is still around, and still (strangely enough) servicing some projects -- it's not like anyone got left behind because they failed to see that SF was "slowly dying" in time.
SF has also been injecting adware into software hosted on it. You stay behind at the expense of everyone around you.
And honestly - it's a lot easier, at least for me, to trust a person whose name and email address I know than a faceless company with interests that don't align with mine.