But still, nice if you want to try it out and test with it.
Nobody cares that your app is written in Rails of NodeJS. People care that it works and does what matters to them. IPv4 is doomed to not work at some point so we "tech nerds" have to care and do something about it.
> IPv6 is used by nobody
From the top of my mind, many of the french ISPs have IPv6 ready on the customer side, a radio button click away, while some are even on by default. I can readily assume that today, every worthwhile machine connected to a LAN supports at least IPv6 local scope. Also, every single Mac out there uses an IPv6 VPN (over IPwhatever) when (at least) Back to my Mac is active (ifconfig utun0).
> in five years it will still be nowhere
Unless you settle for impractical definitions of "nowhere" as "not ubiquitous", it is definitely there already. IPv6 does solve real problems today, locally and globally.
I think this is one of the key points that certain people end up missing.
Windows Vista and later can do IPv6 by default, recent versions of OS X will do it by default as well. All an ISP needs to do is send a user a router which can handle IPv6 traffic - and suddenly the entire network will start doing IPv6 traffic with places like Google who are IPv6 ready.
It will just happen! Add the IPv6 ready equipment and the traffic will flow. The only problem is certain ISPs who are still stuck with their heads in sand, not providing IPv6 connectivity, and still providing customers equipment which can't deal with IPv6 traffic - some of which might not be possible to upgrade.
January 2011: 0.24%
January 2012: 0.41%
January 2013: 1.07%
Not-quite January 2014: 2.54%
Which means that it will be ubiquitous within 5 years, if it carries on this trend.
2016: 10%
2017: 20%
2018: 40%
2019: 80%
Not quite ubiquity. Also, expect some flattening of the growth rate.
I'd also like to mention that we do not have a static IP, it just changes less often than it did with DSL.
[1] http://www.kabeldeutschland.de/portal/faq/article/id/631 (German)
People will start to care when IPv6 takeup hits critical mass and we start seeing services optimised for it. When people start seeing services they want to use not working as well through layers of NAT, they start asking their ISPs why they are having a problem and their friends on other ISPs aren't. Maybe at some point services will start charging a premium for IPv4 access (so IPv6 users aren't subsidising those who haven't moved forward yet) like on retail business did for IE6/7 users (http://www.bbc.co.uk/news/technology-18440979) then people will care. That seems extreme though and might alienate users, less severe option would be to serve more adverts.
There are some places where things are already heading towards being IPv6 only. A friend of mine noticed this when out east for a work related trip, the hotel he was in provided Internet access but IPv6 only internally. They provided a 6-to-4 gateway so IPv4 only sites worked fine (with everyone from several places looking to be coming from the same address) but your device had to speak IPv6 to connect to the network in the first place (which his phone didn't).
When I'm working from outside home, I use a tinc VPN to access my IPv6 services, and also redirect my IPv6 traffic through my home network.
Other fun experiment: if you are ipv6-enabled, look at the percentage of bittorrent peers who are in ipv6 vs ipv4. IPv6 is growing.
It will be a deal in 1-2 years. The world rotates fast these days.
I know that it lists "or about $xx.xx per month" next to the credit cost, but why in the hell even have the credits in the first place? It's easier to just use the actual costs in the customer's local currency than have them try and figure out what exactly a credit/"coin" is worth.
Considering their motto is "No bullshit" you'd have thought they'd just give you the prices and leave you to it
* Being "cloud-ish" and have a pay-as-you-go system * Computing a price to use a 256MB of RAM for 3 hours in real currency was too complicated (like, for example : 0.0000174€) * Having no surprise at the end of the month, as some hosting providers compute the global use and bill the consumption at the end of the month (you may have surprise) * Using credits, to create a new server, adding a new network interface, etc, you do not need to buy 'resources' like it was before * There are two interfaces : historic usage of credits by resources, display the credits consumption as what you use in real currency * No multiple expiration date by product/resource * ...
Many of those advantages are described here : http://wiki.gandi.net/en/iaas/references/billing/credits
As usual, any enhancement/improvement is welcome :-)
https://www.nearlyfreespeech.net/
The latter two do keep track of fractional charges. They deduct $0.01 from prepaid credits once that much is owed. Since you accept multiple currencies, this becomes a bit more complex but still doable. For example, let the user choose the currency to display, or pick a single standard currency (euros?) and use it as your units.
Tarsnap and NFSn choose to refund your prepaid credits if and only if you close your account with them. Not every prepaid system lets you get your prepayments back at all. I am fine with this: I am willing to pay a bit more (prepayment without refund) in order to limit my liability to the amount I intend to pay.
BUT, our bank does it for us, so you can now auto-credit your prepaid account using probe (no more credit, auto credit every month, ...)
And as resources can be micromanaged (per hour, via their api), you'd end up with tiny fractions of local currencies and rounding issues while all credit operations are done on integer afaik.
I transferred my domains away after that and decided it wasn't wise to mix services together due to this risk. So now I have domains with Tucows, DNS with Hurricane Electric and VPS with a provider that only does VPS. And I don't bother running Tor nodes any more.
Gandi allows any service to be run on its platform, abuse is not allowed as it isn't on other provider.
Thus, they must do the necessary legal operations according to the law, policies and their contract.
From the Gandi blog: (http://www.gandibar.net/post/2007/01/11/Gandi-fights-back-ag...)
Domains registered with Gandi must be used in accordance with the rights of third parties (copyrights, intellectual property rights, personality rights, etc.), and current applicable laws and regulations.
For example, Gandi does not tolerate activity that is morally objectionable or that poses a threat to public order, that spreads Computer Contaminants (Viruses, Trojans, etc.), and/or that engages in fraudulent activity such as Identity Theft.
DigitalOcean has excellent documentation and very fast responses to my support queries. Their prices are lower. I'll keep using them and recommending them to others.
Gandi gives me very good performance as well as a few extras that keep me interested. They also offer a broader range of services (like domain registration) and have an excellent track record of supporting good causes. I'll keep using them and can recommend them as well.
If I (maybe unfairly) divide user skill levels up into thirds, I'd recommend DigitalOcean to an average user, and Gandi to those with above & below average needs. Basically, Gandi has simpler products for those new to hosting and also rolls out new things like IPV6 and DNSSEC faster if you really want to test them. These aren't always supported (you break it, you may be on your own) but are available early compared to other hosts.
Rather than look at this as a zero sum proposition, take a look at Gandi's 'supports'[1] page, realise that they continue to thrive despite no advertising, and think about whether you want in on that deal.
This is fantastic news. I have a private network full of them.
With IPv6 you can just ssh into the box directly.
Alternative: http://www.opendns.com/technology/ipv6/
Someone thought it would be cool to publish AAAA addresses before the networky folks had configured v6. In production. Laffs were had.
We're not as cheap as gandi though, heh :)
As a side note, I heard rsync.net have ipv6 too, and offer a special HN discount! https://news.ycombinator.com/item?id=6766478
This is not true. All new LIRs can still receive a /22 - http://www.ripe.net/lir-services/resource-management/allocat...
> This means that an LIR can only receive a one-time /22 allocation (1,024 IPv4 addresses) if it can justify the need and already has an IPv6 allocation