If that were true, then the bnetd devs were essentially asking for details on the CD key creation algorithm.
Blizzard could have provided a simple TCP/IP-based API for them to call to verify a key. Then Blizzard could keep all the details secret, and the bnetd folks could still build in key verification.
Switching to a Nexus One would put you on a more expensive T-Mobile plan to pay back the cost of the phone. Buying it upfront for $530 and staying eligible for the discount plan isn't much more expensive over 2 years:
$200 + 2 years of Even More ($60) = $1640. $530 + 2 years of Even More Plus ($50) = $1730.
So basically, you pay $90 more, but you're not glued to a 2 year contract.
Re:Econ 101: if a niche needs filled, it will be
on
Monty Wants To Save MySQL
·
· Score: 2, Informative
Shared web hosting providers offer only MySQL, not PostgreSQL.
Maybe the really crap ones. I have shared hosting with PostgreSQL for a few bucks a month. I mean, Cpanel has full PostgreSQL support, it's not like the hosting provider has to do a lot of work.
If I download an unauthorized copy of (say) the remastered edition of "The Age of Plastic" by Buggles, Trevor Horn does not actually lose any money.
I know, you say he effectively loses the money he would have earned if I purchased the CD. Except: I wouldn't purchase the CD, because I already have the album on CD, purchased before it was remastered. The one extra track and possible improvements in mastering aren't worth the price of a CD to me. Hence Trevor Horn would never get the money--and hence, whether I download the album or not makes no difference to his income.
Now, you'd think that means these devices are publically accessible, but noooo. If 99% of their '9.x.x.x' equipment that does have internet access attempts a connection, it gets NATed outbound to a different address entirely!
Depends on the IBM site. Some use NAT and/or a proxy, but the sites I've worked at in the US don't. In fact, the NATted sites are a source of technical issues internally, exactly as you'd expect.
I have an N800, and I'm familiar with Maemo. It has a lot of fairly basic deficiencies. For example, there has been a bug open for several years about the fact that it's impossible to set your preferences for date format. That's a bit of a killer for me, trivial as it may seem, as I use ISO format everywhere, and the last thing I need is my phone and organizer using a different format from everything else.
I've also been displeased with Nokia's lack of continuing support for older devices. When I went through the hell of reflashing my N800 for the 2008 OS release, Nokia said that would be the last reflash needed, as they had added a proper package manager. In fact, it was the last reflash needed because they dropped support for older hardware and told everyone to go buy an N900.
Then there's the fact that the windowing toolkit on the N900 is a dead end, due to be replaced by Qt in the inevitable N910--which you will no doubt have to buy, because they won't offer an OS update for the N900.
No, sorry, but Nokia does not fill me with enthusiasm.
My guess? The planes were hijacked, demands were made, and the hijackers were told to go to hell (I don't think GWB would have EVER negotiated with terrorists).
My guess is that the decision was made to do nothing, in the hope of repeating the Reagan trick with the Iran hostage crisis: give Bush, the new and deeply unpopular president, a chance to send in the Marines to kick ass and rescue the hostages. He'd look like a great leader. Unfortunately, they didn't know that the terrorists weren't planning on taking hostages this time.
Ubuntu packagers would have preferred the use of APT instead of RubyGems for Gem installations, despite the fact that APT's lagged behind RubyGems.
The problem is the Debian maintainers. The Ruby community tried to work with them on integrating RubyGems with APT, so that you could have a command to turn a.gem into a.deb and have the best of both worlds. The Debian Ruby packagers weren't interested--it was "my way or the highway".
("We will not under any circumstances admit that Microsoft's wheel-mouse actually rocks")
I'd just like to point out that Microsoft did not, in fact, invent the wheel mouse. It was introduced commercially by Mouse Systems in 1995 in their ProAgio and Genius EasyScroll models. Microsoft didn't launch their scroll wheel mouse until 1996.
That's right, ignore the OTHER part of my reply, where I explained the non-proxy solution to accessing IPv4-only sites from an IPv6-only system. Dishonest tosser.
The transition nodes on the edges of the IPv6-only zone are dual-stack, yes. The hosts inside the IPv6-only zone are not dual stack, nor are the IPv4 servers they connect to.
So you can have 20,000,000 IPv6-only nodes, connecting to a legacy IPv4-only node, via a single IPv4 tunnel broker at the edge of the IPv6-only network.
Just like all the machines on my home network believe they are on an IPv6 network, because the gateway router invisibly handles all the IPv6 over IPv4 tunneling to get them connected via my ISP.
I can go to http://ipv6gate.sixxs.net/ right now. It tells me I'm connecting via IPv6, and lets me connect to various IPv4-only web sites via IPv6. That shows the principle. The rest is just setting up your edge-of-IPv6-net routers to handle it.
An IPv6-only system can communicate with IPv4-only hosts, using the tunneling mechanism described by the RFCs. Example diagram. Note that the IPv6 machine on the IPv6 network doesn't have to handle the tunneling. So there's no reason why an ISP couldn't deploy IPv6 to customers, and provide DSTM tunneling for them to use to reach legacy IPv4-only systems.
The issue of IPv4 over IPv6 was dealt with years ago, so that IPv6-only backbone connections could be deployed without eating further into the IPv4 address space.
Try this experiment: remove the IPv4 addresses on your home machine's network interfaces. Now see how well you can access the rest of the Internet.
A system with IPv6-only connectivity can use a tunnel to access the rest of the Internet. Really. Go read about it, it's RFC 2473.
So if you as a client have native IPv6, there's no reason not to use it, as you can reach the entire Internet that way. Then when enough clients are migrated, servers will start to switch over.
Websites with external consumers cannot stop using IPv4 until all potential consumers use IPv6. So until everyone uses IPv6, every host must continue to run IPv4 or both.
You make it sound like that's a difficult problem, rather than a matter of putting a few extra lines in a config file for the transition period.
Does this mean you cannot run IPv6 at home? No, it just means you must also run IPv4 to get to websites that haven't bothered to support both.
No, you're wrong there. While an IPv4 connection cannot reach IPv6 hosts, an IPv6 connection can reach any IPv4 host using tunneling. You talk pure IPv6 to your IPv6 ISP, and if there's a need to fall back to IPv4, they route the traffic via a tunnel broker.
Using similar technology, you can get IPv6 even if your ISP only supports IPv4. That's how I'm doing it.
Unfortunately, it was beat to the market by Unreal Tournament and Quake 3 (November and December 1999, respectively) and so the graphics for it seemed "antiquated" when it was released in May 2000.
And that's the big problem with chasing the FPS market. It's a non-stop treadmill of graphics technology upgrades with very little room for innovation in game design.
I will admit that I don't understand the standards behind the cell phone industry, but why are cell phones so strongly coupled to the service providers and, well, not open?
Because way back in the mists of time, Qualcomm approached the US government and said "Hey, we shouldn't be using a European technology like GSM... We should be using American technology, CDMA, which is so much better! (And by the way, we have a stack of patents on it.)" Qualcomm were upset because Europe had decided that it made sense to have a single interoperable phone system, and had therefore mandated that only GSM be deployed.
The US government said "OK" and allocated the standard GSM frequencies to CDMA, and Verizon and Sprint rolled out CDMA services. And the undeniable technical advantages of CDMA turned out to be invisible to the end user.
Then VoiceStream (later T-Mobile) and Cingular (later AT&T) decided to try using European GSM service, but on different frequencies. It turned out that because of economies of scale (i.e. 2 billion GSM users vs 60 million CDMA users so manufacturers make GSM equipment first), they could offer cheaper service and a better selection of phones.
Then GSM circuitry got smaller, and it became plausible to offer multiple frequency bands on a single phone. So quad band phones became the norm, and it became possible to switch between AT&T and T-Mobile. But Verizon and Sprint were stuck with their US-only CDMA network. Next, Verizon are dropping CDMA in favor of LTE, the 4G sequel to GSM. So that'll just leave Sprint.
Isn't there a bit of a difference there between the examples (TVs, DVD players, etc) and PC software?
Not these days. Both my DVD player and my TV have required software patches to fix bugs that they shipped with. The DVD player wouldn't play some files it claimed to be able to play, and the TV would randomly turn itself off.
Slashdot Mirror
As soon as Microsoft implements the current SVG standards in IE, they should be welcomed into the process of refining the standards further.
Until they implement the current SVG standards, they should be kept away.
[Opinions mine, not IBM's.]
Blizzard could have provided a simple TCP/IP-based API for them to call to verify a key. Then Blizzard could keep all the details secret, and the bnetd folks could still build in key verification.
Valve dedicated servers don't work with the console versions of their games, of course.
Switching to a Nexus One would put you on a more expensive T-Mobile plan to pay back the cost of the phone. Buying it upfront for $530 and staying eligible for the discount plan isn't much more expensive over 2 years:
$200 + 2 years of Even More ($60) = $1640.
$530 + 2 years of Even More Plus ($50) = $1730.
So basically, you pay $90 more, but you're not glued to a 2 year contract.
Maybe the really crap ones. I have shared hosting with PostgreSQL for a few bucks a month. I mean, Cpanel has full PostgreSQL support, it's not like the hosting provider has to do a lot of work.
If I download an unauthorized copy of (say) the remastered edition of "The Age of Plastic" by Buggles, Trevor Horn does not actually lose any money. I know, you say he effectively loses the money he would have earned if I purchased the CD. Except: I wouldn't purchase the CD, because I already have the album on CD, purchased before it was remastered. The one extra track and possible improvements in mastering aren't worth the price of a CD to me. Hence Trevor Horn would never get the money--and hence, whether I download the album or not makes no difference to his income.
Depends on the IBM site. Some use NAT and/or a proxy, but the sites I've worked at in the US don't. In fact, the NATted sites are a source of technical issues internally, exactly as you'd expect.
[Opinions mine, not IBM's.]
"losses music artists incur from internet downloads"
Music artists don't incur losses from Internet downloads. Rather, they fail to incur profits.
There's an important difference.
So buy a Motorola Sholes. Much the same from a software point of view, has all your other desired features, and has a slide-out keyboard.
I have an N800, and I'm familiar with Maemo. It has a lot of fairly basic deficiencies. For example, there has been a bug open for several years about the fact that it's impossible to set your preferences for date format. That's a bit of a killer for me, trivial as it may seem, as I use ISO format everywhere, and the last thing I need is my phone and organizer using a different format from everything else.
I've also been displeased with Nokia's lack of continuing support for older devices. When I went through the hell of reflashing my N800 for the 2008 OS release, Nokia said that would be the last reflash needed, as they had added a proper package manager. In fact, it was the last reflash needed because they dropped support for older hardware and told everyone to go buy an N900.
Then there's the fact that the windowing toolkit on the N900 is a dead end, due to be replaced by Qt in the inevitable N910--which you will no doubt have to buy, because they won't offer an OS update for the N900.
No, sorry, but Nokia does not fill me with enthusiasm.
My guess is that the decision was made to do nothing, in the hope of repeating the Reagan trick with the Iran hostage crisis: give Bush, the new and deeply unpopular president, a chance to send in the Marines to kick ass and rescue the hostages. He'd look like a great leader. Unfortunately, they didn't know that the terrorists weren't planning on taking hostages this time.
Damn near destroyed 'im.
My web site ATH0.com has an old modem ad on the front page, I scanned it from an 80s magazine.
The problem is the Debian maintainers. The Ruby community tried to work with them on integrating RubyGems with APT, so that you could have a command to turn a .gem into a .deb and have the best of both worlds. The Debian Ruby packagers weren't interested--it was "my way or the highway".
I'd just like to point out that Microsoft did not, in fact, invent the wheel mouse. It was introduced commercially by Mouse Systems in 1995 in their ProAgio and Genius EasyScroll models. Microsoft didn't launch their scroll wheel mouse until 1996.
(They didn't invent the optical mouse either.)
That's right, ignore the OTHER part of my reply, where I explained the non-proxy solution to accessing IPv4-only sites from an IPv6-only system. Dishonest tosser.
The transition nodes on the edges of the IPv6-only zone are dual-stack, yes. The hosts inside the IPv6-only zone are not dual stack, nor are the IPv4 servers they connect to.
So you can have 20,000,000 IPv6-only nodes, connecting to a legacy IPv4-only node, via a single IPv4 tunnel broker at the edge of the IPv6-only network.
Just like all the machines on my home network believe they are on an IPv6 network, because the gateway router invisibly handles all the IPv6 over IPv4 tunneling to get them connected via my ISP.
I can go to http://ipv6gate.sixxs.net/ right now. It tells me I'm connecting via IPv6, and lets me connect to various IPv4-only web sites via IPv6. That shows the principle. The rest is just setting up your edge-of-IPv6-net routers to handle it.
An IPv6-only system can communicate with IPv4-only hosts, using the tunneling mechanism described by the RFCs. Example diagram. Note that the IPv6 machine on the IPv6 network doesn't have to handle the tunneling. So there's no reason why an ISP couldn't deploy IPv6 to customers, and provide DSTM tunneling for them to use to reach legacy IPv4-only systems.
The issue of IPv4 over IPv6 was dealt with years ago, so that IPv6-only backbone connections could be deployed without eating further into the IPv4 address space.
A system with IPv6-only connectivity can use a tunnel to access the rest of the Internet. Really. Go read about it, it's RFC 2473.
So if you as a client have native IPv6, there's no reason not to use it, as you can reach the entire Internet that way. Then when enough clients are migrated, servers will start to switch over.
So if we all link to the Target URL for a search for child porn, Target will become the #1 hit when someone does a Google search for child porn?
Just wondering...
You make it sound like that's a difficult problem, rather than a matter of putting a few extra lines in a config file for the transition period.
No, you're wrong there. While an IPv4 connection cannot reach IPv6 hosts, an IPv6 connection can reach any IPv4 host using tunneling. You talk pure IPv6 to your IPv6 ISP, and if there's a need to fall back to IPv4, they route the traffic via a tunnel broker.
Using similar technology, you can get IPv6 even if your ISP only supports IPv4. That's how I'm doing it.
And that's the big problem with chasing the FPS market. It's a non-stop treadmill of graphics technology upgrades with very little room for innovation in game design.
Well, thinking about it, I know four ex-strippers who completed their education and left for real careers. So maybe they're not as rare as you think?
Because way back in the mists of time, Qualcomm approached the US government and said "Hey, we shouldn't be using a European technology like GSM... We should be using American technology, CDMA, which is so much better! (And by the way, we have a stack of patents on it.)" Qualcomm were upset because Europe had decided that it made sense to have a single interoperable phone system, and had therefore mandated that only GSM be deployed.
The US government said "OK" and allocated the standard GSM frequencies to CDMA, and Verizon and Sprint rolled out CDMA services. And the undeniable technical advantages of CDMA turned out to be invisible to the end user.
Then VoiceStream (later T-Mobile) and Cingular (later AT&T) decided to try using European GSM service, but on different frequencies. It turned out that because of economies of scale (i.e. 2 billion GSM users vs 60 million CDMA users so manufacturers make GSM equipment first), they could offer cheaper service and a better selection of phones.
Then GSM circuitry got smaller, and it became plausible to offer multiple frequency bands on a single phone. So quad band phones became the norm, and it became possible to switch between AT&T and T-Mobile. But Verizon and Sprint were stuck with their US-only CDMA network. Next, Verizon are dropping CDMA in favor of LTE, the 4G sequel to GSM. So that'll just leave Sprint.
Not these days. Both my DVD player and my TV have required software patches to fix bugs that they shipped with. The DVD player wouldn't play some files it claimed to be able to play, and the TV would randomly turn itself off.