> NB: at this point I didn’t want to send any more automated data through my airmiles account in case that got me in trouble somehow. [...] I therefore proved to myself that PySkyWiFi would work on my airmiles accounts too by updating my name ten or so times in quick succession. They all succeeded [...] I then wrote the rest of my code by sending my data through friendly services like GitHub Gists and local files on my computer
> I’m going to keep talking about sending data through an airmiles account, because that’s the point I’m trying to make.
Disappointing! I would not be surprised if things break when updating name millions of times (and you do need millions of updates for basic website) - maybe there is a history table, or a queue, or a easily overloaded service...
I was wondering about this. How well would the protocol cope if the name field suddenly changed back to the previous value, because the database is not that consistent? In addition to counters, you'd probably need signaling to indicate a missing packet, at least.
> NB: at this point I didn’t want to send any more automated data through my airmiles account in case that got me in trouble somehow. [...] I therefore proved to myself that PySkyWiFi would work on my airmiles accounts too by updating my name ten or so times in quick succession. They all succeeded [...] I then wrote the rest of my code by sending my data through friendly services like GitHub Gists and local files on my computer
> I’m going to keep talking about sending data through an airmiles account, because that’s the point I’m trying to make.
Disappointing! I would not be surprised if things break when updating name millions of times (and you do need millions of updates for basic website) - maybe there is a history table, or a queue, or a easily overloaded service...