Hacker News Reader

Comment by BluSyn | Hacker News Reader

I'll play devils advocate. I'm fine with this being default assuming there's an option for advanced users to disable it. 95% of Chrome users will not notice or care about this change, and in fact will make things simpler for them in the long run.

Also, seriously people, ditch www. subdomains already. It's not 2002 anymore. I cringe so hard when I see that crap in print ads and billboards.

View on HN

> ditch www. subdomains already

Sweet, unless you use any other subdomains for web pages, or want to in the future.

Usually you don't want cookies for domain.com to affect api.donain.com, admin.domain.com, test.domain.com etc.

I actually love www subdomains - the origin tells you it is a website.

Separating api. and www. makes authentication messier (thus less secure). [At least I haven't seen a clear and good one yet.]

And with HTTP/2 you don't have to worry about static stuff slowing down or crowding out API req-resp data.

> I actually love www subdomains - the origin tells you it is a website.

It lacks that connotation for the regular user.

I don't think so. Let's say you have one of the new TLDs for your site, say "new-york.florist", a nice domain. It's my belief that writing "new-work.florist" on your ads, business cards or merchandise will not let regular users know that it's a domain name. Writing www.new-york.florist will help indicate that this is your website.

Adding all the new TLDs have made the www prefix more useful than ever.

Or we could put `https://` in front and the www. is redundant.

Let's say you have your business advertised on your vehicle.

Put www.somthing.com on there and it is obvious to most how to find your business online.

https:// is ugly and longer IMHO.

Wouldn't you place it next to some other contact details? A regular person can deduce it's a internet address.

Exactly why don't you want your site's cookies to affect your site? Do you think perhaps you're abusing what cookies are meant to do?

Doing so often requires non-standard DNS hacks such as CNAME flattening or ANAME/ALIAS records to achieve the aesthetic preference of a bare domain name. The www subdomain is still an obvious choice for anyone that's still running their own DNS, until the domain root aliasing gets a standard implementation.

There are legit reasons why you should use a www. sub domain: https://bjornjohansen.no/www-or-not

Quite a few of those "cookies can be read by third parties" things boil down to "we don't know how to use SameSite".

Reply on news.ycombinator.com