Epic, The Privacy Browser

Post by mahyarm » Fri, Sep 06, 2013, 5:32 PM UTC

metastart wrote: post #12

M4v3R wrote: post #8

This is a nice initiative, but I would like to see the source code of this browser. Without it, I cannot be 100% sure that what Epic devs say is true and it's not an elaborate NSA trick to get our data :). No hard feelings, just in the light of current events as reported by NY Times/Guardian about NSA backdooring popular apps and crypto implementations the paranoid inside me has gotten more active lately.

Source Code coming soon. We've made changes to many chromium files & we're a small team, so haven't had a chance to open source it all in a manageable way. In the meantime, don't hesitate to write us if you want to see any code or know any changes we've made. Or use Wireshark to see requests going in/out! Our philosophy is exactly that -- we don't want you to "trust" us, it should be private by design -- that's how E…

Post by Sir_Cmpwn » Fri, Sep 06, 2013, 5:57 PM UTC

metastart wrote: post #38

hngiszmo wrote: post #28

WTF??? Guys, wake up! If it is not open source, it does not protect your privacy. Period. We see how other companies got coerced into breaking privacy for some dollars. The company-driven closed source development is flawed as long as we grant governments this power. What we need is not yet another startup that tries to make money on our private data (yeah, read Epic's FAQ how they make money). We need a stack of har…

Epic is open source...anyone who wants our source code, just write us!! Sorry we've been struggling to get the product ready and hadn't prepared to release all the code yet but will do it fast. Chromium is a huge code base & we're a small team so we hadn't gotten to it yet. We don't make any money from anyone's private data or any data (period). We make revenues at this point exclusively from searches you do via our…

Post by metastart » Fri, Sep 06, 2013, 6:00 PM UTC

mahyarm wrote: post #62

metastart wrote: post #12

Earlier quoted context omitted.

Source Code coming soon. We've made changes to many chromium files & we're a small team, so haven't had a chance to open source it all in a manageable way. In the meantime, don't hesitate to write us if you want to see any code or know any changes we've made. Or use Wireshark to see requests going in/out! Our philosophy is exactly that -- we don't want you to "trust" us, it should be private by design -- that's how E…

You guys are using something like git right? You have a tag for the build you created right? Why not just release a read only github account or tarball of the source released with epic to give people audit peace of mind now. Add a bunch of disclaimers saying 'we are not ready yet, please only use this to audit for now, we'll have a proper open sourcing setup soon'.

Post by tptacek » Fri, Sep 06, 2013, 6:02 PM UTC

psycr wrote: post #45

hoers wrote: post #40

Earlier quoted context omitted.

Chrom(ium), the open source foundation of chrome

But... that's what these guys are building on top of, in which case I'm not sure I understand the sarcasm?

Post by metastart » Fri, Sep 06, 2013, 6:06 PM UTC

qbproger wrote: post #55

metastart wrote: post #30

Earlier quoted context omitted.

Privacy isn't "free", you're right. Epic supports password saving -- since it's the user's choice, we determined that we could leave it in. Many things can be done in a private way, so for example we have implemented local address bar auto-fill, so you can type "f" and have facebook.com appear but it's not based on your history nor any query to a web server. We will be building in more such services to make using Epi…

Can't spell check be a completely local feature without hitting any outside servers? I didn't understand why that was disabled.