Looks like he was pushed out already and now BlackBerry do seem to have a new OS, new model based on numerous modern mobile programming models.
I never bought a BB before but having been a happy Nokia customer for over 12 years, I shall be registering my vote of no confidence in WinPhone8 by selecting a different brand for my contract renewal coming up this year. They seemed to have retained the good stuff they were always good up but made the ecosystem more open and friendly, no more BES lockin and other such ploys.
You'd have thought that if Jim was 100% behind the current new image for RIM we would have stuck around at the recent unveiling to claim some credit. You'd have thought Jim is fully aware of the implication of sell the entire stock holding at this particular time to on lookers.
I can only praise BBs original vision he may have had a hand in, but they did loose their way. I can only praise their current strategy they seem to be the only mobile maker with a strategy right now. If Jim was in the way then it is good for him to find something else to be doing now maybe he can offer his services to a well known Finnish brand that recently picked the wrong Canadian. Call that the final vote of no confidence form him if you will and we might have a 4 horse race to the commodity mobile bottom of the market.
No you fail. Backscatter-spam does not exist if everyone does SPF. Since you can not fake a domain.
The "We have rejected your email due to bad SPF records" will surely get back to the domain whose SPF records are bad, regardless of if the email causing it was fake or not the bad SPF records still need to be fixed and are the responsibility of domain owner to manage.
Correctly setup SPF records on a victims domain will cause fake emails to be rejected (with no "We have rejected..." message generated).
The battery life of mine was great, I believe this was due to the way the unit span up the disc to read a chunk of data then shutdown the motor while it decoded and played, IIRC it would do this every ~5 to 8 seconds. They only held around 120Mb in a Sony audio codec to store the same minutes a CD could.
Red Amber (yes or 'Flashing Amber' often used at pedestrian crossings with traffic lights, however a solid amber means stop, a flashing amber means you may proceed with caution) Green Red + Amber (this is used to provide warning of the Red, no jumping red light ticket can be issued as long as your vehicle has crossed the white line) Red
The sequence is as above so it is possible to tell at a glance if the Amber is going towards Red or Green. There should be reason for a vehicle doing the speed limit should not have been able to stop for the Red light so tickets maybe issued on a clear matter of fact, did the vehicle cross the white line while on a Red light.
We have a similar thing in UK (over past 3 years), right now many standard speeding cameras are not active due to changes in policy they are no longer a revenue generating part of law enforcement and the austerity measures placed on the stakeholders (police, local government, planning, maintenance) involved in their operation means they no department will pay for their upkeep out of their budget. The red light / speeding camera mounting boxes still exist at the side of the road as do the 'cameras are here' warning signs. I'm sure a future change on government policy will bring them back into service at some point in the future.
What is the Applet sandbox plugin if it isn't a piece of software written in ? This plugin is a relic of the dot com boom. It should have been made a separately downloadable and installable product a long time ago so it would not even get accidentally installed by most.
The problem has been the Applet system is not popular enough to generate enough attention to have a complete security audit/rewrite and historically it has been rammed down every JRE installers throat (often without their knowledge). With no simple way to disable it and with it reactivating itself at every future update (yes something has been done to address this only very recently).
As for problems with the Java "language" or the "JVM" I don't see it. Disconnect it from the browser and non of the remaining issues would warrant attention from technical forums.
I think unfortunately because of the way Java tries to brand itself as a single uniform environment many non-Java users and technical people who think they understand it really don't. They fail to separate the many facets of the platform from each other which results in comment like the GP has made.
Java brand != Java language != Java VM != Java applet plugin
But the device is slightly cheaper than the top line phones from others (by ~$80 I read). With this difference the carrier can subsidize the backend stuff and still provide an on-parity plan to the end customer.,
Hmm the price should be dependent on the R&D cost and the relative benefit to other people. Not based on the amount the market would bear and could be taxed. Remember patents are there to ensure publication of what would otherwise be a trade secret of something that was difficult to invent or discover. For doing this society gives you an exclusivity right.
The problem today is that things that could early have been independently developed by those skilled in the art are able to obtain this privilege.
In the UK it is usual to have a 24 month contract of sufficient price per month to cover subsidy (of top end phones). It maybe possible to get a 12 month contract for low end phones. But I've never heard of a 6 month contract term for phone subsidy. Is there a reason why the 'forced subscription' isn't longer in Denmark ?
I like the idea of simply having an installment plan (including borrowing interest/markup) for the phone cost on the bill. One aspect of the 24 month forced contract in the UK is that you will continue to pay that amount even once the 24 month period is over unless you re-negotiate a new plan. Of course you can take a place handset free that is cheaper.
"personally identifiable" is funny... apparently it is not because it is HASHED! ah good we are all safe then.... hmm but most hashes use more bits than are in an ethernet MAC address, so really you transformed on number into another number that is unique so the one person. This is personally identifiable in my book, The only hash that would not be "personally identifiable" would be 1 bit hash such that there were enough collisions to that you had a 50% chance of being in one group or another.
"not personally identifiable"... these technology "inventors" keep using that term... but I don't think it means what they think it means. They use it like a marketing point, they need to say this to keep the public calm. But really it is buzzword lipservice. There should be an international kite mark for such claims that have public and open scrutiny.
dedupe doesn't need to understand what the data is only that the data is identical. so now the 2 copies of data they make are now shared by 2 or more accounts (for that block allocation unit at least). The likelihood of duplication occurring however is small, as any cryptographic file storage system when reformatted by the same user to store inside exactly the same data will have completely different encrypted data. This is due to the session key and block perturbation scheme.
I can only think that this is a clause to cover some kind of legal angle maybe due to the way someone else might claim gained access to your (private) data, when really all they did was have access to an encrypted block of data that both you and the other guy happened to upload that happened to be identical. With copy-on-write when one of you changes that block of data you would presume the system unshares the data. The most obvious case for deduplication would be blocks of zeroed data.
The problem is we don't have access to everybody elses code! Even more of a problem in C++ these direct access to public members will not route via a symbol. This means now I can not change it in future without breaking all the consumers.
The point of 'free as in beer' is that the recipe is free but you have to obtain your own ingredients and your own effort in order to make it. That relates well to the open-source paradigm (re having access to source code and needing to support it yourself) but I fail to see how it relates in your use of the phrase.
Which of the 4 freedoms does the "app store" violate ?
From the GPL v3 ?
the freedom to use the software for any purpose,
the freedom to change the software to suit your needs,
the freedom to share the software with your friends and neighbors, and
the freedom to share the changes you make.
I don't see any of these being violated by VLC itself and it is only VLC that is covered by GPL. The use of an app store does not inhibit the redistribution of source code for the GPL licensed parts.
Furthermore which app store take on complete legal responsibility for the copyrighted works? Meaning if there was an issue with an application the app store itself is not liable but the agreement makes the data uploading party (aka the publishing entity) legally responsibly for their actions.
I see the "walled garden app store" becoming extinct, the public only put up with so much getting shafted and the first movers always profit from it but as it becomes mainstream public awareness will only increase and they will learn how to avoid the trap.
Once it all blows over the public should be left with the results of the technology drive (TPM, white-list only runnable code, signed code) to use for their own useful purpose. There will always be a manufacturer who will make a similar model of the same hardware that isn't crippled and hardware keeps getting replaced/updated. This will all take some years yet to blow over.
> 2) The competing model, by contrast, assumes that events in the world are perfectly consistent and that the job of an intelligent system is to discover this perfection.
This is an interesting point because isn't that how Darwin works ? Except it wasn't an intelligent system making a decision it was simply that bad choices and dead ends did not survive the process. During this process an organisms reward feedback loop developed. Why doesn't that simple model not apply to describe what intelligence is ?
Maybe there is some hope for making an almost self-aware machine then advising it that we're running out of usable energy to keep it switched on then letting it think up solutions so that problem. Ideally in the direction of how to harness the sun's energy for industrial scale photosynthesis, using sunlight to slice CO2 and water modules apart.
> Full disclosure: I fully suspect that if guns were outlawed here in the US, we would see an alarming rise in knife related crime.
I think this is part of the natural journey to reduce violent crime you have to handle when you get there, i.e. there is no easy way to solve all the problems in a short amount of time, but until better gun control is enacted the whole process can not begin. When if/when knife crime becomes the new problem the US will just have to deal with it at that point in time. The switch over from guns to knifes will however clearly indicate the criminal mind-set has changed and in the end that is exactly what you need to happen to get a lasting resolution, by change the mind-set of the criminal.
Yes because the purpose is to provide protection from casual eavesdropping not from full blown MITM.
Also Google is not the only user of the POP3 system, you may have other devices connected to it, but often you can not authorize only a specific certificate you have to authorize the whole CA as trusted. But I don't trust the CA. So running your own self-signed as in effect continuing the trend to trust a CA that happened to be yourself.
But the reverse DNS lookup will never match. Some client check this too. The reverse lookup for 1.2.3.4 will never return "mail.example.com" but "dyn-1-2-3-4-foobar.myprovider.com"
Repeated hashing is done to slow down the speed at which an attempt maybe tried. Take PBKDF2 the point of this is to reduce the ability even by specialized hardware (such as discussed in the article) to brute force the keyspace. If you are not talking about PBKDF2 but some other attempt to repeatably hash then don't bother replace your technique with PBKDF2 or something better still.
Fast hashes are BAD for password security. Slow hashes are GOOD for password security. Repeated hashing is an attempt to make a fast hash algorithm slower but maybe it doesn't salt and maybe it doesn't do it as well as PBKDF2.
Furthermore to this (with PBKDF2) I can simply increase the number of rounds of iteration I make for all new password set after a point in time. So this means I can always stay ahead if the game without significantly redesigning the system. It also means I can store in my password database the number of rounds/iterations as well as the result as well as the date the password as last set/changed. Now I can enforce a policy where by inactive users of the system as locked out (if they have not used their password in 12 months) and when I need to increase the number of iterations to stay ahead in the arms race I give all existing users 12 months to login where by they get notice to reset/change their password. They login with old password maybe doing 10000 rounds and before they can use the system they are forces to change their password. During this reset I re-encode their new password with 20000 rounds and store it in the database.
But there is no such thing as a new product. Someone has to buy 2nd hand raw materials to make it. All transfers of wealth can be taxed, the classification for it to be new or used is not important. If you make it important then everyone will be writing invoices for used goods to make use of your new proposed low tax rate to avoid paying tax.
Did you read what was written ? How many transistors does it take to make a 1Mb ARM CPU Cache ? Then a 1Mb Intel CPU Cache (with has a stronger memory model) ? Now how many transistors for a core ?
I know I have a suggestion, you know those picture of silicon that Intel marketing put out with nice coloured lines painted on them to point out where each functional unit is. Compare the area of the cache to the area used for a core.
So while it is possible for a RISC CPU to use less transistors to implement a whole useful ISA. It is not possible to also make it go fast (and keep the "less transistor" power advantage). This is the struggle ARM now faces. Intel are already ahead and fighting back with power reduction capabilities (i.e. switching whole functional units off when not in use) and in process size reduction around 10 to 20nm.
How much power does a PowerPC chip use, these are the closest competitor in the RISC family to be targeting at the kinds of systems Intel has market share in. Take a look at the industrial cooling solutions for some of those systems then compare heat output against performance and Intel clearly wins. Intel already have chips that will work reliability through a lifetime warranty in a consumer workstation situation. PowerPC doesn't have such a product, they do have slower chips such at those used in gaming consoles and other such devices.
What is so important about the binary encoding being total different ? i.e. most people use assemblers/disassemblers and read mnemonics. Maybe the binary encoding change optimizes for lower power in some way ? If they have a chance to rewrite the rule book and make things better ? They can potentially have versions that remove all 32bit support (i.e. use those transistors for another arm64 core instead of a 32bit mode)
The limit you speak of is the compulsory registration for VAT limit. You MUST become VAT registered if you turnover more than the limit. If you are under this limit it is your choice to voluntarily become VAT registered. You talk of the limit being a minimum turnover, it is not.
Volume is not relevant if you are loosing money on each item. Cutting back production can be a lower risk proposition than signing the contract and becoming bankrupt.
Slashdot Mirror
http://www.thestar.com/business/2012/03/30/jim_balsillie_resigns_from_rim_board.html
> Jim Balsillie stepped down from the Research in Motion board of directors on March 2.
Looks like he was pushed out already and now BlackBerry do seem to have a new OS, new model based on numerous modern mobile programming models.
I never bought a BB before but having been a happy Nokia customer for over 12 years, I shall be registering my vote of no confidence in WinPhone8 by selecting a different brand for my contract renewal coming up this year. They seemed to have retained the good stuff they were always good up but made the ecosystem more open and friendly, no more BES lockin and other such ploys.
You'd have thought that if Jim was 100% behind the current new image for RIM we would have stuck around at the recent unveiling to claim some credit. You'd have thought Jim is fully aware of the implication of sell the entire stock holding at this particular time to on lookers.
I can only praise BBs original vision he may have had a hand in, but they did loose their way. I can only praise their current strategy they seem to be the only mobile maker with a strategy right now. If Jim was in the way then it is good for him to find something else to be doing now maybe he can offer his services to a well known Finnish brand that recently picked the wrong Canadian. Call that the final vote of no confidence form him if you will and we might have a 4 horse race to the commodity mobile bottom of the market.
No you fail. Backscatter-spam does not exist if everyone does SPF. Since you can not fake a domain.
The "We have rejected your email due to bad SPF records" will surely get back to the domain whose SPF records are bad, regardless of if the email causing it was fake or not the bad SPF records still need to be fixed and are the responsibility of domain owner to manage.
Correctly setup SPF records on a victims domain will cause fake emails to be rejected (with no "We have rejected ..." message generated).
No backscatter-spam issue.
The battery life of mine was great, I believe this was due to the way the unit span up the disc to read a chunk of data then shutdown the motor while it decoded and played, IIRC it would do this every ~5 to 8 seconds. They only held around 120Mb in a Sony audio codec to store the same minutes a CD could.
In the UK it is:
Red
Amber (yes or 'Flashing Amber' often used at pedestrian crossings with traffic lights, however a solid amber means stop, a flashing amber means you may proceed with caution)
Green
Red + Amber (this is used to provide warning of the Red, no jumping red light ticket can be issued as long as your vehicle has crossed the white line)
Red
The sequence is as above so it is possible to tell at a glance if the Amber is going towards Red or Green. There should be reason for a vehicle doing the speed limit should not have been able to stop for the Red light so tickets maybe issued on a clear matter of fact, did the vehicle cross the white line while on a Red light.
We have a similar thing in UK (over past 3 years), right now many standard speeding cameras are not active due to changes in policy they are no longer a revenue generating part of law enforcement and the austerity measures placed on the stakeholders (police, local government, planning, maintenance) involved in their operation means they no department will pay for their upkeep out of their budget. The red light / speeding camera mounting boxes still exist at the side of the road as do the 'cameras are here' warning signs. I'm sure a future change on government policy will bring them back into service at some point in the future.
What is the Applet sandbox plugin if it isn't a piece of software written in ? This plugin is a relic of the dot com boom. It should have been made a separately downloadable and installable product a long time ago so it would not even get accidentally installed by most.
The problem has been the Applet system is not popular enough to generate enough attention to have a complete security audit/rewrite and historically it has been rammed down every JRE installers throat (often without their knowledge). With no simple way to disable it and with it reactivating itself at every future update (yes something has been done to address this only very recently).
As for problems with the Java "language" or the "JVM" I don't see it. Disconnect it from the browser and non of the remaining issues would warrant attention from technical forums.
I think unfortunately because of the way Java tries to brand itself as a single uniform environment many non-Java users and technical people who think they understand it really don't. They fail to separate the many facets of the platform from each other which results in comment like the GP has made.
Java brand != Java language != Java VM != Java applet plugin
But the device is slightly cheaper than the top line phones from others (by ~$80 I read). With this difference the carrier can subsidize the backend stuff and still provide an on-parity plan to the end customer.,
Hmm the price should be dependent on the R&D cost and the relative benefit to other people. Not based on the amount the market would bear and could be taxed. Remember patents are there to ensure publication of what would otherwise be a trade secret of something that was difficult to invent or discover. For doing this society gives you an exclusivity right.
The problem today is that things that could early have been independently developed by those skilled in the art are able to obtain this privilege.
In the UK it is usual to have a 24 month contract of sufficient price per month to cover subsidy (of top end phones). It maybe possible to get a 12 month contract for low end phones. But I've never heard of a 6 month contract term for phone subsidy. Is there a reason why the 'forced subscription' isn't longer in Denmark ?
I like the idea of simply having an installment plan (including borrowing interest/markup) for the phone cost on the bill. One aspect of the 24 month forced contract in the UK is that you will continue to pay that amount even once the 24 month period is over unless you re-negotiate a new plan. Of course you can take a place handset free that is cheaper.
"personally identifiable" is funny... apparently it is not because it is HASHED! ah good we are all safe then.... hmm but most hashes use more bits than are in an ethernet MAC address, so really you transformed on number into another number that is unique so the one person. This is personally identifiable in my book, The only hash that would not be "personally identifiable" would be 1 bit hash such that there were enough collisions to that you had a 50% chance of being in one group or another.
"not personally identifiable" ... these technology "inventors" keep using that term ... but I don't think it means what they think it means. They use it like a marketing point, they need to say this to keep the public calm. But really it is buzzword lipservice. There should be an international kite mark for such claims that have public and open scrutiny.
dedupe doesn't need to understand what the data is only that the data is identical. so now the 2 copies of data they make are now shared by 2 or more accounts (for that block allocation unit at least). The likelihood of duplication occurring however is small, as any cryptographic file storage system when reformatted by the same user to store inside exactly the same data will have completely different encrypted data. This is due to the session key and block perturbation scheme.
I can only think that this is a clause to cover some kind of legal angle maybe due to the way someone else might claim gained access to your (private) data, when really all they did was have access to an encrypted block of data that both you and the other guy happened to upload that happened to be identical. With copy-on-write when one of you changes that block of data you would presume the system unshares the data. The most obvious case for deduplication would be blocks of zeroed data.
The problem is we don't have access to everybody elses code! Even more of a problem in C++ these direct access to public members will not route via a symbol. This means now I can not change it in future without breaking all the consumers.
"Free as in beer, as they say."
The point of 'free as in beer' is that the recipe is free but you have to obtain your own ingredients and your own effort in order to make it. That relates well to the open-source paradigm (re having access to source code and needing to support it yourself) but I fail to see how it relates in your use of the phrase.
Which of the 4 freedoms does the "app store" violate ?
From the GPL v3 ?
the freedom to use the software for any purpose,
the freedom to change the software to suit your needs,
the freedom to share the software with your friends and neighbors, and
the freedom to share the changes you make.
I don't see any of these being violated by VLC itself and it is only VLC that is covered by GPL. The use of an app store does not inhibit the redistribution of source code for the GPL licensed parts.
Furthermore which app store take on complete legal responsibility for the copyrighted works? Meaning if there was an issue with an application the app store itself is not liable but the agreement makes the data uploading party (aka the publishing entity) legally responsibly for their actions.
I see the "walled garden app store" becoming extinct, the public only put up with so much getting shafted and the first movers always profit from it but as it becomes mainstream public awareness will only increase and they will learn how to avoid the trap.
Once it all blows over the public should be left with the results of the technology drive (TPM, white-list only runnable code, signed code) to use for their own useful purpose. There will always be a manufacturer who will make a similar model of the same hardware that isn't crippled and hardware keeps getting replaced/updated. This will all take some years yet to blow over.
> 2) The competing model, by contrast, assumes that events in the world are perfectly consistent and that the job of an intelligent system is to discover this perfection.
This is an interesting point because isn't that how Darwin works ? Except it wasn't an intelligent system making a decision it was simply that bad choices and dead ends did not survive the process. During this process an organisms reward feedback loop developed. Why doesn't that simple model not apply to describe what intelligence is ?
Maybe there is some hope for making an almost self-aware machine then advising it that we're running out of usable energy to keep it switched on then letting it think up solutions so that problem. Ideally in the direction of how to harness the sun's energy for industrial scale photosynthesis, using sunlight to slice CO2 and water modules apart.
> Full disclosure: I fully suspect that if guns were outlawed here in the US, we would see an alarming rise in knife related crime.
I think this is part of the natural journey to reduce violent crime you have to handle when you get there, i.e. there is no easy way to solve all the problems in a short amount of time, but until better gun control is enacted the whole process can not begin. When if/when knife crime becomes the new problem the US will just have to deal with it at that point in time. The switch over from guns to knifes will however clearly indicate the criminal mind-set has changed and in the end that is exactly what you need to happen to get a lasting resolution, by change the mind-set of the criminal.
Yes because the purpose is to provide protection from casual eavesdropping not from full blown MITM.
Also Google is not the only user of the POP3 system, you may have other devices connected to it, but often you can not authorize only a specific certificate you have to authorize the whole CA as trusted. But I don't trust the CA. So running your own self-signed as in effect continuing the trend to trust a CA that happened to be yourself.
But the reverse DNS lookup will never match. Some client check this too. The reverse lookup for 1.2.3.4 will never return "mail.example.com" but "dyn-1-2-3-4-foobar.myprovider.com"
Repeated hashing is done to slow down the speed at which an attempt maybe tried. Take PBKDF2 the point of this is to reduce the ability even by specialized hardware (such as discussed in the article) to brute force the keyspace. If you are not talking about PBKDF2 but some other attempt to repeatably hash then don't bother replace your technique with PBKDF2 or something better still.
Fast hashes are BAD for password security. Slow hashes are GOOD for password security. Repeated hashing is an attempt to make a fast hash algorithm slower but maybe it doesn't salt and maybe it doesn't do it as well as PBKDF2.
Furthermore to this (with PBKDF2) I can simply increase the number of rounds of iteration I make for all new password set after a point in time. So this means I can always stay ahead if the game without significantly redesigning the system. It also means I can store in my password database the number of rounds/iterations as well as the result as well as the date the password as last set/changed. Now I can enforce a policy where by inactive users of the system as locked out (if they have not used their password in 12 months) and when I need to increase the number of iterations to stay ahead in the arms race I give all existing users 12 months to login where by they get notice to reset/change their password. They login with old password maybe doing 10000 rounds and before they can use the system they are forces to change their password. During this reset I re-encode their new password with 20000 rounds and store it in the database.
and do standalone versions they require a 13Gb root drive ? like surface ?
But there is no such thing as a new product. Someone has to buy 2nd hand raw materials to make it. All transfers of wealth can be taxed, the classification for it to be new or used is not important. If you make it important then everyone will be writing invoices for used goods to make use of your new proposed low tax rate to avoid paying tax.
Did you read what was written ? How many transistors does it take to make a 1Mb ARM CPU Cache ? Then a 1Mb Intel CPU Cache (with has a stronger memory model) ? Now how many transistors for a core ?
I know I have a suggestion, you know those picture of silicon that Intel marketing put out with nice coloured lines painted on them to point out where each functional unit is. Compare the area of the cache to the area used for a core.
So while it is possible for a RISC CPU to use less transistors to implement a whole useful ISA. It is not possible to also make it go fast (and keep the "less transistor" power advantage). This is the struggle ARM now faces. Intel are already ahead and fighting back with power reduction capabilities (i.e. switching whole functional units off when not in use) and in process size reduction around 10 to 20nm.
How much power does a PowerPC chip use, these are the closest competitor in the RISC family to be targeting at the kinds of systems Intel has market share in. Take a look at the industrial cooling solutions for some of those systems then compare heat output against performance and Intel clearly wins. Intel already have chips that will work reliability through a lifetime warranty in a consumer workstation situation. PowerPC doesn't have such a product, they do have slower chips such at those used in gaming consoles and other such devices.
What is so important about the binary encoding being total different ? i.e. most people use assemblers/disassemblers and read mnemonics. Maybe the binary encoding change optimizes for lower power in some way ? If they have a chance to rewrite the rule book and make things better ? They can potentially have versions that remove all 32bit support (i.e. use those transistors for another arm64 core instead of a 32bit mode)
I wonder how much money I could make with my Stanley knife optimization scheme, splice'n'dice!
The limit you speak of is the compulsory registration for VAT limit.
You MUST become VAT registered if you turnover more than the limit.
If you are under this limit it is your choice to voluntarily become VAT registered.
You talk of the limit being a minimum turnover, it is not.
Volume is not relevant if you are loosing money on each item. Cutting back production can be a lower risk proposition than signing the contract and becoming bankrupt.