Radmon.org API rate limiting and mass upload feature

I've thought of a couple of ideas, both have their pros/cons/caveats.

1 - Employ a mass upload feature. A CSV file or similar between two date/time points. Upload and stuff into the DB. Could be fairly easily done, unless Joomla gets in the way (she's a bitch). It's open to manipulation though - think 'creative' tik-tok influencer. Something happens close by to them, some power station goes into alarm, so for clicks and giggles they create a user/station and feed it a load of fake historical data, make video "OMG the power station 10 miles from me might be melting down!!! Look see my geiger counter here - I'm being irradiated!!" Far out, maybe, but someone if they had all of the bits (of info, knew about radmon.org etc) may actually do this. Some people are literally crazy these days. So I thought of some kind of 'trusted user/station' thing. But how would that work? There are several users/stations I could immediately mark as trusted, but also many that I have no clue about their stations and the validity of their readings. Maybe people could apply to become trusted, but how to validate? Look back at their graphs and if they look good then fine. That could work. The crux of it all though, is that all of that would probably only be for you, gigermantes, and would require manual intervention. I don't know of any other user that would use a manual mass upload from txt/csv.

2 - (this I think is clever, but would require more development). Employ a failover server, somewhere else on the internet. Maybe my server (it has 99+% uptime). This would require everyone to add to their code for submission, and I guess people could just opt out by not using it. Lets assume a counter with an ESP32/8266, add into the code a failover server url. If the ESP submits to radmon.org and doesn't get the OK, or a 200, anything else, then it simply fires the submission to another server. On this server it could, potentially, drag down the stations table (some mysql sync, or php, but dragging the data across in text/json form, I'm not too keen on. It would have to be encrypted or something) so the server has a copy of the user names and station passwords, that way the submissions could be verified against the user base. If good the readings are stored on a database. A cron or task schedule runs every so often and if radmon.org becomes available again, the failover server runs a script and hoofs all the data right into radmon's database, and can verify the user/station name and password for every record going back in. Then once done purge the failover data.

I actually really like #2, and it would work for every station if the user wants. It's quite a lot of work though and developing radmon.org is hard for me at best - I'm old/seasoned hardcore (back in the day) microsoft sysadmin with very little nix experience, and radmon is a nix box, hardened too, with Joomla guarding the web front end. It's like developing half blind, through a keyhole using chopsticks, where I'm used to romping around playground. But I do like the idea, a lot.