mjpizz

7 ms·

31.
by mjpizz 16y ago
absolutely, fork it and contribute :) http://github.com/mjpizz/reclaimprivacy
32.
by mjpizz 16y ago
yea, I understand the concern, that is partially why I linked the source to my own github account (adds some accountability) and left everything uncompressed and commented. Unfortunately, it isn't possible to put the entire source into the
33.
by mjpizz 16y ago
done. I left the compressed version deployed for now, but the source code is now 100% uncompressed and commented: http://github.com/mjpizz/reclaimprivacy/blob/master/javascri... thanks for the feedback, esp about the PARTNER_APPS constan
34.
by mjpizz 16y ago
thanks! The scanner definitely does not collect your data, privacy policy pasted below for clarification ------ Our privacy policy is not long: * we never see your Facebook data * we never share your personal information Simple. The scanner
35.
by mjpizz 16y ago
I doubt you're the only one - thats why I made the source code completely open: http://github.com/mjpizz/reclaimprivacy/blob/master/javascri... The only compressed stuff is jQuery javascript, all other Javascript is uncompressed and comme
36.
by mjpizz 16y ago
right now I'm not sure what the numbers will be - AppEngine's estimate is currently fluctuating a lot because of the big traffic draw. Haven't decided about other things that might make money in the future (maybe a Diaspora node?), but I fu
37.
by mjpizz 16y ago
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
38.
by mjpizz 16y ago
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.
39.
by mjpizz 16y ago
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 bac
40.
Facebook Privacy Scanner is launched(reclaimprivacy.org)
321 points by mjpizz 16y ago|59 comments
41.
by mjpizz 16y ago
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.
42.
by mjpizz 16y ago
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.
43.
by mjpizz 16y ago
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 s
44.
Rally HN: help build an independent Privacy Scanner for Facebook
120 points by mjpizz 16y ago|28 comments
45.
by mjpizz 16y ago
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
46.
by mjpizz 16y ago
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?
47.
by mjpizz 16y ago
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 ch
48.
by mjpizz 17y ago
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.