Chase here, I'm an attorney and the CEO. If you don't like our boilerplate language, you can clone the code and run it yourself.
It's FOSS, P2P and E2EE. We can't control, see or manipulate data shared via the Impervious Browser. We claim zero ownership or interest in your data. Anything to the contrary is contrived.
Happy to have someone tweak the terms to clarify, but this is literally nothing. Love you all.
Thanks for the clarification.
"Boilerplate" or not, could you expand on why you added the clauses into the license that provide your company with the right to monetize content provided by users?
To me, and I suspect many others, it's the antithesis of what I understood you were trying to do with impervious, and as the licensing verbiage stands, appears to align with the type of behaviour we've seen and experienced from large listed tech companies that monetize their users.. which is what we're all totally OVER.
If it's just a case of throwing in boilerplate (time and cost) with light review, then it's an easy fix to revise right?
100 fucking percent. Why the fuck would anyone in the bitcoin space support Impervious now? Fucking insane... I was really looking forward to Impervious and was having fun playing with it last night. But you own everything I type? What the shit guys?!?!!
+1000 thanks for coming here and clarifying.
So we can just build it ourselves without the T&Cs? That's really great and a nice incentive for people to do exactly that (or maybe we'll end up with a situation like VS Codium with a "T&C free" build).
FYI I did try to build it and fell into some issues, probably really stupid ones but just so you're aware: #83510
If I could adjust my title now, I would :-)
Even if the code is harmless now, the language used in the T&C is concerning since it essentially gives you free reign to introduce invasive mandatory telemetry at any point in the future.
Sure, the code is free, anyone can fork it but I find it hard to believe someone else will maintain a fork of a fork of a web browser.
Also, the p2p functionality can be restricted in "forked" builds that do not comply with new mandated telemetry by making protocol changes that impede interop.