Re: The endless influx of low-quality, low-realism, quantity-over-quality aircraft into FGAddon
An Phúc Nguyễn Vạn <[email protected]> Thu, 28 May 2026 22:04:22 +0700
| Newsgroups | gmane.games.flightgear.devel |
|---|---|
| Message-ID | <CAKX87K=N4P2HvgNDP2SCf9iO1kXjtDXF=RiL3HsqLQvKa-D_XA@mail.gmail.com> |
Currently ramping up the prototype. should be available in a few days Vào Thứ 5, 28 thg 5, 2026 vào lúc 19:07 James Turner <[email protected]> đã viết: > > > On 28 May 2026, at 12:45, An Phúc Nguyễn Vạn <[email protected]> > wrote: > > I was thinking the rating would be submitted through a web page, but if > the launcher is going to POST it directly then yes, the awkward part is > mostly authentication / abuse prevention. > > For a first version I’d probably keep the backend very small: just accept > a rating for an aircraft-id, store it, and expose an aggregate JSON/XML > file that the catalog builder can fetch. > > That’s fine. > > For storage, SQLite might be enough at first and would keep backups > simple. The main question is whether anonymous ratings are acceptable. We > could do basic rate limiting and maybe have the launcher generate a local > anonymous id, but of course that would not be abuse-proof. > > We already have an anonymous ID for Sentry, so fine to use that to avoid > duplicate submissions, and if we can rate limit by IP as well, ideally. > > The cleaner version, in my opinion, it would be to open a web page from > the launcher and let the user sign in with GitLab/GitHub(or a different > service if you prefer) before rating. More friction, but much easier to > reason about. > > Then we’re into OAuth (etc) territory right, to allow sign-in? That > doesn’t fill me with joy, the friction level is a bit high. (Based on > feedback I see here about using GH/GitLab…) > > I think we should start with a once-per day manual approval step: eg I SSH > in, check the last N hours of submitted data, and merge it into the > aggregate if it looks plausible. If it looks like something strange has > happened, I can check the NGnix logs and maybe discard that window of data? > This solution won’t work long term but it feels like a good way to test the > approach? > > I can sketch a small backend/API/export prototype if that would be useful. > > Yes, it would, if you can manage it. > > Kind regards, > James > > _______________________________________________ > Flightgear-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel