3 ms·

> but I fundamentally disagree with you ["We actually have a functioning standard for this on mobile"] I wouldn't expect any less. https://quoteinvestigator.c

by cxr 5y ago

> but I fundamentally disagree with you ["We actually have a functioning standard for this on mobile"] I wouldn't expect any less. https://quoteinvestigator.com/2017/11/30/salary/ https://quoteinvestigator.com/2017/11/30/salary/ > In practice [...] There's your problem. Try fixing that.

Spivak 5y ago
Moving everything under a single domain makes no sense for the use-case of cross-organization sharing though. Domain as as the root identity on the web is just broken and there's no way to make it work. mysharedhosting.com/customer1 mysharedhosting.com/customer2 Two separate identities. Is it even possible to let the browser know that they should be segmented? Nope. customer1.mysharedhosting.com customer2.mysharedhosting.com How about this? No again, not without getting yourself on the suffix list which is just a hack. mycompany.com joinmycompany.com Can you tell the browser that these are actually the same and shouldn't be segmented? Nope!
- tatersolid 5y ago
  This makes more sense and doesn’t dilute your brand, improves SEO, and helps protect against phishing by making your customers and staff look for a single known-good domain: https://mycompany.com/join
horsawlarway 5y ago
Your take is wrong. Having a domain is identical to having a driver's license: This org says I am "X". It is fundamentally different from uniquely identifying me. I am still the same person if I give you my library card - a different ID from a different org that says I am "Y".
- cxr 5y ago
  Nah, the problem is definitely on your end. > Having a domain is identical to having a driver's license: This org says I am "X". Nope. You just described two different documents. http://horsawlarway.example/drivers-license.html http://horsawlarway.example/drivers-license.html http://horsawlarway.example/library-card.rdf http://horsawlarway.example/library-card.rdf It's very odd the position you're taking here, given the sentiment in your other tirade about being digital sharecroppers to Facebook and Google <https://news.ycombinator.com/item?id=27369652 https://news.ycombinator.com/item?id=27369652>. Your proposed solution is dumping more fuel in their engines—which is why it's the kind of solution they prefer themselves—and completely at odds with e.g. Solid and other attempts to do things thing would actually empower and protect individual users. I'm interacting with your digital homestead, why are you so adamant about leaking my activity to another domain?

by cxr 5y ago

Spivak 5y ago

Moving everything under a single domain makes no sense for the use-case of cross-organization sharing though. Domain as as the root identity on the web is just broken and there's no way to make it work. mysharedhosting.com/customer1 mysharedhosting.com/customer2 Two separate identities. Is it even possible to let the browser know that they should be segmented? Nope. customer1.mysharedhosting.com customer2.mysharedhosting.com How about this? No again, not without getting yourself on the suffix list which is just a hack. mycompany.com joinmycompany.com Can you tell the browser that these are actually the same and shouldn't be segmented? Nope!

tatersolid 5y ago
This makes more sense and doesn’t dilute your brand, improves SEO, and helps protect against phishing by making your customers and staff look for a single known-good domain: https://mycompany.com/join

horsawlarway 5y ago

Your take is wrong. Having a domain is identical to having a driver's license: This org says I am "X". It is fundamentally different from uniquely identifying me. I am still the same person if I give you my library card - a different ID from a different org that says I am "Y".

cxr 5y ago
Nah, the problem is definitely on your end. > Having a domain is identical to having a driver's license: This org says I am "X". Nope. You just described two different documents. http://horsawlarway.example/drivers-license.html http://horsawlarway.example/drivers-license.html http://horsawlarway.example/library-card.rdf http://horsawlarway.example/library-card.rdf It's very odd the position you're taking here, given the sentiment in your other tirade about being digital sharecroppers to Facebook and Google <https://news.ycombinator.com/item?id=27369652 https://news.ycombinator.com/item?id=27369652>. Your proposed solution is dumping more fuel in their engines—which is why it's the kind of solution they prefer themselves—and completely at odds with e.g. Solid and other attempts to do things thing would actually empower and protect individual users. I'm interacting with your digital homestead, why are you so adamant about leaking my activity to another domain?