I've known many people with busted iPhone screens, but guess what? The touchscreen element still works just peachy for them. Can't see a damn thing on the display from shattered glass, but it still works.
Just wakes it for whatever services registered with the sleep proxy as important enough to wake the system. Hitting it with ICMP isn't important. Hitting it with SMB is.
There's a friends system built-in. You can either friend a game specific player's avatar, or if you know their email address and they approve your request you can setup a mutual "RealID" friend connection, which even works cross-Blizzard games (friend in WoW? See if they want to join you in SC2). From there you can setup a 'party' and play your games as a group.
Why do all recent games feel that a list/lobby based multiplayer environment is a bad thing?
Because the average Internet using gamer has proven to be a douchebag and not suitable to be out in public.
That and it doesn't scale well at the numbers Blizzard is looking at for SC2. What's the benefit of a list, when you have 21,000 games in it? What's the benefit of a lobby when you have 2,000 lobbies? You can't realistically find something by looking manually and produce a good user experience, so you let matchmaking take over for you.
IPv4 went live with a Flag Day. You either switched to it, or you fell off the network. Unfortunately, the network is a bit large and varied to do that today. Which is why there are so many mechanisms to ease transition: 6to4, 6in4, 6RD, DSlite, Teredo, etc.
In any case, the current burn rate of allocations from IANA to the regional registries is about one/8 per month. No amount of reclamation of existing space, or even more efficient use of it will make a less than 32bit space sufficient to handle the world's network addressing needs.
At best Verizon could have gone/31 on your router-router link, gaining two addresses, since it wouldn't have a broadcast or network address.
If that link was privately addressed, your average office tech wouldn't be able to do your trick since it's really heavy on the configuration and prone to cause anyone else who has to admin it to tear their hair out.
In any case, as the case with all the other "Why don't we work the 32bit space more efficiently?", it only buys time, and is a heck of alot more work than just implementing the solution that's already there, and ready to go. The only solution is a larger address space, since 6 billion people do not fit a 4billion IP space. The Internet's been muffintopping for a while. Time to let that belt out.
Because it's classified as Experimental Use, so who knows what the existing IP implementations out there did to special case it in the code. So then you're out to updating firmwares and OSs to cope with the ability to us 240/4. Now as that's 16/8s, and we're currently burning through a/8 per month, that's 1.33 years of additional time before we're out of v4 again. The proper solution is to use that time spent updating firmware and OSs, to do just that, but for IPv6, which will be able to go for much more time than 1.33 years.
Don't know where you saw that. Check the vehicle code, sections 21451-21453. Only red has been changed since 1987, and that in 2002. Whoever wrote subsection (c) needs to be beaten by an English teacher.
Oh, and did I forget to mention that if you accelerate just a little slower than most people, someone could legitimately enter the intersection on a green light and potentially T-bone the turning traffic? Sunnyvale, CA, I'm looking at you. Pretty much every side street off of Sunnyvale Rd. has this problem....
Actually, if they T-bone you, they're at fault if you entered the intersection on a green or yellow. CA Vehicle Code, section 21451: "A driver facing a circular green signal shall proceed straight through or turn right or left or make a U-turn unless a sign prohibits a U-turn. Any driver, including one turning, shall yield the right-of-way to other traffic and to pedestrians lawfully within the intersection or an adjacent crosswalk." 21452 and 3 cover yellow and red. In California red ultimately means no entry, and defines turn on red rules.
While you may be facing a red on your previous direction of travel, you were still lawfully in the intersection when you entered. Just because the light changed doesn't make it illegal, as long as you're on your way out of it.
Small consolation if you _do_ get t-boned, however.
Apple wins this one. I'm sorry, but the AppStore is far more polished and suitable for business use.
iPhone/AppStore: - Daily reports, with regional totals for downloads and updates. - Five screenshots for your apps - Keyword search - Large app descriptions - Descriptions for app updates - Semi-opaque approval process, but it's getting better and tools are moving many of the code-level stoppers to dev visible before submission. - iTunes. For as many things that have been bolted onto it, it's better than nothing, and gets the job done. - Up to date SDK with current examples on all major code paths, and iTunesU access to the Stanford iPhone Dev course.
Android: - No reporting aside from a total download and currently installed count. (Yes, your android device phones home and lets Market know that app hasn't been deleted) - Two screenshot max (Pet peeve: zero or two screens... one isn't permitted.) - No keyword search - 325 character app description - No update descriptions, you get to fit them in the above. - No approval, aside from the $25 to register on Market. - No access to your app reviews, unless you're on the handset. - SDK docs are up to date, but can be annoyingly sparse or wrong in spots. What examples there are often down-rev, hiding on the net and using deprecated APIs. Alas, it's a common fault in OSS: the code is the fun bit, the docs and examples aren't so much fun. They're often quickly written, are terse or flat out wrong.
The biggest problems I have, aside from the search problem, are the seemingly arbitrary limits on things, and the last of any meaningful web side to Market. It really feels like Market is someone's 20% project.
So we have a simple question: Can I tether an iPad to the iPhone? Let's break this down.
Within US: Non-issue, you can't tether anything to your iPhone. Who's fault? AT&T.
Outside US: If you've got a provider which permits tethering of devices to your iPhone, you can start to have a case to be miffed at Apple. However... iPhone tethering is available over USB (isn't one on the iPad), and BlueTooth. While you can tether your devices to your iPhone over BT, you've never been able to do it the other way. So why are people surprised that the iPad is the same?
Stanford is a geographically small piece of network, with the added bonus of having periods of time with a much smaller network footprint (think summer and the ability to severely curtail the resnet). Of the large allocations they were the ones able to do it with the least amount of pain. Plus I'm sure it made for some good case studies for CS majors.
No, it's APNIC (Asia Pacific) which got those blocks, not AFRINIC (Africa) or LACNIC (Latin America/Caribbean). If you have need to communicate with Japan, China, India, etc., you'll need to switch.
And for each of those/8s, you buy maybe 1.5-2 months more time until v4 exhaustion. Most of those/8s were also allocated prior to any policies permitting reclamation. Any recovery of them would involve legal wrangling, which would be expensive and time consuming. Prolonging the end result isn't a viable solution to the problem, when the solution is available now.
Repurposing the D and E spaces won't fly. The D space is used. Think of the hell entailed if 224.0.0.5 and 224.0.0.6 get routed. Bye bye OSPF. Plus you'd have to recode every OS and firmware that understands those as multicast addresses to treat them as unicast. That's not even discussing what might be coded in for the E space in random OSes and firmwares. And after all that work, it'd buy us maybe two more years. Just go v6, it's already in the OSes, and would be in the firmwares if the end-user ISPs would just push the CPE manufacturers a little bit.
They limit liquid/gel capacity only on carry-ons, not checked bags. You could throw a couple gallons of liquids in your checked bags and they'd be "ok" with it. You can bring alot of otherwise restricted items in your checked bags.
Not digitally signed, but it's easy enough to validate the source from the source IP and headers anyway for this kind of thing. The main item of note would be the deletes, as they indicate a return of address space.
No, it's not how it works in the IPv4 world. You come to a provider with your own PI/24 and up of IPv4 space, and they'll take your announcements, or likely even announce it for you if you're not doing BGP, depending on the arrangement./48s are the v6 version of v4/24s at this point in time. We also don't have mass deaggregation in the IPv6 table so far, and we certainly won't see 75k v6 prefixes (~same size as 300k v4 prefixes) for a while. Currently, v6 tables are about 2000 prefixes, ~1500 ASNs announcing v6 space.
World of Warcraft subscribers include individuals who have paid a subscription fee or have an active prepaid card to play World of Warcraft, as well as those who have purchased the game and are within their free month of access. Internet Game Room players who have accessed the game over the last thirty days are also counted as subscribers. The above definition excludes all players under free promotional subscriptions, expired or cancelled subscriptions, and expired prepaid cards. Subscribers in licenseesâ(TM) territories are defined along the same rules.
Blizzard has to do it this way. The only outside source (har) with something similar is Valve. Since Valve seems to be allergic to Mac development, they're a non-starter for even considering them as a potential source for community features.
Slashdot Mirror
I've known many people with busted iPhone screens, but guess what? The touchscreen element still works just peachy for them. Can't see a damn thing on the display from shattered glass, but it still works.
Just wakes it for whatever services registered with the sleep proxy as important enough to wake the system. Hitting it with ICMP isn't important. Hitting it with SMB is.
Someone already posted it up a few comments: http://en.wikipedia.org/wiki/Sleep_Proxy_Service
Traditionally WWDC is the iPhone launch keynote, and the iPod related updates (iPod, iTunes, etc.) happen at a September event.
There's a friends system built-in. You can either friend a game specific player's avatar, or if you know their email address and they approve your request you can setup a mutual "RealID" friend connection, which even works cross-Blizzard games (friend in WoW? See if they want to join you in SC2). From there you can setup a 'party' and play your games as a group.
Why do all recent games feel that a list/lobby based multiplayer environment is a bad thing?
Because the average Internet using gamer has proven to be a douchebag and not suitable to be out in public.
That and it doesn't scale well at the numbers Blizzard is looking at for SC2. What's the benefit of a list, when you have 21,000 games in it? What's the benefit of a lobby when you have 2,000 lobbies? You can't realistically find something by looking manually and produce a good user experience, so you let matchmaking take over for you.
IPv4 went live with a Flag Day. You either switched to it, or you fell off the network. Unfortunately, the network is a bit large and varied to do that today. Which is why there are so many mechanisms to ease transition: 6to4, 6in4, 6RD, DSlite, Teredo, etc.
In any case, the current burn rate of allocations from IANA to the regional registries is about one /8 per month. No amount of reclamation of existing space, or even more efficient use of it will make a less than 32bit space sufficient to handle the world's network addressing needs.
At best Verizon could have gone /31 on your router-router link, gaining two addresses, since it wouldn't have a broadcast or network address.
If that link was privately addressed, your average office tech wouldn't be able to do your trick since it's really heavy on the configuration and prone to cause anyone else who has to admin it to tear their hair out.
In any case, as the case with all the other "Why don't we work the 32bit space more efficiently?", it only buys time, and is a heck of alot more work than just implementing the solution that's already there, and ready to go. The only solution is a larger address space, since 6 billion people do not fit a 4billion IP space. The Internet's been muffintopping for a while. Time to let that belt out.
Because it's classified as Experimental Use, so who knows what the existing IP implementations out there did to special case it in the code. So then you're out to updating firmwares and OSs to cope with the ability to us 240/4. Now as that's 16 /8s, and we're currently burning through a /8 per month, that's 1.33 years of additional time before we're out of v4 again. The proper solution is to use that time spent updating firmware and OSs, to do just that, but for IPv6, which will be able to go for much more time than 1.33 years.
Don't know where you saw that. Check the vehicle code, sections 21451-21453. Only red has been changed since 1987, and that in 2002. Whoever wrote subsection (c) needs to be beaten by an English teacher.
Oh, and did I forget to mention that if you accelerate just a little slower than most people, someone could legitimately enter the intersection on a green light and potentially T-bone the turning traffic? Sunnyvale, CA, I'm looking at you. Pretty much every side street off of Sunnyvale Rd. has this problem....
Actually, if they T-bone you, they're at fault if you entered the intersection on a green or yellow. CA Vehicle Code, section 21451: "A driver facing a circular green signal shall proceed straight through or turn right or left or make a U-turn unless a sign prohibits a U-turn. Any driver, including one turning, shall yield the right-of-way to other traffic and to pedestrians lawfully within the intersection or an adjacent crosswalk." 21452 and 3 cover yellow and red. In California red ultimately means no entry, and defines turn on red rules.
While you may be facing a red on your previous direction of travel, you were still lawfully in the intersection when you entered. Just because the light changed doesn't make it illegal, as long as you're on your way out of it.
Small consolation if you _do_ get t-boned, however.
Apple wins this one. I'm sorry, but the AppStore is far more polished and suitable for business use.
iPhone/AppStore:
- Daily reports, with regional totals for downloads and updates.
- Five screenshots for your apps
- Keyword search
- Large app descriptions
- Descriptions for app updates
- Semi-opaque approval process, but it's getting better and tools are moving many of the code-level stoppers to dev visible before submission.
- iTunes. For as many things that have been bolted onto it, it's better than nothing, and gets the job done.
- Up to date SDK with current examples on all major code paths, and iTunesU access to the Stanford iPhone Dev course.
Android:
- No reporting aside from a total download and currently installed count. (Yes, your android device phones home and lets Market know that app hasn't been deleted)
- Two screenshot max (Pet peeve: zero or two screens... one isn't permitted.)
- No keyword search
- 325 character app description
- No update descriptions, you get to fit them in the above.
- No approval, aside from the $25 to register on Market.
- No access to your app reviews, unless you're on the handset.
- SDK docs are up to date, but can be annoyingly sparse or wrong in spots. What examples there are often down-rev, hiding on the net and using deprecated APIs. Alas, it's a common fault in OSS: the code is the fun bit, the docs and examples aren't so much fun. They're often quickly written, are terse or flat out wrong.
The biggest problems I have, aside from the search problem, are the seemingly arbitrary limits on things, and the last of any meaningful web side to Market. It really feels like Market is someone's 20% project.
Those addresses should be on your tunnel's detail page.
So we have a simple question: Can I tether an iPad to the iPhone? Let's break this down.
Within US:
Non-issue, you can't tether anything to your iPhone. Who's fault? AT&T.
Outside US:
If you've got a provider which permits tethering of devices to your iPhone, you can start to have a case to be miffed at Apple. However... iPhone tethering is available over USB (isn't one on the iPad), and BlueTooth. While you can tether your devices to your iPhone over BT, you've never been able to do it the other way. So why are people surprised that the iPad is the same?
They're working with 256 potential /8 networks, since the old classful designations went obsolete with the advent of CIDR.
ip6tables -A INPUT -p tcp -s 2001:db8::/32 -j DROP
Same thing, just diff command, and you use the diff block. This one is the example block for IPv6.
Stanford is a geographically small piece of network, with the added bonus of having periods of time with a much smaller network footprint (think summer and the ability to severely curtail the resnet). Of the large allocations they were the ones able to do it with the least amount of pain. Plus I'm sure it made for some good case studies for CS majors.
No, it's APNIC (Asia Pacific) which got those blocks, not AFRINIC (Africa) or LACNIC (Latin America/Caribbean). If you have need to communicate with Japan, China, India, etc., you'll need to switch.
And for each of those /8s, you buy maybe 1.5-2 months more time until v4 exhaustion. Most of those /8s were also allocated prior to any policies permitting reclamation. Any recovery of them would involve legal wrangling, which would be expensive and time consuming. Prolonging the end result isn't a viable solution to the problem, when the solution is available now.
Repurposing the D and E spaces won't fly. The D space is used. Think of the hell entailed if 224.0.0.5 and 224.0.0.6 get routed. Bye bye OSPF. Plus you'd have to recode every OS and firmware that understands those as multicast addresses to treat them as unicast. That's not even discussing what might be coded in for the E space in random OSes and firmwares. And after all that work, it'd buy us maybe two more years. Just go v6, it's already in the OSes, and would be in the firmwares if the end-user ISPs would just push the CPE manufacturers a little bit.
Key words there: "checked baggage."
They limit liquid/gel capacity only on carry-ons, not checked bags. You could throw a couple gallons of liquids in your checked bags and they'd be "ok" with it. You can bring alot of otherwise restricted items in your checked bags.
You mean something like http://lists.arin.net/pipermail/arin-issued/?
Not digitally signed, but it's easy enough to validate the source from the source IP and headers anyway for this kind of thing. The main item of note would be the deletes, as they indicate a return of address space.
No, it's not how it works in the IPv4 world. You come to a provider with your own PI /24 and up of IPv4 space, and they'll take your announcements, or likely even announce it for you if you're not doing BGP, depending on the arrangement. /48s are the v6 version of v4 /24s at this point in time. We also don't have mass deaggregation in the IPv6 table so far, and we certainly won't see 75k v6 prefixes (~same size as 300k v4 prefixes) for a while. Currently, v6 tables are about 2000 prefixes, ~1500 ASNs announcing v6 space.
No, the 11.5 million number is accurate as at least up to 23Dec2008:
From: http://www.blizzard.com/us/press/081121.html
World of Warcraft's Subscriber Definition
World of Warcraft subscribers include individuals who have paid a subscription fee or have an active prepaid card to play World of Warcraft, as well as those who have purchased the game and are within their free month of access. Internet Game Room players who have accessed the game over the last thirty days are also counted as subscribers. The above definition excludes all players under free promotional subscriptions, expired or cancelled subscriptions, and expired prepaid cards. Subscribers in licenseesâ(TM) territories are defined along the same rules.
Blizzard has to do it this way. The only outside source (har) with something similar is Valve. Since Valve seems to be allergic to Mac development, they're a non-starter for even considering them as a potential source for community features.