Thanks for your work!<p>Actually we (laut.fm) are using the HTTP Push Module for our public API for a live stream of tracks which get played on our ~ 1500 icecast stations. We offer 3 formats: <a href="http:&#x2F;&#x2F;api.laut.fm&#x2F;song_change.stream.json" rel="nofollow">http:&#x2F;&#x2F;api.laut.fm&#x2F;song_change.stream.json</a> for a line separated JSON HTTP stream, ws:&#x2F;&#x2F;api.laut.fm&#x2F;song_change.ws.json for the same as websocket endpoint and <a href="http:&#x2F;&#x2F;api.laut.fm&#x2F;song_change.chunk.json" rel="nofollow">http:&#x2F;&#x2F;api.laut.fm&#x2F;song_change.chunk.json</a> for the last x songs. It&#x27;s not really high volume, just 6 to 7 per second. But it runs basically unattended for years now and I&#x27;m pretty happy with it.<p>Is there any reason to update to the new one (other than new features; admittedly I haven&#x27;t really looked into NCHAN)?