One needs to send 1 mln HTTP requests concurrently, in batches, and read the responses. No more than 100 requests at a time.

Which way will it be better, recommended, idiomatic?

• Send 100 ones, wait for them to finish, send another 100, wait for them to finish… and so on

• Send 100 ones. As a a request among the 100 finishes, add a new one into the pool. “Done - add a new one. Done - add a new one”. As a stream.

The news of ~~Russian~~ Western isolation

I have an Android app which I haven't been to activate because of it requires that during the activation a phone to be a) on mobile data b) with the same sim card that assinged to me by a service of the app.

I have a sim card, but I can't turn on mobile data because firstly I can't top it up here, in other country. Secondly, it'd eat up lots of money, if I could somehow.

Is there a way to trick an Android app to believe that it uses mobile data whilst in relality it's on Wifi? Reverge engeneering would the last resort. Is there an easier way?