> In this way, I will be legally able to loosen the license over time if I so wish. Without CLA's for customers, I couldn't do that.
Or you can make it poprietary, which is the exact reason I would not want to sign a CLA with you, because I want a guarantee that my contribution remains foss.
You will not have stolen in the same way that Google/FB don't "steal" your data.
Instead, the end user is simply forced into the position to give away their IP to you, where you can adjust the licensing per your whims, even to sell it back to them.
It's fine to consider your lack of contributors is related to the "no individual" contributors" choice that you have made, but it would be disingenuous to avoid recognition of how your choices probably result more in "no contributors".
It is not a matrix client. I haven't dug too deep into their system, but it looks to me like a centralized server with additional steps (ie. still a single entity owning the server infrastructure)
From what I read in their documentation[1], session's network is built upon an onion routing system where nodes are registered in the OXEN blockchain; you stake 15000 $OXEN to create a node and if you are "well-behaved" you get rewards in that blockchain -- otherwise you lose your stake.
I haven't dug too deep either but it doesn't sound much more centralized than the tor network for example.
Encryption in transit is assumed, and rightfully so. That still means that telegram gets full access to the plaintext and as such is able to give that information to anyone, and do with it as they wish.
I suppose there are some people pit there that think "unencrypted" here means everyone can listen in, but certainly not the hackernews crowd.
This looks cool! I have been using qalculate (https://qalculate.github.io/) recently, which seems similar. Has anyone used both and can tell me how they compare?
SpeedCrunch is less powerful but I find its interface much easier to understand. SpeedCrunch is really nice. It'd be nice if it was a tad more powerful (for example, to plot quick graphs)
Of course, untrusted clients can do all kinds of evil things after having authenticated. (And also clients still need the plaintext password at least client-side no matter what we do)