Anyone know what the current procedures are in Canadian airports? (The real procedures, although the theoretical "these are your rights" is mildly interesting I guess.) I live close enough to the border that I might consider flying out of a Canadian airport.
So are you saying that you wouldn't ever rent bits under any circumstances, for example even if the rental was openly deemed to be such and the "return" (i.e., removal of the bits from your storage) were based on the honor system? Because I for one wouldn't find such an arrangement problematic.
Or are you saying that you're insulted by the miasma of pretense and deception that surrounds DRM?
However, I will not spend money on a book that will, in all likelihood in the future, not be accessible as I'll be damned if I'll buy something twice. I'll not buy at all rather than have to buy twice as DRM history has taught us is very likely.
I generally agree and follow the same practice. However, I'd consider buying ("licensing"?) DRM'd ebooks if their price reflected their reduced value. Essentially, any DRM'd media you "buy" is in effect a rental whose term is unpredictable. If the price of an ebook were, say, 10% to 20% of the corresponding paper book, that would reflect my perception of its value.
I'm really bummed about the micro-SIM. I'm accustomed to buying a local prepaid SIM when I travel abroad for a long time (jailbroken, unlocked iPhone of course). Until and unless micro-SIMs become commonplace, I guess that wouldn't be possible with this phone. AT&T might like that, but I sure don't.
Anyone know if there's a straightforward fix to this problem? (Can we skip all the "buy an Android phone instead" comments. You know what I mean.)
Yes, the story headline is talking about something totally different. I mean, how do YOU read "100-Petabit Internet Backbone"? Most people would not interpret it to mean "15.5 Tbps delivered over 7000 km." (The headline error is repeated in TFA. Ironically if you click all the way through to the AlcaLu press release the headline is more accurate: "Alcatel-Lucent Bell Labs announces new optical transmission record and breaks 100 Petabit per second kilometer barrier".)
I will grant you that optics geeks may find the bandwidth-distance metric familiar... but I continue to assert that [Inter]net geeks do not.
At the very least I assume we can agree that "100-Petabit Internet Backbone" is a gross misrepresentation of what the press release describes. "15.5 Tbit long haul" would have been accurate.
Maybe old hat to you network engineers, but I was previously unfamiliar with "bits per second.kilometer".
Thanks for the info. No, this is not old hat to network engineers. I've never heard of it and I've been working in the industry for more years than I care to admit. I think it might be old hat to marketing people though, since it appears to be a classic BIG MARKETING NUMBER. Normal networking people would call 15.5 Tbps * 7000 km... 15.5 Tbps.
Maybe it's true that optics geeks really do use numbers this way, I dunno. But the fact it comes from an AlcaLu press release doesn't lend it a whole lot of credibility.
I am massively unimpressed by the headline on the Slashdot story. Maybe another article headlined "kdawson swallows inflated AlcaLu marketing fluff hook, line and sinker" would be in order?
Almost anything that is uploaded to the Kindle store that was based on a public domain work is no longer entirely public domain.
That may be, but the GP says that it potentially only takes a single DRM'd PD work to establish a legal use for DRM circumvention. If that's so, then "almost" isn't good enough for someone in the DRM business. If your goal is to execute this kind of legal hack, your first step would be to create and upload a work which you explicitly place into the public domain. That would seem to address your points.
it doesn't really matter unless you were planning on getting the server edition, anyway.
Which I, for one, was. BTW, they'd also confirmed (before they pulled it) that ZFS would be supported in Client at the CLI level -- just no GUI sugar. Oh well. Easy come, easy go.
Did you RTFA? The point that O'Reilly (and others like Cory Doctorow) is making is essentially that according to his data (and he does have data), people who publish on closed platforms using DRM make less profit than people who publish on open platforms.
Yes, it's counter-intuitive. But so far, the people who use actual evidence in making their arguments seem to be showing that's how it is.
If you resent unpaid use of your work so much that you are willing to make less profit in exchange for preventing it, that's your call. But if you really do create for profit, you might want to read the article, and others like it, and think hard about it.
I can't quite believe I'm feeding the trolls, but...
i am not like them and i am glad of it. if they want to have the same "freedom" we have and the same "prosperity" we have.
Riiight, those are the only motivations. Or maybe that's a strawman that was set up by the Bush administration.
then they can move here and quit their whining and jihad bullshit. nobody is forcing them to live in a giant catlitter box. they are choosing to live there and complain about their "plight" seriously they are just bitching for the sake of bitching because they are too fucking dumb or assholish or small minded to do something different. i may sound racist
Yes, you do. But at least you balance it out by sounding ignorant as well.
but at least i am being honest.
Though not well-informed.
and like i said before. they want out of the cat box all they have to do is move somewhere else... i hear Hawaii is rather nice...
Here's a cartoon flow-chart based on actual research and facts explaining a few of the things you clearly don't understand about how difficult it is to immigrate to the USA. I expect other Western countries have similar, or worse, flowcharts of their own.
(One thing I would add to the flow chart is an initial box for "do you have enough money to travel from your home country to the USA?". You may find this http://en.wikipedia.org/wiki/List_of_countries_by_GDP_(nominal)_per_capita>chart of GDP per capita for various countries to be illuminating. Sorry, not a cartoon. Remember that the chart is overoptimistic because it only gives you the mean, not the median. The median is likely to fall below the mean.)
Again, this is pretty misleading unless you consider the specific cancer rather than "pancreatic cancer" as a generic. The statistic you cite is for "Estimated Five-year Relative Survival Ratio (%) (and 95% Confidence Interval) for the Most Common Cancers", and you read off the "pancreas" line. The specific case in question is not one of "the most common cancers" but (AFAICT) a different disease of the same organ.
Neuroendocrine tumors of the pancreas (islet cell tumors) are much less common than tumors arising from the exocrine pancreas. Reports often indicate that there are about two to three thousand cases diagnosed in the U.S. each year
and
The natural history of islet cell and carcinoic tumors tends to be favorable as compared with pancreatic adenocarcinoma. For example, the median survival duration from the time of diagnosis for patients with non-functioning metastatic islet cell tumors approaches five years.
The Pancreatica article says this compares to a median survival time of 15.5 months for adenocarcinoma of the pancreas ("pancreatic cancer") treated with the same surgery Jobs had.
I haven't heard of anyone getting better from pancreatic cancer.
Now you have. A few minutes with Wikipedia reveals that "Jobs was lucky; he had an extremely rare form called an islet cell neuroendocrine tumor that can be treated surgically, without radiation or chemotherapy." (From the Fortune article the Steve Jobs Wikipedia article links to.)
It's really dicey for non-experts (or, probably even experts) to make generalizations based on the common name of a cancer, without knowing exactly what variety of the disease it is, what stage it's at, and so on. Jobs has been (apparently) cancer-free since his surgery in July 2004.
Start by taking a look at RFC 2827/BCP 38, "Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing."
Sadly, ten years since publication we're still not there, which would seem to suggest (GP's wishful thinking notwithstanding) that you not hold your breath.
That sounds like a good reason not to select Silverlight if I wanted to deliver some kind of media myself. But I'm looking at this from the perspective of a consumer -- specifically, of a (prospective) user of Netflix's streaming video. Silverlight is already "cross platform" at least to the extent of being supported on Macs as well as Windows, else we wouldn't be having this conversation. Beyond that, why should I, from my narrow perspective, care about how cross platform it is if all I want to do is watch a video? As long as that data type is supported on my platform, the naive analysis says that's all I need.
At the moment the choice for watching Netflix streaming video isn't between Silverlight and Flash (or pick your technology). It's between Silverlight and not watching.
I take your point. On the other hand, I don't see the individual Mac (or Linux, etc) user having a whole lot of leverage in this situation. Up until now with Netflix's streaming video, the Windows version hasn't merely had "more features" but rather all the features since Macs haven't been supported at all. And since streaming video is not the primary reason I (or I'd venture to guess most people) subscribe to Netflix, I'm not about to fire Netflix over this lack... which means they're not particularly motivated to fix it.
The counter-argument is that clearly Netflix must perceive some benefit from having their subscribers stream video, else they wouldn't be offering the service at all. But the question as I see it is whether my refusal (and that of some other subset of Mac using Netflix subscribers) to adopt Silverlight and thus the streaming service would make enough of a dent in their overall business strategy to warrant a change in the technology they've adopted. My guess is that it wouldn't.
So I'm not quite sure what the "valuable lesson" is that I'm expected to learn. That I as an individual have very little leverage over ginormous corporations? And that they want to screw me? I learned those ones a long time ago.
Darn, I said I didn't want to discuss business strategies. Oh well.
Thanks, but I think these (modulo the "problems with Firefox" item) basically come under the "DRM is bad" and "Microsoft is bad" umbrella, at least to my way of thinking. I guess I should have added that I'm not really looking for reasons having to do with business practices or philosophy. I don't mean to trivialize the importance of such things, but they're just not what I'm looking to discuss right now -- I understand these arguments well already. What I'm looking for are specific technical reasons not to like Silverlight. Examples of such reasons might be "it makes your Mac less stable," "it interferes with Flash playback" or "it phones home with your personal information". (Evidence is always a plus of course.)
Slashdot Mirror
Anyone know what the current procedures are in Canadian airports? (The real procedures, although the theoretical "these are your rights" is mildly interesting I guess.) I live close enough to the border that I might consider flying out of a Canadian airport.
Though in the scenario GP seems to be talking about (multihoming a SOHO network), BGP based multihoming is a nonstarter.
ILNP, on the other hand, looks interesting.
So are you saying that you wouldn't ever rent bits under any circumstances, for example even if the rental was openly deemed to be such and the "return" (i.e., removal of the bits from your storage) were based on the honor system? Because I for one wouldn't find such an arrangement problematic.
Or are you saying that you're insulted by the miasma of pretense and deception that surrounds DRM?
However, I will not spend money on a book that will, in all likelihood in the future, not be accessible as I'll be damned if I'll buy something twice. I'll not buy at all rather than have to buy twice as DRM history has taught us is very likely.
I generally agree and follow the same practice. However, I'd consider buying ("licensing"?) DRM'd ebooks if their price reflected their reduced value. Essentially, any DRM'd media you "buy" is in effect a rental whose term is unpredictable. If the price of an ebook were, say, 10% to 20% of the corresponding paper book, that would reflect my perception of its value.
enough sense to diversify.
Ah, I hadn't realized FB hasn't IPO'd. So GP is right, he could end up with the short end of the stick.
Prove to me he has billions in the bank.
I thought I was clear -- "assuming he's had enough sense to diversify".
I'm certain he does not considering his lifestyle.
It must be nice to be so sure of things!
leaving him with nothing.
... except a lousy few billion in the bank, assuming he's had enough sense to diversify.
Yeah, the laugh will definitely be on him.
I'm really bummed about the micro-SIM. I'm accustomed to buying a local prepaid SIM when I travel abroad for a long time (jailbroken, unlocked iPhone of course). Until and unless micro-SIMs become commonplace, I guess that wouldn't be possible with this phone. AT&T might like that, but I sure don't.
Anyone know if there's a straightforward fix to this problem? (Can we skip all the "buy an Android phone instead" comments. You know what I mean.)
And financial institutions that do their best to keep you from using a password manager.
Guess it'll be the iPhone after all.
I really do want to be able to tether, because we occasionally travel and don't have WiFi access and I want to use the laptop.
Tethering is indeed very handy and if you're willing to go to the trouble of jailbreaking your iPhone it can still be done.
Yes, the story headline is talking about something totally different. I mean, how do YOU read "100-Petabit Internet Backbone"? Most people would not interpret it to mean "15.5 Tbps delivered over 7000 km." (The headline error is repeated in TFA. Ironically if you click all the way through to the AlcaLu press release the headline is more accurate: "Alcatel-Lucent Bell Labs announces new optical transmission record and breaks 100 Petabit per second kilometer barrier".)
I will grant you that optics geeks may find the bandwidth-distance metric familiar... but I continue to assert that [Inter]net geeks do not.
Thing is, it wouldn't, which is why the headline is so totally wrong. (Yes I saw the smiley.)
At the very least I assume we can agree that "100-Petabit Internet Backbone" is a gross misrepresentation of what the press release describes. "15.5 Tbit long haul" would have been accurate.
Maybe old hat to you network engineers, but I was previously unfamiliar with "bits per second.kilometer".
Thanks for the info. No, this is not old hat to network engineers. I've never heard of it and I've been working in the industry for more years than I care to admit. I think it might be old hat to marketing people though, since it appears to be a classic BIG MARKETING NUMBER. Normal networking people would call 15.5 Tbps * 7000 km... 15.5 Tbps.
Maybe it's true that optics geeks really do use numbers this way, I dunno. But the fact it comes from an AlcaLu press release doesn't lend it a whole lot of credibility.
I am massively unimpressed by the headline on the Slashdot story. Maybe another article headlined "kdawson swallows inflated AlcaLu marketing fluff hook, line and sinker" would be in order?
Almost anything that is uploaded to the Kindle store that was based on a public domain work is no longer entirely public domain.
That may be, but the GP says that it potentially only takes a single DRM'd PD work to establish a legal use for DRM circumvention. If that's so, then "almost" isn't good enough for someone in the DRM business. If your goal is to execute this kind of legal hack, your first step would be to create and upload a work which you explicitly place into the public domain. That would seem to address your points.
it doesn't really matter unless you were planning on getting the server edition, anyway.
Which I, for one, was. BTW, they'd also confirmed (before they pulled it) that ZFS would be supported in Client at the CLI level -- just no GUI sugar. Oh well. Easy come, easy go.
Did you RTFA? The point that O'Reilly (and others like Cory Doctorow) is making is essentially that according to his data (and he does have data), people who publish on closed platforms using DRM make less profit than people who publish on open platforms.
Yes, it's counter-intuitive. But so far, the people who use actual evidence in making their arguments seem to be showing that's how it is.
If you resent unpaid use of your work so much that you are willing to make less profit in exchange for preventing it, that's your call. But if you really do create for profit, you might want to read the article, and others like it, and think hard about it.
I can't quite believe I'm feeding the trolls, but...
i am not like them and i am glad of it. if they want to have the same "freedom" we have and the same "prosperity" we have.
Riiight, those are the only motivations. Or maybe that's a strawman that was set up by the Bush administration.
then they can move here and quit their whining and jihad bullshit. nobody is forcing them to live in a giant catlitter box. they are choosing to live there and complain about their "plight" seriously they are just bitching for the sake of bitching because they are too fucking dumb or assholish or small minded to do something different. i may sound racist
Yes, you do. But at least you balance it out by sounding ignorant as well.
but at least i am being honest.
Though not well-informed.
and like i said before. they want out of the cat box all they have to do is move somewhere else... i hear Hawaii is rather nice...
Here's a cartoon flow-chart based on actual research and facts explaining a few of the things you clearly don't understand about how difficult it is to immigrate to the USA. I expect other Western countries have similar, or worse, flowcharts of their own.
(One thing I would add to the flow chart is an initial box for "do you have enough money to travel from your home country to the USA?". You may find this http://en.wikipedia.org/wiki/List_of_countries_by_GDP_(nominal)_per_capita>chart of GDP per capita for various countries to be illuminating. Sorry, not a cartoon. Remember that the chart is overoptimistic because it only gives you the mean, not the median. The median is likely to fall below the mean.)
Pancreatic Cancer has a 6% 5-year survival rate.
Again, this is pretty misleading unless you consider the specific cancer rather than "pancreatic cancer" as a generic. The statistic you cite is for "Estimated Five-year Relative Survival Ratio (%) (and 95% Confidence Interval) for the Most Common Cancers", and you read off the "pancreas" line. The specific case in question is not one of "the most common cancers" but (AFAICT) a different disease of the same organ.
Pancreatica.org has this to say about islet cell tumors:
Neuroendocrine tumors of the pancreas (islet cell tumors) are much less common than tumors arising from the exocrine pancreas. Reports often indicate that there are about two to three thousand cases diagnosed in the U.S. each year
and
The natural history of islet cell and carcinoic tumors tends to be favorable as compared with pancreatic adenocarcinoma. For example, the median survival duration from the time of diagnosis for patients with non-functioning metastatic islet cell tumors approaches five years.
(Johns Hopkins agrees.)
The Pancreatica article says this compares to a median survival time of 15.5 months for adenocarcinoma of the pancreas ("pancreatic cancer") treated with the same surgery Jobs had.
I haven't heard of anyone getting better from pancreatic cancer.
Now you have. A few minutes with Wikipedia reveals that "Jobs was lucky; he had an extremely rare form called an islet cell neuroendocrine tumor that can be treated surgically, without radiation or chemotherapy." (From the Fortune article the Steve Jobs Wikipedia article links to.)
It's really dicey for non-experts (or, probably even experts) to make generalizations based on the common name of a cancer, without knowing exactly what variety of the disease it is, what stage it's at, and so on. Jobs has been (apparently) cancer-free since his surgery in July 2004.
Recall the the Air Force also places several types of sensors so they know when folks are trying to take a photo from afar
Can you provide evidence of this? Or evidence that any such sensor technology exists at all?
Start by taking a look at RFC 2827/BCP 38, "Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing."
Sadly, ten years since publication we're still not there, which would seem to suggest (GP's wishful thinking notwithstanding) that you not hold your breath.
That sounds like a good reason not to select Silverlight if I wanted to deliver some kind of media myself. But I'm looking at this from the perspective of a consumer -- specifically, of a (prospective) user of Netflix's streaming video. Silverlight is already "cross platform" at least to the extent of being supported on Macs as well as Windows, else we wouldn't be having this conversation. Beyond that, why should I, from my narrow perspective, care about how cross platform it is if all I want to do is watch a video? As long as that data type is supported on my platform, the naive analysis says that's all I need.
At the moment the choice for watching Netflix streaming video isn't between Silverlight and Flash (or pick your technology). It's between Silverlight and not watching.
I take your point. On the other hand, I don't see the individual Mac (or Linux, etc) user having a whole lot of leverage in this situation. Up until now with Netflix's streaming video, the Windows version hasn't merely had "more features" but rather all the features since Macs haven't been supported at all. And since streaming video is not the primary reason I (or I'd venture to guess most people) subscribe to Netflix, I'm not about to fire Netflix over this lack... which means they're not particularly motivated to fix it.
The counter-argument is that clearly Netflix must perceive some benefit from having their subscribers stream video, else they wouldn't be offering the service at all. But the question as I see it is whether my refusal (and that of some other subset of Mac using Netflix subscribers) to adopt Silverlight and thus the streaming service would make enough of a dent in their overall business strategy to warrant a change in the technology they've adopted. My guess is that it wouldn't.
So I'm not quite sure what the "valuable lesson" is that I'm expected to learn. That I as an individual have very little leverage over ginormous corporations? And that they want to screw me? I learned those ones a long time ago.
Darn, I said I didn't want to discuss business strategies. Oh well.
Thanks, but I think these (modulo the "problems with Firefox" item) basically come under the "DRM is bad" and "Microsoft is bad" umbrella, at least to my way of thinking. I guess I should have added that I'm not really looking for reasons having to do with business practices or philosophy. I don't mean to trivialize the importance of such things, but they're just not what I'm looking to discuss right now -- I understand these arguments well already. What I'm looking for are specific technical reasons not to like Silverlight. Examples of such reasons might be "it makes your Mac less stable," "it interferes with Flash playback" or "it phones home with your personal information". (Evidence is always a plus of course.)
Can you say more about "problems with Firefox"?