The big question I have is what happens next? Do icann ask the losing registrars nicely to folow policy and transfer the domains or do they actually force the transfer?
EasyDNS isn't the least expensive registrar, but they aren't the most expensive either. The fact they in Canada (and therefore outside USA jurisdiction) is an added bonus.
Surely by using a registrar in a jurisdiction other than the one the TLD in question is based in you are increasing your vulnerability to court orders forcing transefer of the domain. If you registrer a.com domain with a canadian register then surely a US court could order ICANN to transfer it while a canadian court could order your registrar to transfer it.
Authoratative namesevers (including the root nameservers) just serve up the information they are authoratative form.
The process of collecting the data needed to resolve a name from multiple disparate nameservers and then caching those results is the job of a "recursive resolver". Generally your ISP provides a recursive resolver for your use.
Out of the box the kernel sees the USB stick but the userland doesn't do anything with them. You can read them with third party software without rooting but if you want to mount them or write them then you need to root.
Correct me if I'm wrong here but AIUI this is about the cable that tesla sells that has multiple adaptors so you can charge you car from your cooker circuit or your drier circuit or whatever. Not about the fixed chargers that are custom installed.
Yeah, Aluminum wiring really sucks, which is why all of the high voltage transmission lines in the US are made of it.
Like with anything "best" depends on what your criteria are.
For a given resistance an aluminium cable will be lighter and cheaper than a copper cable. IIRC witht he right alloys it also self-supports for longer distances. On the other hand aluminium (especially older alloys*) needs careful termination practices to avoid joints that fail over time.
For long overhead and underground cables which are maintained and altered by well trained jointers the advantages of aluminium outweigh the disadvantages. For house wiring which is often maintained and altered by householders or cowboy tradesmen and where joints are much more frequent things are the other way round.
* Pure aluminium is almost never used for anything because it's too soft, practical aluminum is nearly always alloyed and the details of the alloy can significantly affect eht properies of the material. This creates the further complication that different aluminium alloys have different termination requirements.
You see, the problem with putting a 15A outlet on a 20A circuit is that it violates the cardinal rule in electrical wiring: You put a fuse wherever you go from thicker wire to thinner wire.
In both europe and america portable appliances frequently have cords that are too thin to carry the full rated current of the plug that is attatched to them and yet very few countries used fused plugs.
Tesla could just modify their charger so that if the wiring isn't done right, your garage won't burn down due to your electrician's negligence.
No they can modify it so a subset of things that could be wrong with your wiring will be less hazardous.
Not saying that is a bad thing but there are many things they can't do anything about. Fundamentally it's impossible to reliablly detect undersized cables. You can look for heat at the outlet but the situation at the outlet may be ok either because it's in a better thermal situation than other wiring in the circuit (required cable sizes go up massively for cables burried in thick thermal insulation) or the circuit may change wiring sizes part way along.
I do wonder if tesla should have made this cable at all or if they should have stuck to the very slow emergency charging cable and the proffessionally installed charging stations (where presumablly the electrician installing it checks things right back to the supply intake point).
Of course putting overheat protection in the charger plug only reduces the problem it doesn't solve it. It's perfectly possible for the wiring at the outlet to be just fine while further back in the circuit there is a bad connection or undersized wire.
For sufficiently small values of "standardised". The C standard is very loose leaving lots of stuff as "implementation dependent" or "undefined".
Anyone remember the whole strict aliasing thing where the gcc guys decided it was ok to break long established but strictly speaking undefined code in the persuit of performance.
he presumed difficulty of linking wallets to individuals
It's the presumed difficulty of linking addresses to individuals......................
A "wallet" is just a data file used by the client, not part of the protocol. Indeed the whole point of having a "wallet" with the keys to many seperate bitcoin addresses rather than just having a single address and associated key is to make it harder for people to track your transactions.
Lets consider what a bitcoin transaction looks like if neither the buyer or the seller wants to hold bitcoins and neither the buyer or the seller wants to leave their money in a bitcoin exchange.
The buyer transfers fiat currency to an exchange (fees). The buyer buy bitcoins (more fees) The buyer transfers the bitcoins out of the exchange (probablly no fees) The buyer buys the item with bitcoins (probablly no fees) The vendor transfers the bitcoins back to the exchange (probablly no fees) The vendor sells the bitcoins (more fees) The vendor transfers the money out of the exchange (more fees)
Overall this is likely to cost just as much in fees as using paypal or a credit cards.
To bring the fees down to a reasonable level one has to do one of two things, either hold bitcoins or hold fiat currency at a bitcoin exchange. Holding bitcoins is risky because their value is unstable (this has been masked somewhat so-far by the fact that the overall trend has been upwards. Holding fiat currency at a bitcoin exchange is risky for reasons that should be obvious
If you use utf8, then unicode is as efficient as ascii.
For storage.
But when you actually come to display stuff rendering engines that can handle massive character sets, variable byte count encodings of code points, converting mixed directionality text from logical order to physical order, combining elements in various ways to apply arbitary diacritics to a character and so-on doesn't come free. Having those things in your text rendering engine comes at a price even if you don't actually use them.
Did they though? Ok they didn't get to leave the poster up as long as they planned but they did get a news article written about them drawing attention to the fact that obama wore their products. And presumablly they can put a different billboard up in the space so they probablly haven't wasted the money they paid for the space (which I would guess is the most expensive part of putting up adverts in manhatten)
No. Don't bring Y2K into this. Y2K was a money grab by salesfolk to fleece idiots. Here's a hint sparky: "All computers have clocks" is true of most computers. But the clock is a square wave sync pulse.
As well as using those clock pulses to synchronise logic they also count them to measure the passage of time and record and process those date values in various ways. There are a few popular methods of such counting (and lots of strange custom ones). Some use simple linear counts, others use the same date structures we humans use. Which is chosen for a particular system is pretty arbitary and as systems grow more complex it is very likely that there will be many conversions between different date formats.
Since a complex system will likely use multiple date formats in different places different parts of system will respond in different ways to the rollover. Taking the year 2000 as an example some will handle itfine because they don't use a vulnerable date format. Some will wrap round to 00 (which may be later interpreted as 1900), some will produce malformed dates (like 1/1/100 which may later end up being interpreted as 1/1/0100 or 1/1/19100 or 1/1/A0 or 1/1/:0). So suddenly different parts of your system may have very different ideas of the date and anything that compares those dates to measure elapsed time will start generating nonsensical results or possiblly even crashing.
THERE ARE NO industrial controllers, microcontrollers, embedded systems of any kind that use COBOL
Even if that is true (and I find it doubtful) COBOL is far from the only place that human style date formats with 2-digit years are used (and if you think Y2K stopped people using such date formats you are sadly mistaken).
The electrical power grid was never in any danger
A wraparound in a common date format is a risk because it can break many independently developed systems at the same time. A power grid can handle a few plants dropping off at once because they shutdown due to a control software bug but if too many drop off you have a grid collapse.
Was Y2K overhyped? somewhat Was there a need to check big systems to make sure they weren't vulnerable to systematic failure when one of the worlds most common date formats wrapped round? yes
Ethernet controller chips don't generally contain MAC addresses. The MAC address is usually loaded on startup from an EEPROM or other configuration store. So generally* if you are designing your own boards and having them made you need to supply the MAC address.
Some vendors do offer EEPROMs pre-programmed with MAC addresses but afaict it's fairly unusual.
P.S. As the name suggests the MAC address is used by the MAC, not by the PHY
Unfortunately the cost of credit card fraud is pushed largely onto the retailers (who can't really do much about it) and those retailers are depending on jurisdiction either forbidden or strongly discouraged from charging extra for credit card use.
So in the end everyone pays for them (and for the month or so of interest free credit that credit card users get), whether they use credit cards or not.
Hidden cameras require a level of premediation, they basically require someone to make a concious premeditated descision to record secretly.
Phone cameras allow one to record video on the "spur of the moment" but it's pretty obvious when they are being used because they way you hold a phone when recording is pretty different to how you would hold it when just using it as a PDA.
If glasses with built in cameras become commonplace (and less obviously camera containing) then you will have to seriously consider that whenever you talk to wearing glasses they could make a spur of the moment decision to record the conversation without your knowlege.
It's a common head type on which the patents ran out years ago and which has been standardised in international standards so I can get compatilble tools from virtually any screwdriver vendor.
Admittedly the name is still trademarked so vendors have to use other names but i'd hardly say that makes a screw head style "propietary"
To be fair a few years back eSATA ports were everywhere but now USB3 has come along eSATA is falling out of favor in the PC world too. In all this talk about thunderbolt and eSATA everyone seems to be forgetting that the mac pro DOES have USB3 which is the dominant interface for external hard drives now.
Slashdot Mirror
The big question I have is what happens next? Do icann ask the losing registrars nicely to folow policy and transfer the domains or do they actually force the transfer?
EasyDNS isn't the least expensive registrar, but they aren't the most expensive either. The fact they in Canada (and therefore outside USA jurisdiction) is an added bonus.
Surely by using a registrar in a jurisdiction other than the one the TLD in question is based in you are increasing your vulnerability to court orders forcing transefer of the domain. If you registrer a .com domain with a canadian register then surely a US court could order ICANN to transfer it while a canadian court could order your registrar to transfer it.
Authoratative namesevers (including the root nameservers) just serve up the information they are authoratative form.
The process of collecting the data needed to resolve a name from multiple disparate nameservers and then caching those results is the job of a "recursive resolver". Generally your ISP provides a recursive resolver for your use.
MS may be encouraging PC vendors to push windows 8 but you CAN still buy PCs with windows 7.
When I go to dells site and look at the optiplexes I see win7 as the default option.
Using a quad core Pentium that's about four years old now.
ERM I don't think there has ever been any quad core chip marketed under the pentium brand.
Out of the box the kernel sees the USB stick but the userland doesn't do anything with them. You can read them with third party software without rooting but if you want to mount them or write them then you need to root.
Correct me if I'm wrong here but AIUI this is about the cable that tesla sells that has multiple adaptors so you can charge you car from your cooker circuit or your drier circuit or whatever. Not about the fixed chargers that are custom installed.
Yeah, Aluminum wiring really sucks, which is why all of the high voltage transmission lines in the US are made of it.
Like with anything "best" depends on what your criteria are.
For a given resistance an aluminium cable will be lighter and cheaper than a copper cable. IIRC witht he right alloys it also self-supports for longer distances. On the other hand aluminium (especially older alloys*) needs careful termination practices to avoid joints that fail over time.
For long overhead and underground cables which are maintained and altered by well trained jointers the advantages of aluminium outweigh the disadvantages. For house wiring which is often maintained and altered by householders or cowboy tradesmen and where joints are much more frequent things are the other way round.
* Pure aluminium is almost never used for anything because it's too soft, practical aluminum is nearly always alloyed and the details of the alloy can significantly affect eht properies of the material. This creates the further complication that different aluminium alloys have different termination requirements.
You see, the problem with putting a 15A outlet on a 20A circuit is that it violates the cardinal rule in electrical wiring: You put a fuse wherever you go from thicker wire to thinner wire.
In both europe and america portable appliances frequently have cords that are too thin to carry the full rated current of the plug that is attatched to them and yet very few countries used fused plugs.
Tesla could just modify their charger so that if the wiring isn't done right, your garage won't burn down due to your electrician's negligence.
No they can modify it so a subset of things that could be wrong with your wiring will be less hazardous.
Not saying that is a bad thing but there are many things they can't do anything about. Fundamentally it's impossible to reliablly detect undersized cables. You can look for heat at the outlet but the situation at the outlet may be ok either because it's in a better thermal situation than other wiring in the circuit (required cable sizes go up massively for cables burried in thick thermal insulation) or the circuit may change wiring sizes part way along.
I do wonder if tesla should have made this cable at all or if they should have stuck to the very slow emergency charging cable and the proffessionally installed charging stations (where presumablly the electrician installing it checks things right back to the supply intake point).
Of course putting overheat protection in the charger plug only reduces the problem it doesn't solve it. It's perfectly possible for the wiring at the outlet to be just fine while further back in the circuit there is a bad connection or undersized wire.
the language is standardized
For sufficiently small values of "standardised". The C standard is very loose leaving lots of stuff as "implementation dependent" or "undefined".
Anyone remember the whole strict aliasing thing where the gcc guys decided it was ok to break long established but strictly speaking undefined code in the persuit of performance.
he presumed difficulty of linking wallets to individuals
It's the presumed difficulty of linking addresses to individuals......................
A "wallet" is just a data file used by the client, not part of the protocol. Indeed the whole point of having a "wallet" with the keys to many seperate bitcoin addresses rather than just having a single address and associated key is to make it harder for people to track your transactions.
Lets consider what a bitcoin transaction looks like if neither the buyer or the seller wants to hold bitcoins and neither the buyer or the seller wants to leave their money in a bitcoin exchange.
The buyer transfers fiat currency to an exchange (fees).
The buyer buy bitcoins (more fees)
The buyer transfers the bitcoins out of the exchange (probablly no fees)
The buyer buys the item with bitcoins (probablly no fees)
The vendor transfers the bitcoins back to the exchange (probablly no fees)
The vendor sells the bitcoins (more fees)
The vendor transfers the money out of the exchange (more fees)
Overall this is likely to cost just as much in fees as using paypal or a credit cards.
To bring the fees down to a reasonable level one has to do one of two things, either hold bitcoins or hold fiat currency at a bitcoin exchange. Holding bitcoins is risky because their value is unstable (this has been masked somewhat so-far by the fact that the overall trend has been upwards. Holding fiat currency at a bitcoin exchange is risky for reasons that should be obvious
If you use utf8, then unicode is as efficient as ascii.
For storage.
But when you actually come to display stuff rendering engines that can handle massive character sets, variable byte count encodings of code points, converting mixed directionality text from logical order to physical order, combining elements in various ways to apply arbitary diacritics to a character and so-on doesn't come free. Having those things in your text rendering engine comes at a price even if you don't actually use them.
The company wasted their money.
Did they though? Ok they didn't get to leave the poster up as long as they planned but they did get a news article written about them drawing attention to the fact that obama wore their products. And presumablly they can put a different billboard up in the space so they probablly haven't wasted the money they paid for the space (which I would guess is the most expensive part of putting up adverts in manhatten)
No. Don't bring Y2K into this. Y2K was a money grab by salesfolk to fleece idiots. Here's a hint sparky: "All computers have clocks" is true of most computers. But the clock is a square wave sync pulse.
As well as using those clock pulses to synchronise logic they also count them to measure the passage of time and record and process those date values in various ways. There are a few popular methods of such counting (and lots of strange custom ones). Some use simple linear counts, others use the same date structures we humans use. Which is chosen for a particular system is pretty arbitary and as systems grow more complex it is very likely that there will be many conversions between different date formats.
Since a complex system will likely use multiple date formats in different places different parts of system will respond in different ways to the rollover. Taking the year 2000 as an example some will handle itfine because they don't use a vulnerable date format. Some will wrap round to 00 (which may be later interpreted as 1900), some will produce malformed dates (like 1/1/100 which may later end up being interpreted as 1/1/0100 or 1/1/19100 or 1/1/A0 or 1/1/:0). So suddenly different parts of your system may have very different ideas of the date and anything that compares those dates to measure elapsed time will start generating nonsensical results or possiblly even crashing.
THERE ARE NO industrial controllers, microcontrollers, embedded systems of any kind that use COBOL
Even if that is true (and I find it doubtful) COBOL is far from the only place that human style date formats with 2-digit years are used (and if you think Y2K stopped people using such date formats you are sadly mistaken).
The electrical power grid was never in any danger
A wraparound in a common date format is a risk because it can break many independently developed systems at the same time. A power grid can handle a few plants dropping off at once because they shutdown due to a control software bug but if too many drop off you have a grid collapse.
Was Y2K overhyped? somewhat
Was there a need to check big systems to make sure they weren't vulnerable to systematic failure when one of the worlds most common date formats wrapped round? yes
I just googled for giraffe meat and I found quite a few people talking about eating it though I didn't find anywhere listing current prices and stock.
Ethernet controller chips don't generally contain MAC addresses. The MAC address is usually loaded on startup from an EEPROM or other configuration store. So generally* if you are designing your own boards and having them made you need to supply the MAC address.
Some vendors do offer EEPROMs pre-programmed with MAC addresses but afaict it's fairly unusual.
P.S. As the name suggests the MAC address is used by the MAC, not by the PHY
Unfortunately the cost of credit card fraud is pushed largely onto the retailers (who can't really do much about it) and those retailers are depending on jurisdiction either forbidden or strongly discouraged from charging extra for credit card use.
So in the end everyone pays for them (and for the month or so of interest free credit that credit card users get), whether they use credit cards or not.
Prior to the iPhone and andriod taking off I suspect people said similar things about smartphones.
Just because one generation of an idea isn't well enough executed to really take off doesn't mean the idea itself is doomed.
Hidden cameras require a level of premediation, they basically require someone to make a concious premeditated descision to record secretly.
Phone cameras allow one to record video on the "spur of the moment" but it's pretty obvious when they are being used because they way you hold a phone when recording is pretty different to how you would hold it when just using it as a PDA.
If glasses with built in cameras become commonplace (and less obviously camera containing) then you will have to seriously consider that whenever you talk to wearing glasses they could make a spur of the moment decision to record the conversation without your knowlege.
If it worked like the UK National Health Service, all those things would be free at the point of delivery.
Note that prescriptions and dentistry are not free in the UK (though they are subsidised).
It's a common head type on which the patents ran out years ago and which has been standardised in international standards so I can get compatilble tools from virtually any screwdriver vendor.
Admittedly the name is still trademarked so vendors have to use other names but i'd hardly say that makes a screw head style "propietary"
To be fair a few years back eSATA ports were everywhere but now USB3 has come along eSATA is falling out of favor in the PC world too. In all this talk about thunderbolt and eSATA everyone seems to be forgetting that the mac pro DOES have USB3 which is the dominant interface for external hard drives now.