<div dir="ltr">I been monitoring metadata and connections statistics by a polling the server and recording the information require. Including the current Metadata., I ended up polling on a min bases and the radion stations station that use use been happy with the information for past couple years. This is via the server status page. I like to present each of our customers with listeners counts, times listen, how long a listen has been listing, and how many unique listeners. And for other they need unique tags, <div><br></div><div>I event per request set up means of putting out custom meta data that is diferent from the content stream that is blocked cause of DMC concerns. <br><div><br></div><div> Its a real pain to present it in a useable form. But I also found out different stations have different needs .and its all based on the contracts they have. </div></div><div><br></div><div> IT can be done without any modifications. </div><div><br></div><div>:) </div><div><br></div><div><br></div><div><br></div><div> </div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Dec 1, 2014 at 7:05 PM, Philipp Schafft <span dir="ltr"><<a href="mailto:lion@lion.leolix.org" target="_blank">lion@lion.leolix.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">reflum,<br>
<span class=""><br>
On Mon, 2014-12-01 at 22:28 +0000, Dean Sauer wrote:<br>
> On Fri, 21 Nov 2014 15:59:42 +0000, Philipp Schafft wrote:<br>
><br>
> > Also: would it be ok for you to have a global user that is allowed to do<br>
> > that or does it need to be the source user or does it need to be any<br>
> > source user (anyone allowed to stream to that mountpoint)?<br>
><br>
> Since I am likely the source case of this request...<br>
><br>
> A global user, other than the existing one setup for sources??<br>
><br>
> NO. I don't wish to give out any more information to sources other than:<br>
><br>
> server URL/IP<br>
> mountpoint name<br>
><br>
> Setup darkice as follows... with the above...<br>
><br>
> That's all they get.<br>
><br>
> If I specify specific credentials per mountpoint then ONLY THOSE *AND*<br>
> ADMIN should be able to send metadata.<br>
<br>
</span>As I told in the other mail on this thread with 2.4.2 you can set the<br>
right to do so on every role. This includes mount specific roles.<br>
<span class=""><br>
<br>
> I actually like the idea of white listing IP's as well...<br>
><br>
> > That is a very important question to answer the above!<br>
> ><br>
> > Thank you and have a good evening!<br>
><br>
> I am in no rush, as 2.3.2 is the only version in the repos for my distro,<br>
> and I don't compile, ever, never, ever, never. (I have enough headaches<br>
> to deal with already without self inflicted ones.)<br>
><br>
> We won't upgrade past 2.3.2 till this is resolved in our favor, or not at<br>
> all if a choice is made to forgo this option. This option is more<br>
> important than the security, and I am not giving out admin credentials to<br>
> any one.<br>
<br>
</span>I'm sorry to say so, but if you don't care about security at all you can<br>
also just publish your admin password.<br>
<br>
<br>
Current trunk (that will be 2.4.2) contains what you need. I would be<br>
happy to see you on IRC or drop me a mail offering some help with<br>
testing the changes.<br>
<br>
Have a nice evening!<br>
<div class="HOEnZb"><div class="h5"><br>
--<br>
Philipp.<br>
(Rah of PH2)<br>
</div></div><br>_______________________________________________<br>
Icecast mailing list<br>
<a href="mailto:Icecast@xiph.org">Icecast@xiph.org</a><br>
<a href="http://lists.xiph.org/mailman/listinfo/icecast" target="_blank">http://lists.xiph.org/mailman/listinfo/icecast</a><br>
<br></blockquote></div><br></div>