mirror of
https://github.com/Droid-Deck/DroidDeck.git
synced 2026-11-19 04:46:08 +00:00
Stores: Show mature content, off by default
The storefront's shelves and search leave out titles the store itself rates or tags as adult unless Show mature content is on (Setup > Stores and the cog). Library, Installed and owned games always show, and a title without rating data stays. GOG's catalog gives ratings[].ageRating per system and content tags; 17+ in any system or a mature / nsfw / sexual content / nudity tag marks a title. Epic's store GraphQL carries no age rating on an offer, so only an adult content tag would mark one.
This commit is contained in:
1 parent
37b6f336a7
commit
ff9807ad29
12 files changed
+103
-5
No files matched your search
@@ -144,6 +144,15 @@ without it and Setup says "Stores engine not built").
|
||||
(`token`, `__token__`, `f_token`, `hdnts`, access/refresh/id tokens, `code=`) and Authorization /
|
||||
Cookie headers are blanked outside URLs too. `StoreLogTest` covers a GOG secure link and an Epic
|
||||
Akamai URL. The engine's own logcat lines (tag `EpicNative` etc.) are written on the native side.
|
||||
- **Show mature content** (Setup › Stores and the cog; off by default): the storefront's shelves
|
||||
and search leave out titles the store itself rates or tags as adult; Library, Installed and owned
|
||||
games always show, and a title without rating data stays. GOG: `ratings[].ageRating` 17+ (ESRB M
|
||||
17, PEGI / USK / GOG 18) or the tags `mature`, `nsfw`, `sexual-content`, `nudity` - the catalog
|
||||
API has no server-side filter for either, so it is client-side. Epic: its public store GraphQL
|
||||
carries no age rating on an offer (no age-gating or rating field on CatalogOffer or StoreConfig;
|
||||
introspection is off), so only an adult content tag would mark one, and none of the probed
|
||||
titles have one - Epic's storefront is effectively unfiltered. Amazon's Store tab is the user's
|
||||
own games.
|
||||
- **UI slow while downloading (device):** engines report per chunk or file, and each report
|
||||
published a new queue that the whole front end read (the rail badge was computed from it in the
|
||||
root composition). Now progress-only changes reach the UI at most four times a second (stage and
|
||||
|
||||
Reference in new issue
Block a user