Finding module with high external traffic

[mmmmh]

@Sean I think I found the “culprit”, it may be the Spotify module’s polling. I just increased the interval and will see if the traffic decreases.

[mmmmh]

@sdetweil the IP resolves to a generic Google host, currently 53.224.186.35.bc.googleusercontent.com - I think it is used by Spotify.

[A Former User]

@mmmmh Yes, it retrieves requests per 1~2 seconds. Unfortunately Spotify Web API doesn’t support push mechanism to get status updated. So it needs pooling. I recommend 2000 ms or more frequency to update current playback if you don’t care.

[mmmmh]

@Sean I think I read somewhere that callback addresses could be provided (perhaps I misread this). If I have a DynDNS-backed FQD host and forwarded port I can provide, would this stop the polling requirement?

[A Former User]

@mmmmh I don’t think so. To update current playback info (The playing status, playing time,…) on real time, This module has to call Spotify Web APIs frequently.

[mmmmh]

@Sean I checked again, you are right, polling is the only option. Thanks for your cool module!