even if I can indulge in speculating on the methods used
The only thing though is that you spend a whole lot of time/verbosity describing in detail all the good points about the product, and then just mention it’s anti-FOSS nature at the very end of your long comment.
Usually someone very pro-FOSS will mention that negative up front.
Or seek to implement those features in a free & open way; but the features have to necessitate the effort & if the features are not clarified then no effort, especially a distributed one can even begin to replicate them. What do you suppose ought to be done first when building an app - the feature request or the code?
In any case, I wrote this right at the top of the post before getting to the good stuff, so you could have stopped there if you wanted to:
“We will release the design and/or reference code to the public when the initial version is stabilized.”
as I see it, the problem in your statement is that while you mention you’re pro-FOSS, you got overexcited by the claims of an unknown entity over technologies that you like and at the same time you have no source. Just promises. They could even be a startup that has just put all the buzzwords there while in fact on their code they don’t do anything of that and they just use a centralized server with symetric encryption and have the symmetric key stored in the code. The app will look like it works till proven that it is not. As long as they don’t want to publish their code, you getting overexcited (at least for me), is pointless.
There was an example with a startup that was doing something similar to that, not in that magnitude with a stored key, but something equally bullshit until they were exposed. Quite early in their journey. Cannot remember the name right now but there was a good analysis by a researcher. If I remember it, I will add it.
The only thing though is that you spend a whole lot of time/verbosity describing in detail all the good points about the product, and then just mention it’s anti-FOSS nature at the very end of your long comment.
Usually someone very pro-FOSS will mention that negative up front.
Or seek to implement those features in a free & open way; but the features have to necessitate the effort & if the features are not clarified then no effort, especially a distributed one can even begin to replicate them. What do you suppose ought to be done first when building an app - the feature request or the code?
In any case, I wrote this right at the top of the post before getting to the good stuff, so you could have stopped there if you wanted to:
as I see it, the problem in your statement is that while you mention you’re pro-FOSS, you got overexcited by the claims of an unknown entity over technologies that you like and at the same time you have no source. Just promises. They could even be a startup that has just put all the buzzwords there while in fact on their code they don’t do anything of that and they just use a centralized server with symetric encryption and have the symmetric key stored in the code. The app will look like it works till proven that it is not. As long as they don’t want to publish their code, you getting overexcited (at least for me), is pointless.
There was an example with a startup that was doing something similar to that, not in that magnitude with a stored key, but something equally bullshit until they were exposed. Quite early in their journey. Cannot remember the name right now but there was a good analysis by a researcher. If I remember it, I will add it.
If you take a 5-second look into any of the accounts promoting that software, you will realize it’s a scam. I wouldn’t recommend defending it.