Rants: Phones, Code and the Lindy
634162
Readers opine on freeing technology, the value of BitTorrent's new family member, and the plight of the not-so-modern man.
47672
(InfoWorld) - What a world. We have to fight off viruses, zombies, bots, phishing, and on and on. Can you believe how many just plain evil people there are in the world? And what is their point? Simple thievery? To prove they are smarter than the rest of us? And think of all the money that's spent on defending, as best we can, against these miscreants or in cleaning up the mess when they get the better of us? Indeed, what a waste. While viruses have appeared on mobile devices, they are, thankfully, few and far between. Part of the reason for this has been a lack of standardization of software environments on handsets, and part is due to the minimal functionality that is typical on these products. It's hard for the socially challenged to overwrite boot sectors, corrupt data, or otherwise run amok on most cell phones today. Apple's decision to limit local software execution on the iPhone is undoubtedly due, at least in part, to a fundamental fear of hackers. While the Macintosh hasn't been much of a target for the hacker community, the iPhone could be a lot more tempting. There will be far more iPhones than Macs in the world in just a few years. Plus, Apple partner AT&T doesn't need the support headaches that come with having a large number of users jamming its 800 numbers with reports of bizarre symptoms on their iPhones. Regardless, being a Web services guy, I absolutely applaud Apple for moving the Web services art forward a notch or two with a very capable platform that might indeed replace PCs for many of us over the next decade or so. We don't need to run a lot of local code to have a meaningful IT experience while on the go. Of course, the iPhone will be hacked over time, requiring updates and fixes, just as is the case with the PC. There are already reports of hackers working diligently to unlock the phone so that non-AT&T SIM cards can be used, and to avoid cellular activation so that the device would be used only Wi-Fi networks -- with VoFi services, of course. Any programmable device runs this kind of risk, and defending against unauthorized code will remain a challenge for some time to come. Which brings me to a really obscure but very important, shall we say, "opportunity" for hackers. Last year, I wrote about one of the most exciting technology developments in wireless, software-defined radio (SDR). Basically, SDR simplifies radio hardware design by replacing specialized circuitry with software. Among the many benefits of SDR are over-the-air bug fixes, the ability to add new features on demand, and dynamic reprogrammability -- turning, for example, a GSM phone into a CDMA phone or even Wi-Fi or Bluetooth or UWB or whatever on the fly. With so much software at play here, the question has to be asked: Could an SDR get hacked? Suppose someone figures out how to build a virus that quickly spreads to SDR-based handsets, disabling them or using them as jammers or worse? What if those handsets are being used for public-safety applications? This is not to say that hacking is the only vector for wireless disruptions. After all, anyone can use a jammer to disable communications in a local area, and any moron with a reasonable shortwave transmitter can pretend to be an air traffic controller. That fact that we still use an unencrypted, unauthenticated communications protocol for such a critical service boggles my mind. The FCC is rightfully concerned about SDR hacking and has issued new regulations for SDRs that mostly attempt to deal with open source software in SDR applications. There is significant concern that open source software creates specific vulnerabilities that hackers could exploit. I don't think this is very likely for two reasons. First, open source isn't the same as open architectures. Each product vendor would of necessity keep certain elements of their implementation secret, locking out all but the most determined hackers. But secondly, and more importantly, the real issue is how to protect individual phones from ever loading harmful software. We already have pretty good techniques for this from the PC world, and there are many effective approaches to solving this particular security concern. It could even be argued that the technical scrutiny that comes with open source actually enhances security and integrity; the real issue is controlling what software, open source or not, gets onto the mobile device. As I noted in my last column, the big issue with SDR isn't hackers or security: It is the need to lower the power demands of SDR implementations so that they have a prayer of running on batteries. The road to SDR-based handsets isn't at all paved yet, but open source is a relatively minor concern.
160257
I've apparently been carrying around pretty dumb cell phones over the years - and I bet many of you have as well. That's what the telecom geniuses would have us believe, anyway. These phones don't organize our lives, don't play music, don't take pictures or videos and don't handle e-mail.
140916
Blog: As an industry we are terrible at working on interoperability.  The open source world should be the one to fix this.
241567
Function, features, features and functions Mobile Clinic Choosing mobile handsets that keep the increasingly pushy and tech savvy user base in the organisation happy â without destroying the hard work put in to keep networks and data secure â is one of the most emotive issues we've had to deal with in this month's Mobile Clinic.â¦
483306
Dan Farber: "It's not hard to imagine a contextual ad showing up every time you Twitter something. Twitter 'I am drinking beer with friends' and a Budweiser ad shows up. Now imagine the Twitter revolt." Oh yes there would be quite a revolt, a powerless one, unless there was an alternate service we could all switch to and then assuming we could get off our asses and actually switch. Yeah, we're good at screaming, but not too great at acting, here. I'm a bit of a Twit, myself, and I'd find it revolt-worthy if they tried to interrupt or punctuate discourse with product placements, but then Twitter's destiny is, imho, to be acquired by a phone company and sold as a feature that gives users a reason to use one brand of phone over another. Not as a way for advertisers to hitch their "messages" on our discourse. We've seen how well that has (not) worked with advertising on email. Not likely to work much better on Twits. Imagine if Nokia offered a cell phone with Twitter built-in, a checkbox for SMS users (default on?) -- "Do you want to send SMS messages to your buddy list?"  Don't you think the kids would go for that? (Maybe they can already do it, it's likely that I'm that cluelss.)
395621
According to Saul Hansell at the NY Times, Apple intends to break phones that have been unlocked.  But Francine Hardaway and Patrick Scoble both updated this afternoon, and bad things happened. Hardaway's phone was "fried," she needed a new phone, and Scoble lost all his data. Hardaway: "Trust me, I didn't hack it." Jeff Clavier: "This effing piece of s..t is bricked." Robert Scoble, Patrick's dad, updated successfully, and got the new features. Spaley's iPhone is "a useless piece of crap." Looks like Josh Bancroft's iPhone was hosed too. I would hold off on the update until we find out what's going wrong.  Sugar Attack: "It wasn't until I saw a friend tweet about the new iPhone firmware upgrade that I realized I could now access the iTunes WiFi store."
567686
It&#39;s easy to be wowed by Japan&#39;s mobile communications infrastructure. &quot;Next-generation&quot; 3G coverage is now so ubiquitous that carriers have already stopped launching 2G phones; an impressive array of attractive handsets offer free digital TV; phones can be used to pay for goods and train rides, thanks to embedded contactless smart cards; and on the mobile information superhighway data whizzes along at 3.6Mbps. But watch out for the off-ramps.While Japan has led the world with many of the services offered to consumers, in some ways the mobile ecosystem here is downright backward as I found out last weekend when I tried to buy a new phone. A broken handset necessitated a new model and this is where my story begins.In Japan, phones are sold by carriers and not the phone makers. Companies like Fujitsu, NEC, Sony Ericsson, and a few foreign vendors including Nokia, Samsung, and LG sell their phones in the thousands to carriers. This gives carriers the ability to pretty much dictate to the phone maker what software needs to be installed.This model is one of the reasons that mobile Internet services like I-mode took off here so quickly. There was no chicken-and-egg situation with phone makers and users waiting for each other to take the plunge. NTT DoCoMo decided I-mode would be in new phones and so it was.But this model has a downside. Phones are so tightly customized to each carrier that it&#39;s not practical to keep the same handset when switching carriers, and if you see a phone you like you can only buy it if it&#39;s offered by your carrier.Back to my story. The new phone was looking quite expensive so I decided to switch carriers and take advantage of a free phone on a competitor network. Japan launched number portability a year ago, so I could make the jump without losing my cell-phone number. I&#39;d still have the hassle of a new e-mail address, but it appeared a small price to pay.Before long I had a new phone in my hands, but my phone numbers remained locked in the old handset. The new carrier didn&#39;t have a cable to hook up to my old phone so they couldn&#39;t transfer the address book and it wasn&#39;t possible to beam it between the phones. While my old carrier was gung-ho on Bluetooth, my new carrier wasn&#39;t so enthusiastic, so the new phone had no support. Similarly, while the new phone offered infrared, the old phone didn&#39;t. Heavy customization strikes again.Back home I fired up my PC and managed to get my address book from the old phone into the computer. Getting it to the new phone via a memory card seemed like an easy task ... but no! The VCard file wasn&#39;t being properly read by the new phone. Carriers, it was explained to me when I called the help line, often used custom fields in their VCards so there were sometimes problems. So much for a common standard.I won&#39;t bore you with the technicalities of how I eventually got my address book into my new phone, but suffice to say this story has a happy ending. I&#39;m now back in cruise control, enjoying all the attractions the mobile superhighway has to offer.The number portability system that enabled me to keep my phone number is coincidentally one-year-old this week. About 3 percent of users in Japan -- roughly 3.7 million people -- have made use of the system during its first year -- far less than the industry predicted, or feared.One thing that&#39;s said to be stopping users from switching is the inability to keep their e-mail addresses. While carriers fussed over the details of keeping numbers, they forgot, or perhaps ignored, the need to carry e-mail addresses between carriers. In other countries this wouldn&#39;t be a big deal because most messaging is done via SMS, which relies on phone numbers, but in Japan the advanced stage of the market has again caused hassle for consumers.
748202
Not since the introduction of the cell phone has the plain old home phone been in for such upheaval. The device long used for landline calling, recording voice mails, and storing phone lists may find itself replaced.
145390
You know itâs been a strange week when youâre mulling over cellular plans for your pet. But I seem to be doing just that. Scottsdale, Ariz.-based PetsMobility Networks is developing a phone that clips to your dogâs collar. Fido can hear his masterâs voice and, I suppose, respond in kind. Iâm not entirely convinced this is a good idea. I can just see Apache running up my cell bills with crank calls (âDo you have Alpo in the can?â).
615792
iPhone users have felt the sting of high roaming charges with their devices, and many of them are complaining to the company or on blogs.
324599
Getting the right mobile services mix With such a range of potential options in terms of devices and functions, one could say we are spoilt for choice. Or is it a Hobson's choice â plenty of options, but none really cut the mustard?â¦
124567
Blog: A reflection on a firey response to my 4th of July posting about the dangers of defaulting one's way through the iPhone activation process.
49126
A lot of things are happening in the Ruby world right now, and I wanted to highlight a few of them here:  At FOSCon this year, Amy Hoy has asked people to start writing more instructive articles about parts of Ruby or Rails so that newbies would have more "fine manuals" to read.  I've tried to do my part with two short series (so far), one on RubyInline and the other on ruby-prof.  The RubyInline articles are: RubyInline, making making things faster easier, and RubyInline: Going a bit Further.  The ruby-prof articles are:  Profile and ruby-prof, ruby-prof and call graphs, and Profile and ruby-prof:  getting specific. Another blog related event is the current blogging contest being run by Ruby Inside.  They're offering $100 US to their favorite informativ, ruby related blog post this week (Aug 14-20).  There have been a lot of interesting entries so far.  It would be pretty cool to see more contests like this crop up. We're getting close to a couple of Ruby conferences, I wrote about RubyConf*MI in my last post.  RailsConfEurope is also comingu up quickly.  If you're reasonable close to either of these, you should consider registering. O'Reilly has released the Ruby Cookbook.  It's a massive tome, chock-full of Ruby goodness.  I haven't had time to read the whole thing yet, but what I've read looks good, and I'm hearing good things from folks I trust.  Looks like another good book to add to your Ruby bookshelf. APress is getting ready to jump into Ruby and Rails in a big way.  They've got ten titles listed on their 'Rails Roadmap', and have lined up some well known Ruby names to write for them.  They're still looking for some Ruby authors according to this blog post. No Starch Press is also starting to make some Ruby related noises.  I can't be specific yet, but there's a good looking Ruby book on its way into their catalog.  If the book is half as good as what they've talked to me about, it's going to be another 'must have'. The Pragmatic Programmers also look like they're set to add some more titles to their Facets of Ruby line.  James Gray has said that he's writing a book for them that should be announced soon, Ezra Zygmuntowicz also has a book on the way, and I've recently signed a contract with them for a Ruby related book.  It looks like the PragProgs aren't going to be content to sit on their Ruby laurels. Finally, Developerdotstar is close to announcing a couple of books about programming.  Neither of these is Ruby specific, but from everything I've heard I think they're going to be solid, language independant books about becoming a better programmer.  Just the kind of thing you'd expect from these guys.
179601
Printing with Lightroom on Leopard...getting Photoshopped for Christmas...cell phones with 5x optical zoom...the optical triangle illusion
498015
By Colin Stewart, The Orange County Register, Calif.  Jun. 19--Editor's note: Second of two columns on new uses of mobile  phones. Last week: an info-on-demand service for cell phones.
481653
I'm back, with a very interesting topic too!  Joel Spolsky, ex-Microsoft Manager and software engineering guru has a new essay, How Microsoft Lost the API War that is creating quite a big storm in the blogging communitiy.  Joel posits that the priests in the holy Temple of Microsoft have lost their way, because it has split into two factions, and the wrong faction is winning. One faction worships on the alter of backward compatibility, while the other is led by fervent priests who are proselytizing to raise up the new gods of .NET and Longhorn. Joel suggests that the new gods will cause the destruction of the holy Temple because Microsoft's great victories were built on the altar of keeping customers happy with backward compatibility. Furthermore the old gods of the Windows API continue to grow more grotesque and cruel with the passing of time, driving former worshipers into the arms of the friendlier gods of World Wide Web.  This story sounds extremely plausible. I must admit that i fit the profile of the developer who used to develop on the Window's API, is familiar with COM and Win32 who now develops mostly using PHP and Python. However I continue to develop and maintain Windows apps that keep our customers happy, and we still plan to develop new Windows apps. Some points:  Temple of the Blind? Firstly, Microsoft is still a compelling place to work for to people who feel that they can make a difference. The Temple continues to attract talented people with a Unix background. For example we have the recent hiring of Ward Cunningham, author of the Wiki.  Microsoft is still able to keep talented people like Raymond Chen, and others like him who continue to look after the Windows API, and Longhorn apparently will still give high priority to backward compatibility. Open sourcerers like Miguel Icaza are sufficiently attracted to the .NET vision to stake their careers on Mono. Longhorn and .NET are compelling technologies, so even if Win32 is not so cute anymore, M'soft is providing something that remains very attractive.  What i do see M'soft doing wrong is that they aren't disseminating the .NET runtime fast enough. It remains an optional install in XP Service Pack 2 for example. Also their IE dev team appears to be hog-tied due to political reasons; nevertheless IE remains good enough, particularly when I can embed IE as an activeX control, something I cannot do with Mozilla (AFAIK) - Update: I'm wrong.  Temple of the Spider?  Secondly, people don't merely use a web browser. They run the web browser in the OS.  So let me ask you, if you are using DreamWeaver or HomeSite or Photoshop or vi or emacs or Gimp, how many of you are willing to give it up for a java applet (or whatever your favorite technology is) running in your web-browser? Precisely.  Temple of the Abandoned?  Third, Joel makes the claim that developers are not developing to the Windows API. Well he could be right. But I bet a lot of them are still calling Win32.  If you are using a framework or IDE like Delphi or wxWindows (or .NET or VB) then you certainly are insulated from the Windows API, but that doesn't mean that you're not calling the Windows API all the time. I don't see Borland dropping their Windows version of Delphi at any point in time.   In fact, the fact that many developers are using some form of framework is a compelling argument for Microsoft to enhance the .NET framework to attract developers who are using other frameworks.  Today, not that many students learn x86 assembler, but that doesn't mean that Intel lost the CPU wars. Just because fewer people are learning Win32 doesn't mean Microsoft has lost the API wars, if the frameworks run predominantly on Win32.  Temple of the Lost  Joel even warns you in the beginning that "because I'm talking about big trends, I need to exaggerate and generalize". But you still get sucked in because Joel Spolsky is a first-class writer, in the same order as Philip Greenspun or Eric Raymond. That makes him so persuasive and plausible. But this is not Indiana Jones and doomed temples, but Steve Jobs and reality distortion fields.  Other opinions:  Harry Fuecks (PHP is ASP's upgrade path),  Dennis Hamilton (M'soft is just covering all bases), Robert McLaws (Joel is wrong in 7 points), Oliver Travers (the web is not good enough), One Run-time to Rule them all....