Sadly, the log_id in the URL reflects not just deleted logs representing actual interaction by actual trig baggers, but also cleanups after various hacking attempts. So
https://trigpointing.uk/logs/500000 reflects not only on the site's success, but also its vulnerabilities to randomly annoying scroats with nothing better to do. (Sorry Brian M!)
By its nature, it's always going to be somewhat arbitrary. However, if you're willing to accept it potentially changing over time, then an API call to
https://api.trigpointing.uk/v1/logs?ord ... kip=399999, with the 3 changed to a 4, will show the 500,000'th currently valid log in the database.
I'm not going to be brave enough / tempt fate enough to guess a date! Total logs per month and total active users have noticeably increased since the rewrite. However logs per month from "power users" with >300 visits already logged is significantly down. (Which is very concerning, but aligns with various negative posts on this forum and emails from frustrated "community figures" I have received. Constructive criticism / forward-looking suggestions most welcome!)
Maybe there should be some sort of reward? Perhaps a customised Trigfig for the first person to have the 500000th valid log?(*) And another for the first person to have the 500000th valid photo (though that's a bit further off)?
(*) yes, the API is
open and documented; yes, that makes it trivial to write an exploit script to ensure you're the 500,000th; no that won't get you a Trigfig, though it might well get you a ban!
