KEYBOX Experimental Sale

Just a small post to say that I have decided to conduct an experimental sale to test volume pricing with KEYBOX.

Starting today, KEYBOX will be sold at $1.99 USD, down from $4.99!  (A 60% mark down)

I’m not sure how long this sale will last or if it will be a permanent move.  If the new volume pricing resonates with more customers then I’ll consider keeping it low.  Naturally, if there is little change I’ll go back to experimenting with a higher price point.

KEYBOX has been a labor of love for me and I want to see it benefit as many people as it can.  For those who have been on the fence about whether to buy KEYBOX or not… NOW IS YOUR CHANCE!  KEYBOX will never be more affordable than this!

 

Keybox search

Post to Twitter

iPad Trademark Kerfuffle – Is It Worth It?

This week has seen much news about Apple’s trademark dispute with Proview, a Chinese company which purports to own the trademark to the word “IPAD” within China.  Trademarked names, at least within western countries, tend to be regarded as case insensitive and are usually registered in ALL CAPS causing obvious overlap here.

The iPad is indeed a great product name but not as great as the product.  Apple should know when to hold them and when to fold them and it has past experience in these matters.

Airmac Extreme

Remember the Airport trademark dispute?  I-O Data, a Japanese computer parts maker owns the trademark for the word “Airport” in Japan.  This forced Apple to rename their Wi-Fi base station the “AirMac”.  And now it’s all water under the bridge.

The name is decent but the product is great.  I use the AirMac Extreme and whole heartedly recommend it to anybody who wants a trouble-free Wi-Fi base station that doubles as a wireless printer and external hard disk hub.

Going forward, Apple should simply rename the iPad to something else like “iTab” or other within China to appease Proview and go back to selling a great product!

Post to Twitter

Path & Address Book Privacy

Vic Gundotra has today shared via Google+ the below report that the Path iOS app has been found uploading each user’s entire address book to the Path servers without first notifying users or otherwise asking permission.

http://mclov.in/2012/02/08/path-uploads-your-entire-address-book-to-their-servers.html

 

How Path Works

Dave Morin, the CEO of Path was quick to comment on the report and explained this behavior citing the reason below…

“We upload the address book to our servers in order to help the user find and connect to their friends and family on Path quickly and effeciently as well as to notify them when friends and family join Path. Nothing more.”

 

Regardless of reason, this is in clear violation of at least rule 17.2 of Apple’s App Store Review Guidelines and possibly rule 17.1 depending on your definition of “user data”.

Matt Gemmell, directly beneath Dave Morin’s comment, offers a proactive solution to the issue in hashing the data prior to upload (it neatly skirts around Apple’s rules, protects the user’s privacy and still accomplishes the task at hand with zero server-side performance impact).  Hashing transforms the private data into a stream of garbage data that is unique for each data entry.  It allows Path to go on matching contacts without knowing who those contacts are.

 

Going Forward

What concerns me about all of this is that this solution is so trivial (anybody developer who understands one way hashing can do it) that Path should have implemented it right the first time (had they care enough to do so).

I want to give Dave Morin and his company the benefit of the doubt here but it’s a bit hard.  I don’t think the security and privacy of Path’s users is a topic with which they are concerned.  There are simply too many mistakes here to think otherwise.  Everybody who follows my blog knows how I feel about privacy matters and usually I would advocate immediately removing the Path app until the issue is resolved but in this case it will do little good.  The damage, as they say, is done.  The best recourse is perhaps to report this issue to Apple instead.

Many companies violate user privacy, until they get caught, and they need to be taken to task lest this negligent behavior become even more widespread.

 

Path should consider itself lucky that a sole individual discovered this issue just by poking around and not by having every user’s private data their servers house leaked into the wrong hands as a result of having their servers hacked.  It’s still a possibility until they rectify the issue.

 

 

 

 

Post to Twitter

Freedom.txt – Add It To Your Site

Today I added a freedom.txt file to my website.

 

We Came This Close!

The fact that the SOPA bill made it as far as it did in the American political process is a travesty and warrants that Internet users everywhere finally draw a line in the sand.  I make software and without a free and open Internet I most likely could not survive.  I too understand the threat of large-scale piracy but I understand that SOPA is NOT the right way to thwart it and that this is more of a power grab under the guise of championing copyright protection.

 

What Can We Do?

There are many things we all can do (boycotting SOPA supporters being one of them) and perhaps the simplest of those is to install a freedom.txt file on our websites and blogs.

 

What Good Will It Do?

Putting this file on your servers lets web crawlers count us easily.  It’s like a census tallying all the people who believe in Internet freedom.  When news articles involving SOPA or related laws are published, they can cite such statistics which provide concrete numbers rather than just a less tangible “public opinion”.

This is far from over and the same hands are behind similar bills being pushed on other nations to ratify.  This is now a war.  If you believe in an open Internet I invite you to join in and take action today starting by adding freedom.txt to your own websites!

 

Post to Twitter

Google PageRank Flaw

In the autumn of 2008 I interviewed for a front end design and development position at an internet shopping portal company in Tokyo.

It was an excruciating process to say the least.  They first had me accomplish a set of assignments.

These included…

  1. Implementing the Google PageRank algorithm as described in Larry Page and Sergey Brin’s paper The PageRank Citation Ranking: Bringing Order to the Web.
  2. Writing an essay outlining my personal thoughts on PageRank
  3. Writing a web spider that could crawl the internet both depth-first and breadth-first

I spent 3 weeks of my spare time getting it all just right and submitted my work for consideration.  Reasonably impressed with my work, they invited me for what would become a 5 hour long interview.

Towards the end I was told by my interviewers that my PageRank algorithm was nearly perfect but my essay was puzzling. (only at this point did I learn that the employees of this company were what you could call Google Fanboys Extraordinaire)

I was asked to clarify my essay’s point that PageRank is flawed and the discussion went along these lines…

Me: PageRank does not properly model a given page’s authoritativeness.

Interviewer: And, how, could, that, be?

Me: A link, in and of itself, is not a vote for a page’s authoritativeness.

Interviewer: Uh…. of course it is!  You read the PageRank paper we provided you right?  Let’s see, it says here you implemented the algorithm nearly perfectly.  This was your work right?  Explain to me again why you have a problem with PageRank.

Me: A link is merely a reference to another page, nothing more, nothing less.  It doesn’t capture enough information to call it a vote.

Interviewer: <Unconvinced, lets out a small chuckle>

Me: <Getting a bit impatient>  Alright, let me put these questions to you then.

Me: Is a link from Mothers Against Drunk Driving with the intent to draw attention to an offensive site condoning drunk driving a vote for its authoritativeness?  Is a link from a blogger who is against owning firearms to the NRA’s website a vote for its authoritativeness?  Is a link from a religious site against abortions to an abortion clinic a vote for its authoritativeness?

Interviewers: <Exchanging looks with one another, waiting for somebody to cut this awkward silence>

Some of these reasons against links being votes were explained in my essay but I suppose were glanced over.  I apparently destroyed the foundation upon which a few otherwise intelligent people had built their beliefs.  Needless to say I didn’t get the job and that is for the better.  I’m by no means a Google worshiper and most likely would not have fit in.  I only wish I hadn’t wasted 3 weeks to find this out about them.

 

Solving The Flaw

The only positive outcome of this interview process is perhaps this blog post.  If I can hold out PageRank’s flaw to people interested in a case study of how not to model software some good might come of it.

So to summarize: A link can be a vote but is not necessarily one.  The world’s most popular search engine has been improperly modeled around this incorrect view of the problem.

It warrants pointing out that all of this may no longer be true as Google is famous for frequently tweaking their algorithms.  But unless their current algorithm is smart enough to guess the linker’s intent, it still isn’t modeled right.  To do it right (and cheaply) you need to have the linker tell you the intent of the link.

Authoritativeness is subjective and that makes solving this problem difficult but if I were tasked with at least improving upon this problem I might propose a new HTML attribute for the anchor tag which would declare that intent.  Such an attribute would be taken into account by the search engines when judging the link.  It might look like this…

<a href="http://www.jayfuerstenberg.com/blog" link-intent="authoritative" />

The lack of an intent would be taken to mean that the reason is unknown and should not count as a vote for that page’s authoritativeness.  The only problem with this proposal is that web content developers would need a reasonable amount of time to get onboard with it.

But following the whims of search engine algorithms has never been a big issue for people interested in maintaining their pages’ SEO so it’s a rather small problem.

 

 

Post to Twitter

The True Definition Of Success

Success is not a binary, it’s a range.

Success is not an occupation like doctor, lawyer, president or other.

Success is not an amount of money in a bank account nor all the possessions you might have.

Success is not about how many friends you have.

Success is not about impressing other people.

Success is not having never failed at anything.

 

Success is simple. (and it doesn’t come in a new-age 12 easy steps video)

It’s being able to wake up each morning, be honest with yourself, and have the freedom to spend that day in a way that’ll matter to you and make you happy.

 

Today I was a more successful person than I was yesterday.  This is because I did less of the things that aren’t important to me and more of the things that are.

 

If you feel less successful than you should be after reading this that’s okay.  It’s not a failure, it’s an opportunity for more success, that is if you want it to be.

Post to Twitter

How To Prevent Hacking Of Passwords With Random Passwords

ThreatPost is carrying an article highlighting the weakness of common words as passwords.  I won’t duplicate the article here but I just want to discuss some simple points regarding HOW NOT to do it and HOW to do it.

 

Some of the pathetic passwords (as in: please stop doing this, thanks!)

  • 123456
  • 11111111
  • 123123

If you have any of these as your passwords please learn more about passwords and specifically how their security is completely contingent on their remaining a secret.

 

How to secure your passwords against hacking

  1. DON’T USE COMMON WORDS, PERIOD!  Hackers have dictionaries of these and only need to look up your hashed password against their dictionaries to find out your password.  They can do this in a matter of minutes.
  2. DON’T JUST APPEND A ’1′ OR ’123′ OR SOMETHING EQUALLY PREDICTABLE ONTO A COMMON WORD, THINKING IT MAKES IT UNCOMMON.  You’re not a genius, thousands of people before you have used the EXACT same password thinking they too were clever.  You are a hacker’s best source of entertainment.
  3. DON’T REUSE THE SAME PASSWORD ACROSS 2 OR MORE SITES/SERVICES.  If and when your password gets hacked the damage will spread far.  If I hack your Gmail account password I’m going to assume you used this password for your Facebook account, your Flickr account etc…
  4. NEVER, UNDER ANY CIRCUMSTANCES EMAIL YOUR PASSWORDS!  Once emailed, they are no longer secure and potentially belong to everybody.
  5. USE A RANDOM PASSWORD GENERATOR!   Hackers thrive on patterns so stop giving them.  A random password has little to no patterns (depending on the generator).  Don’t just stare at your keyboard and make one up yourself, use an app like (shameless plug) KEYBOX to do it for you and help you remember them.

 

The take-aways from this article

  • You don’t need to be a highly experienced hacker or cryptanalyst to break hashed passwords.  Just use an application like hashcat.
  • Even the advanced hash algorithms in the SHA family can succumb to recovery if common words are used as passwords.  Time to support the BCrypt algorithm.
  • It’s survival of the fittest out there.  Those of you who are aware of the dangers and decide to protect yourselves will fall victim less often.  Those of you who keep using ‘password’ as your password are convincing the rest of us that the equivalent of driver’s licenses for computers are warranted.

 

Security can be easy thing, if you care enough to invest in it and the benefits are immediate and everlasting so get to it if you haven’t already.

Post to Twitter

Wither KEYBOX lite?

Now that KEYBOX 2 is slated for release later this month, I am announcing that KEYBOX lite, the 30-day free trial edition, will be dropped.

The purpose of the lite edition was to demonstrate the full edition’s power, quality and professionalism to those who were on the fence about buying it.  However looking back at the download-to-purchase ratio, I’m not sure the lite edition was ever really necessary, and if anything, may even be hurting sales.

Although the lite edition can only be used for 30 days, it doesn’t auto-destruct and will remain installed until the user removes it.  I suspect the mere presence of the KEYBOX lite icon on people’s iPhone dashboards endows a false sense of security regardless of whether the app is used or not.  By removing the choice between lite and full editions I’m asking would-be-downloaders to decide upfront how serious about security they want to be.

People who really understand the importance of digital privacy and security tend to already be victims and don’t need a demonstration.  They are glad to pay just about any price if it means avoiding the hassle and stress of remembering and resetting all their site accounts and PIN codes before it’s too late.

People who have yet to personally feel these pains fall into two categories: those who know they never want to, and those who don’t give it much thought.  Chances are that those who don’t give their own security much thought will not have arrived at my website in the first place so I’m not overly concerned about them.  I want to reach those who are looking into being more secure and are now comparison shopping between KEYBOX and the alternatives.

 

In the end, security is up to each user and even if you purchase KEYBOX, you may leave it on your iPhone without using it but I would urge you to get value out of it on a daily basis.  It’s an investment in your own security.

Removing KEYBOX lite is something I couldn’t foresee myself doing back when I released it but in retrospect makes perfect sense from a security standpoint as well as for sales.  I hope users will understand.

 

If you have any questions or concerns regarding this decision please feel free to let me know at support@jayfuerstenberg.com.

Post to Twitter

KEYBOX 2 Submitted To Apple

After weeks of testing KEYBOX 2 against iOS 5.0 and the new iPhone 4S as well as fixing some bugs introduced by both I’ve finished testing and finally submitted KEYBOX 2 to Apple.

Barring any approval process snafus I expect to release it Saturday Dec 17th 2011, just in time for the year end holidays!

Release 2 is of course a free upgrade from the first release and users purchasing it now will not have to pay twice.

 

I want to thank all the people who’ve expressed their enthusiasm for the next release for their continued patience.  I hope to make more incremental releases in the future.

Stay tuned for the release 2 and the new revamped website that will accompany it!

Post to Twitter

Serious Security Flaw in iPad 2

Some KEYBOX users ask me why it is needed when iOS devices are protected by passcode screens.

I respond along the lines that the passcode screen only prevents people from using the device and not accessing the data that resides within (by backing up that data to a computer).

Now it seems a serious security flaw has emerged that that allows anybody with a Smart Cover to break into an iPad 2, even when protected with a passcode.

9TO5Mac has an excellent breakdown of how to recreate it here.  This is yet another reason why apps like KEYBOX are beneficial to people who value their privacy.

If you own an iPad 2, make sure to apply the workaround detailed there.

Post to Twitter

Thank You Steve Jobs

Today Steve Jobs passed away and the internet has been abuzz about his contributions and his greatness.

I want to thank him for making me who I am today.  Without him I certainly would not have been able to become a software developer, for there would not be this industry in which I could apply my craft.  He and Steve Wozniak kickstarted it with the Apple I.

Since then, he has touched literally BILLIONS of people in the same way.  Not a bad dent in the universe if you ask me!

 

He is already being held in the same high esteem as Thomas Edison and Henry Ford and it there should be no contesting his deserving to be so.

Steve, you were and continue to be an inspiration to me and many others.  You taught us how to light that fire within each of us and to strive to be our best.

 

Rest in Peace…

Post to Twitter

Site Hacked Today

I regret to notify my readers that www.jayfuerstenberg.com was hacked today.  I apologize to all the users who were unable to reach my site during the period for which it was unavailable.  Currently I am following up the matter with my hosting company InMotion Hosting, who have been overall great hosts.

 

What this means for visitors, users of KEYBOX

As I do not collect user information either via my site or via the KEYBOX app there was absolutely none for the hacker(s) to discover.  This site is literally a set of static web pages and a blog.  All the content within is open to the public and there is nothing to be learned by hacking into it.

There was no damage except the inconvenience to visitors.  The content of this site is managed on my local machine using Coda and MarsEdit and I can reconstruct the site at whim.

I’m happy to say that KEYBOX was instrumental in both protecting me from further damage and in quickly getting me back up on my feet.  Because I never use the same password twice the hackers were only able to get so far (FTP access apparently).  The other aspects of my site remained completely intact.  Nevertheless, with KEYBOX’s help, I generated new strong random passwords for every part of my site that uses them.

 

Going Forward

Nothing serious was lost except an hour of my time fixing things and writing this blog post.  Well, that and my professionalism.

I want everybody to know that I am serious about security and guard my passwords with KEYBOX (I’m not only the developer, I’m perhaps its biggest user) and it is as safe as can be.  I suspect the hacker gained entry to my site via a weakness in-between myself and the hosting company (across the wire).  KEYBOX was what kept a bad situation from becoming worse and I’m thankful for that.

I hope you’ll continue to enjoy visiting my site and I hope to hear from more of you.

 

Sincerely,

Jason Fuerstenberg

 

UPDATE:  It appears a large number of sites hosted by InMotion Hosting were subject to a defacement attack.  They have issued a statement to this effect.

Post to Twitter

Direct the Patent Office to Cease Issuing Software Patents

The US White House is hosting an open petition to let American citizens voice their opinions on software patents.  As I’m not American I cannot directly participate but I can spread the word.

For those not versed on software patents, I’ve voiced my opinions regarding them in a previous post.

The abolishment of software patents will trigger innovation in America and throughout the world, creating jobs everywhere and driving healthy competition as a result.  Everybody but lawyers stand to benefit.

Don’t wait, sign the petition today and make it clear you’ve had it with software patents!

Post to Twitter

AU To Carry The iPhone 5 In Japan!

According to this Yahoo Headlines Japan article, KDDI has revealed on September 22nd that it has officially signed on to carry the next-generation iPhone under its AU carrier brand.  AU will sell the iPhone 5 (tentative name) in October.

The old one-carrier-per-country model previously favored by Apple is being abandoned in its bid to better compete with Android which is supported by all 3 major Japanese carriers.

It is expected that this move will have a deep impact on current smartphone shares for iOS and Android.

Also, it is curious that NTT DoCoMo was not the next carrier to offer the iPhone as its network is much better prepared for it.  Prior to the arrival of smartphones, AU was better known for its less-is-more strategy and its limited 3G network rollout as a reflection of this.  It’s clear that KDDI has cemented its reversal of this strategy with this announcement.

Interesting times ahead!

Post to Twitter

Portable Media Security

David Harley has written a thoughtful post at ESET ThreatBlog on the insecurity of portable media like CDs and USB thumb drives.

Portable media, by virtue of its portability, is obviously more prone to loss and theft than say, stationary desktop computers.  For this reason it is crucial that encryption be used to protect any data stored by these devices.

With the advent of the iPhone equipped with encryption apps, we would hopefully see less incidents of private data leakage.  Ultimately it is up to people to be aware of the options and risks, and to make the proper choices.

Post to Twitter

Choosing a Safe Password

A lot of opinions about what makes a password strong have been thrown about lately.  Unfortunately, a lot of them are wrong.

If you only take away one thing from this article let it be this…  Don’t believe everything you read about password best practices.  Today I’m going to dispel some of these myths and I want to tackle 2 approaches in particular that concern me.

 

Correct Horse Battery Staple – http://xkcd.com/936/

This comic has been linked to a lot since its release and at least gets points for trying.  The only problem with it however is that it relies on common dictionary words.  According to Oxford Dictionary there are 171,476 words in current use in the English language.  If we were to assign a unique number to each of these 171,476 words and use a 4-word combination of them we’d end up with a truly staggering amount of combinations to exhaust!  Problem solved right?

No.  The average English speaking person can’t even spell “hippopotamus” correctly and is limited to a vocabulary of 25,000~50,000 words (this number varies depending on demographics, education level etc… and is still disputed).  And of these, most people limit themselves further to words dealing with their daily lives: “coffee”, “office”, “stapler”, “fire” and other equally common words.  That is if they are not completely lazy and go with “password123″.

What we end up with is maybe 500 highly common words that would form the pool from which to construct such pass phrases.  500 words in 4-word combinations is just under 62.5 trillion combinations.  Sounds great right?  ”My little brother will have to pass the work onto his grandson before my password will be discovered!” I hear you say.  Except with a technique called brute force searching, 62.5 trillion combinations can be computed in significantly less time.  In fact, the more patterns a hacker can discern from your word choice the smaller the search space and the process will speed up accordingly.

Furthermore this approach does not scale.  There are only so many nonsensical word combinations a person can remember.  After a while they begin to diverge and soon you can’t tell if it was “house ball sky dog”, “ball cucumber torch pin”, or “house pin sky torch”.

 

Memorable Passwords – http://lifehacker.com/184773/geek-to-live–choose-and-remember-great-passwords

First let me say that I have a tremendous amount of respect for Gina Trapani.  But this time I’m afraid she is wrong.  Why?  Again, patterns.

What makes the password memorization technique she advocates easy for you to use makes it equally insecure for hackers who anticipate that you’ll follow her advice.  Using public knowledge like a spouse’s name or your anniversary date is questionable at best.  If I know you, chances are I know your spouse.  Even if I don’t know you I can dig through your trash and find out.

The only way this excels compared to the XKCD approach is that it’s easier to associate a password to a web site because there is an underlying pattern uniting them, not that this is a good thing remember.  It’s just harder to get confused.

 

What Makes A Password Safe?

The short answer: randomness.

The long answer:

  • Don’t use patterns.
  • Use nonsensical words or sensical ones, whatever you like.  Don’t follow a rule.
  • When possible, don’t limit yourself to how you choose your passwords.
  • Use numbers, punctuation, spaces and even Kanji characters if you feel like, or don’t.
  • Go short or go long.  The choice is up to you.

Remember, from whom are you trying to keep your password safe?  Your nosy siblings and coworkers?  Or somebody more nefarious like a hacker?  Your password is only as safe as it is unknown to people who would attempt to discover it.  Understanding the discussed tools and knowledge they possess should demonstrate why just about all the advice flying out there is flat out wrong.

 

 

But It’s Still Too Hard To Remember “e$-UqPs3″

That IS hard to remember, there’s no contesting that.  But again, what makes it hard for you to remember makes it more secure.  A hacker is still going to pull out the brute force search here and will perhaps arrive at your password.  However this password is stronger if for no other reason than it has no discernible patterns.

Moreover, if you occasionally change your password it becomes a moving target.  By the time the hacker finds your password, you’ve already moved on to a new one!

How should you remember this password?  Don’t.  There’s an iPhone app for that! All you need to do with this app is create one memorable login password behind which all your hard-to-remember passwords are protected.  This memorable login password is encrypted with an algorithm called BCrypt which is extremely resilient against brute force attacks because it takes an inordinate amount of time to encrypt each password.  So even if you lose your iPhone the likelihood of your login password being discovered is near zero.

 

There is no magical solution that will result in memorable and safe passwords.  But we can up the ante against hackers by equipping ourselves with the tools and discipline to combat theirs.

Post to Twitter

KEYBOX 2 – Code Complete!

Just an update for everybody eagerly awaiting the newest release of KEYBOX…

I’ve officially finished work on Release 2 and will be heavily testing it while waiting for Apple’s supposed iPhone hardware refresh to be announced on October 4th.  Barring any issues I’ll release KEYBOX 1 week after I get my hands on an iPhone 5, and well after the iPhone commotion dies down.

 

I want to thank everybody for your continued patience!

Jason Fuerstenberg

Post to Twitter

MUFG, The Unprofessional Bank

Disclaimer: This post is a rant, but also an advisory for ex-pats residing in Japan against using the Bank of Tokyo – Mitsubishi UFJ, or MUFG for short.

 

As my readers know well, I’m not the biggest fan of Japanese banks and as of today even less so.

Since July I have been selling KEYBOX for iPhone and decided to use MUFG as my bank for receiving my 70% earnings from Apple.  I already had an MUFG account as their branch and ATM locations are convenient for me.

Opening the additional bank account to keep the money separate was a battle in its own right.  You see, MUFG frowns upon account holders having more than a single savings account.  Why, I couldn’t tell you. Another mystery of Japanese banking perhaps.  I had to explain to them my purposes with the account and really twist the branch manager’s arm to get permission.

And now that I have the account and KEYBOX is selling I have been eagerly awaiting my first deposit from Apple, a measly 890 yen for the first week of sales, but still – my first cheque!

Only it was not meant to be.  MUFG rejected the payment.

Rejected payment mail from Apple

As you can see they neglected to mention why.

I finally had time to go to the bank today and get my answer.  I prepared EVERYTHING.  Whenever you visit a Japanese bank they will refuse service if you’re lacking your inkan (ancient ID stamp), and bankbook.  I brought all that and everything else that could identify me so that turning me away wouldn’t be an option for them.  Lastly, I printed the above e-mail Apple gave me as well as the Bank Information page in iTunes Connect to show them I registered the account correctly.

When I asked why the payment was rejected I was completely floored by their answer, or should I say lack of one.

They don’t know why it was rejected.  Seriously.

If you know anything about business in Japan you know that companies here have an almost unhealthy fetish for documenting everything, EVERYTHING.  The idea is that if a mistake is made we can backtrack in the documents to find the reason and improve upon the processes to prevent it in the future.  Well MUFG didn’t document squat.

MUFG then told me the paying bank has to be contacted to learn the reason the accepting bank refused the payment.  Yes, you’re reading this right.  I hope, I really really hope it’s just MUFG that is capable of being this fucking retarded. It’s like I stomp on your foot and you ask me why I did it, only to have me tell you that only you could possibly know.

I tried to make the teller see reason that MUFG made the decision and therefore should have a documented reason to justify that decision.  Being the robot that she was, she just kept repeating this “you gotta contact the paying bank” nonsense to me.  Then I got tired of it all and asked to talk to her manager.

This goes on and on and in the end there was no resolution.  MUFG says it will try and contact the paying bank on my behalf and get back to me but I’m not sure there is much of a point and I’ll likely close the account.

Before leaving, the teller then updated my bankbook and lo-and-behold the 2nd payment from Apple was accepted.  So it seems there was certainly no mistake on my part and that it is MUFG that can’t decide whether payments from Apple are worth accepting or rejecting.

I’ve learned my lesson the hard way that we can’t expect much from Japanese banks.

Tomorrow, on the recommendation of friends with experiences in these matters, I’m going to open a bank account at Shinsei Bank.  They are a smaller Japanese bank but have a more international mindset and level of service.  The rest of the Japanese banking industry is quite literally stuck in the Edo-era (17th~19th century) and it’s too frustrating for us 21st century foreigners to deal with.

If you’ve just moved to Japan or are planning to do so in the future AVOID THE BIG BANKS (MUFG, Mizuho, etc…) and go with international banks or Shinsei Bank instead.  They work the same way banks do abroad so there won’t be as much friction for you.

 

UPDATE:  It seems MUFG is not only a bad place to take your banking business, it’s also a bad place to be employed according to this GlassDoor post.

Post to Twitter

Scarlett, I Heard about your Nude Pics and I Want to Help

Dear Scarlett Johansson,

 

I’m sorry to hear about your private pics getting leaked out onto the internet.  As it turns out I created an app called KEYBOX that could’ve prevented this unfortunate happening.  These screenshots show what I mean…

Unfortunately, most people seek my app out only after becoming victims like yourself.

 

In a previous blog article entitled “How to Keep Photos Private on iPhone – A Step by Step Guide” I demonstrate how KEYBOX can be used to encrypt images so that even if your iPhone is stolen your private photos won’t be easily recovered and subsequently won’t be leaked out on the internet.

 

If your new phone ends up being an iPhone, contact me and I’ll gladly help you get KEYBOX up and running.

 

Best of Luck!

Jason Fuerstenberg

Post to Twitter

The Great East Japan Earthquake – 6 Months Later

Today marks the 6 month anniversary of the Great East Japan Earthquake.

Much of the Tohoku region of Japan still lays in waste as a result of the tsunami that ensued after the megaquake and it will be decades before it is restored.

With that in mind I would ask that you please find it in your hearts to donate money to the Japan Red Cross.

http://www.jrc.or.jp/english/relief/l4/Vcms4_00002070.html

 

Lastly, I would ask that you please pass the word on to family and friends to bring more awareness to this cause.

 

Sincerely,

Jason Fuerstenberg

Post to Twitter

KEYBOX Release 2

I’ve been hard at work on the development of KEYBOX Release 2 and I’m happy to report that it is nearing completion.

My plan is to make it available after I’ve confirmed compatibility on the next version(s) of the iPhone with iOS 5.0.

Aside from many improvements, Release 2 includes an important fix for a compatibility issue regarding importing secrets via Safari 5.1 in Mac OSX Lion. Safari 5.1 caught me off-guard because I released KEYBOX just prior to obtaining lion.

As much as I want to get this fix into everybody’s hands as soon as I possible I am not willing to do so at the expense of getting caught off-guard again by such OS changes. I could risk breaking the working order of KEYBOX for everybody.

Having said all this, I appreciate everybody’s patience and Release 2, like all upgrades, will be free of charge, and a worthwhile one you’ll all love.

Post to Twitter

MAC Address as UDID Replacement

I have been testing the solution proposed by StackExchange user ‘shipmaster’ for obtaining a MAC address as a device ID.

I’m a private person, as everybody knows, so I won’t be posting the MAC addresses of my various iOS devices but I will say that I was able to confirm the the MAC address’ suitability as a UDID replacement.

 

How I conducted my testing

Across two iPhone 3GS units and one iPod touch 4th gen unit with two apps (KEYBOX and KEYBOX lite) I was able to reliably retrieve the per-device MAC addresses across distinct apps regardless of whether using Wi-Fi, 3G (only tested on iPhone 3GS as iPod touch doesn’t do 3G) and in Airplane Mode.

I do not own an iPad or iPad 2 with which to test but I suspect MAC addresses will make for reliable UDID substitutes there also.

It would be great to hear from iPad owners who have tried this technique.  Please contact me at jay@jayfuerstenberg.com.

Post to Twitter

PHP Crypto Bug Found

An embarrassing day for PHP as threatpost is reporting that PHP 5.3.7 includes a rather serious cryptography bug

In some cases, when the crypt() function is called using MD5 salts, the function will return only the salt value instead of the salted hash value.

As anyone worth their salt knows (sorry, couldn’t resist), salts are meant to nullify the advantage of rainbow tables which drastically shorten the period required to successfully carry out a brute force attack.  Salts are left unencrypted as they are used again for hashing login passwords and the like.  As such there is no hashed password here but instead just a known salt used as not only one password but everybody’s password.

Very scary!  PHP team, next time unit test!

 

 

 

Post to Twitter

Troubleshooting Failed Imports in KEYBOX

Some KEYBOX lite users who are upgrading to the full edition of KEYBOX are reporting issues where the below error alert is shown.

Failed upload

 

 

 

 

 

 

 

 

 

 

I apologize for any troubles you may be experiencing and offer a few workarounds for this:

  • Remove other apps from memory by double clicking the home button and making the bottom list empty.  This is especially important for people with large secrets files (1MB or larger).
  • If you’re using Mac OS X 10.7 Lion try using Firefox. Safari 5.1 (included in Lion) seems to be more susceptible to this condition.

I believe I have identified and solved the culprit and will be making the fix available in KEYBOX release 2 after thorough testing. Your patience is much appreciated.

If you have any questions or concerns please contact me at support@jayfuerstenberg.com.

Post to Twitter

Early Earthquake Warning in iOS 5

Nobody in Eastern Honshu (Japan’s main island), myself included, will ever forget the March 11th M9.2 Mega Quake.

An earthquake of this scale produces aftershocks the likes of M6~7 and during the first month we witnessed aftershocks at least M5 every hour.  It tested everyone’s nerves to say the least.

Shortly after the megaquake many iPhone owners proceeded to download a free app ゆれくるコール (Roughly translated: It’s about to shake call).  For a few months this app worked extremely well.  The sound it emitted was similar to the early warning we hear on TV.

But in recent months this app’s reliability has degraded.  So it’s welcome news (as reported by 9to5mac.com) that Apple will be embedding early earthquake detection service directly into iOS itself!

This is a facility DoCoMo subscribers have had forever, even in feature phones and it’s a joke among Japanese and expats here that we hope to be near a DoCoMo user whenever the big one hits!  Now we’ll have to extend that to iPhone users on SoftBank as well!

Post to Twitter

Overcoming UDID Deprecation by Using GUIDs

As posted yesterday, the UDID is being deprecated from from iOS 5 and will possibly be phased out in iOS 6.

This is mostly a good thing.  Since the UDID does not change between the apps we use nor the sites we visit a very specific bread-crumb trail of our movements can be determined.  It’s akin to leaving your business card at every restaurant and shop you patron.  If all those cards were entered into a shared database the type of person you are and what your likely interests are can easily be guessed.

However, some of us developers simply want a means to distinguish the users who use our apps.  The UDID was the silver bullet and its deprecation presents challenges for us.

A GUID is one partial solution to this.  GUID stands for Globally Unique IDentifier.

 

The properties of a GUID

  • Each is only issued once
  • Not linked to the device generating it
  • Does not have 1:1 relationship to a user

Unlike a UDID which is tied to the device, a GUID is not necessarily tied to anything.  It’s just a unique ID.

A user could have many GUIDs so it’s impossible to say that GUID A and GUID B are 2 distinct people as the same person could own both.  However for most purposes a system which separates content by GUID can reliably keep my documents separate from yours on the cloud.

 

GUID Generation In Objective C

Generating GUIDs is trivial.  KEYBOX generates GUIDs to uniquely identify each secret across exports and imports.  Here is the relevant snippet of the GUID generation implementation used by KEYBOX.

+ (NSString *) generateGuid {

CFUUIDRef uuid = CFUUIDCreate(NULL);

CFStringRef uuidStr = CFUUIDCreateString(NULL, uuid);

CFRelease(uuid);

[(NSString *) uuidStr autorelease];

return (NSString *) uuidStr;

}

It won’t help determine the exact device or its user nor will it help track users across sites or apps but it will help to assign identifiers like Twitter User Numbers to users who want to sign up to a cloud-based service.

In the end it may prove the most balanced ID system for users and developers.

Post to Twitter

UDID is Deprecated in iOS 5

TechCrunch’s Erick Schonfeld is reporting today that iOS 5 comes with a big surprise in that developer access to the UDID, the device’s unique ID number, is being deprecated.

 

What does this mean?

As early as i0S 6 perhaps, we developers will no longer be able to uniquely identify devices.  These are good and bad outcomes of this.  Developing user profiles based on the apps downloaded and ads clicked begins to get a bit creepy and this will now be thwarted.  But some of us developers use the UDID in ways that are not evil per se.

 

What about KEYBOX?  Is it impacted by this change?

Somewhat, yes.

KEYBOX lite uses the device’s UDID to detect when a user is importing an export secret file onto the same device that generated it when the secret file is obviously older than the install date.  In other words, cheaters who thought they could back up their secrets, uninstall KEYBOX lite and reinstall it and get another free 30 days of use.

KEYBOX lite then issues a stronger recommendation to purchase the full edition.  After all, anybody who loves KEYBOX enough to go through the hassle of reinstalling it over and over ought to just purchase it and support further development.

At no time was this UDID ever transmitted in any form to my site or any other by KEYBOX or KEYBOX lite.  In any case I will phase out this check in KEYBOX release 2.  I don’t like relying upon deprecated functionality in my apps.

Post to Twitter

Researchers Find Weakness In AES

Summary:  KEYBOX is unaffected by recent research findings against the AES-128 encryption algorithm.

 

It was reported a couple of days ago (17th of August 2011) that researchers found the first weakness in the AES-128 algorithm.  This weakness is said to reduce the amount of time required to brute-force attack an encrypted secret by a factor of 4. This means that a secret could be hacked in 1/4 the time it would normally take had this approach not been discovered.

 

As any visitor to my website is well aware AES-256 is the cryptography algorithm used in KEYBOX.  I would like to take this time to spell out what all this means for all KEYBOX users.

 

How this impacts KEYBOX?

It doesn’t.  At all.

 

The research is applicable only to AES-128, a much weaker variant of the AES-256 algorithm.  The article explains that AES-128 becomes AES-126 as a result of this exploit.  That is to say that the effort required to encrypt secrets is 4 times less but still so high as to be impractical.

 

The key quote which spells out how much effort is now required to discover a secret’s contents via brute-force:

To put this into perspective: on a trillion machines, that each could test a billion keys per second, it would take more than two billion years to recover an AES-128 key.

AES-128 is still regarded as a strong algorithm, even after this discovery.  Furthermore, KEYBOX uses the much stronger AES-256.  The number of computation rounds used here is considerably higher than that of AES-128 and it’s strength is equally higher.  You and I will be long passed away before our secrets could be broken into.

 

Conclusion:

The sky is not falling.  There is no change needed in how KEYBOX should operate as such attack vectors were well considered during its design and development.

 

If you have any questions or concerns please contact me at jay@jayfuerstenberg.com.

 

 

 

Post to Twitter

Apologies for Outage Today

Today around 8pm Japan Standard Time the server hosting the www.jayfuerstenberg.com domain was unavailable for an unknown period of time.

I apologize to visitors who were denied access and am working with my hosting company to identify the nature and period of the outage.

I’ll report any findings here as they become known to me.

 

Sincerely,

Jason Fuerstenberg

Post to Twitter

Back to School Sale for Articles by Sophiestication!

I love to support indie developers and Sophia Teutschler is the talent behind Articles, the refined Wikipedia client for iPhone.

She has just announced a Back to School Sale making Articles for the iPhone now only $0.99!  The iPad edition is similarly marked down to $1.99!

It’s a great deal for a great app so run to the AppStore and grab your copy today!

Post to Twitter

How to Keep Photos Private on iPhone – A Step by Step Guide

We all have private photos we want to keep away from prying eyes.

KEYBOX not only keeps your photos private by requiring a login, it encrypts your photos using AES-256, the encryption algorithm used throughout the eCommerce industry. So if your iPhone is stolen the chances of the criminal ever gaining access to your photos is almost zero.

How to add a photo in KEYBOX

Photos can be added to any KEYBOX secret but let’s assume you want to create a photo collection.

 

Login to KEYBOX using your login password.

If the login succeeds you will be taken to the TOP screen.

 

 

 

 

 

 

 

 

From the TOP screen tap the All Secrets icon.

This will take you to the All Secrets screen shown here. Tap the + button in the top-right corner.

You’ll now be taken to the Add screen.

 

 

 

 

 

 

Usually the basic type of new secrets is “Custom”.

You want “Photo” so tap the basic type cell.

This will take you to the Basic Type selection screen.

 

 

 

 

 

 

From here select “Photos” (at the very bottom of the list).

Doing so brings you back to the Add screen.

 

 

 

 

 

 

 

Now 3 “Photo / Image” fields have been added. Tap the top one.

This will take you to the photo screen.

 

 

 

 

 

 

 

In the bottom left corner is an action button. Tap it.

 

 

 

 

 

 

 

 

A menu will appear.

If you want to select the photo from your camera roll select “Choose from camera roll”. Remember to delete the photo from the camera roll later if you use KEYBOX to safeguard it! If you just want to take a photo now select “Take a photo”.

 

 

 

 

 

Once you’ve chosen the image you want to safeguard tap the Done button in the top-right corner.

 

 

 

 

 

 

 

The photo has been given a unique ID which is now visible from the Add screen. Next, and at a minimum give the secret a name and tap the Save button.

 

 

 

 

 

 

 

You’ve now added a private photo to KEYBOX! It really is this easy!

Post to Twitter

Eye Candy: Levitating Girl Natsumi Hayashi

I don’t often visit Reddit but when I do I look for gems like this…

http://www.geekologie.com/2011/08/eye-candy-levitating-girl-natsumi-hayash.php Natsumi Hayashi, managing to vacuum the floor without tracking dirt with her feet.

Natsumi photographed here is incredibly talented.  She not only photographs these images herself but also maintains her normal facial composure and somehow manages to not let her hair or skirt flutter in the slightest!

It’s hard to believe she doesn’t use a high-speed shutter for these and actually jumps upwards of a 100 times to get just the right shot.  I hope her knees hold out.

Post to Twitter

KEYBOX In-Depth Feature at AppAdvice!

The fine folks at AppAdvice have an in-depth feature of KEYBOX and have posted lots of screenshots for all to see!

Clinton Ferreira, the reviewer, does a great job describing how to use KEYBOX and how flexible it is.  Although he attests to not knowing just how secure KEYBOX’s algorithms are (a certain level of paranoia is very healthy!), he and all of KEYBOX’s users can rest assured that under the hood the best of the best of encryption algorithms is at work.

I’d like to take this chance to remind everybody that KEYBOX’s greatest strength is its lack of vendor lock-in.  You can put as many secrets in KEYBOX as you’d like and if you decide to move to another security product you can always export your secrets as a text file.  This text file is completely readable to humans like you and me and you don’t even need another application to view it.

THEY’RE YOUR SECRETS and you have every right to manage them any way you decide to.

 

Thanks again Clinton and the AppAdvice team for spreading the word about KEYBOX!

Post to Twitter

Software Patents – The Growing Epidemic

Preamble

I write this article out of concern for the future of my craft and it’s practitioners. Like many, I’ve been developing software since childhood (My 8th birthday present was a TRS-80).  As ludicrous as it sounds, we software developers live in a world where extortion is not only allowed but is actively encouraged and codified into law by many governments.  I’m of course speaking of patent systems.

 

Where I Stand

I’m not against patents per se. However, being a software developer qualifies me to understand where they succeed, where they fail and WHY.  This article captures my thoughts on the topic and I’d love to hear the opinions of others. (mail me: jay@jayfuerstenberg.com)

 

Where Patents Work

The patent system, in a nutshell, aims to reward inventors and innovators with limited-time exclusive rights to implement a product. The logic being that, without this incentive, companies and entrepreneurs might never invest resources to drive innovation forward. Nations then might become less competitive and end up buying more of their products from abroad. This would lead to job losses and whatnot so patents are the silver bullet to prevent this from happening.  Great!

My favorite example of where patents go right is the story of a Japanese company, HARD LOCK Industry Co., Ltd. Through trial and error this company spent years researching how to make a screw that never loosens. Yes, you heard me correctly, a screw that NEVER loosens! HARD LOCK holds 50 registered patents regarding the various technologies involved in keeping a screw in place.

Their screws are employed in a variety of areas such as heavy machinery where high vibrations would cause any other screw to eventually nudge loose and fall out. If you’re lifting a steel beam with a crane when a screw loosens and something goes wrong millions of dollars of damage and even the loss of human life may result.

If you can grasp how beneficial HARD LOCK’s contribution to humanity is proceed to clap your hands now. The patent system did, and awarded HARD LOCK the limited-time exclusive rights to the technology. HARD LOCK’s competitors cannot simply walk in, reverse-engineer their hard work and sell the same thing at a reduced price (reduced because less R&D goes into reverse-engineering). And this is as it should be.

 

Where Patents Fail

Wait, wasn’t this article supposed to address the evil of software patents? Yes, and to get to that we need to first consider why the software world is nothing like the real world you and I inhabit.

What most people fail to understand (or perhaps don’t care to) is this: Unlike the real world that we are still learning to master, the software world was made by… WE HUMANS.

We designed and created the CPUs, the RAM memory, the hard drives and all the other hardware components that go into a computer, and for one purpose…. so we could have a framework within which to host the software world.

Software is another creation of us cool humans. If you’ve ever watched The Matrix what I’m about to explain will be old hat to you. The reason it’s called SOFTware is that it can be changed at will. In fact, software is infinitely malleable and can model any concept that its developer conceives. The reason software should therefore never be patentable is because there is little to no challenge in creating it. Let me demonstrate this for you…

Here is my software screw (in the Java programming language) that never loosens.

public class Screw {

	/** Screw tightness from 0.0 (fallen out) to 1.0 (tight and snug) */
	private float tightness;

	public void ensureTightness() {
		if (isLoose()) {
			// I'm loose so tighten me!
			tighten();
		}
	}

	private boolean isLoose() {
		return tightness < 1.0f;
	}

	private void tighten() {
		tightness += 0.1f;
		if (tightness > 1.0f) {
			// Whoa, too tight!
			tightness = 1.0f;
		}
	}
}

It didn’t take me years of blood, sweat and tears to make this as it did for HARD LOCK. It took less than 2 minutes for me to write and review its correctness. While I’ve developed in Java for 14 years, even a developer with as few as 2 months Java experience could accomplish the same implementation in the same time frame.

 

 

The point I’m making here is simple, this isn’t the real world. There are no physics to conquer, no biology or chemistry to balance, no gravity to obey.

I and my fellow software developers are masters over the software worlds we create and we make the rules by which they abide. As a consequence, there is very little, if any, R&D needed to create software.

This is patently evident in the software development democratization explosion we have been and are continuing to witness in the smartphone industry. Even before smartphones and the Internet, the software world NEVER needed patents as incentives to innovate. The barrier to entry was already low enough. And now with the Internet, it is only getting lower as computers become ever more affordable and the skills/knowledge more transferable. Time and time again, the only thing software patents have proven themselves to accomplish is the stifling of innovation.

 

Enter the Patent Trolls

Until recently we software developers did not give much thought into defending ourselves from patent trolls. Only recently have patent trolls stepped up their offensive tactics.

What is a patent troll? The term is seen everywhere these days and I imagine most readers who made it this far know the answer. But for those who’d like an introduction, patent trolls are entities who lurk in the dark, waiting for somebody like myself to independently implement something. That something somehow bears resemblance to a diagram or a process they wrote on a paper and submitted to their government. When I stumble into a troll’s hiding grounds, it’ll pounce on me, claiming to own the exclusive rights to implement the idea it says I infringed upon. So am I in the wrong?

What makes patent trolls different from companies like HARD LOCK, is that patent trolls don’t bother implementing the ideas they think they own.

Imagine if HARD LOCK never made screws at all, but still patented the ever tight screw. If another screw manufacturer decided to contribute ever tight screws to society HARD LOCK could not only stop them from selling them but litigate the competitor right out of business. And believe it or not, currently this is entirely legal in many nations. The reason we don’t see patent trolls asserting themselves as much in the real world as we do in the software one is because, again, overcoming physics is a hard thing to do and HARD LOCK’s competitors might never figure it out. If it were easy the HARD LOCK screw would’ve been invented ages ago.

It warrants repeating at this point that software is infinitely malleable. Software developers all have great ideas for products and while they may be innovative, none of them is truly unique. Usually we are just recombining design patterns to solve well known problems that have existed for decades and where the solutions are openly documented for all to see and use.

Development is a creative endeavor and we don’t reference the patent office’s full collection whenever we carry out our craft. So it stands to reason that we are unknowingly infringing upon software patents on a daily basis.

If you were watching the earth from orbit and could visualize each instance of a software patent being infringed upon as an exploding building you would not like what you see. Most if not all the ideas that can be modeled in software have people claiming to be their owners. Do you believe an idea can become property?

 

I Don’t Develop Software. Why Should I Care?

Not everybody makes software but almost everybody uses it. Sometimes it’s the big software maker that gets punished, sometimes it’s the little guy. But in every case the consumer loses. The results for consumers are less selection, and less innovation. The more competition there is, the harder each party fights for your hard-earned money. So if you like low low prices (and who doesn’t?) on top of a healthier economy with more jobs you really should care.

 

Solutions

Many software developers bemoan the state of their respective nations’ patent systems (with America’s USPTO getting its fair share of the love). Some solutions range from abolishing software patents altogether to limiting the amount of money patent trolls can be awarded so as to remove the incentives for trolling in the first place.

While I’m in favor of total abolishment of software patents, I want to introduce a real-world example of a fairly balanced approach.

The Japanese patent system, with it’s stipulation that all inventions (software or not) must somehow overcome an obstacle posed by nature/science, is an interesting approach to patenting from which others could learn. It respects the difference I highlighted earlier between the challenges posed by the real world and the lack of such challenges within the software world. I won’t pretend to be a lawyer and I’m still learning about Japan’s approach but it warrants a read by those interested in patent law.

Another solution, albeit not favorable, might be time itself. China right now is amassing a huge patent portfolio and in time it may be impossible for other nations to make anything without paying licensing fees to Chinese companies. This might force nations like the USA to declare patents as the stiflers to innovation we already know them to be. I’m not advocating doing nothing and just waiting until this happens but it’s one scenario that is currently unfolding and should be on everybody’s radars.

I feel like we are on the cusp of something major here. The internet, for better or for worse, is changing the way we live and work and there are a lot of vestiges of pre-internet life we know we need to cast aside. But a thing like the patent system that was built on the efforts of thousands and which has stood the test of time is not going to roll over willingly. It’s up to people like us to raise voices and take action.

Things we can do right now to protect ourselves from patent trolls and to create change:

Consider what could happen if patent trolls win? Once all the ideas in the software world are taken they could move to other industries:

  • What would the housing industry look like if “shapes engraved on blueprints” could be patentable? Would we all be living in tents?
  • What would the music industry do if “a song rhyming the words ‘girl’ and ‘world’ accompanied by a mellow track” were patentable? No more love songs?
  • What would the fashion industry do if its current environment of open copying went away. Would we all be wearing zippered uniforms if “a combination of convex and concave metal joiners called buttons” were patentable?
I know which future I want to live in.  Do you?

 

Post to Twitter

Plain Text Offenders

In noticing this article today via Hacker News I started to wonder if I should start a “Security Hall of Shame” listing companies that don’t take our security/privacy seriously so people could avoid doing business with them.  Then I discovered that such a site already exists in Plain Text Offenders.  As always I’m the last to know about such great sites.  In case I’m wrong and you haven’t been there you owe it to yourself to check it out and stay safe.

Post to Twitter

KEYBOX on Your Favorite Device

As a result of prMac’s promotion of KEYBOX, the August 6-7 weekend was the best sales weekend to date since it was released a few weeks ago.

Thanks to all of you who purchased KEYBOX! And a special thank you to those who took a moment to rate KEYBOX in the AppStore for your fellow users!

This weekend showed an equal increase in e-mails from customers and prospective customers. The road to releasing KEYBOX to the public has been a long one and it’s great to be able to talk with you and hear all your feedback. One of the recurring themes from these e-mails has been when KEYBOX will be on the iPad/Mac/Android/Windows Phone? Although I like to keep things under wrap (so as not to disappoint anybody) I think it’s time to discuss KEYBOX’s future on different platforms.

Let’s start with the easy ones:

Windows Phone

Unless the market share for this platform grows I won’t be able to recoup my investment. As of today, it’s rapidly losing market share, not gaining it.

Android phones and tablets

Never say never but yeah, probably never. Among its many problems Android is too fragmented a platform (different display resolutions, memory and CPU specs, etc…). The original KEYBOX appeared on Vodafone Japan’s (now SoftBank’s) J2ME platform and was a victim of fragmentation issues. I am not keen on going back to that.

iPad

The iPad could be perhaps in some respects an even better device for using KEYBOX than the iPhone. I’m seriously considering supporting it. Currently KEYBOX works on an iPad in iPhone compatibility mode and if/when an optimized for iPad version is made it’ll be a universal app so that current iPad KEYBOX users won’t need to pay twice. If/When iPad is supported I intend to raise the price to reflect the benefits afforded by the platform.

Mac OS X

KEYBOX on the Mac would perfect the trifecta (phone, tablet, desktop/laptop) in that it could make backups/syncing all the easier. This would obviously be a separate download from the iOS version and the price would be inline with the features/benefit afforded by the Mac platform.

For now…

For the time being taking KEYBOX on iPhone further is the highest priority. Release 1 was about locking down the security and giving it in a simple and clean UI. There are so many great features that didn’t make the first cut and it was difficult to to draw the line but I had to ship KEYBOX at some point. There is a lot in store and I’m thrilled so many of you have joined along for the ride! I value your contributions, and continued feedback and your praise has been a source of inspiration for me!

So thank you! ありがとうございました! Merci! Gracias!

Post to Twitter

Why Digital Privacy and Security are Important for Development

The Guardian is running an article about why digital privacy and security are important for developing nations.

Even developed nations are affected as illustrated by The Tokyo Two who formerly exposed what many already knew about the Japanese Whaling Programme.

 

The take-away from this story: If you use technology, back it up with encryption.  Enough said.

Post to Twitter

The Other Gender – Designing Software for the 21st Century

Half way into KEYBOX‘s development I read this article about somebody who was irritated at always having to declare him/herself as a man or woman. Why would that be an issue?

This person could not identify with being a man, or with being a woman.

I won’t pretend to be able to relate to this. But what I can relate to is being different and being constantly treated as an outsider because of that difference. As a foreigner in japan most websites don’t accept my full name since it’s so long. Japanese names are usually 4-6 kanji characters in length (like 山田太郎).

Japanese website designers rarely if ever consider foreigners whose names aren’t comprised of kanji and it irriates me to no end. Back when I lived in Canada I always developed apps that allowed 50 characters for the first name (well over the likely length) and another 50 for the last name.

So although I cannot relate to being anything other than being a man I can sympathize with being punished for not fitting in.

The Other Gender

Adding “Other” to the list of genders in KEYBOX is a trivial task for me to say the least and it makes me part of the solution, not a perpetuator of the problem. On top of that, users don’t even have to fill in the gender for contacts they add if they prefer not to.

 

I invite more software and website developers to follow suit and enter the 21st century.

 

And maybe one day Japanese websites will hear the plight of us oddball foreigners. Hopefully they can begin to realize that Japan, while still 99% populated by Japanese, has a few of us foreigners who have cash in our wallets and are willing to fork it over if we can fill in our names.

Post to Twitter