Closed bkrem closed 1 year ago
@tfalencar We hear you. We want this out as much as you.
Can you please clarify what the GDPR issues are that prevent you from using our cloud version? I'd like to investigate this.
Can you please clarify what the GDPR issues are that prevent you from using our cloud version? I'd like to investigate this.
For every external service we add to a web app, there is need to get a lawyer to understand said service's privacy policy, see what is data collected and what not, then adapt the privacy policy to include that, as well as investigate all external fetches the third party is loading and do the same there, and constantly keep monitoring external service's behaviour / privacy policy to remain compliant. This implies a very big cost, that not everyone can afford, specially for smaller proof-of-concept projects.
Not to mention it delays testing proof of concepts because suddenly it becomes expensive and cumbersome to just put something online... But since this is an "open protocol", there should be a cheaper and easier way! That is, by just having a server and a domain (which many more can afford), we should be able to host the service ourselves, not collect any user data, and not have to spend precious resources and time on this at all! Right? or, it turns out these assumptions were wrong.. ?
Now that I answered your question, would you mind answering mine? In case you need a small copy & paste for your team, I rephrase it below:
" Can the community expect a simple, supported, 'centralised' relay service software (like we had before), to be available fairly soon, that people can use self-host the relay/bridge - just to connect the wallet from the mobile to the front-end (with no other bells and whistles) ? If this is not in the roadmap or priority, that is totally fine: just be clear about it so we can set our expectations straight please. Thank you! "
Hey @tfalencar thanks for the context. I appreciate it!
For your question, that is our aim. We hope to have something available, but I can't give a date right now. It is on the roadmap, but it won't be shipped in the next couple of months.
@chadyj @finessevanes I'm still in the dark here: why not develop the "new version" in the open, so that others can contribute? how far are we from promised version ? 3 months? 1 year? I really need to know this to decide how to go forward with my project. For context, I don't have the resources to make my project compliant with GDPR when it comes to walletconnect, so I need to host the server on my own.