this post was submitted on 22 Jun 2024
396 points (99.0% liked)
Technology
59575 readers
5890 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The registrar doesn't have anything to do with TLS. I use LetsEncrypt on my domains through NameCheap, no problems whatsoever. I get my hosting elsewhere (previously Vultr, currently Hetzner).
A company's business practices are relevant regardless of which of their services you're subscribing to.
I care if they have poor privacy policies or something in features I don't use as that can indicate future impact on features I do use, but I don't care if they have limited product offerings generally. So to me, it's completely irrelevant.
You should probably separate your hosting from your registrar anyway so you can switch one without impacting the other. I did just that when I bailed on Vultr due to their unprofessional (IMO) handling of a TOS update (blocked access to my account, so I couldn't close my account w/o accepting the terms), but I didn't have to change my registrar and all that, I just spun up an instance at another host and redirected DNS entries. I also separated my DNS mappings from my domain registrar (they're combined now @ cloudflare, which is a little unfortunate).