Two user reports (watchporn scenes 5716e1c5 + another): "resolver fails but the scene plays in the diagnostic browser". Verified server-side the watchporn extractor is reliable (8/8) and returns 2 clean links; the zload remote_control.php CDN URL is a valid range-supporting mp4 (206) that plays cross-IP and via the /proxy fallback (206). So the failure is purely the mobile native player choking on that URL, and native-mp4-only tube sources carried NO fallbackEmbedUrl, so there was nothing left after native+proxy. Now: when a resolved source has direct links but no embed, use the tube page_url as the WebView fallback. Native + proxy are still tried first; only if both fail does it load the site page in the WebView player (phone-side, residential IP, no VPS bandwidth) which is exactly what the diagnostic browser does and the users confirmed plays. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| android | ||
| assets | ||
| src | ||
| .gitignore | ||
| app.json | ||
| App.tsx | ||
| babel.config.js | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| tsconfig.json | ||
goon mobile (Expo / React Native)
Mobile client do self-hosted goon backendu. iOS/Android jeden codebase.
Setup
cd mobile
npm install
npx expo start
Następnie:
- Expo Go (iOS/Android): zeskanuj QR z terminala
- Android emulator:
npm run android - iOS simulator:
npm run ios(tylko macOS) - Web preview:
npm run web
Konfiguracja
Po pierwszym uruchomieniu zobaczysz ekran logowania:
- Backend URL — adres twojego goon backendu, np.:
http://192.168.1.10:8000(LAN)https://goon.tvojadomena.dev(przez Cloudflare Tunnel/Caddy)http://100.x.x.x:8000(przez Tailscale)
- API Key — klucz wygenerowany dla backendu, ustawiony w
.env:
Generowanie:API_KEYS=<klucz>python -c "import secrets; print(secrets.token_urlsafe(32))"
Klucz jest trzymany w expo-secure-store (Keychain na iOS, Keystore na Androidzie).
Ekrany
- Login — backend URL + API key, weryfikacja przez
/healthz+/scenes - Scenes — lista scen z search; pull-to-refresh
- Scene detail — performerzy, tagi, źródła, opis
- Merge queue — pending merge candidates, sortowane po score (desc)
- Merge detail — side-by-side dwóch scen + reasons + akcje:
- Merge → keep LEFT (default — left to wcześniejsza/kanoniczna)
- Merge → keep RIGHT (gdy nowsza wersja ma lepsze metadane)
- Reject (keep both) — to nie jest duplikat, zostawiamy oddzielnie
Stack
- Expo SDK 52 + React Native 0.76 (new architecture)
- TypeScript strict
- React Navigation 7 (native stack)
- TanStack Query 5 (cache, optimistic invalidation)
- expo-secure-store (credentials)
Build .apk (sideload na Androida)
npx eas build --profile preview --platform android
Wymaga konta Expo. Bez niego można użyć expo prebuild + gradlew assembleRelease.
Dlaczego nie PWA
Wybrany RN+Expo zamiast PWA bo:
- swipe gestures pasują do triage merge queue
- secure-store jest natywny (Keychain/Keystore) zamiast localStorage
- pull-to-refresh i FlatList virtualization out-of-the-box
- Jeden .apk można rozdać testerom bez App Store