Huh? What the fuck is wrong with skype, exactly? Or are you just hating on it by default because it's, like, all popular and mainstream and stuff, maaaan.
Well, given FB has been around for 6 years, now, and shows absolutely no signs of decline, I think it might be a little early to declare its demise, even if Netcraft confirms it...
But that's already what happens. The permissions list on an Android app isn't an honor system -- if the app tries to access your contacts list, and that permission isn't in the manifest, the app will throw and exception and fail.
Yeah, the problem is, you don't know what the hell the app is doing with said permission. Great, you know it's accessing the network, but what is it sending? You have no idea. The only way to know that is to vet the code. But the claim was you can't, 'cuz, it's like, hard and stuff. But as I said, there's already a mechanism to detect if the app *might* be doing something nefarious, at which point you can narrow in and grill the developer to find out.
Nobody, at any marketplace service, is going to have time to do a code review of everything that gets submitted.
It's kinda funny you should say that, and then say:
"Android's model of showing you what special access the software uses is about as good as I think you can get"
If you have that up there, then it's trivial to "review everything that gets submitted". Just run the fucking app for five minutes. If it requests a permission, write it down. Then go back to the developer and ask them what the hell they're doing.
Even better, force the developer to enumerate the permissions their app requires up-front, and then con-check the submitted list against what the app requests during testing. Any discrepancy causes the app to be rejected immediately.
What? I'm supposed to take someone seriously when that person buys products from a company notorious for getting things wrong?
Yup, once again, missing the forest for the trees... *sigh*
Apparently I need to point this out, as your arrogant self-importance is getting in the way of your ability to comprehend: Cheap, consumer-grade router hardware sporting broken v6 stacks are extremely common. To support that, I cited a specific example of a common, mainstream device with a fundamentally broken v6 stack, thus contradicting the OP, who claimed this issue isn't that widespread. And if such devices have broken IPv6 implementations, and thus users of them cannot reach popular sites which advertise AAAA records, this will impact site viewership. And so sites will use that as an excuse to not to deploy IPv6 or advertise AAAA records for their primary domains.
Yes, there is a lot of that crap out there. If IPv6 plays a role in killing the crap off, outstanding!
Huh, yeah, you *really* didn't get the point. v6 won't kill off bad devices. The bad devices will kill off (or, at least substantially hamper the adoption of) v6.
Does that make sense to you? Or are you going to continue your pointless, entirely beside-the-point bitching about D-Link?
If you can't figure out at age 7+ that a magnet isn't food and that chemicals aren't treats, either you have a mental handicap or your parents have utterly failed.
I'll repeat to you what I said to the other guy: you *clearly* underestimate how stupid kids can be. Good judgment and common sense are something most people learn the hard way through trial and error. Spend a little time in a trauma ward and just see how intelligent your average fucking adult is, let alone a 7-year-old...
Um, yeah. Past the age of like two your kid shouldn't be swallowing random stuff.
Yeah, either you don't have kids, or you've forgotten what it's like to be one, and so drastically underestimate just how fucking stupid they can be...
Well, I take it back. There's definitely evidence that truly chronic users (like, regular, daily users) experience some amount of withdrawl after cessation. 'course, when you start to think about it, that makes sense, as you're no longer taking a sleep aid or an appetite stimulant, and so your body reacts accordingly, with insomnia and appetite loss.
Here's a thought: teach your kids not to swallow magnets.
Exactly! It's like all these packages with "choking hazard" warnings or, like, "danger, this is poison" warnings. Just teach your kids not to swallow these things, and they'll just totally not do it, 'cuz kids are like that! Right?
Depends, a lot of ndslib (at least in 2005-6'ish when I last used it) is just memory mapped registers in #defines and light wrappers for them. Hard part is reverse engineering the hardware design and bypassing the security mechanisms, after that the sdk is just a matter of sitting down and writing it.
Talk about underestimating complexity.
It took *years* for the homebrew community to get a decent wifi library for the NDS, as the only real way to write one was to poke registers and see what happened. Really, the only reason the DS video hardware was so easy to reverse-engineer is because:
a) much of the 2D subsystem carried over from the GBA, and b) the 3D support is fairly simplistic.
The 3DS, OTOH, is likely to be a much more complicated piece of hardware, with a much more powerful 3D pipeline. I strongly suspect it'll take a lot more than just "sitting down and writing it" to reverse-engineer how it works.
I'd like to know if it has proper hibernation support. When you closed the screen, the current DS went into what could be best described as "sleep". Whilst it was quick to come out of, the battery life was shorter than when the device was off and if the power went, you lost everything before your last save.
Sure, but... come on... suspended, the DS has a battery life measured in *days*. How hard is it, really, to find an outlet during that time?
Meanwhile, to do as you propose, you'd suddenly need a large chunk of solid-state storage on the thing, which would increases the costs substantially.
All those who said that sterescopic 3d is inherently a bad thing, that it's not "real", that it's offensive to you somehow, are you going to say the same about this? Or is it great because it's nintendo?
Are you going to erect another strawman so you can then knock it down in a show of your Extreme Manliness and Great Insightfulness?
That'll only happen after campaign finance is reformed... pity the people, particularly right-wingers, love to vote against their own interests on that topic.
It is highly stressed that inside a single network only IPv4 or IPv6 be used.
Bullshit. Dual-stack has *always* been part of the transition plan.
Now, design a method of tunneling IPv4 packets across an IPv6 network
Why would you ever need that? The core network can be dual-stack. Edges slowly migrate to v6-only. v4 machines work as they always have.
Now also design a way to tunnel IPv6 packets between two IPv6 networks separated by an IPv4 network.
There are *myriad* solutions for this. Hell, 6to4 was first described nearly ten years ago!
Now we need the ability for IPv6 only clients to be able to connect to IPv4 only servers.
NAT64 and DNS64.
but as far as I can tell, they were not all ready when IPv6 was first announced.
That's only true for your last example... unfortunately, the IETF failed hard, there, underestimating the cost and complexity of transition. Fortunately, companies like Comcast, dealing with the real-world issues of transition, convinced them than NAT64/DNS64 are necessary technologies to make the transition possible.
I'm glad someone finally said it. NAT is the (slightly slower) Plan B.
Ah, if only.
Go ask Comcast how that's going. They've exhausted private IP space in their network. So now you, what, want them to double-NAT their networks next?
Anyone proposing NAT as a serious solution to the IP shortage issue is either a) sticking their head in the sand, or b) simply doesn't understand the scope of the problem.
I've wondered why this hasnt been done sooner. There are some relatively small groups out there with class A blocks (16.7m) still.
Because:
1) There's no process for doing clawbacks, 2) It would be horribly expensive for those networks to renumber, 3) It would put off exhaustion by, at most a year, maybe two if you're lucky, and so the effort simply isn't worth it.
heise.de, a major German tech news site ran a test for precicely that reason about two weeks ago: they added an AAAA to heise.de in addition the normal AA record. Out of the thousands of visitors they have each day less than 10 were unable to reach that site in that configuration and wrote in about their problems and only one turned out to be unfixable because of a router misconfiguration somewhere else in the network.
Counter-anecdote. I've been running v6 at home for about a year now with absolutely no problems (Hurricane Electric, seriously, you guys kick ass). But I decided I wanted to add a new private 802.11n router to my network, so I went and picked up a DIR-625, which is a lower-end, 2.4Ghz-only 802.11n-capable D-Link WAP.
Now, I have a *slightly* unusual setup, in that I have a dedicated firewall (m0n0wall, you guys also kick ass), and I wanted this private, WPA2-secured AP to sit on my internal network and basically bridge the wireless pool directly to my network (no, in an enterprise scenario, I wouldn't advise this, but at home, with a properly secured WAP, I think it's safe). Furthermore, the firewall sends out v6 router advertisements, and I use simple v6 auto-configuration, so that any device connected to my LAN or existing 802.11g WAP automatically gets v6 connectivity (the latter is open and sits in its own DMZ). All of this works perfectly.
So I plug in the WAP so that the LAN-side of the device is connected to my network (this bridging the networks), and then connect to it with my laptop... and my v6 connectivity is shot. Attempts to connect to any v6 hosts time out. Odd. So I check my routes, and lo and behold, inexplicably, I have a default v6 gateway route that corresponds to a *loopback* address. A little digging, and I discover this POS AP is sending out router advertisements, and advertising it's *loopback address* as the gateway address. Buh??
So naturally I log into the AP and make sure v6 is disabled. Except it is. And it's *still sending out radv messages for it's loopback address*. The solution? I had to reflash the blasted thing and replace D-Link's firmware with dd-wrt.
Now, this is an incredibly common piece of consumer-grade hardware. And their IPv6 implementation is, apparently, horribly broken. If I were a regular user, and, say, Google, advertised AAAA records for www.google.com, I would've been unable to hit their website. So can you really blame service providers for choosing to either a) not advertise AAAA records for their services, or b) only do so to whitelisted ISPs?
Slashdot Mirror
Huh? What the fuck is wrong with skype, exactly? Or are you just hating on it by default because it's, like, all popular and mainstream and stuff, maaaan.
Well, given FB has been around for 6 years, now, and shows absolutely no signs of decline, I think it might be a little early to declare its demise, even if Netcraft confirms it...
But that's already what happens. The permissions list on an Android app isn't an honor system -- if the app tries to access your contacts list, and that permission isn't in the manifest, the app will throw and exception and fail.
Yeah, the problem is, you don't know what the hell the app is doing with said permission. Great, you know it's accessing the network, but what is it sending? You have no idea. The only way to know that is to vet the code. But the claim was you can't, 'cuz, it's like, hard and stuff. But as I said, there's already a mechanism to detect if the app *might* be doing something nefarious, at which point you can narrow in and grill the developer to find out.
Nobody, at any marketplace service, is going to have time to do a code review of everything that gets submitted.
It's kinda funny you should say that, and then say:
"Android's model of showing you what special access the software uses is about as good as I think you can get"
If you have that up there, then it's trivial to "review everything that gets submitted". Just run the fucking app for five minutes. If it requests a permission, write it down. Then go back to the developer and ask them what the hell they're doing.
Even better, force the developer to enumerate the permissions their app requires up-front, and then con-check the submitted list against what the app requests during testing. Any discrepancy causes the app to be rejected immediately.
What? I'm supposed to take someone seriously when that person buys products from a company notorious for getting things wrong?
Yup, once again, missing the forest for the trees... *sigh*
Apparently I need to point this out, as your arrogant self-importance is getting in the way of your ability to comprehend: Cheap, consumer-grade router hardware sporting broken v6 stacks are extremely common. To support that, I cited a specific example of a common, mainstream device with a fundamentally broken v6 stack, thus contradicting the OP, who claimed this issue isn't that widespread. And if such devices have broken IPv6 implementations, and thus users of them cannot reach popular sites which advertise AAAA records, this will impact site viewership. And so sites will use that as an excuse to not to deploy IPv6 or advertise AAAA records for their primary domains.
Yes, there is a lot of that crap out there. If IPv6 plays a role in killing the crap off, outstanding!
Huh, yeah, you *really* didn't get the point. v6 won't kill off bad devices. The bad devices will kill off (or, at least substantially hamper the adoption of) v6.
Does that make sense to you? Or are you going to continue your pointless, entirely beside-the-point bitching about D-Link?
Congratulations, you've managed to expertly demonstrate the phrase "missing the forest for the trees".
If you can't figure out at age 7+ that a magnet isn't food and that chemicals aren't treats, either you have a mental handicap or your parents have utterly failed.
I'll repeat to you what I said to the other guy: you *clearly* underestimate how stupid kids can be. Good judgment and common sense are something most people learn the hard way through trial and error. Spend a little time in a trauma ward and just see how intelligent your average fucking adult is, let alone a 7-year-old...
Um, yeah. Past the age of like two your kid shouldn't be swallowing random stuff.
Yeah, either you don't have kids, or you've forgotten what it's like to be one, and so drastically underestimate just how fucking stupid they can be...
Well, I take it back. There's definitely evidence that truly chronic users (like, regular, daily users) experience some amount of withdrawl after cessation. 'course, when you start to think about it, that makes sense, as you're no longer taking a sleep aid or an appetite stimulant, and so your body reacts accordingly, with insomnia and appetite loss.
The fact is that when you quit, most people experience anxiety, extreme agitation, loss of appetite, and even nightmares for several days afterwards.
ROFL, no they don't. Where'd you get that absurd idea? From your local DARE chapter?
Here's a thought: teach your kids not to swallow magnets.
Exactly! It's like all these packages with "choking hazard" warnings or, like, "danger, this is poison" warnings. Just teach your kids not to swallow these things, and they'll just totally not do it, 'cuz kids are like that! Right?
Depends, a lot of ndslib (at least in 2005-6'ish when I last used it) is just memory mapped registers in #defines and light wrappers for them. Hard part is reverse engineering the hardware design and bypassing the security mechanisms, after that the sdk is just a matter of sitting down and writing it.
Talk about underestimating complexity.
It took *years* for the homebrew community to get a decent wifi library for the NDS, as the only real way to write one was to poke registers and see what happened. Really, the only reason the DS video hardware was so easy to reverse-engineer is because:
a) much of the 2D subsystem carried over from the GBA, and
b) the 3D support is fairly simplistic.
The 3DS, OTOH, is likely to be a much more complicated piece of hardware, with a much more powerful 3D pipeline. I strongly suspect it'll take a lot more than just "sitting down and writing it" to reverse-engineer how it works.
I'd like to know if it has proper hibernation support. When you closed the screen, the current DS went into what could be best described as "sleep". Whilst it was quick to come out of, the battery life was shorter than when the device was off and if the power went, you lost everything before your last save.
Sure, but... come on... suspended, the DS has a battery life measured in *days*. How hard is it, really, to find an outlet during that time?
Meanwhile, to do as you propose, you'd suddenly need a large chunk of solid-state storage on the thing, which would increases the costs substantially.
All those who said that sterescopic 3d is inherently a bad thing, that it's not "real", that it's offensive to you somehow, are you going to say the same about this? Or is it great because it's nintendo?
Are you going to erect another strawman so you can then knock it down in a show of your Extreme Manliness and Great Insightfulness?
That'll only happen after campaign finance is reformed... pity the people, particularly right-wingers, love to vote against their own interests on that topic.
This kind of thing is happening everywhere. Cleaning up that kind of junk will give us time to convert to IPv6
Ahh, the naivete.
Delaying the inevitable will just give the ostriches a little more time to pretend all is well.
It is highly stressed that inside a single network only IPv4 or IPv6 be used.
Bullshit. Dual-stack has *always* been part of the transition plan.
Now, design a method of tunneling IPv4 packets across an IPv6 network
Why would you ever need that? The core network can be dual-stack. Edges slowly migrate to v6-only. v4 machines work as they always have.
Now also design a way to tunnel IPv6 packets between two IPv6 networks separated by an IPv4 network.
There are *myriad* solutions for this. Hell, 6to4 was first described nearly ten years ago!
Now we need the ability for IPv6 only clients to be able to connect to IPv4 only servers.
NAT64 and DNS64.
but as far as I can tell, they were not all ready when IPv6 was first announced.
That's only true for your last example... unfortunately, the IETF failed hard, there, underestimating the cost and complexity of transition. Fortunately, companies like Comcast, dealing with the real-world issues of transition, convinced them than NAT64/DNS64 are necessary technologies to make the transition possible.
I'm glad someone finally said it. NAT is the (slightly slower) Plan B.
Ah, if only.
Go ask Comcast how that's going. They've exhausted private IP space in their network. So now you, what, want them to double-NAT their networks next?
Anyone proposing NAT as a serious solution to the IP shortage issue is either a) sticking their head in the sand, or b) simply doesn't understand the scope of the problem.
I've wondered why this hasnt been done sooner. There are some relatively small groups out there with class A blocks (16.7m) still.
Because:
1) There's no process for doing clawbacks,
2) It would be horribly expensive for those networks to renumber,
3) It would put off exhaustion by, at most a year, maybe two if you're lucky, and so the effort simply isn't worth it.
heise.de, a major German tech news site ran a test for precicely that reason about two weeks ago: they added an AAAA to heise.de in addition the normal AA record. Out of the thousands of visitors they have each day less than 10 were unable to reach that site in that configuration and wrote in about their problems and only one turned out to be unfixable because of a router misconfiguration somewhere else in the network.
Counter-anecdote. I've been running v6 at home for about a year now with absolutely no problems (Hurricane Electric, seriously, you guys kick ass). But I decided I wanted to add a new private 802.11n router to my network, so I went and picked up a DIR-625, which is a lower-end, 2.4Ghz-only 802.11n-capable D-Link WAP.
Now, I have a *slightly* unusual setup, in that I have a dedicated firewall (m0n0wall, you guys also kick ass), and I wanted this private, WPA2-secured AP to sit on my internal network and basically bridge the wireless pool directly to my network (no, in an enterprise scenario, I wouldn't advise this, but at home, with a properly secured WAP, I think it's safe). Furthermore, the firewall sends out v6 router advertisements, and I use simple v6 auto-configuration, so that any device connected to my LAN or existing 802.11g WAP automatically gets v6 connectivity (the latter is open and sits in its own DMZ). All of this works perfectly.
So I plug in the WAP so that the LAN-side of the device is connected to my network (this bridging the networks), and then connect to it with my laptop... and my v6 connectivity is shot. Attempts to connect to any v6 hosts time out. Odd. So I check my routes, and lo and behold, inexplicably, I have a default v6 gateway route that corresponds to a *loopback* address. A little digging, and I discover this POS AP is sending out router advertisements, and advertising it's *loopback address* as the gateway address. Buh??
So naturally I log into the AP and make sure v6 is disabled. Except it is. And it's *still sending out radv messages for it's loopback address*. The solution? I had to reflash the blasted thing and replace D-Link's firmware with dd-wrt.
Now, this is an incredibly common piece of consumer-grade hardware. And their IPv6 implementation is, apparently, horribly broken. If I were a regular user, and, say, Google, advertised AAAA records for www.google.com, I would've been unable to hit their website. So can you really blame service providers for choosing to either a) not advertise AAAA records for their services, or b) only do so to whitelisted ISPs?
If it's old and decrepit(to stay in context), then let the fscker burn down!
ROFL, wow... people are bitching about 10% unemployment now. Your solution? Double it.
Yeah, good call buddy.
Wow... you're either 13, or a mennonite... 'cuz no one else can possibly be this naive. Or this dull and uninteresting.
But the thing is, almost nobody who wasn't already a huge fan of the previous series actually gave a damn about DS9.
And almost nobody who wasn't already an arrogant, self-important twit watched B5. What's your point?
Didn't watch DS9 past the first season, did ya? Come on, just admit it, it's okay...
but how are you going to get the HDMI output of your DVR into your GPU?
without doing the handshake right, there will be no stream to decode later on.
Huh? I think you misunderstand. If you can do this handshake on the CPU, you can, in principle, accelerate it in the GPU.
The idea isn't to use the GPU to display the video. The idea is to (mis-)use the GPU as a high-speed vector processor for doing real-time decoding.