3 ms·

pepsi@pepsi.com seems better than pepsi@pepsi.pepsi in my opinion.

by fredsted 15y ago

eli 15y ago
moreover, it would make no sense to own www.pepsi without also already owning www.pepsi.com
- setrofim_ 15y ago
  Why not? Some companies only own <company>.net or <company>.co.uk, without owning <company>.com.
  - eli 15y ago
    Fair point. But www.pepsi looks broken to me. If you're going to decide you care about people who type addresses in by hand, it seems counterproductive to go against the conventions they're used to. But if new TLDs become common I guess that will change with time.
    - icebraining 15y ago
      www.pepsi does look broken, but http://pepsi/ http://pepsi/ is fine. We just need browsers to stop ignoring bare TLDs, like they do now if you don't put the http:// http:// before.
      - leejw00t354 15y ago
        This opens up more problems though. For example how would the Google Chrome browser work (and search to a degree), does a user who types "pepsi" into their omnibar want to go to http://pepsi/ http://pepsi/ or search for pepsi? It also adds confusion for webmasters trying to parses URLs on their website. When a user types pepsi.com/coke into their blog for example that link can be made clickable to http://pepsi.com/coke/ http://pepsi.com/coke/ where it can't for pepsi/coke
        evincarofautumn 15y ago
        The problem of detecting URLs with weird TLDs could be solved by using relative URLs (RFC 1808 §4) with the protocol omitted. It would put that vestigial // to good use—//coca-cola is a URL just as @cocacola is a Twitter handle.
setrofim_ 15y ago
Yes, but you're not forced to repeat "pepsi". It could be alex@customerrelations.pepsi or inquiries@distribution.pepsi
DanWaterworth 15y ago
there's no need for pepsi.pepsi as the domain, it could be pepsi@pepsi
- davidu 15y ago
  There's a ton of legacy code and email software that will make that not work. At best, it would be pepsi@pepsi. (note trailing dot). My buddy used to be root@ws. but only a few MUAs and MTAs could handle delivering mail there, and always with the trailing dot.
  - ianburrell 15y ago
    You have to put the dot at the end to make it a fully-qualified name otherwise the resolver will think it is a hostname and add the local domain.
coopdog 15y ago
Why do I suddenly feel like buying pepsi..

pepsi@pepsi.com seems better than pepsi@pepsi.pepsi in my opinion.

eli 15y ago

moreover, it would make no sense to own www.pepsi without also already owning www.pepsi.com

setrofim_ 15y ago
Why not? Some companies only own <company>.net or <company>.co.uk, without owning <company>.com.
- eli 15y ago
  Fair point. But www.pepsi looks broken to me. If you're going to decide you care about people who type addresses in by hand, it seems counterproductive to go against the conventions they're used to. But if new TLDs become common I guess that will change with time.
  - icebraining 15y ago
    www.pepsi does look broken, but http://pepsi/ http://pepsi/ is fine. We just need browsers to stop ignoring bare TLDs, like they do now if you don't put the http:// http:// before.
    - leejw00t354 15y ago
      This opens up more problems though. For example how would the Google Chrome browser work (and search to a degree), does a user who types "pepsi" into their omnibar want to go to http://pepsi/ http://pepsi/ or search for pepsi? It also adds confusion for webmasters trying to parses URLs on their website. When a user types pepsi.com/coke into their blog for example that link can be made clickable to http://pepsi.com/coke/ http://pepsi.com/coke/ where it can't for pepsi/coke
      - evincarofautumn 15y ago
        The problem of detecting URLs with weird TLDs could be solved by using relative URLs (RFC 1808 §4) with the protocol omitted. It would put that vestigial // to good use—//coca-cola is a URL just as @cocacola is a Twitter handle.

setrofim_ 15y ago

Yes, but you're not forced to repeat "pepsi". It could be alex@customerrelations.pepsi or inquiries@distribution.pepsi

DanWaterworth 15y ago

there's no need for pepsi.pepsi as the domain, it could be pepsi@pepsi

davidu 15y ago
There's a ton of legacy code and email software that will make that not work. At best, it would be pepsi@pepsi. (note trailing dot). My buddy used to be root@ws. but only a few MUAs and MTAs could handle delivering mail there, and always with the trailing dot.
- ianburrell 15y ago
  You have to put the dot at the end to make it a fully-qualified name otherwise the resolver will think it is a hostname and add the local domain.

coopdog 15y ago

Why do I suddenly feel like buying pepsi..