goon-foss/goon
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
goon/mobile
History
goon-foss 4df1e01b31 feat(jav): separate JAV section (tab + feed gating) + enable javflix ingest 
JAV is a distinct vertical (user decision): Asian codes/titles that do not dedup
against the western catalog, so they must not flood the main feed.

Backend (scenes.py): JAV_ORIGINS = {tube:javflix, tube:javguru, tube:vjav,
tube:supjav}; list_scenes gains a `jav` param. Default (jav=false) excludes any
scene with a live JAV-origin source; jav=true returns only those. The cached
default-count and _is_pure_default also exclude JAV so the main feed count matches.
JavflixScraper is now registered in ALL_BROWSE_SCRAPERS (scheduled ingest lands in
the JAV section, gated). Scraper hardened: requires a real server button
(class="myLink") so static pages (Terms/FAQ) are skipped, and unescapes HTML
entities in the title.

Mobile: a "JAV" top tab reuses ScenesScreen with { jav: true } (route param ->
listScenes jav=true). The 60s minimum-duration default is disabled in the JAV tab
because javflix does not expose duration (NULL >= 60 would hide the whole section).

Verified on prod: 16 javflix scenes appear only in the JAV feed and are excluded
from the 2.29M main feed; playback resolves to voe/doodstream/emturbovid.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-10 11:16:31 +02:00
..
android fix(apk 0.2.1): in-app installer "nic się nie dzieje" + oo launcher icon 2026-05-31 13:15:37 +02:00
assets feat(brand): oo logo — app icons, landing, in-app mark (Gemini-generated) 2026-05-30 22:38:52 +02:00
src feat(jav): separate JAV section (tab + feed gating) + enable javflix ingest 2026-07-10 11:16:31 +02:00
.gitignore Initial commit 2026-05-20 10:10:22 +02:00
app.json fix(apk 0.2.1): in-app installer "nic się nie dzieje" + oo launcher icon 2026-05-31 13:15:37 +02:00
App.tsx fix(watchporn): re-resolve stale CDN URL in-player, drop WebView page fallback 2026-07-05 01:18:08 +02:00
babel.config.js Initial commit 2026-05-20 10:10:22 +02:00
package-lock.json feat(mobile): custom fonts (General Sans + Geist Mono) + logo rework 2026-05-30 22:25:26 +02:00
package.json feat(mobile): custom fonts (General Sans + Geist Mono) + logo rework 2026-05-30 22:25:26 +02:00
README.md Initial commit 2026-05-20 10:10:22 +02:00
tsconfig.json Initial commit 2026-05-20 10:10:22 +02:00

README.md

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: 
    API_KEYS=<klucz>
    Generowanie: 
    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