Re: The endless influx of low-quality, low-realism, quantity-over-quality aircraft into FGAddon
James Turner <[email protected]>
| Newsgroups | gmane.games.flightgear.devel |
|---|---|
| Message-ID | <[email protected]> |
> On 28 May 2026, at 11:27, An Phúc Nguyễn Vạn <[email protected]> wrote: > > I think I can look into prototyping the web/backend side of this. My initial thought is to keep the launcher offline-friendly: the backend collects authenticated ratings, stores/moderates them, and periodically exports aggregate JSON/XML for the catalog generator to merge. I’d avoid written reviews in v1 and only support one 1–5 rating per authenticated user per aircraft, since reviews add moderation complexity. The launcher would only consume the exported rating field, not call the backend live. Does that match the direction you’re imagining James? Uh, I was assuming the launcher would submit the ratings via a HTTP POST : it’s the authentication or lack of around that, that I’m unsure about. QNetworkRequest (which is what I will use to POST) lets me set arbitrary heads / SSL cert / etc of course; it’s just a question of what is actually sensible, in an open-source application. Agreed about leaving reviews out for now. On the catalog side, the catalog is built by: https://gitlab.com/flightgear/fgmeta-python/-/blob/next/src/flightgear/meta/aircraft_catalogs/catalog.py?ref_type=heads So long as the wrapper script can download a JSON / XML of the ratings by aircraft-id, I can parse that and include it when the catalog.xml is generated. In terms of the backend, it needs to run on probably ‘my’ FG Hertzner server, which is Linux of course. And ideally be something small and easy to back up. (As far as I know, we can’t run anything dynamic on GitLab, only static stuff) Kind regards, James _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel