mjpizz

I completely agree with you about photo privacy, and I was hoping to keep it soft-launched while I added photo and wall-post privacy checks (my free time is limited). Lifehacker and RWW wrote about it this morning though, so not much of a choice.

Facebook is constantly changing this stuff though, so I'm hoping that the Facebook page and Twitter announcements will keep people up-to-date and re-running new privacy checks.

Source code is open, think you might have free time to help add some of those checks in tonight?

http://github.com/mjpizz/reclaimprivacy

great suggestion. Maybe a screenshot on mouseover? I'm trying to watch bandwidth at the moment though.

Originally I made the scanner walk through each step and show what was happening, but it was too flaky.

also, a lesson: enable capacity billing on your AppEngine account ahead of time, you never know when you're going to wake up in the morning and find out somebody launched your project :)

luckily AppEngine made it really easy to spring back, so it should be fine now (hopefully donations cover costs)

I considered SSL. However, Facebook already serves all of their own pages over plain HTTP, so serving the bookmarklet on HTTPS won't add any security AFAIK.

thanks! The checks aren't too sensitive, but the one-click fixes can be flaky. FF3 periodically has issues, haven't had time to delve into it yet. I'm hoping some other Javascript pros take a look at the code.

yea, I'm considering changing some of the "one click" fixes and just directing the users to the relevant privacy settings. The main goal is to be able to give this to my less-technical friends and family, so they can fix up their privacy settings without getting confused by all the deep navigation.

we haven't felt any limit to the Gmail inbox approach - even moving beyond breakeven - and chat actually tends to reduce our overall support traffic by making our conversations quick, and avoiding drawn-out support threads.

In general, I'd say support bandwidth is dedicated more to a "moving window" of how many new customers you have, rather than total customer base. Most customers tend to be pretty low-touch after the first month, where they get most of their questions answered.

(btw, just posted a more detailed reply to your comment on the article itself)

yea, I figured it probably doesn't work out for all. Though, most "inbox CRM" people I've talked to have scaled well past 200 customers (including us). What is the biggest pain that a specialized CRM solves for you?

I see what you mean, but...there are a few things that make it different than a phone number. For one, you can just set an away status (when busy), which you can't do with a phone. And customers never get your IM screen name, they just chat from a chatbox on the page itself :)

Also, sorry if it came off as a rant - I actually agree with thafman that extra tools can help large organizations with big customers. For us, we deal with many SMBs and other small organizations, so email is more than adequate for communicating with those customers.

ditto. Adding Mixpanel tracking was incredibly quick in both Javascript and Ruby, and setting up basic funnel stats is far simpler than with Google Analytics. They've also been really responsive to suggestions.