• key95@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    5
    ·
    11 hours ago

    Yes. Sorry that I didn’t make clear, I am awarw of those kind of work arounds. However, strange that I have to point out the obvious, that yoir “solution” completely defeats the purpose of the endeavour. You might be stuck in believing, it’s about owning the name, but it’s about control and privacy policies on one’s own terms. Something, that should be as obvious as blinking neon-lights, considering context. The name of a domain is mere decoration, with little functionality (i.a. think memorability, ease of verbal transmission etc.).

    • CorrectAlias@piefed.blahaj.zone
      link
      fedilink
      English
      arrow-up
      4
      ·
      edit-2
      10 hours ago

      I didn’t say anything about “owning the name” other than just buying a domain in general (which you’d also need to do for something self hosted). I am simply saying that using providers that allow for catch all can give you privacy while also giving you the ability to jump ship.

      My primary domain, for example, is not memorable, and it does not have ease of verbal transmission. It’s a string I randomly generated.

      What is this endeavor? Control? Your own domain gives you control. Privacy? This is dependent on your provider, VPS, or otherwise. SMTP is generally blocked on residential IPs, so you’re going to have to trust and give up control and some level or privacy somewhere. Having a domain gives you the ability to self host if you desire, and if you don’t want to do that, then having a domain gives you the ability to easily change mail providers if needed, without the need to change hundreds of accounts.