@thehatfox@lemmy.world to Selfhosted@lemmy.worldEnglish • 4 months agoICANN approves use of .internal domain for your networkwww.theregister.comexternal-linkmessage-square150fedilinkarrow-up1502arrow-down15cross-posted to: tech@programming.devsysadmin@lemmy.world
arrow-up1497arrow-down1external-linkICANN approves use of .internal domain for your networkwww.theregister.com@thehatfox@lemmy.world to Selfhosted@lemmy.worldEnglish • 4 months agomessage-square150fedilinkcross-posted to: tech@programming.devsysadmin@lemmy.world
minus-square@fine_sandy_bottom@lemmy.federate.cclinkfedilinkEnglish1•4 months agoNo one is saying it is their job. Merely that using a TLD like .internal requires some consideration regarding ssl certificates.
minus-square@lud@lemm.eelinkfedilinkEnglish-1•4 months agoBut why are people even discussing that? This is about an ICANN decision. TLS has nothing to do with that. Also you don’t really need TLS for self hosting. You can if you want though.
minus-square@fine_sandy_bottom@lemmy.federate.cclinkfedilinkEnglish2•4 months agoBecause people can discuss whatever they like? If you don’t like it just down vote it.
minus-squareJackbyDevlinkfedilinkEnglish1•4 months agoPeople can talk about whatever they want whenever they want. The discussion naturally went to the challenges of getting non-self-signed certificates for this new TLD. That’s all.
No one is saying it is their job.
Merely that using a TLD like .internal requires some consideration regarding ssl certificates.
But why are people even discussing that?
This is about an ICANN decision. TLS has nothing to do with that. Also you don’t really need TLS for self hosting. You can if you want though.
Because people can discuss whatever they like?
If you don’t like it just down vote it.
People can talk about whatever they want whenever they want. The discussion naturally went to the challenges of getting non-self-signed certificates for this new TLD. That’s all.