Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

#c0ffee is the color

c0ffee.surge.sh

Post reply on HN
Print view View original

41–50 of 127 posts

Re: #c0ffee is the color

#41

Post by germanier »

kyledrake wrote: post #38

This isn't related to the post content (which was great), but I noticed that HN lists the domain as "surge.sh", which doesn't make a lot of sense because surge.sh is just the web hosting service this site is on. With the web, the convention right now is to treat the subdomain as a different security origin (with the exception of www). So the link should show c0ffee.surge.sh, not surge.sh. If this is a manual setting,…

There is the Public Suffix List but it doesn't seem to contain those domains. Does HN use that list? https://publicsuffix.org

Re: #c0ffee is the color

#44

Post by Twirrim »

asmosoinio wrote: post #16
lol768 wrote: post #3

Got to admit I was hoping it'd be a coffee-ish colour before I sorta parsed the colour in my head and realised it was mostly green. With that said there are some pretty cool ones (e.g. 5afe57 = safest = a green) that do match up. Can't say I can think of many hugely practical uses for this, but it's kinda neat!

I also plan to use 54FE57 somewhere. Have to do that. Though with the numbers in the beginning it's not as readable as e.g. BADA55.

Hmm. BADA55 didn't make it on to that site, strangely enough.

Re: #c0ffee is the color

#45

Post by kyledrake »

germanier wrote: post #41
kyledrake wrote: post #38

This isn't related to the post content (which was great), but I noticed that HN lists the domain as "surge.sh", which doesn't make a lot of sense because surge.sh is just the web hosting service this site is on. With the web, the convention right now is to treat the subdomain as a different security origin (with the exception of www). So the link should show c0ffee.surge.sh, not surge.sh. If this is a manual setting,…

There is the Public Suffix List but it doesn't seem to contain those domains. Does HN use that list? https://publicsuffix.org

I was warned to not use it by it's maintainers because it would make the root of our domain potentially unusable. If I understand it correctly, it's designed for things like domain roots (.com), not domains with subdomains.

Re: #c0ffee is the color

#46

Post by sr2 »

germanier wrote: post #41
kyledrake wrote: post #38

This isn't related to the post content (which was great), but I noticed that HN lists the domain as "surge.sh", which doesn't make a lot of sense because surge.sh is just the web hosting service this site is on. With the web, the convention right now is to treat the subdomain as a different security origin (with the exception of www). So the link should show c0ffee.surge.sh, not surge.sh. If this is a manual setting,…

There is the Public Suffix List but it doesn't seem to contain those domains. Does HN use that list? https://publicsuffix.org

Surge is not notable enough to be on that list. I think it only applies to institutions, museums, and things like that. Judging from this anyways: https://publicsuffix.org/list/public_suffix_list.dat

Re: #c0ffee is the color

#48

Post by myth_buster »

lol768 wrote: post #3

Got to admit I was hoping it'd be a coffee-ish colour before I sorta parsed the colour in my head and realised it was mostly green. With that said there are some pretty cool ones (e.g. 5afe57 = safest = a green) that do match up. Can't say I can think of many hugely practical uses for this, but it's kinda neat!

Coffee beans before roasting are infact "Green"[0] and are referred as green coffee. The roasting process makes it brown.darker.

[0] https://en.wikipedia.org/wiki/Coffee_roasting#Roasts

Re: #c0ffee is the color

#50

Post by jacobwg »

kyledrake wrote: post #45
germanier wrote: post #41

Earlier quoted context omitted.

There is the Public Suffix List but it doesn't seem to contain those domains. Does HN use that list? https://publicsuffix.org

I was warned to not use it by it's maintainers because it would make the root of our domain potentially unusable. If I understand it correctly, it's designed for things like domain roots (.com), not domains with subdomains.

It is useful for some security protections in such a hosted subdomain scenario which is why herokuapp.com, herokussl.com, github.io, gitlab.io, etc are on the list, but yes, you would not be able to use your primary domain there, you'd need a dedicated domain for your customers and their subdomains.

Namely, having your hosting domain on the public suffix list means that browsers will not allow setting cookies on the suffix (similar to how you cannot set a cookie for ".com"), which prevents rogue websites on the same root domain from stealing sensitive cookie values from other subdomains.

Post reply on HN