I didn't want to be break this story over here but since no one else seems to be posting about it here I am sharing a screenshot from the other side with @scan's post.

[liaizon@social.wake.st]

RE: https://mastodon.social/@poohlaga/116218374295960280

the Executive Director of @OpenSourceCollective replied:

[betree@framapiaf.org]

@opsocket @liaizon copy-pasting the reply I've made on the Github issue:

We (opencollective.com) are agnostic to the KYC provider that fiscal hosts use. Our integration was built primarily as a manual KYC tool, and you can use any backend you want - or even run your own program.

[betree@framapiaf.org]

@opsocket @liaizon

We're indeed adding a persona integration on the platform to help Open Source Collective manage their KYC program. It is not something we're forcing on anyone, just a bridge we're creating for fiscal hosts relying on this service.

For the rest, I'll let Open Source Collective comment.

They're aware of this thread and are preparing a reply as we speak.

[liaizon@social.wake.st]

RE: https://framapiaf.org/@Betree/116218444650414138

the developer who is currently adding this Persona integration into @opencollective has replied to this thread here:

[opsocket@mamot.fr]

@Betree @liaizon I just read it, thanks for trying to shed some light here

[nextgraph@fosstodon.org]

@liaizon @OpenSourceCollective another I never liked about open collective is that they store all their data on AWS in the US, unencrypted. that means all the fiscal data, invoices, payment details, of all their users, including all collectives using their online platform. as open collective is difficult to self host, everybody uses their website. when i asked for more details, they said they are a US based organisation, that they won't care, and that GDPR does not apply to them. i stop using it

[malte@anticapitalist.party]

@liaizon @opencollective i don't understand any of this. is this one second away from them implementing a persona *killswitch*, and debating what "persona" actually *means*?

[poohlaga@mastodon.social]

@liaizon Yes, I have a draft response on how we intend to use the platform connection, but I'd like the engineers to review it for accuracy, as the feature is still in development.
I will say it was fundamental for us that any personal data entered in Persona remain in Persona and any user information on the platform remain on the platform. We are not passing any user data from the platform to Persona. And if a user elects not to do our KYC with Persona, then we do our best to find another way.

[liaizon@social.wake.st]

@malte which part don't you get? why they are shooting them selves in the foot?

[malte@anticapitalist.party]

@liaizon what this "bridge" is, and who the hosts are that potentially need a kyc-persona. i'm lost when people start using abbreviations, and i'm doubly lost when they shroud those abbreviations in vague abstractions.

[poohlaga@mastodon.social]

@liaizon Regarding edge cases, the most common are when we are unable to verify the payee's identity or when they are in a jurisdiction flagged by US sanctions. Roughly .005% of expenses each month are flagged. Additionally, for each flagged expense, we communicate what is blocking us from moving the payment forward and offer alternatives so we can resolve the issue in a way the payee also feels comfortable with.

[wcbdata@vis.social]

@poohlaga @liaizon @scan As a USian, I'd strongly recommend you get the org off any Thiel-connected platform and tools that share data with law enforcement without a valid judicial warrant.

[liaizon@social.wake.st]

@poohlaga the statement "We are not passing any user data from the platform to Persona" makes no sense in this context. You are integrating Persona's API into the platform. You are paying money to Persona to process the personal data of people on Open Collective. Why are you even considering using Persona at all? Using them is antithetical to every point that Open Source Collective lists in your "Values"

[liaizon@social.wake.st]

hey @Wtebbens have you seen this thread? seeing as you just set up a fiscal host on Open Collective and have been talking about the need to move away from Big Tech I would think chiming in, in this situation would be useful

[jdp23@neuromatch.social]

@liaizon yikes! thanks for getting the word out about this!

[liaizon@social.wake.st]

@jdp23 your welcome, I wish I didn't have to be in the position to be posting about this at all. But open collective is super important as a funding source and the one that so much of the fediverse relies on. I think we really need to convince them to change course on this.

[ohir@social.vivaldi.net]

@liaizon @scan
> you can see directly how much @OpenSourceCollective is paying to use Persona

I am more interested in the reverse flow. As I just can not imagine someone within the FLOSS environment did not due dilligence about "third party contribution". The first page of nojs DDG search is full of "persona" warnings so it flashes.

[li@tech.lgbt]

@poohlaga @liaizon hello yes just dont comply with sanctions thanks

[poohlaga@mastodon.social]

@liaizon Not antithetical at all. If someone chooses to not do the KYC with Persona, we respect their privacy and will offer other solutions. And no, we are not passing any user data to Persona. The integration is only intended for us (fiscal host admins) to copy/paste the persona inquiry ID into a reference field in the OC platform to make it easier for us to link into Persona later to check on the verification status. That's it. The ID# and the status is all we bring from Persona to OC.

[poohlaga@mastodon.social]

@liaizon and again, it's the user's choice, and they can always opt out.