Free-form brainstorm. What’s stopping you? Comment below.
I could be more creative if…
Learn. Teach. Grow.
This is the second part of a two-part review of Abine’s privacy solution. See the previous post, Abine to Protect Privacy for the first part of the review.
Rob Shavell from Abine and I discussed some questions about Abine’s application, the company itself, and the future.
J: In June this year Abine purchased TACO. How did that come about, what was the process like, and was this something that Abine had always considered pursuing?
R: It’s really not about economics: Abine wants to support privacy-enhancing technologies. We’ve always been open to working with other privacy add-ons that do the right things for users. Any add-on or Web service that truly respects users privacy is someone we want to talk to, no matter what. On the other hand, we don’t want to partner with add-ons owned by advertising companies, or developers looking to collect data, for example. If any add-on developers who love privacy read this, please get in touch with us – my email is rob at getabine.com
J: TACO v3 has already received some updates. How does Abine anticipate TACO evolving in the future?
R: TACO is evolving fast and is getting more development time and resources. TACO users have told us over 300 changes they’d like, and we’re busy at work with these. We also support the older TACO 2 versions, BEEF TACO, etc. Of course, we are 100% convinced that TACO 2. alone doesn’t provide an adequate level of online privacy and users should consider combining a few add-ons together or try TACO 3 with Abine to get better privacy online.
J: What are somethings you’ve all learned along the way since starting Abine?
R: Bringing together privacy features into one place is complex. The users and developers giving us critical feedback are our best teachers. We also learned that we must commit to native Firefox development even though we have an IE version as well. Performance is too important – the community let us hear that one pretty loudly.
J: Who is Abine’s target demographic?
R: We want to target the non-technical web user. Anybody who uses the web for anything at all or that has a bundle of important accounts they want to protect and keep private.
J: How do you plan to instill trust in your users?
R: We aren’t asking users to trust us. We’re asking them to trust themselves. By this we mean something very important. We have no access to our users data. This is super important. First, our users “own their data” – of course. But we also do NOT store or see our users private data. This is a key reason why many of our users today store all their passwords in our Privacy Suite and do all their browsing using Abine: they don’t have to make any complicated decisions about who they can trust: it’s simply, factually, technically, more private.
Other key points on trust:
J: With regards to instilling trust, I’d agree that you’re not directly asking users to trust Abine. Given the stated target demographic (non-technical users) their basis for trusting the application may be different from say, a security researcher or coder that might review code and sniff traffic. As a result, they may make an evaluation of trustworthiness based on your website, usability, or how Abine communicates with them. There’s the notion that trust is a function of competence plus likability. An example I see of this is people trusting Google based on their performance, actions, and statements rather than their code, or people trusting Mint.com based on good design and the fact that it does what they want it to. For less savvy users, what do you see as challenges in establishing and maintaining a good reputation in order to grow the business?
R: Great points. Regular users of course can’t do technical reviews of applications. They’ll need to trust the technical reviews and press. This is why we make our code available to reviewers who ask for it even though we haven’t open-sourced it yet. It’s really important for people – no matter how technical they are – to have a basis to trust a company with their personal information. A somewhat more unfortunate way users learn about how Abine does what it says is when they lose their Abine Master Password: since we really don’t know it, they have to re-install!
J: You history mentions working on previous startups and security projects. What were some of those efforts?
R: Andrew was at @stake as well as the create of linux-based public access terminals in the Boston are in the mid-to-late 90s. Eugene was the founder of Datapower and the Linux Hardware Database. Rob helped companies comply with data privacy laws and worked on products for consumer identity protection at Identity Force.
J: The Abine website mentions companies “helping people” that were basically slick marketing outfits out to get cash. What are some examples, and what should people look out for?
R: We think consumers should beware of many “identity protection and monitoring services”, “million dollar guarantees” and “free 10 day trials”. As always, when the marketers come visiting, these kinds of terms pop up. In reality, while these subscription services can help you track down problems once and a while after they happen, they do not address the root causes of privacy. If you’re using these kinds of things, come try Abine. It’s free, and free forever (not just for 10 days).
J: What is the relationship between opyaq.com and Abine?
R: Opayq.com is simply the first of several domains we offer for our users to have safe disposable email addresses (similar to say, www.Mailinator.com.)
J: After purchasing TACO, Abine received some mixed feedback from users regarding the upgrade to version 3.
R: Check out the page and the copy on it, it’s as clear as our team could possibly make it:
J: Why is Abine better than other established solutions used for privacy such as LastPass, Tor, RoboForm, or Google Voice?
R: Now Jason, we love your insightful reviews, but we have to take issue with this question! LastPass stores your passwords online (see your trust question) and Google Voice is the opposite of a privacy product, right? Tor does one thing (and well) and is probably a future partner of ours. The time has come for a company to integrate privacy features and make them available to everyday users, with fantastic customer support.
J: Where does the name Abine come from?
R: For privacy… A Bit Is Not Enough
J: What is your revenue model?
R: We are going to make our money selling additional products and services that directly protect and enhance users privacy, for example fast proxy servers, disposable phone numbers, etc. Whatever value-added services people want around privacy will offer as a business. If it costs us money to provide than we will charge, if it doesn’t than we can offer for free.
J: Are there any plans for a version of Abine for Safari, Chrome, or mobile devices?
R: Yes. We’ll be making announcements here in the next few months, for sure. We have a looong waiting list of users that want this on their browser and platform of choice.
J: Does the eventual shift to HTML5 have any impact on Abine or its functionality?
R: We see HTML5 as having only a minor impact on our vision and technology roadmap at this point, though some of the demos out there are pretty impressive.
J: What do you see as upcoming challenges for Abine?
R: Because of recent press and users concerns, we expect a lot of competition. We just want to stay close to the community that cares about their online privacy and to take our direction from them instead of worrying about others.
J: What do you see as some upcoming milestones for Abine in the next 6-12 months?
R: Abine’s got to earn the respect of the privacy and technical community by building a great set of solutions. We’re totally focused on product: performance, simplification, better smoother features, in short, online privacy that works.
Follow Jason on Twitter @jason_owens
Facebook recently implemented a new feature, called Places, that allows you to post your physical location, much the same way that other applications like Foursquare, Gowalla, and others do. The Facebook feature also allows others to check you in at location, enabling people to post where you are and where they saw you.
This feature is enabled by default. If you turn off this feature for yourself, it can still be possible for other people to post your location on your behalf. Granted, there’s nothing preventing someone from posting a status update saying they saw you somewhere, but if you want to disable the ability to be tracked with Facebook’s new location services, read on.
From what I can tell there are three different setting that need to be disabled. Go to Account > Privacy Settings > Customize and make the following changes:
Under “Things I Share”
Under “Things others share”
Facebook also has a Places FAQ page that provides more information on this new feature.
UPDATE: After reading “How to Disable Facebook Places” tonight on Lifehacker I found I missed a fourth item. You have to also prevent your friend’s applications from collecting your location. This is not in the same Privacy settings screen, it’s under Account > Privacy Settings > Applications and Websites (in the lower left.)
A coworker sent a note about a recent AppleInsider article that discuses new federal rules regarding people jailbreaking their iPhones. The article quotes the Associated Press, stating that the government approved several new exemptions. I’ve never really had a need to jailbreak an iPhone, but I have found Apple’s app approval process and control over how owners use their own phones frustrating, regardless of intent. Note that this doesn’t change anything about what Apple can or can’t do during software upgrades, releases, or support.
According to the AP article by Joelle Tessler, the government exemption rules include the following:
I wonder if this will have ramifications in other parts of the technology, movie, or music industries, such as the recent Kaleidescape and RealDVD lawsuits.