his isn't a scientific paper, it's a piece of journalism. In that case, there's nothing wrong with using numbers that aren't completely reduced to demonstrate scale.
No, standard != wrong.
In this case, there's precisely the same thing wrong that is with all of journalism: use specific language constructs to push certain emotional messages along with information. AKA manipulation.
Actually, the truth is the law is on your side in these cases but it doesn't stop big companies from bullying you and if you can't afford a good lawyer to defend your case, they WILL win. But dollar for dollar in lawyer fees for both sides, the victory is yours.
Obviously you are a cheapskate who lives in a town full of cheapskates
So that's how you call these from former eastern bloc countries in USA nowadays?
but even we have the whole Discworld series in multiple copies in our library.
Sorry, we don't. We don't have even a single complete series of it. Price:salary ratio is worse on almost everything here, and that includes books. One paperback book the class of Discworld is about an average daily salary, few can afford such donations and it's not tax-deductable here.
And if you feel like the author deserves the money, you buy the DRM'd versions from Amazon and promptly delete them
I'm offered a choice between a sub-par, restricted, limited, crippled version of something for $MUCH and the same thing without these flaws for $NONE.
I'm ready to pay the $MUCH for the unrestricted version. I don't want the restricted version, its price being moot.
So where's the evil of grabbing the 'open' version of the books from torrent, buying the same books in DRM format, then just never using the DRM version?
That I don't pay premium for a reader device with restriction chips? That I can backup them, I can read them on any device I have, without the publisher's approval?
Or that I can decide not pay for the book if I give up reading it one chapter deep, deciding it's utter crap and not worth the money by far, and that the advertisement was deceiving?
I can scan entire bookshelves in a glance. No time needed for indexing, just a quick look is necessary.
OTOH if you want to read a specific book, and you have more than one bookshelf, finding it can be a bitch. If you have much more than one bookshelf, it can be a REAL bitch.
If I want an e-book reader that does just that - displays the text - without web browser, wireless purchases, touchscreen, accelerometers, WiFi, EVDO, DRM, DMCA, PATRIOT, WMD and all this crap that does little to user experience and lots to the price. Not every country considers 2 salaries worth of money a good price for a device to just read books.
A paperback book with 1MB hardly fits in a pocket and is maybe 6h of reading for an average reader. A 1GB SD card is easily months of reading, pluggable into a device that is the size of the 1MB book - and thanks to the e-paper, the batteries won't die on you while you read and the readablity will be just like with a paper book.
Imagine you want to read the whole Pratchett's Discworld series on your daily way to work, 1h each direction, on a train daily. You either go to a bookstore and (with lots of luck if it's all in stock) buy some 10 pounds of paper, then remember to take one part for your travel, or two if you're about to finish the 'current' one. You pay a small fortune.
Or you rent them at a library. Good luck getting them all, good luck getting them in parts and none of the parts missing, you're bound by return schedules and you need to go to said library.
Or you visit piratebay and download the whole series in ebook format, then read it on your pocket reader. Cost: zero. You have them all, no management. You read on your own schedule. They fit on one tiny card. And so on... And if you feel like the author deserves the money, you buy the DRM'd versions from Amazon and promptly delete them, or just buy the paper version and put them on a shelf in your house, never opening them.
So, you're saying it's like comparing points at the ceiling a bulb, to suddenly releases a powerful camera flash into the person's eyes a flash? Nothing wrong about this, I believe?
The ridiculous thing about Trademark law is that it works back in time. Unlike with patents, there's no 'prior art' to overturn it and unlike copyright which requires some level of creativity, as long as it's not a common word (but a phrase of 2 common words is ok) you can trademark it. And then you can sue everyone who uses it, even if they kept using it years before you were born.
2 weeks is time since picking up the book till you can start writing your first PHP app.
And your app will be obviously of the 'my first app' quality.
The whole point of my post was that you need a month to get from zero to "Yay, I know how to write AJAX" level. Then you need another 2-3 months to realize "I don't really know AJAX at all." Then another year to really know it.
(this is assuming you're working on AJAX full-time, not 'in between other projects'.)
Yes, I have 'Programmer' on my resume.
No, I don't really know AJAX. I just know how much I don't know.
This is programming 2 languages and 2 platforms (with one in at least 3 slightly incompatibile variations) plus epsilon.
Way too many people neglect the server side part of AJAX as 'trivial'. It is often just as tricky or trickier than the front end part of the business (note the JS part can not be trusted so you MUST implement all of the security checks server-side (while often keeping them client-side redundantly) and put a clear and well-defined line between the secure and insecure parts (which is often quite difficult). So you have one platform: the server, and one language: the server-side CGI language (PHP, Ruby, Java etc)
Then there's the client-side language (Javascript) and the client-side platforms - the browsers. And their incompatibilities alone are enough to give a headache to everyone.
The 'epsilon' is the glue between the platforms, AJAX transport - XML, JSON or whatever you choose. Luckily these are rather easy comparing to the rest.
What needs to be kept secure, is kept secure, server side. But a lot of the presentational layer and lots of the glue logic between raw data and the presentational layer can be moved to client side.
You don't send a GIF with a graph. You send raw data, and let the client side software to generate captions, calculate scale, find top value and trend lines, then feed the result to a flash library that will create a pretty graph from it. You don't send every single junk character the user types to the server. You perform client-side validation, discard invalid input. Then you repeat exactly the same validation server-side, but you accept 99% of the input, and pay close attention to users whose input didn't validate (because they are trying to hack you) instead of discarding 50% of entries server-side. Your server load halves. Your only danger is that you expose your checks to the public, so your 'security through obscurity' suffers.
The beginnings are easy. Learn basics of HTML and CSS. A week and you're intermediate. You still don't know all the hacks and caveats but you know quite enough.
Learn basics of Javascript. Say, 3 days. Simple JS is easy. If you think all JS is easy, read some scripts by Douglas Crockford and see how wrong you were. But for a starter, you need simple JS.
Then learn using DOM. This isn't all that hard. There are some caveats like some browsers inserting whitespace text nodes between tags and such, but that's all doable. One evening to master it.
Learn some backend language. PHP probably. With some database too. Quite easy but the amount of knowledge you need to absorb is at least 2 weeks of learning.
Next you learn basics of using xmlHttpRequest. This is one evening and you know how it works and you know there's no sense using it as-is.
You spend the next afternoon picking an AJAX framework/library/toolbox and another day learning it.
They you spend another year writing AJAX and learning how to properly react to unreliable connections and handle all kinds of errors, corrupted data, browser incompatibilities, how to protect your apps from script injection attacks or exploiting your application server by someone "from outside", deal with load ballancing on the server side, sharing scripts between domains, making the code non-conflicting with other JS and self (2 instances of the same AJAX-based tool on one page? It's broken more often than you think!), creating javascript files dynamically using PHP to allow better flexiblity of your app, parsing, traversing, modifying and extracting data from style sheets, interacting with Flash, Java and APIs of a dozen external services, writing XUL based apps, optimizing data for transfer, porting large parts of business logic to JS to offload your application servers, then finally using the advanced javascript where modifying system methods and objects is not a taboo anymore.
A few days ago I took apart one of the first barracuda disks (broken) and found, besides the 10 plates (beauty!) and some interesting parts of more or less unknown purpose, two extremely strong magnets for moving the head. The magnets are really strong and the drives can be bought dirt cheap or even for free.
The cost of the service (room occupied by the seat) is somehow proportional to the cost of the ticket. Not directly, and the price is somewhat outrageous, but you are aware that serving everyone the first class standard for the price of economy class in unrealistic. There is some correlation between cost and price. It may feel somewhat unfair, but not as badly. In case of Vista though, the cost to manufacture one CD of Ultimate Edition and one CD of Home Edition is exactly the same. Both programs exist, both are shipped just the same and to make a copy of one costs the same as making a copy of the other. You're getting inferior service with no cost from the maker. Have your coffee for $10 or have your coffee for $5 with the waiter spitting in it.
The tricky thing here is that you can argue logic as much as you want, and it won't matter the least bit. It completely doesn't matter whether the customer is cheated on or not, who is right and who is wrong. What absolutely matters is, does the customer perceive the activity as being cheated on?
Here "The Customer Is Always Right" is the law. If the customer feels like being treated unfairly, the reaction you can expect is exactly like he was actually treated unfairly, objective truth be damned. If the customer complains, and you explain the activity is unfair, the customer will perceive that as further unfairness, using loopholes in the system and further trickery.
This is a kind of catch-22. Even though your pricing scheme fits the market perfectly, the guy who gets the 'economy class' feels treated like 'second class citizen', and the one who gets the business class, feels like being ripped off. Both hate the system and both feel cheated, both feeling like not getting their money's worth. If they both paid the same middle price and got the same middle-class product, given only choice to buy or not to buy, they would be both happier, but then the chance is quite a few of the "economy class" wouldn't afford the higher price, so sales would be lost, and the richer ones would pay less than they are ready to pay, so profits would be lost. So you either differentiate prices and piss people off (losing profits in the long run), or you keep them the same and lose customers and profits now.
It's not uncommon, but it isn't fair (or, taking more objective standpoint: "is perceived unfair by a major percentage of customers") - you're paying 400% the base price to get like 40% extra functionality. Besides, people don't perceive the high-end versions as extended variants of the low-end base system, but the low-end versions as purposedly crippled high-end base.
This still works as profit source in the short run, but it annoys the customer base, undermines loyalty, encourages seeking alternatives. And once alternatives are found, you lose in the long run. You squeeze $50 for Home Premium from an user today, and lose the whole sale and the customer entirely tomorrow.
Except the analysis hardly ever takes into account reasons why people switch to other OS, and even if it does, it comes to entirely wrong conclusions (they are cheaper, they have better marketing) while your own faults - trying to squeeze last penny off the customer - are hardly ever taken into account as the 'real evil'. People hate being cheated and perceive this as cheating. And it doesn't matter you don't and your marketing people will explain to your CEO that it really isn't cheating. For people, it is, and people will hate you for that. And will jump the ship at the first opportunity... or steal from the thieves, not a crime to many.
They are not equivalent but that's not entirely the question. The question is do they provide satisfactory functionality?
Because actually, 100 sub-$200 PC systems running Win98SE would probably work faster and be cheaper in means of TCO, and quite likely provide all the functionality needed as well (with exception of stability and security).
If I need email, office, file sharing and some, get the work done in acceptable comfort, you ask yourself what you need. You may get Vista and $1000 PCs, you can get XP and $500 PCs, or Linux and $300 PCs and the user experience and efficiency of work will be the same. You can get $150 PCs and Win98 too, but the risk of data loss and intrusion is prohibitory, otherwise it would have the work done as well. This way Linux can compete just fine and seems to be the best choice.
OTOH if you need a development environment of 4GB RAM quad-core 4GHZ CPU computers for all the 100 desktops, the price difference between OSes and their efficiency overhead becomes much lower. Linux doesn't fare just as well here, especially if you need to run WINE to have some essential apps working. If you need a high-end hardware not because it's required to run the OS, but because your application requires it, choice of the OS should be guided by other factors than just price of purchase or TCO. Although not disqualified here (by far), Linux doesn't have the upper hand of "vastly cheaper setup to get the same things done" here.
A little known fact: producing a solar cell consumes more power than the cell is able to produce during its whole lifetime.
This may change sometime in the future. Not anytime soon though. (The cells MAY cost you than grid energy, because they are manufactured in bulk, power bought in bulk. Doesn't mean they provide actual energetical savings)
If you're really innocent, then no matter how much you lie, use nasty, sneaky tactics, act dirty and play a cunning villain, the ruling should be "not guilty".
...unless you know the type of the device you're trying to crack.
A large part of the key is manufacturer ID and some product metadata of very low enthropy. Cracking the PIN was described as relatively easy, and upon narrowing the search to one type of devices, the time of break-in drops drastically.
AFAIK - no. Man In The Middle would be possible (if difficult) at the moment of pairing. You could also try to hack the keyboard controller itself, or use vulnerablities of the PC with bluetooth plugged in and active (the dongle must be working to allow the keyboard to connect) depending on what besides keyboard the PC allows. I'm also not sure you can't try coupling with the PC acting as its keyboard while the real keyboard is off (then you don't snoop but you have actual access.)
These are all guesses on my side though. I don't know if any actual work was done in this direction. BlueBag was about coupling with other devices, what you can do with this connection was barely hinted.
Slashdot Mirror
his isn't a scientific paper, it's a piece of journalism. In that case, there's nothing wrong with using numbers that aren't completely reduced to demonstrate scale.
No, standard != wrong.
In this case, there's precisely the same thing wrong that is with all of journalism: use specific language constructs to push certain emotional messages along with information. AKA manipulation.
Actually, the truth is the law is on your side in these cases but it doesn't stop big companies from bullying you and if you can't afford a good lawyer to defend your case, they WILL win. But dollar for dollar in lawyer fees for both sides, the victory is yours.
Obviously you are a cheapskate who lives in a town full of cheapskates
So that's how you call these from former eastern bloc countries in USA nowadays?
but even we have the whole Discworld series in multiple copies in our library.
Sorry, we don't. We don't have even a single complete series of it. Price:salary ratio is worse on almost everything here, and that includes books. One paperback book the class of Discworld is about an average daily salary, few can afford such donations and it's not tax-deductable here.
But then, indexing them takes DAYS!
And if you feel like the author deserves the money, you buy the DRM'd versions from Amazon and promptly delete them
I'm offered a choice between a sub-par, restricted, limited, crippled version of something for $MUCH and the same thing without these flaws for $NONE.
I'm ready to pay the $MUCH for the unrestricted version. I don't want the restricted version, its price being moot.
So where's the evil of grabbing the 'open' version of the books from torrent, buying the same books in DRM format, then just never using the DRM version?
That I don't pay premium for a reader device with restriction chips? That I can backup them, I can read them on any device I have, without the publisher's approval?
Or that I can decide not pay for the book if I give up reading it one chapter deep, deciding it's utter crap and not worth the money by far, and that the advertisement was deceiving?
I can scan entire bookshelves in a glance. No time needed for indexing, just a quick look is necessary.
OTOH if you want to read a specific book, and you have more than one bookshelf, finding it can be a bitch. If you have much more than one bookshelf, it can be a REAL bitch.
If I want an e-book reader that does just that - displays the text - without web browser, wireless purchases, touchscreen, accelerometers, WiFi, EVDO, DRM, DMCA, PATRIOT, WMD and all this crap that does little to user experience and lots to the price. Not every country considers 2 salaries worth of money a good price for a device to just read books.
It would be good if it was pocket-sized too.
What would you recommend?
Content:size ratio.
A paperback book with 1MB hardly fits in a pocket and is maybe 6h of reading for an average reader. A 1GB SD card is easily months of reading, pluggable into a device that is the size of the 1MB book - and thanks to the e-paper, the batteries won't die on you while you read and the readablity will be just like with a paper book.
Imagine you want to read the whole Pratchett's Discworld series on your daily way to work, 1h each direction, on a train daily. You either go to a bookstore and (with lots of luck if it's all in stock) buy some 10 pounds of paper, then remember to take one part for your travel, or two if you're about to finish the 'current' one. You pay a small fortune.
Or you rent them at a library. Good luck getting them all, good luck getting them in parts and none of the parts missing, you're bound by return schedules and you need to go to said library.
Or you visit piratebay and download the whole series in ebook format, then read it on your pocket reader. Cost: zero. You have them all, no management. You read on your own schedule. They fit on one tiny card. And so on... And if you feel like the author deserves the money, you buy the DRM'd versions from Amazon and promptly delete them, or just buy the paper version and put them on a shelf in your house, never opening them.
So, you're saying it's like comparing points at the ceiling a bulb, to suddenly releases a powerful camera flash into the person's eyes a flash? Nothing wrong about this, I believe?
Actually, it could STILL work for the OP.
The ridiculous thing about Trademark law is that it works back in time. Unlike with patents, there's no 'prior art' to overturn it and unlike copyright which requires some level of creativity, as long as it's not a common word (but a phrase of 2 common words is ok) you can trademark it. And then you can sue everyone who uses it, even if they kept using it years before you were born.
http://www.youtube.com/watch?v=SNVyIwuywzE
Yep. It's fun. Too bad well over 50% of the users don't have it. (yeah, -I- know there is a MSIE plugin...)
2 weeks is time since picking up the book till you can start writing your first PHP app.
And your app will be obviously of the 'my first app' quality.
The whole point of my post was that you need a month to get from zero to "Yay, I know how to write AJAX" level.
Then you need another 2-3 months to realize "I don't really know AJAX at all."
Then another year to really know it.
(this is assuming you're working on AJAX full-time, not 'in between other projects'.)
Yes, I have 'Programmer' on my resume.
No, I don't really know AJAX. I just know how much I don't know.
Not really.
This is programming 2 languages and 2 platforms (with one in at least 3 slightly incompatibile variations) plus epsilon.
Way too many people neglect the server side part of AJAX as 'trivial'. It is often just as tricky or trickier than the front end part of the business (note the JS part can not be trusted so you MUST implement all of the security checks server-side (while often keeping them client-side redundantly) and put a clear and well-defined line between the secure and insecure parts (which is often quite difficult). So you have one platform: the server, and one language: the server-side CGI language (PHP, Ruby, Java etc)
Then there's the client-side language (Javascript) and the client-side platforms - the browsers. And their incompatibilities alone are enough to give a headache to everyone.
The 'epsilon' is the glue between the platforms, AJAX transport - XML, JSON or whatever you choose. Luckily these are rather easy comparing to the rest.
Not ALL of the business logic of course.
What needs to be kept secure, is kept secure, server side. But a lot of the presentational layer and lots of the glue logic between raw data and the presentational layer can be moved to client side.
You don't send a GIF with a graph. You send raw data, and let the client side software to generate captions, calculate scale, find top value and trend lines, then feed the result to a flash library that will create a pretty graph from it. You don't send every single junk character the user types to the server. You perform client-side validation, discard invalid input. Then you repeat exactly the same validation server-side, but you accept 99% of the input, and pay close attention to users whose input didn't validate (because they are trying to hack you) instead of discarding 50% of entries server-side. Your server load halves. Your only danger is that you expose your checks to the public, so your 'security through obscurity' suffers.
It is not quite as easy.
Assuming you start from zero...
The beginnings are easy. Learn basics of HTML and CSS. A week and you're intermediate. You still don't know all the hacks and caveats but you know quite enough.
Learn basics of Javascript. Say, 3 days. Simple JS is easy. If you think all JS is easy, read some scripts by Douglas Crockford and see how wrong you were. But for a starter, you need simple JS.
Then learn using DOM. This isn't all that hard. There are some caveats like some browsers inserting whitespace text nodes between tags and such, but that's all doable. One evening to master it.
Learn some backend language. PHP probably. With some database too. Quite easy but the amount of knowledge you need to absorb is at least 2 weeks of learning.
Next you learn basics of using xmlHttpRequest. This is one evening and you know how it works and you know there's no sense using it as-is.
You spend the next afternoon picking an AJAX framework/library/toolbox and another day learning it.
They you spend another year writing AJAX and learning how to properly react to unreliable connections and handle all kinds of errors, corrupted data, browser incompatibilities, how to protect your apps from script injection attacks or exploiting your application server by someone "from outside", deal with load ballancing on the server side, sharing scripts between domains, making the code non-conflicting with other JS and self (2 instances of the same AJAX-based tool on one page? It's broken more often than you think!), creating javascript files dynamically using PHP to allow better flexiblity of your app, parsing, traversing, modifying and extracting data from style sheets, interacting with Flash, Java and APIs of a dozen external services, writing XUL based apps, optimizing data for transfer, porting large parts of business logic to JS to offload your application servers, then finally using the advanced javascript where modifying system methods and objects is not a taboo anymore.
Then you know AJAX.
A few days ago I took apart one of the first barracuda disks (broken) and found, besides the 10 plates (beauty!) and some interesting parts of more or less unknown purpose, two extremely strong magnets for moving the head. The magnets are really strong and the drives can be bought dirt cheap or even for free.
The cost of the service (room occupied by the seat) is somehow proportional to the cost of the ticket. Not directly, and the price is somewhat outrageous, but you are aware that serving everyone the first class standard for the price of economy class in unrealistic. There is some correlation between cost and price. It may feel somewhat unfair, but not as badly. In case of Vista though, the cost to manufacture one CD of Ultimate Edition and one CD of Home Edition is exactly the same. Both programs exist, both are shipped just the same and to make a copy of one costs the same as making a copy of the other. You're getting inferior service with no cost from the maker. Have your coffee for $10 or have your coffee for $5 with the waiter spitting in it.
The tricky thing here is that you can argue logic as much as you want, and it won't matter the least bit. It completely doesn't matter whether the customer is cheated on or not, who is right and who is wrong. What absolutely matters is, does the customer perceive the activity as being cheated on?
Here "The Customer Is Always Right" is the law. If the customer feels like being treated unfairly, the reaction you can expect is exactly like he was actually treated unfairly, objective truth be damned. If the customer complains, and you explain the activity is unfair, the customer will perceive that as further unfairness, using loopholes in the system and further trickery.
This is a kind of catch-22. Even though your pricing scheme fits the market perfectly, the guy who gets the 'economy class' feels treated like 'second class citizen', and the one who gets the business class, feels like being ripped off. Both hate the system and both feel cheated, both feeling like not getting their money's worth. If they both paid the same middle price and got the same middle-class product, given only choice to buy or not to buy, they would be both happier, but then the chance is quite a few of the "economy class" wouldn't afford the higher price, so sales would be lost, and the richer ones would pay less than they are ready to pay, so profits would be lost. So you either differentiate prices and piss people off (losing profits in the long run), or you keep them the same and lose customers and profits now.
It's not uncommon, but it isn't fair (or, taking more objective standpoint: "is perceived unfair by a major percentage of customers") - you're paying 400% the base price to get like 40% extra functionality. Besides, people don't perceive the high-end versions as extended variants of the low-end base system, but the low-end versions as purposedly crippled high-end base.
This still works as profit source in the short run, but it annoys the customer base, undermines loyalty, encourages seeking alternatives. And once alternatives are found, you lose in the long run. You squeeze $50 for Home Premium from an user today, and lose the whole sale and the customer entirely tomorrow.
Except the analysis hardly ever takes into account reasons why people switch to other OS, and even if it does, it comes to entirely wrong conclusions (they are cheaper, they have better marketing) while your own faults - trying to squeeze last penny off the customer - are hardly ever taken into account as the 'real evil'. People hate being cheated and perceive this as cheating. And it doesn't matter you don't and your marketing people will explain to your CEO that it really isn't cheating. For people, it is, and people will hate you for that. And will jump the ship at the first opportunity... or steal from the thieves, not a crime to many.
They are not equivalent but that's not entirely the question.
The question is do they provide satisfactory functionality?
Because actually, 100 sub-$200 PC systems running Win98SE would probably work faster and be cheaper in means of TCO, and quite likely provide all the functionality needed as well (with exception of stability and security).
If I need email, office, file sharing and some, get the work done in acceptable comfort, you ask yourself what you need. You may get Vista and $1000 PCs, you can get XP and $500 PCs, or Linux and $300 PCs and the user experience and efficiency of work will be the same. You can get $150 PCs and Win98 too, but the risk of data loss and intrusion is prohibitory, otherwise it would have the work done as well. This way Linux can compete just fine and seems to be the best choice.
OTOH if you need a development environment of 4GB RAM quad-core 4GHZ CPU computers for all the 100 desktops, the price difference between OSes and their efficiency overhead becomes much lower. Linux doesn't fare just as well here, especially if you need to run WINE to have some essential apps working. If you need a high-end hardware not because it's required to run the OS, but because your application requires it, choice of the OS should be guided by other factors than just price of purchase or TCO. Although not disqualified here (by far), Linux doesn't have the upper hand of "vastly cheaper setup to get the same things done" here.
A little known fact: producing a solar cell consumes more power than the cell is able to produce during its whole lifetime.
This may change sometime in the future. Not anytime soon though. (The cells MAY cost you than grid energy, because they are manufactured in bulk, power bought in bulk. Doesn't mean they provide actual energetical savings)
Translating to human:
If you're really innocent, then no matter how much you lie, use nasty, sneaky tactics, act dirty and play a cunning villain, the ruling should be "not guilty".
Personal mail parcels have been added to forbidden materials list.
...unless you know the type of the device you're trying to crack.
A large part of the key is manufacturer ID and some product metadata of very low enthropy. Cracking the PIN was described as relatively easy, and upon narrowing the search to one type of devices, the time of break-in drops drastically.
AFAIK - no. Man In The Middle would be possible (if difficult) at the moment of pairing. You could also try to hack the keyboard controller itself, or use vulnerablities of the PC with bluetooth plugged in and active (the dongle must be working to allow the keyboard to connect) depending on what besides keyboard the PC allows. I'm also not sure you can't try coupling with the PC acting as its keyboard while the real keyboard is off (then you don't snoop but you have actual access.)
These are all guesses on my side though. I don't know if any actual work was done in this direction. BlueBag was about coupling with other devices, what you can do with this connection was barely hinted.