Poking around their website, it looks like they used to have all-black keyboards, but they're not available at present...It's not obvious whether they're ever coming back....
PROTIP: Buying a ticket for "next flight to <X>" at the airport using cash gets you instantly flagged for Special Treatment... Handy if you're at a busy airport.:-)
This is what I've been waiting for - word from Boeing and Airbus. Not one media outlet has come out and announced "Boeing says volcano ash not bad for engines". That headline, and that headline alone, will make the "overreaction" claim stick.
Oh, yep... I should probably have mentioned that... Minimo was the previous attempt at a Mozilla-based mobile browser, and Fennec is the new one.
Many of the Fennec-related pages on the Mozilla site still occasionally referred to Minimo up until a few months ago when I last checked...
I'm glad that there's some progress on that front; I look forward to seeing a Windows Mobile release soon... (Or hopefully getting Linux running on my Hermes, and then running Fennec under that...:-) )
It seems to me that a mobile version of Chrome would end up almost easier than the desktop version. Since you can only view one page (or tab, if you will) at a time on a mobile browser...
Mozilla's Minimo running on my Windows Mobile-based phone already runs with tabbed browsing... Just because we're used to ridiculously high-resolution screens doesn't mean we should forget that early computer screens had lower resolutions than many current phone screens...
Umm, also, you seem to have the whole operation of DNS upside down; you start at the root servers, which delegate you to the.com servers, which delegate you to the google.com servers, which can then tell you the address of www.google.com.
Hopefully you also cache the results along the way, so that when you want to find news.google.com later you don't have to go to the root or.com servers, and when you want to find yahoo.com you don't have to go all the way back to the root and can start at.com.
However, when you want to get slashdot.org, you have to go back to the root, which will direct you to the.org servers, etc...
Can you answer a relevant question which is buzzing around in the background - did CommunityDNS and/or Diyixian have permission to advertise the address space?
Also, as someone else above asked, why did you choose to set up a server at that address, given the bandwidth load and technical effort involved?
*shrug* There are 12 other fail-over points. I certainly wouldn't notice if one of the root-servers fell off the internet.
Granted, someone much bigger than me might notice that 8% of their queries are failing and being re-tried... But I don't know how long it would take before it happened...
Really? Where is this documentation? (Not that I don't believe you, I just haven't come across it, and neither, it appears, has the OP...) I'd be very interested to see it, and I know a whole lot of others who would love to see such things up and running...
Firstly, there's nothing spooky about the fake servers, the article lists who was running them... Not listing them in the summary was just simple Slashdot sensationalisation...
And as far as how they got traffic (which they did, as per the graph in the FA), the hosting companies in question, (in the UK, US, and Hong Kong) started advertising the routes through BGP, (the protocol which tells the backbone routers on the Internet which routers host which IP addresses). So routers which were closer to Community DNS would send their packets to it, while those closer to ICANN would route theirs there instead, and likewise for those closer to ep.net (US) and Diyixian.com (HK).
The IP addresses in question belong to ep.net, so one might argue that they were within their rights to use the address space. Whether Community DNS and/or Diyixian.com were operating with permission or not is unclear at this stage...
Oh, yeah, I realise that. In fact, given that the article states that the transition time is around 6 months, you could probably just update every 3 months, even.
The point is, you have to have some system in place, either manual or automatic, to perform the update... Because it's easy to copy the file the first time, insert it into your configuration master image, and then forget about it as you roll out machines, and leave them in production for years with out-of-date hints files.
I know - I've probably done it on machines before, too... Thankfully I've long since moved away from the naive default BIND setup which includes a copy of the hints file from some arbitrary date, used long after it's safe to do so...
The problem is, if you do grab the hints file from there, you have to make sure you keep refreshing it to stay up to date... Otherwise you're just setting yourself up for the same attack the next time this happens...
That said, I don't know if trusting your upstream provider is any better...
Except that apparently ICANN switched their machine off on May 2nd. However, anticipating such a switch off, three other organisations around the world stepped in over the past 6 months to fill the void, and mostly went undetected for the last 6 months...
Slashdot Mirror
Poking around their website, it looks like they used to have all-black keyboards, but they're not available at present...It's not obvious whether they're ever coming back....
but how did you acquire your ticket? cash?
Yes, actually.
PROTIP: Buying a ticket for "next flight to <X>" at the airport using cash gets you instantly flagged for Special Treatment... Handy if you're at a busy airport. :-)
This is what I've been waiting for - word from Boeing and Airbus. Not one media outlet has come out and announced "Boeing says volcano ash not bad for engines". That headline, and that headline alone, will make the "overreaction" claim stick.
Or something like this...
MS Office skills are marketable at any age.
What exactly are MS Office skills?
Typing, and bold.
"Advanced skills" include italics and
If you check the summary information on the Wikipedia page, it links you to http://www.flickr.com/photos/dannysotzny/3589316608/ which is titled "WGT vom 1.Juni 2009" and claims
so I guess you're onto something...
Surely, that should be
m = e / c^2
But more importantly, that equation is for a particle at rest.
It's a special case of the Energy-momentum relation, for objects as observed from their rest frame.
For light, (or other massless quantities), the relevant special case is:
E = pc
(energy = momentum * speed of light)
Oh, yep... I should probably have mentioned that... Minimo was the previous attempt at a Mozilla-based mobile browser, and Fennec is the new one.
Many of the Fennec-related pages on the Mozilla site still occasionally referred to Minimo up until a few months ago when I last checked...
I'm glad that there's some progress on that front; I look forward to seeing a Windows Mobile release soon... (Or hopefully getting Linux running on my Hermes, and then running Fennec under that... :-) )
I think the trick was downsampling the images to reduce load times, (with a corresponding saving in data consumption as well)...
And plenty of people without unlimited data plans surf on their phone.
Mozilla's Minimo running on my Windows Mobile-based phone already runs with tabbed browsing... Just because we're used to ridiculously high-resolution screens doesn't mean we should forget that early computer screens had lower resolutions than many current phone screens...
The thing I'm confused about is - how is this different from MMIO? Or is the new thing that we can do MMIO for programs when they're on flash?
Umm, also, you seem to have the whole operation of DNS upside down; you start at the root servers, which delegate you to the .com servers, which delegate you to the google.com servers, which can then tell you the address of www.google.com.
.com servers, and when you want to find yahoo.com you don't have to go all the way back to the root and can start at .com.
.org servers, etc...
Hopefully you also cache the results along the way, so that when you want to find news.google.com later you don't have to go to the root or
However, when you want to get slashdot.org, you have to go back to the root, which will direct you to the
HTH. HAND. Cheers.
Oh, and I should probably also say: thanks for all the work you've done so far to contribute to getting DNS to be as useful as it is...
Someday I hope you succeed in getting all the IPv6 stuff going - we'd all like to see that...
Oh, you're here...
Can you answer a relevant question which is buzzing around in the background - did CommunityDNS and/or Diyixian have permission to advertise the address space?
Also, as someone else above asked, why did you choose to set up a server at that address, given the bandwidth load and technical effort involved?
Umm, ICANN puts out a public notice, and then implements a 6-month transition period?
*shrug* There are 12 other fail-over points. I certainly wouldn't notice if one of the root-servers fell off the internet.
Granted, someone much bigger than me might notice that 8% of their queries are failing and being re-tried... But I don't know how long it would take before it happened...
And if they connected to the old l. address?
Really? Where is this documentation? (Not that I don't believe you, I just haven't come across it, and neither, it appears, has the OP...) I'd be very interested to see it, and I know a whole lot of others who would love to see such things up and running...
Firstly, there's nothing spooky about the fake servers, the article lists who was running them... Not listing them in the summary was just simple Slashdot sensationalisation...
And as far as how they got traffic (which they did, as per the graph in the FA), the hosting companies in question, (in the UK, US, and Hong Kong) started advertising the routes through BGP, (the protocol which tells the backbone routers on the Internet which routers host which IP addresses). So routers which were closer to Community DNS would send their packets to it, while those closer to ICANN would route theirs there instead, and likewise for those closer to ep.net (US) and Diyixian.com (HK).
The IP addresses in question belong to ep.net, so one might argue that they were within their rights to use the address space. Whether Community DNS and/or Diyixian.com were operating with permission or not is unclear at this stage...
Cool, then we are in agreement. :) Cron is really the way to go.
October + 6 months = April. Also, the effective date of that notice was 1 November, which means that the 6 months expired on May 1.
ICANN's server was switched off on May 2.
Oh, yeah, I realise that. In fact, given that the article states that the transition time is around 6 months, you could probably just update every 3 months, even.
The point is, you have to have some system in place, either manual or automatic, to perform the update... Because it's easy to copy the file the first time, insert it into your configuration master image, and then forget about it as you roll out machines, and leave them in production for years with out-of-date hints files.
I know - I've probably done it on machines before, too... Thankfully I've long since moved away from the naive default BIND setup which includes a copy of the hints file from some arbitrary date, used long after it's safe to do so...
There is DNS Security... But really, it's like any fix for SMTP - nobody bothers using it because nobody is using it...
The problem is, if you do grab the hints file from there, you have to make sure you keep refreshing it to stay up to date... Otherwise you're just setting yourself up for the same attack the next time this happens...
That said, I don't know if trusting your upstream provider is any better...
Except that apparently ICANN switched their machine off on May 2nd. However, anticipating such a switch off, three other organisations around the world stepped in over the past 6 months to fill the void, and mostly went undetected for the last 6 months...