You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Actively maintained compatibility fork for live Google Flow changes
#60
The fork is focused on fast fixes when Google changes Flow’s internal request shapes or browser/session behavior, plus server-oriented features such as project/session lifecycle, account/credit diagnostics, generation guards, and trusted UI recovery. I’m still sending portable fixes back upstream rather than treating it as a separate replacement project — current example: #59.
The upstream project is still the original source and has broader pipeline/review work that I’m not trying to replace. The idea is simply to give users who run FlowKit as a server/API somewhere to get live compatibility fixes quickly when Flow changes.
If this is useful to the community, would you be open to a short ‘community-maintained compatibility fork’ mention in the README or another visible place? I’m happy to keep the wording neutral and make clear that this is an unofficial fork, not the canonical repo.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
I’ve been running FlowKit against the live
flow.google.comfrontend and maintaining a compatibility-focused fork here:https://github.com/Bl0ck154/flowkit
The fork is focused on fast fixes when Google changes Flow’s internal request shapes or browser/session behavior, plus server-oriented features such as project/session lifecycle, account/credit diagnostics, generation guards, and trusted UI recovery. I’m still sending portable fixes back upstream rather than treating it as a separate replacement project — current example: #59.
The upstream project is still the original source and has broader pipeline/review work that I’m not trying to replace. The idea is simply to give users who run FlowKit as a server/API somewhere to get live compatibility fixes quickly when Flow changes.
If this is useful to the community, would you be open to a short ‘community-maintained compatibility fork’ mention in the README or another visible place? I’m happy to keep the wording neutral and make clear that this is an unofficial fork, not the canonical repo.
All reactions