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

Varnish saves the day, in unexpectedly awesome ways.

Four and half years ago, I wrote a blog post about Varnish, a 'front-end proxy' for webservers. My best description of it then was as a protective bubble, analogous to how it's namesake is used to protect furniture. I've been using it happily ever since.

But last week, I got to really put Varnish through a test when the picture here, posted by Fair Vote Canada (one of my clients), went viral on Facebook. And Varnish saved the server and the client in ways I didn't even expect.

1. Throughput

Varnish prides itself on efficiently delivering http requests. As the picture went viral, the number of requests was up to about 1000 per minute, which Varnish had no trouble delivering - the load was still below 1, and I saw only a small increase in memory and disk usage. Of course, delivering a single file is exactly what Varnish does best.

2. Emergency!

Unfortunately, Varnish was not able to solve a more fundamental limitation, which was the 100Mb/s network connection. Becaus…

What to do in the age of Trump?

Well, that's the question of the day. If you're part of an organization that does advocacy work, rather than waiting to see what happens first, might as well get yourself ready, even if the details are sketchy still. Here's one opportunity that's ready for you now, message courtesy of Steve Anderson of OpenMedia.

OpenMedia, David Suzuki Foundation, SumOfUs and a range of other organizations are supporting a new shared set of civic engagement tools.

Vancity Community Foundation is providing some support to subsidize some of the cost of the tools to select values-aligned organizations that sign up before February 28th.

Interested? You can learn more or book a demo from here: http://tools.newmode.net/

Here's some live examples of the tools you can take a look at:

1. Click to Call: http://www.davidsuzuki.org/blogs/healthy-oceans-blog/2016/11/to-help-protect-canadas-oceans-weve-made-it-easy-to-call-your-mp/#newmode-embed-4-266

Check out this video of David Suzuki's d…

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…