[2] [standards-jig] NEW: JEP-0118: User Tune Information

Ralph Meijer jabber.org at ralphm.ik.nu
Wed Sep 24 11:44:08 UTC 2003

On Thu, Sep 11, 2003 at 11:13:09PM +0100, milk wrote:
> damn, just realised i sent this to jdev, woopsy
> Ralph Meijer <jabber.org at ralphm.ik.nu> wrote on 11/09/2003 09:42:23:
> >> how about information for format, bitrate, and possibly some (if not all) id3v2 elements?
> >
> >Seriously, would anyone be interested in this kind of data? I can imagine
> >people finding it of interest what I'm listening to, but I would say they
> >couldn't care less whether it is an ogg, mp3 or which bitrate.
> well, if someone is say, running an mp3 stream and also a jabber bot that handles requests and track information; because mp3 streams can't handle any information 
> other than the stream title and current track (well, as one whole string), it would be handy so that if a listener wants information about the track beyond 'artist - title', 
> they could have it provided to them via jabber. that a point; 'filename' might be a handy value as well.
> Julian Missig <julian at jabber.org> wrote on 11/09/2003 19:01:44:
> >I agree with Ralph, we should try to keep this simple. The less data 
> >we're sending out all the time, the better. Remember that these get 
> >updated every couple of minutes... and there will be lots of people 
> >sending this data. Sending lots of useless data will just hurt the 
> >network.
> might it be an idea to have (in the implementation, rather than the jep?) two different forms of data sent; a 'simple' version with just the basics, and an 'expanded' 
> version that hold more information about a track for those who would like it.

I can imagine being able to disco the current song for detailed information
such as filetype, duration, album, link to performers' fan page, etc.
In another namespace, preferably.



More information about the Standards mailing list