[Fink feature request] Ability to allow community to the editor for private repos

[Jadiction]

Not sure if I haven't explored enough to find if it's possible, but I'd love a way to allow others to be able to access the translation editor even if the repo is private.

The idea: The repository provides initial authorization access, the access gets cached and (probably make a setting to allow it to be publicly accessible or not) and allow others to be able to submit PRs from the URL by visiting the repo from an authorized account, rather than theirs. This way private repos can allow translators as well. Although, I imagine this may require the PR to only be sent from the authorized account and not their own, maybe it'll just have their Github name in the PR description?
I haven't really looked at how it works yet, so I'm sure if this is even possible.

If this isn't possible, is it possible to import Fink on NextJS to allow you to display a translations page & have users submit a PR under a (secret env stored) authorized Git user?

[LorisSigrist]

This currently isn't possible, but it is a use-case we want to cover soon. Afaik, fink isn't built to be embeddable so the NextJS workaround might not be easy (feel free to try though, would be very cool).

@martin-lysk, isn't this exactly what you were suggesting with shareable-sessions?

[NiklasBuchfink]

We are looking for a solution allowing external contributors such as community members and non-technical users such as translators to submit translations.

Your idea is very similar to the concept of signed URLs, where the link includes the authorization and others can access data with it. We would need to store your keys and the authorized URLs on our git proxy server, which we are not currently doing. At the moment, it is just a client-side app that calls our proxy to load your repo in the browser.

Embedding Fink in NextJS would also involve some challenges, as it:

1. runs on SolidJS
2. requires some secret imports
3. calls our git proxy (CORS)

[samuelstroschein]

hey @Jadiction,

the feature is on our radar. the question is whether we can build the right solution (lix hosted platform), or need to do an interim workaround. we can't give an answer today. rest assured, it's coming this year though :)