john/capsule
1
0
Fork 0
mirror of https://github.com/jbowdre/capsule.git synced 2024-11-22 13:12:19 +00:00
Code Issues Projects Releases Packages Wiki Activity

update post

Browse source
This commit is contained in:
John Bowdre 2024-03-18 19:01:28 -05:00
parent b28bc4d27b
commit 340dbec817
2 changed files with 9 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
gemlog/bad-domain-registrars.gmi
View file

@ -2,7 +2,7 @@ I have a small-but-growing collection of domains. Some are used for public proje
Assembling this collection has taken me through many different domain registrars, with varying levels of user-unfriendliness. If you, as a registrar, do any of (let alone *all* of) the following, know that your business model is hot+wet garbage: Assembling this collection has taken me through many different domain registrars, with varying levels of user-unfriendliness. If you, as a registrar, do any of (let alone *all* of) the following, know that your business model is hot+wet garbage:
* Parking 1000 CNAMEs on newly-registered domains, which then have to be manually removed because you don't offer a user-facing API. * Parking 1000 CNAMEs on newly-registered domains, which then have to be manually removed because you don't offer a user-facing API.*
* Pushing a paid "ID Protection" add-on for domains whose registries already employ WHOIS protection/redaction by default. * Pushing a paid "ID Protection" add-on for domains whose registries already employ WHOIS protection/redaction by default.
* Requiring users to submit a support ticket to request an EPP/auth code so they can transfer to a registrar that doesn't disrespect its customers. * Requiring users to submit a support ticket to request an EPP/auth code so they can transfer to a registrar that doesn't disrespect its customers.
* Automatically re-locking a domain when an auth code is requested so that the first transfer attempt will fail. * Automatically re-locking a domain when an auth code is requested so that the first transfer attempt will fail.
@ -16,4 +16,9 @@ Fortunately, we don't have to do business with shady registrars like that. I've
=> https://porkbun.com/ Porkbun: An Oddly Satisfying Experience => https://porkbun.com/ Porkbun: An Oddly Satisfying Experience
=> https://www.cloudflare.com/products/registrar/ Cloudflare Registrar: Domain registrar with no-markup pricing => https://www.cloudflare.com/products/registrar/ Cloudflare Registrar: Domain registrar with no-markup pricing
On the other hand, if you want a registrar that ticks all the shitty boxes above, gen.xyz is a choice (a bad one). On the other hand, if you want a registrar that ticks all the shitty boxes above, gen.xyz is an option.
===
* Or use a handy utility to nuke 1000 bogus records after shifting DNS responsibilities to Cloudflare:
=> https://cloudflare-utils.cyberjake.xyz/dns/purge/ DNS Purge - Cloudflare Utilities

4
gemlog/bad-domain-registrars.yaml
View file

@ -1,6 +1,6 @@
id: "urn:uuid:7ba24cd6-a430-4234-9210-2cc6bec668f2" id: "urn:uuid:7ba24cd6-a430-4234-9210-2cc6bec668f2"
title: "Bad Domain Registrars" title: "Habits of Bad Domain Registrars"
published: "2024-03-18T23:44:56Z" published: "2024-03-18T23:44:56Z"
updated: "2024-03-18T23:45:03Z" updated: "2024-03-18T23:44:56Z"
summary: |- summary: |-
If you, as a registrar, do any of (let alone *all* of) the following, know that your business model is hot+wet garbage. If you, as a registrar, do any of (let alone *all* of) the following, know that your business model is hot+wet garbage.