aeden

You should be very concerned about your registrar, then, because they are not paying attention to ICANN policy.

No, this is incorrect - it is part of the new Registry Registrar Agreement that ICANN ratified earlier this year. It goes into effect 1 January. All accredited registrars will have to agree to it this year to retain their accreditation.

The difference is that the registrar is now obligated to shut down any domains where the registrant changes first name, last name or email address and does not verify the email address using the link from the sent email. This is why it's such a big deal.

If the organization makes it clear to potential hires before they are hired that the company has an open salary policy then the potential hire can choose to maintain their privacy and work elsewhere that does not have an open policy. In this case it probably is not an intrusion into employee privacy.

If an organization were to do this after the fact (i.e. when there are already employees on board) then I think you are right.

HipChat provides a couple things that I don't think you can get from Skype:

1. Searchable backlog for all discussions.

2. API for connecting bots (which can be used for C&C).

3. Web-based and native clients.

4. Public and private rooms chat rooms.

HipChat is more like IRC than like IM, which, for distributed teams, is often very useful.

I'm glad to see they're rolling out all over the US. I really wanted to use them when I first heard about them but couldn't. It looks like I still have to wait until 2014 until they support a small business (i.e. < 20 employees) like mine, but I'm glad to hear they're on track to handle it.

Now the next question: who is going to buy them, how long will it take, and when they are finally purchased will they be torn apart by the buyer?

Java was fun to play with back in the early days. It was fast, had a VM, garbage collection and was OO. Sadly the fun was gradually removed over the years as a result of design-by-committee and a desire to try to solve some of its core issues.

Fortunately you can still have fun on the JVM, even though I prefer to avoid it these days given its current custodians.

Interesting. I spoke about this concept at Speakerconf Munich in 2012. I'm happy someone is working on it and at the same time surprised that someone was bold enough to try. :-)

Come for the conference, stay for Paris. Seriously, if you've never been to Paris you really should do yourself a favor and hang out before or after the conference. It's an amazing city and October is a really great time to be there.

Yes! Why is support for PUT and DELETE not specified in HTML specs? Also, why hasn't a browser implementation gone ahead and added support for both of those verbs as an extension beyond the spec?

Does this work with private repos? If so then SHUT UP AND TAKE MY MONEY!

There was a really good post earlier this year about how Erlang does scheduling (http://jlouisramblings.blogspot.fr/2013/01/how-erlang-does-s...). I think one of the important takeaways is this: "[Erlang] values low latency over raw throughput, which is not common in programming language runtimes". It's worth a quick read.

Ultimately I find that Erlang's strength is not one thing or another, it's a combination of all of its traits: from the functional nature, to OTP for providing a consistent application structure, to its VM; all of these things put together make it interesting and useful.

I've yet to get into Haskell (I will eventually) but I really do find that constructing applications in a functional manner, with state being stored in independent processes within the running application, is a superior way to build systems.

One final note: I really like Go as well, for very specific reasons. Go's resource usage (both in terms of CPU consumption and RAM) is soooo nice, especially coming from Ruby. I was never a C programmer but I can wrap my head around Go and use it to build low resource usage apps with specific purposes, and sometimes this is exactly what is required.

I'll be presenting on using Erlang for an authoritative DNS server at StrangeLoop this year (https://thestrangeloop.com/sessions/erlang-for-authoritative...). If you can make it hopefully you'll get some good tidbits on why I selected Erlang and what kinds of benefits and drawbacks became evident as the system developed. If not then perhaps the sessions will be recorded (I believe they are supposed to be, but I'm not 100%).

My experience was quite similar, although it took me three tries to get it. I think it was http://learnyousomeerlang.com that finally helped me understand enough to really start to enjoy Erlang.

Unfortunately this may not be sustainable in the long run unless more people create new businesses in France, and starting a business here seems daunting due to the expense for the social and welfare system. The more I learn about the welfare system in France though the more I believe that building a profitable business here is possible, but it takes an understanding on how to work within the system. The problem is that there will continue to be cheaper options by setting up shop outside of France and that will continue to be an attractive option to low-margin businesses.

The point being that you do it once for a repo, and then never again (in most cases).

You'll get the current prices if you open your account and activate it before July 1st. Even if you're in the trialing period when the price changes, you'll still remain on the current pricing plan (until you change plans).

Thanks, I've updated it so the logo goes to the primary site. There was a link in the footer, but you'd never see it.

1. We've invested a significant amount of time and capital into our Anycast network. There are both up front and ongoing costs for this. We could make due with the revenue we have now but it would leave little margin.

2. We want to hire additional developers so we can get our ICANN accreditation and add new functionality to the system. I won't go into specifics, but we have a long backlog of things we want to make. We're still going to hire slowly and deliberately, however we want to grow none-the-less.

3. We feel that the value to customers is higher than what we are charging now, and thus we are adjusting the prices for that reason as well.

Anthony Eden, founder of DNSimple here. I'm happy to take questions or comments here or directly through our support address (support@dnsimple.com), regardless if you are a customer or not.

Our goal is to be transparent about what we're doing and why we're doing it.

It's somewhat random, so it seems you had good luck today.

Yep, it seems the same registry runs .io, .sh and .ac.

It looks like all of the nic.io root name servers are delegating again.

On top of that some customers will still end up on the name servers that are still failing, resulting in NXDOMAIN results still ending up cached in resolvers.

Only because the market will bear the cost.

Unfortunately it may appear up for you and for monitoring systems yet still not resolve for others, depending on DNS cache freshness as well as which root name server you (randomly) fall on.

It is not possible to move away from them. nic.io is the registry for .io domains, so you can't move to anyone else. They also act as a registrar for their own TLD, so you could move to another registrar, but ultimately they're responsible for .io delegation.

Anthony from DNSimple here. I'll pass along what I know so far: some of nic.io's name servers appear to be no longer delegating .io domains out to authoritative name servers. Some of their name servers are still delegating properly, but some are not.

This issue also affects .sh and .ac TLDs I believe since they are the same registry. If I find out anything new I'll post on Twitter in the @dnsimple account and here.

No, this was not due to open resolvers in this case. We do not run public resolvers - we only provide authoritative DNS.

Yes. We use it for our redirector (which is the project I mentioned that I switched over) and we're using it for a new zone server that we're working on that is used by our new name servers (which are written in Erlang).