UPDATE: they have dropped Persona!

[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.

[li@tech.lgbt]

@poohlaga demanding users verify themselves by 'other means' is not "opting out", its asking them to choose if they want to be shot with a shotgun or a pistol, either way their still shot- where is the option to _not_ "verify my identity"

[li@tech.lgbt]

@sef @nullagent @liaizon @scan big FOSS developers have no problem actively maintaining and contributing to mass survailence and fascism, its been shown time and time again at this point

like yknow i feel like we all got the gist of how these things will go.. we all say 'hey what the fuck why are you doing "identity verification" let alone with fucking surveillance state company

they give some speil about """safety""" and [insert scapegoat here].. and basically ends up with 'fuck you were doing it anyway' ..

this is how it goes every fucking time

[poohlaga@mastodon.social]

@seabass @liaizon Happy to discuss. I've tried to respond to questions directly in this thread, but I want to make sure any user/hosted collective's concerns are addressed. If it's easier, we'll be at FOSS Backstage next week, and we can always be reached directly at hello@oscollective.org

[li@tech.lgbt]

@Betree @opsocket @liaizon

oh boy i sure cant wait for the next round of 'we heard your concerns and we totally understand.. and listening to feedback .. anyway here is some spiel about ""safety"" and [insert scapegoat here] .. so fuck you were doing it anyway.'

[solonovamax@tech.lgbt]

@liaizon @scan hey, uh, @OpenSourceCollective, what the fuck?

[poohlaga@mastodon.social]

@wcbdata @liaizon @scan Thanks, we agree. We recognize that identity verification raises legitimate privacy concerns, especially in the open source ecosystem.

If you know of identity verification providers that operate outside the US, and align with strong privacy standards, we would love suggestions.

Handling funds responsibly while respecting the privacy of contributors and maintainers is a balance we take very seriously.

[abekonge@venner.network]

@liaizon @jowek @ukrudt @tak @ruben @magnus

Yes haven't checked out the state of petition-software lately.

One low effort/complexity way of doing it would be to write a letter in ukrudt's hedgedoc and just ask projects to sign it if they agree - sign it by way of writing their name in the bottom: https://hedgedoc.ukrudt.net/ - we can then create a public read-only link and share that.

[betree@framapiaf.org]

@nextgraph @liaizon @OpenSourceCollective On encryption: it's not accurate to say all data is stored unencrypted. Sensitive documents like tax forms uploaded to S3 are encrypted before upload (https://github.com/opencollective/opencollective-api/blob/main/server/lib/tax-forms/index.ts#L44), as are certain sensitive fields in the database (https://github.com/opencollective/opencollective-api/blob/5e374c160750fc259ee4163230c764956efda36f/server/graphql/v2/mutation/LegalDocumentsMutations.ts#L126).