It's so easy to go to docs and click on search button and make any question on https://docs.spark.money/start/overview
The search works like an IA. I'm sure all doubts can be easily answered there.
I have the same question. From a technical perspective, I can’t quite understand how Spark describes itself as nodeless and self-custodial. I hope someone can clarify this for me.
https://github.com/CodyTseng/jumble/pull/638#issuecomment-3477436664
It's so easy to go to docs and click on search button and make any question on https://docs.spark.money/start/overview
The search works like an IA. I'm sure all doubts can be easily answered there.
I’ve already spent quite a bit of time understanding Spark, and I don’t think I’m obligated to continue doing so.
If you’d like to convince me, please correct my misunderstandings from a technical perspective.
I think your are biased when the subject is Spark, so I think there's nothing I can do more to try to convince you. You have easy docs, search mode on docs in IA mode, you have videos that is not promotional videos. You have everything.
You think that the trust model is the same as a custodial solution, something that is very easy to understand that is not.
I understand that you have no interest in integrate it, and it's ok. Maybe someday if you have a really genuine interest to look on Spark with not a biased vision, you can change your opinion.
I believe I have a better understanding of how Spark works than you do. Over the past couple of days, I’ve thoroughly gone through the Spark and Breez API documentation, as well as reviewed the PR for integrating Spark. Only after this did I raise my concerns about Spark and why it is not a good fit for Jumble. If you think there’s an issue with my understanding, please point it out directly rather than making meaningless remarks.
Of course if you try to understand it, you will have better understand than me (you are more intelligent than me and you are a developer). This is the reason why I don't understand you came to the wrong conclusion about Spark.
It's not a question of being smarter or more knowledgeable, but rather that those of us who don't understand the more technical aspects shouldn't assume that others are wrong.
If Cody says he's studied it thoroughly and has doubts about Spark, it's likely that he's right, and he's not the only one who has doubts.
Even though I use Spark every day, I always remain cautious and simply suggest trying it out, then everyone can make their own choice.
I don’t care who’s smarter, nor am I certain that my understanding is correct. Spark’s documentation doesn’t reveal much about the technical details, so I can only arrive at a conclusion that makes sense to me based on the information I’ve read. Perhaps I’m wrong, and I welcome anyone to point out my mistakes.
However, if the assumption is that I’m simply biased or haven’t made the effort to understand, then there’s nothing more for me to say. After all, I’m under no obligation to investigate this, and I’ve already done more than I needed to.
I read documents, I saw many interviews.
My conclusions 1- :
Or Spark is spending a lot of money to create a protocol with the same tradeoffs of a custodial solution, something that doesn't make any sense in my mind. Or they are lying, what doesn't make any sense too.
My conclusions 2. People who are capable to understand don't really want to understand how things works. The reason: I have no idea.
The things people in my opinion are right concerned about Spark: Privacy.