• Decronym@lemmy.decronym.xyzB
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    11 months ago

    Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

    Fewer Letters More Letters
    CA (SSL) Certificate Authority
    DNS Domain Name Service/System
    HTTP Hypertext Transfer Protocol, the Web
    HTTPS HTTP over SSL
    IP Internet Protocol
    SSL Secure Sockets Layer, for transparent encryption
    TLS Transport Layer Security, supersedes SSL
    VPN Virtual Private Network

    6 acronyms in this thread; the most compressed thread commented on today has 6 acronyms.

    [Thread #910 for this sub, first seen 8th Aug 2024, 09:05] [FAQ] [Full list] [Contact] [Source code]

    • dhtseany@lemmy.ml
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 year ago

      I still haven’t heard a convincing argument to not use .local and I see no reason to stop.

      • anytimesoon@feddit.uk
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 year ago

        I’m using .home and have not had any issues. Would you mind sharing what problems you’ve come across so I know what to expect?

        • ayyy@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          The main problem I have is waking up in the middle of the night worrying that ICANN pulled some more stupid corrupt bullshit that only makes networking worse and breaks my config.

          Just look elsewhere in this thread: someone thinks that using .honk as a joke is safe. But what about .horse? .baby? .barefoot? .cool? (I stopped scrolling through the list at this point but you can see how arbitrary and idiotic things have become.)

  • Wilzax@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 year ago

    Why do I care what ICANN says I can do on my own network? It’s my network, I do what I want.

      • Wilzax@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 year ago

        Well as long as the TLD isn’t used by anyone it should work internally regardless of what ICANN says, especially if I add it to etc/hosts

        • friend_of_satan@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          Sure, you can do whatever you want. You could even use non-rfc1918 addresses and nobody can stop you. It’s just not always a great idea for your own network’s functionality and security. You can use an unregistered TLD if you want, but it’s worth knowing that when people and companies did that in the past, and the TLD was later registered, things didn’t turn out well for them. You wouldn’t expect .foo to be a TLD, right? And it wasn’t, until it was.

        • Magiilaro@feddit.org
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          German router and network products company AVM learned the hard way that this is a bad idea. They use fritz.box for their router interface page and it was great until tld .box became publicly available and somebody registered fritz.box.

          Having a reserved local/internal only tld is really great to prevent such issues.

    • Melllvar@startrek.website
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      The value of the DNS is that we all use the same one. You can declare independence, but you’d lose out on that value.