Skip to main content

Are you living in a bubble?

I've been trying to extract a domain from Namespro, a registrar. After (I hope) springing it from them, I gave them a little honest feedback. I'll provide their answer here verbatim, enough said. Okay, almost enough: I want to note that, considering the spelling mistakes, the support person who wrote this probably believed it. And for reference: my favourite registrar (hover.com) provides users the ability to generate auth codes themselves, not to have to search badly worded help systems to find the right invocation. In this case, it required a request via a hidden form, and a simple email request was ignored. After the invocation, they came back with an "are you really, really sure" reply to the ticket, which it took me a few days to notice as well. They provide no phone number to actually talk to a support person. In other words, unless you really know what you're doing and have a lot of patience, the chance of getting your domain out of Namespro is pretty slim.

Me:

If you really want an honest answer to your question: it's because of your policy of making it so hard to transfer anything our of your system. You appear to deliberately obscure the process of moving services out of your clutches. I'm not interested in doing business with a company that I don't trust to be upfront and honest.

Them:

Thank you for your reply and comment. The process of getting an Auth Code is not made public is because very few Namespro.ca users transfer out from Namespro.ca to another registrar to being with.

That being said, we have forwarded our suggestion to our management team for further review.

Popular posts from this blog

Me and varnish win against a DDOS attack.

This past month one of my servers experienced her first DDOS - a distributed denial of service attack. A denial of service attack (or DOS) just means an attempt to shut down an internet-based service by overwhelming it with requests. A simple DOS attack is usually relatively easy to deal with using the standard linux firewall called iptables.  The way iptables works is by filtering the traffic based on the incoming request source (i.e., the IP of the attacking machine). The attacking machine's IP can be added into your custom ip tables 'blacklist' to block all traffic from it, and it's quite scalable so the only thing that can be overwhelmed is your actual internet connection, which is hard to do.

The reason a distributed DOS is harder is because the attack is distributed from multiple machines. I first noticed an increase in my traffic about a day after it had started - it wasn't slowing down my machine, but it did show up as a spike in traffic. I quickly saw that…

Confused by online payment processing? You're not alone.

In the old days during "polite" conversation, it was considered rude to talk about sex, politics, religion and money. You might think we're done with taboos, we're not (and I'll leave Steven Pinker to make the general argument about that, as he does so well in The Better Angels of Our Nature).

The taboo I'm wrestling with is about money - not how much you make, but about online payment processing, how it works, and what it costs. In this case, I think the taboo exists mainly because of the stakes at hand (i.e. lots of money) and the fact that most of those who are involved don't get much out of explaining how it really works - i.e. the more nuanced communications are overwhelmed by sales-driven messaging, and the nuanced stuff is either proprietary secrets or likely to get slapped down by the sales department.

In other words, if you want to really understand about online payment processing because you want to decide between one system and another, you'…

Upgrading to Drupal 8 with Varnish, Time to Upgrade your Mental Model as well

I've been using Varnish with my Drupal sites for quite a long while (as a replacement to the Drupal anonymous page cache). I've just started using Drupal 8 and naturally want to use Varnish for those sites as well. If you've been using Varnish with Drupal in the past, you've already wrapped your head around the complexities of front-end anonymous page caching, presumably, and you know that the varnish module was responsible for translating/passing the Drupal page cache-clear requests to Varnish - explicitly from the performance page, but also as a side effect of editing nodes, etc.

But if you've been paying attention to Drupal 8, you'll know that it's much smarter about cache clearing. Rather than relying on explicit calls to clear specific or all cached pages, it uses 'cache tags' which require another layer of abstraction in your brain to understand.

Specifically, the previous mechanism in Drupal 7 and earlier was by design 'conservative' …